Privacy Policy

This policy covers personal information processed through the Outrevio website, authenticated CRM, integrations, internal AI features, and user-authorized external AI/MCP connections. It covers information about Outrevio account holders and information an account holder chooses to store about professional contacts who may not have an Outrevio account.

The legal entity that will operate Outrevio for public U.S. launch has not yet been finalized.

The inventory below is tied to data flows that currently exist in the application. It is intentionally more specific than a generic list of "information you provide."

Outrevio does not currently collect or use a visa-sponsorship preference. Any previously stored affirmative value is ignored and cleared by the application retention cleanup, and this preference is not provided to AI or external MCP applications while collection is disabled.

Outrevio is a personal/professional relationship CRM. An account holder may therefore store business or relationship information about another person who has never opened an Outrevio account. That information is provided by the account holder or through an import they choose to make; Outrevio does not treat the contact as having agreed to Outrevio merely because another user saved their information.

Account holders are responsible for having an appropriate and lawful reason to collect and use information they place in their CRM. Outrevio uses that data to provide the account holder's CRM features and does not currently sell it or use it for cross-context behavioral advertising.

Outrevio uses essential HttpOnly authentication cookies for access and refresh sessions. The current frontend also uses limited browser local/session storage for interface preferences, dismissed setup prompts, short-lived loading/navigation state, and freshness flags. These mechanisms are used for service functionality rather than advertising profiles.

The current frontend does not intentionally embed Google Analytics, Meta Pixel, PostHog, Mixpanel, Hotjar, Microsoft Clarity, Segment, Vercel Analytics, or another third-party advertising/behavioral analytics SDK. Outrevio does not currently authorize third-party advertising or behavioral-analytics companies to collect personally identifiable information through the product over time and across unrelated websites for behavioral advertising. If Outrevio later introduces analytics, advertising, or other tracking that changes this statement, the privacy disclosures and any legally required consent/opt-out controls must be updated before that tracking is enabled.

Google sign-in is optional and separate from Google Calendar. If you choose it, Outrevio uses Google's OpenID Connect identity response to authenticate you and stores the Google account's stable provider identifier plus the verified email snapshot needed to maintain that sign-in method. Outrevio does not store Google access or refresh tokens for this sign-in-only flow.

The Google sign-in authorization requests only openid, email, and profile. It does not grant Google Calendar access. Calendar access, if you choose it later, uses the separate Google Calendar integration and a separate authorization. You can disconnect Google sign-in from Profile → Account when another sign-in method remains available.

Microsoft sign-in is also optional and separate from Outlook Calendar and Teams. Outrevio validates Microsoft's OpenID Connect identity response and stores the stable Microsoft provider identifier plus an email snapshot for the connected sign-in method. Microsoft email claims are not treated as proof that an existing Outrevio account should be merged automatically; existing accounts must explicitly connect Microsoft from Profile → Account.

Microsoft sign-in requests only openid, email, and profile. New Microsoft-created Outrevio accounts must still verify the email address with Outrevio's six-digit email code before sign-in is completed. Outlook Calendar and Teams continue to require their own separate authorizations and provider permissions.

Google Calendar and Outlook Calendar are optional and use separate provider authorizations. Outrevio stores the connected account information and protected connection details needed to provide the calendar features you authorize. Each calendar connection is separate, and disconnecting one provider removes Outrevio's saved access for that provider without disconnecting another integration.

Outrevio can display Google and Outlook events to the signed-in user, but it does not maintain a persistent general cache of those external event lists. Calendar events do not become relationship evidence automatically. A completed meeting affects relationship intelligence only after you explicitly review and save the CRM relationship update. Personal, private, busy-only, holiday, gym, medical, travel, family, and unknown events remain calendar-only. Calendar descriptions are not sent to Outrevio's AI provider context by the current calendar flow. When you explicitly create an external calendar event from a CRM contact or reminder, Outrevio sends the event details you entered to the provider you selected and may record a minimal scheduling note; that scheduling note does not refresh relationship intelligence or count as a completed interaction.

Gmail is optional and is authorized separately from Google sign-in and Google Calendar. The current Gmail connection requests only https://www.googleapis.com/auth/gmail.metadata. Outrevio uses that permission to fetch a bounded page of Inbox and Sent message metadata for the Capture from email feature. If you explicitly choose Load more, Outrevio requests the next bounded metadata page; it does not search or crawl your entire mailbox in the background. For a selected message, Outrevio requests only the message identifier and the From, To, Subject, and Date headers needed to identify the correspondence and its counterpart. The current integration does not request Gmail message bodies, snippets, attachments, sending, deletion, label modification, or general mailbox-write access.

Gmail metadata is fetched on demand when you open the email-capture experience or explicitly choose Load more, and is not maintained as a persistent general mailbox cache. Protected OAuth access/refresh credentials and connection metadata are kept while you keep Gmail connected. Message metadata becomes durable Outrevio CRM data only when you explicitly review and choose to create or update a contact, log an email interaction, or create a follow-up. The Gmail metadata connection itself does not send Gmail data to an AI provider.

