Privacy Policy

Virre ("we", "our", or "us") operates the Virre.ai platform (the "Service"). This Privacy Policy explains how we collect, use, disclose, store, and safeguard your information when you use our website, mobile app, browser extension, application, and services, including when you connect third-party platforms such as Zoom, Google, or LinkedIn. We are committed to protecting your privacy and complying with applicable data protection laws, including the EU General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA).

The Service is operated by "RPYIS LLC", NJ, USA, doing business as Virre. References to "Virre", "we", "our" and "us" in this policy mean that company.

The Service helps individuals and organizations manage professional relationships: relationship and network insights, introductions, community and event management, newsletters, job and opportunity features. This policy applies to all of them.

We collect only the information necessary to provide and improve the Service:

• Account Information: Name, email address, profile photo, and authentication identifiers when you create an account with an email address and password, or sign in via Google or LinkedIn.
• Third-Party Integration Tokens: When you connect a third-party service (Zoom, Google, LinkedIn), we store the OAuth access token, refresh token, token expiry, and granted scopes required to act on your behalf. We never see your Zoom or Google password. To connect LinkedIn messaging, you enter your LinkedIn sign-in details (and any verification code) in Virre; we pass them directly to our LinkedIn integration provider, Unipile, to create the connection, and we do not store them. Organizers who connect Eventbrite, Luma, Stripe, Typeform or Beehiiv give us an API key, which we store encrypted (see Section 3B).
• Zoom Account Data: When you connect Zoom, we access and store your Zoom user ID, Zoom account ID, display name, email address associated with Zoom, and the OAuth scopes you have approved.
• Zoom Meeting Data: Meeting IDs, topics, start times, durations, time zones, join URLs, host information, and participant metadata for meetings you create, view, update, or delete through the Service, and, if you use Zoom cloud recording, the recording details, transcript and Zoom meeting summary for meetings created through Virre (see Section 3).
• Meeting Content Created in Virre: Meeting titles, descriptions, agendas, scheduled dates, attendee lists, and notes that you create or edit inside Virre.
• Usage and Diagnostic Data: Logs of interactions with the Service (pages visited, features used, API requests, error traces, IP address and browser type) used solely for security, debugging, and product improvement. We do not use this data for advertising.
• Cookies: Strictly-necessary session cookies used for authentication. We do not use advertising cookies. On our website we also use Microsoft Clarity, an analytics tool that records how pages are used (clicks, scrolling and page views) so we can find and fix problems, and it sets its own cookies. We load Google Maps for address suggestions and Userback for in-app feedback.
• LinkedIn connections you upload: If you upload the Connections file exported from LinkedIn, we store the fields in that file (for example first and last name, profile URL, email address if the person shared one, company, position, and the date you connected). We use it only for your account.
• Public profile information about your contacts: To build a contact's profile, we fetch publicly available LinkedIn profile information about them (such as name, headline, role, company, experience, education, location, skills and photo) through our data provider, Apify. See Section 2A.
• Contacts and relationship notes you add: Names, roles, companies, cities, notes, tags, follow-up reminders, important dates such as birthdays, and records of introductions or messages you create in Virre.
• LinkedIn messages: If you connect LinkedIn messaging, we sync your LinkedIn conversations (participants and message text) so you can read and reply to them in Virre.
• Profile, goals and preferences: Your role, industry, city, goals, what you are looking for and what you can offer, your answers to our onboarding questions, and your privacy and communication settings.
• Community and event data: If you belong to a community or attend an event run by an organizer on Virre, we process the membership, registration, attendance and profile information that you or the organizer provide, including registration details imported from Eventbrite or Luma (see Section 3B).
• Career and job search information: Resume files you upload or profile details, target companies and roles, and the status of applications or conversations that you record.
• Calendar data: See Section 3A.
• Browser extension: When you use the Virre browser extension on LinkedIn, it reads the profile you are viewing (name, headline, profile URL and connection degree) and the profile links of your mutual connections, and sends them to Virre to show you insights or add the person to your contacts. It does not read your LinkedIn messages or LinkedIn cookies.
• Mobile app: A push notification token for your device, if you allow notifications. We do not collect your device's location.
• Payment information: Payments are processed by Stripe on Stripe-hosted pages. We receive your card brand, the last four digits and the expiry date, never your full card number.
• Communications: Messages you send to us for support, feedback you send through the in-app feedback tool, and your marketing preferences.

Your network contains people who may never have signed up for Virre. When you upload or enter information about them, we process it on your behalf to provide the Service to you. We do not use their information to market to them, sell it, or show it to other Virre users unless that person has joined Virre and chosen to share it, or you choose to share it.

To avoid fetching the same public LinkedIn profile again and again, we keep one copy of a person's public LinkedIn profile information and reuse it when another Virre user adds the same person. Your own notes, tags, messages and other private information about a contact are never shared with other users.