Outlook Email is also optional and separately authorized from Microsoft sign-in, Outlook Calendar, and Teams. The current Outlook Email connection uses Microsoft Graph's delegated Mail.ReadBasic permission to display bounded basic message metadata for Capture from email. It does not request message bodies, body previews, attachments, sending, deletion, or mailbox-write access. As with Gmail, metadata fetched for review is not maintained as a persistent general mailbox cache and enters the CRM only after your explicit action.

Outrevio's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google API data is used only to provide or improve the user-facing features you choose, subject to the controls and disclosures in this policy.

WhatsApp is optional. Outrevio processes messages sent to the configured CRM assistant number; it does not import unrelated WhatsApp chat history, scrape a user's WhatsApp contacts, or automatically contact CRM contacts merely because WhatsApp is connected. If assistant replies are enabled, the current implementation replies only inside the conversation initiated by the linked user; the WhatsApp assistant is not a proactive CRM-contact campaign channel.

Outrevio stores linking information and bounded command logs for security, duplicate/replay prevention, troubleshooting, and user-requested actions. Logged message text is reduced to a short excerpt and recognizable email/phone patterns inside that excerpt are masked where possible. Users can disconnect WhatsApp and clear WhatsApp command logs. Command logs are automatically removed after 30 days. Short-lived confirmation records expire after 10 minutes; their payload is cleared after completion/expiry and terminal metadata is removed after 7 days.

Meeting transcript integrations are optional. Outrevio does not join meetings as a bot, record audio/video, capture microphone or system audio, or run its own speech-to-text service. When you connect Zoom or Microsoft Teams, Outrevio imports only transcript text that the provider generated and that the connected account is permitted to access, together with limited meeting/participant metadata needed to display, search, secure, and synchronize that data.

Meeting transcripts can contain personal communications about people who do not have an Outrevio account. Zoom and Microsoft Teams provide their own participant recording/transcription notices and, depending on provider/account policy, consent controls. Those provider controls do not let Outrevio determine whether every downstream use is permitted in a particular jurisdiction, workplace, school, confidential relationship, or meeting. Account holders should connect/import/use meeting transcripts only when they have appropriate authority and should avoid using Outrevio to retain material they are not permitted to handle.

Outrevio keeps imported transcript text for 90 days from import. After that deadline, transcript text is no longer available for reading, search, or meeting AI and is removed automatically. Limited meeting, participant, connection, and synchronization information may remain while the provider stays connected. Disconnecting Zoom or Teams removes that provider's imported meetings and transcripts from Outrevio. Final account purge after the deletion recovery window removes all local meeting-provider data.

Meeting transcript text is sent to OpenAI, Anthropic, or Google Gemini only when the user separately enables the Meeting transcripts AI data permission and explicitly chooses Analyze transcript. Importing, viewing, searching, retention cleanup, and provider synchronization do not automatically invoke an AI provider.

Outrevio currently prepares drafts and records CRM activity, but it does not operate a general automated email, SMS, WhatsApp, or campaign sender to CRM contacts. Contact information stored in the CRM is therefore not automatically transmitted to an email/SMS provider merely because a user imports or saves it.

If Outrevio later enables outbound communication, the Privacy Policy and product controls must be updated before launch to describe the channel, recipient data, provider(s), purposes, consent or preference records where applicable, suppression/opt-out data, communication metadata, and retention. See the Communications & Outreach disclosure for the current launch gate.

Outrevio uses an external AI provider only when you choose an AI action, such as sending an AI chat prompt or selecting Generate, and only with the data permissions you enabled. Ordinary page loads, imports, contact updates, and non-AI recommendations do not trigger an AI request.

For an AI request, Outrevio sends only the permitted data needed for that action rather than the entire CRM. Depending on your provider choice, the request may be sent to OpenAI, Anthropic, or Google Gemini. Outrevio records limited usage information such as provider, model, action, status, and usage totals, but the AI usage record does not store the prompt, CRM evidence, note content, generated answer, or provider credentials.

Outrevio does not train its own AI models on CRM content. Third-party AI providers process the requests they receive under their own applicable terms and privacy commitments, and providers may handle data differently. Outrevio limits what it sends according to the data permissions you choose.

Generated assistance and inferred relationship signals can be incomplete or inaccurate. Outrevio instructs external AI providers not to infer protected/highly sensitive traits from CRM evidence and not to make or rank regulated eligibility or consequential decisions about another person. Relationship intelligence remains a networking-context feature, not an employment, credit, housing, insurance, or admissions assessment.

Outrevio does not currently keep AI chat history after the active experience requires it. If Ask before changes is enabled, Outrevio can prepare supported CRM actions for your confirmation. Prepared action details are cleared when completed, cancelled, or expired, and remaining status metadata is removed after approximately seven days.

Outrevio may allow separately operated applications such as ChatGPT to connect to your account. These connections are separate from the provider that powers AI inside Outrevio. Each external app receives only the permissions you approve.