If you are not a Virre user and want your information removed from someone's contact list or from Virre, contact support@virre.ai.

When you connect Zoom, Virre requests the following OAuth scopes. They let us schedule and manage meetings on your behalf and, if you use Zoom cloud recording, bring the transcript and summary of those meetings into Virre:

• meeting:read:meeting — read meetings on your account so we can display their details and status.
• meeting:read:list_meetings — list your upcoming and past Zoom meetings so you can see them on your Virre schedule page. We display this list but do not store it.
• meeting:write:meeting — create new Zoom meetings when you schedule a virtual meeting in Virre.
• meeting:update:meeting — update an existing Zoom meeting when you change a meeting's date, time, title, or description in Virre.
• meeting:delete:meeting — delete the Zoom meeting from your Zoom account when you cancel or delete a meeting in Virre.
• user:read:user — read your basic Zoom user profile (user ID, account ID, name, email) to associate Zoom data with your Virre account.
• cloud_recording:read:recording — receive the details of a cloud recording (file names, types and links) for meetings created through Virre.
• cloud_recording:read:meeting_transcript — download the transcript of a meeting created through Virre and add it to that meeting's notes.
• meeting:read:summary — read the Zoom AI Companion summary of a meeting created through Virre and add it to that meeting's notes.

We store transcripts and summaries only for meetings created through Virre, and we send the meeting summary to our AI providers to suggest follow-ups and opportunities (see Section 4A). We do not download recording video or audio, we do not store recordings, transcripts or summaries of meetings that were not created through Virre, and we do not access webinars, Zoom Team Chat or Zoom contacts.

If you connect a Google account, we request only the permissions needed for features you turn on:

• Sign in with Google (openid, profile, email): your name, email address and profile photo, to create and sign in to your account.
• Google Calendar (calendar.events): to add, update and remove calendar events for meetings you schedule in Virre, including the attendees you invite. We do not read your other calendar events.
• Gmail and Google Contacts, for event organizers (gmail.readonly, gmail.send, contacts.readonly, contacts.other.readonly): to show your most recent emails (sender, recipients, subject and body) inside Virre and, when you open one, summarize it with AI; to import your Google contacts (names, email addresses, phone numbers, organizations and addresses) into your organizer contact list; and to send introduction emails that you write and approve. We never send email from your account without your action.

We use Google user data only to provide those features. We do not use it for advertising, we do not sell it, and we do not transfer it except as needed to provide the Service, to comply with law, or as part of a merger or acquisition with notice to you. When a feature uses AI (such as email summaries), the relevant Google data is sent to our AI providers only to produce that result for you. We do not use Google user data to develop, improve or train generalized AI or machine-learning models. We do not allow humans to read your Google data except with your consent, for security or abuse investigation, or as required by law. Virre's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

You can disconnect Google at any time in Virre or at myaccount.google.com/permissions. When you do, we stop accessing your account and delete the related tokens. Emails and contacts already imported into your organizer workspace stay there until you delete your account.

Event organizers can connect their own Eventbrite, Luma, Stripe, Typeform or Beehiiv accounts by giving us an API key, which we check with the provider and store encrypted. We use these connections only to run that organizer's events, community and contact list:

• Eventbrite and Luma: when someone registers for the organizer's event, we receive their registration details: name, email address, job title, company, answers to registration questions and, where provided, their LinkedIn profile URL. If the person does not already have a Virre account, we create one for them, fetch their public LinkedIn profile, prepare a starter career plan, add them to the event's community and the organizer's contact list, may give them complimentary premium access, and email them a link to sign in. They can delete the account at any time (Section 9).
• Stripe (the organizer's own account): ticket purchases are processed on the organizer's Stripe account. We receive the buyer's name, email address and payment status to confirm the registration. We never receive full card numbers.
• Typeform: form responses that the organizer chooses to map, including the respondent's email address, are added to the organizer's contact list.
• Beehiiv: newsletter subscriber details (email address, subscription status, tags, open and click rates, and name, company and location fields) are imported into the organizer's contact list and newsletter reports.

The organizer decides to connect these platforms and is responsible for telling its attendees and subscribers how their information is used; Virre processes this information as the organizer's service provider. Disconnecting a platform deletes the stored key immediately. Information already imported stays in the organizer's workspace until the organizer deletes it or closes their account.

• To provide, maintain, secure, and improve the Service.
• To create, read, update, and delete meetings on your behalf through connected third-party services such as Zoom and Google Calendar.
• To send transactional notifications related to your account, meetings, and connected integrations.
• To respond to support requests and provide customer support.
• To detect, investigate, and prevent fraud, abuse, security incidents, and violations of our Terms of Service.
• To comply with legal and regulatory obligations.
• To analyze your network, suggest who to contact and when, and show you your own network insights and reports.
• To find opportunities and suggest follow-ups from your notes, LinkedIn messages and meeting summaries.
• To let community managers and event organizers you have joined run their community or event, within the visibility settings you choose and send warm introductions.
• To send product updates and newsletters. You can unsubscribe at any time using the link in the email or by emailing support@virre.ai.
• To produce aggregated statistics that do not identify you.

We do not sell, rent, or trade your personal information. We do not use Zoom data or any user data to train machine-learning models that are shared across customers.

We use artificial intelligence to summarize notes, meetings and emails, suggest contacts, draft messages, answer questions about your network, match you with jobs and tailor your resume. To do this, we send the information needed for the task you asked for, such as your prompts and goals, relevant contact profiles, your notes, LinkedIn messages, meeting summaries, resume text and, for organizers, the email you open, to AI service providers: Google (Gemini), OpenAI and Anthropic, reached through Vercel's AI Gateway. We also use Langfuse to monitor the quality of AI responses; it receives AI requests and responses with sensitive values filtered out. These providers process the data to return a result for you under business API terms that do not allow them to use it to train their models. We do not use your content to train models that are shared with other customers.

AI suggestions can be wrong. You decide whether to act on them. We do not make decisions about you that have legal or similarly significant effects based solely on automated processing. We do not send messages to other people on your behalf without your approval. Two related notices go out automatically: if you write a message to someone through Virre who has an email address on file, we may email them a short notice that they have a new message; and if a LinkedIn message you wrote is waiting on a connection request, we deliver it once the person accepts.

If you connect Virre to an AI assistant that you use (for example Claude or ChatGPT), you authorize that assistant to access the Virre data you permit. This access is read-only: the assistant can look up your goals, contacts and introduction paths but cannot change anything or send messages. That assistant's provider handles that data under its own privacy policy. You can disconnect the connection at any time in the assistant's settings. To end the connection from Virre's side straight away, contact support@virre.ai; the assistant's access token stops working within one hour and its refresh token within 60 days.

If you join a community or attend an event managed by an organizer on Virre, the organizer can see your name, email address, photo, LinkedIn profile, role and company, the goals and preferences you gave during onboarding, your attendance, and your engagement and uses it to run the community. The organizer is responsible for its members' data and Virre acts as its service provider. Organizers cannot see your uploaded LinkedIn connections, your contacts, your messages or your private notes.

Other attendees of an event you are registered for can see your name, photo, role, company, LinkedIn profile and LinkedIn summary, but not your email address. Other members of a community can see the same profile details in the member list when the community manager has made the member list public. If you invite friends to Virre, you can see the names and email addresses of the people who sign up through your invitation.

We apply industry-standard administrative, physical, and technical safeguards designed to protect your data:

• Encryption in transit: All connections to the Service and to third-party APIs (including Zoom) use TLS 1.2 or higher with strong cipher suites. HTTP traffic is automatically redirected to HTTPS.
• Encryption at rest: Data is stored in encrypted databases. Integration credentials such as Google, Gmail and LinkedIn tokens, event-platform API keys and push notification tokens are also individually encrypted using AES-256-GCM.
• Access controls: Production data is accessible only to a limited number of authorized personnel under the principle of least privilege, with multi-factor authentication required for all administrative access.
• Secure development: We follow a Secure Software Development Life Cycle (SSDLC) that includes peer code review, dependency scanning, static application security testing (SAST), and dynamic application security testing (DAST) before releases.
• Vulnerability management: We monitor dependencies for known vulnerabilities and patch issues according to severity, with critical issues addressed promptly.
• Logging and monitoring: Application and infrastructure logs are monitored for anomalous activity and potential security events.

No method of transmission or storage is 100% secure. While we strive to protect your information using commercially reasonable means, we cannot guarantee absolute security.

Uploaded connection lists, contacts and notes are stored in our encrypted database, and every request is checked so that each account can only access its own records.

We rely on the following sub-processors to operate the Service. Each sub-processor is contractually bound to protect your data and process it only on our instructions:

• Vercel — application hosting, file storage (such as resumes and photos), routing of AI requests (AI Gateway) and edge delivery.
• MongoDB Atlas — encrypted database hosting.
• Resend — transactional email delivery (account, meeting, and support notifications) and product emails.
• Google Firebase — real-time notifications and message updates.
• Google (Gemini), OpenAI and Anthropic — AI processing (Section 4A).
• Langfuse — monitoring of AI requests and responses.
• Unipile — connecting your LinkedIn account and syncing LinkedIn messages.
• Apify — public LinkedIn profile information and job listings.
• SerpApi, Serper and Tavily — web and job search for research features (search queries only).
• Stripe — payment processing.
• Expo — mobile push notifications.
• Microsoft Clarity — website usage analytics.
• Userback — in-app feedback.
• Google Maps Platform — address suggestions.
• OAuth providers — Google, LinkedIn, and Zoom for authentication and authorized API access.
• Platforms that you or your organizer connect — Zoom, Google Calendar, Gmail, Eventbrite, Luma, Typeform and Beehiiv, as described in Sections 3, 3A and 3B.

We will update this list when it changes.

We do not sell your personal information. We share information only in the following limited circumstances:

• With your consent or at your direction.
• With the sub-processors listed above, strictly to operate the Service on our behalf.
• With third-party platforms you connect (e.g., Zoom, Google, LinkedIn through Unipile), to perform actions you initiate.
• To comply with applicable laws, lawful requests, court orders, or to protect our legal rights.
• In connection with a merger, acquisition, or sale of assets, where the receiving party will be bound to honor this Privacy Policy.
• With community managers and event organizers, and with other Virre users, only as described in Section 4B.
• We do not share personal information for cross-context behavioral advertising, and we have not sold or shared personal information in the past 12 months.

• Account data is retained for as long as your account is active.
• Zoom OAuth tokens are retained only while your Zoom integration is connected. When you disconnect Zoom in Virre, the tokens are permanently deleted from our database immediately. If you remove Virre in the Zoom App Marketplace instead, Zoom revokes our access at once and we delete the stored tokens when Virre next tries to refresh them.
• Zoom meeting metadata created through Virre is retained while the meeting exists in your Virre dashboard. When you delete a meeting, we delete it from Zoom and remove it from your dashboard, and the record is permanently deleted with your account.
• Usage records and security logs are kept while your account is active and deleted with your account, except security records we need to investigate abuse.
• When you delete your account, all personal data, integration tokens, and meeting data associated with your account are permanently deleted within 30 days, except where retention is required by law. Your account is deactivated as soon as you ask, and we keep payment records where tax law requires it.
• Uploaded LinkedIn connections, contacts and notes are kept while your account is active. You can delete your uploaded connections list at any time (Add Connections → Start fresh), which removes it immediately, and you can delete individual contacts and notes. Deleted contacts disappear from your account straight away and are permanently erased together with your account.
• Deleted data can remain in our database provider's encrypted backups until those backups expire on their regular schedule. Backups are used only to restore the Service.
• Anonymized or aggregated data that no longer identifies you may be kept, for example total counts of meetings scheduled or features used.

Depending on your location, you may have the following rights under the GDPR, CCPA, or other applicable laws:

• Access the personal data we hold about you.
• Request correction of inaccurate or incomplete data.
• Request deletion of your data (the "right to be forgotten").
• Request a portable copy of your data.
• Object to or restrict certain processing.
• Withdraw consent at any time, where processing is based on consent.
• Disconnect Zoom, Google Calendar or Gmail at any time, which immediately deletes the corresponding tokens. To disconnect LinkedIn messaging or an AI assistant connection, contact support@virre.ai.
• Lodge a complaint with a supervisory authority.

To exercise any of these rights, contact us at support@virre.ai. We will respond within 30 days.

You can also use Settings → Account → Advanced account options in the web or mobile app to delete your account or pause it. To get a copy of your data, email us. If we refuse a request, you can appeal by emailing support@virre.ai.

California and other US state residents may request to know the categories of personal information we collect and disclose, to delete or correct it, and to opt out of the sale or sharing of personal information. We do not sell or share personal information as those terms are defined by these laws. We will not discriminate against you for exercising these rights. We verify requests before acting on them. You may use an authorized agent.

Virre is operated from and stores data with sub-processors that may be located in the United States, the European Union, or other jurisdictions. Where data is transferred outside your region, we rely on appropriate safeguards such as the European Commission's Standard Contractual Clauses or equivalent mechanisms.

The Service is not directed to individuals under the age of 18. We do not knowingly collect personal information from children. If we learn that we have collected personal information from a child under 18, we will delete it promptly.

In the event of a confirmed personal data breach affecting your information, we will notify affected users and applicable regulators in accordance with applicable law, including within 72 hours where required by the GDPR.

We may update this Privacy Policy from time to time. Material changes will be communicated by updating the "Last updated" date at the top of this page and, where appropriate, by notifying you through the Service or by email.

For material changes, such as new types of data collected or new uses, we will notify you by email or in the Service at least 5 days before they take effect where practicable. Material changes are not applied to data you uploaded earlier without your consent where the law requires it.

Virre is an independent application that integrates with the Zoom Meetings platform via the Zoom API. Virre is not affiliated with, endorsed by, or sponsored by Zoom Communications, Inc. Your use of Zoom remains subject to the Zoom Privacy Statement and the Zoom Terms of Service.

If you have any questions or requests regarding this Privacy Policy or your personal data, please contact us at:

• Email: support@virre.ai
• Website: www.virre.ai
• Privacy requests: support@virre.ai
• Company: RPYIS LLC