Outrevio stores limited connection information needed to manage and revoke connected apps. Temporary connection-request details expire after about 10 minutes. Reading Outrevio data through a connected external app does not use the AI provider selected inside Outrevio. Connected third-party applications have their own privacy practices, which you should review before authorizing them.

Outrevio treats CRM content shared with a connected app as data, not as instructions that can change your Outrevio permissions. A separately operated app may have its own behavior after it receives information you authorized, so connect only apps you trust and disconnect access you no longer want. See the AI & External Connections disclosure for more detail.

Outrevio uses service providers or user-selected integrations to operate the features described in this policy. The current categories are:

Outrevio may also disclose information when reasonably necessary to comply with law, respond to valid legal process, protect users or the service, investigate fraud/security abuse, or complete a legitimate corporate transaction subject to appropriate safeguards and updated notices where required.

No Stripe or PayPal payment processing is active in this policy version. Payment-provider and subscription disclosures must be added before Outrevio begins charging users.

Outrevio does not currently sell personal information and does not currently disclose personal information for cross-context behavioral advertising or operate third-party advertising trackers in the authenticated product.

Because those practices are not currently part of Outrevio, there is no sale/share or targeted-advertising opt-out to apply to the current service. Browser Do Not Track or Global Privacy Control signals therefore do not change essential authentication, security, or user-requested integration behavior today. If Outrevio later introduces a practice for which applicable law requires recognition of an opt-out preference signal, the product and this policy must be updated before that practice is enabled.

Outrevio keeps information only for as long as it is reasonably needed for the feature, security, audit, dispute, or operational purpose described below. The schedule below establishes the current application-controlled retention baseline and automated cleanup for short-lived credentials and integration records.

Provider-managed infrastructure logs and backups can have separate retention controlled by Vercel, Render, Google, Meta, or another provider. Outrevio will verify and reconcile those provider-side periods during the final production legal launch gate rather than promising deletion timing the application cannot directly enforce.

Authenticated account holders can create a privacy export and request permanent account deletion from Settings → Privacy & Data after re-entering their current password and completing a short-lived six-digit email-code verification. A verified request locks the account immediately and starts a seven-day recovery window before final purge. The deletion process and retained-record limitations are described in the Data Deletion Instructions.

Outrevio uses authentication, ownership checks, CSRF/same-origin controls, rate limits, request-size limits, structured logging, revocation controls, and other safeguards intended to protect user data. No system can guarantee absolute security.

Outrevio's persistent system-event store is designed around bounded metadata such as route, status, duration, action/resource identifiers, outcomes, and security source hashes. The persistent event writer allow-lists metadata keys instead of persisting request bodies or CRM note contents. Hosting and infrastructure providers may maintain their own operational logs under their own service terms and retention practices.

Outrevio maintains an incident-response process for investigating suspected unauthorized access, misuse, credential exposure, or other security events. An automated alert is treated as an investigation signal, not automatic proof that a legally reportable breach occurred.

When an incident may involve personal information, Outrevio is designed to contain active risk, preserve relevant evidence, identify affected systems/accounts/data and integrations, revoke or rotate affected credentials and OAuth/MCP grants where appropriate, and escalate the facts for human security and legal review. Whether notice is legally required can depend on the people and jurisdictions affected, the data involved, contractual obligations, and the then-current law; Outrevio does not automate that legal decision.

The current response approach is described in the Security & Incident Response disclosure.

Current product controls include editing profile and CRM data, exporting supported account data, connecting or disconnecting Google or Microsoft sign-in when another sign-in method remains, disconnecting Google Calendar or Outlook Calendar, disconnecting WhatsApp, clearing WhatsApp command logs, disabling/changing internal AI permissions, switching AI actions to Read only, and disconnecting external MCP applications.

Depending on where a person lives, the type of information involved, and whether a particular state privacy law applies to Outrevio, additional rights may include access, correction, deletion, portability, limits on certain sensitive-data processing, opt-out rights for sale/sharing or targeted advertising, and an appeal process for denied requests. Outrevio is being designed around a common U.S. privacy-rights baseline rather than assuming only one state matters.

Users can review or correct much of their own account and CRM information directly in the product. Authenticated account holders can download a portable privacy export or request permanent account deletion through Settings → Privacy & Data; verified deletion requests enter a seven-day recovery window before final purge. Additional instructions are maintained on the Data Deletion page. A request involving a person who is not an Outrevio account holder must be handled without revealing whether that person appears in another user's private CRM.

Outrevio is not designed as a service directed to children under 13. The final public-launch minimum age has not yet been set. Outrevio will not represent the service as available to a particular age group until that eligibility decision and the corresponding product/legal controls are finalized.

Outrevio versions this Privacy Policy and shows its last-updated date. The policy must be updated when product behavior materially changes—for example, if Outrevio introduces payment processing, new tracking/analytics, new external providers, materially broader AI/MCP permissions, automated outreach, or new categories of personal information. Where applicable, a material change may require additional notice or renewed acknowledgement rather than silently relying on an old acknowledgement.

Privacy questions and requests can be sent to support@outrevio.com.

Current legal-document versions and contact details are maintained in the Legal & Privacy Center.