Your context stays under your control.

When you connect an account, you choose the sources Pryveo may read and the private or shared space they belong to. Pryveo stores the source material you select and the context derived from it so it can build your memory, keep it current, create the views you request, and answer your questions with source evidence.

Pryveo does not ingest an account, file, calendar, mailbox, label, channel, or page merely because you signed in. Source authorization and source selection are separate choices.

For the public email journey, Pryveo gives each space a private, revocable forwarding address. Pryveo receives only the new messages your mailbox rule forwards to that address; it does not receive permission to browse, send, edit, move, or delete anything in your mailbox. You may pause or close the address at any time.

If you connect Google, Pryveo receives your Google account identifier and email address to label the connection. For Drive, Pryveo can read only files you expressly open or share with Pryveo through Google Picker. For Calendar, Pryveo lists calendars you can read and reads event details and later changes only from calendars you select. A separate Google Workspace Preview may be offered only to approved operators or design partners. That isolated preview can request read-only Gmail and broader Drive access, remains in Google Testing status, and is never shown as part of the ordinary public journey.

These Google permissions are read-only. Pryveo cannot send, edit, move, or delete Gmail messages, Calendar events, or Drive files.

Raw or derived Google Workspace data is used only to provide or improve Pryveo’s visible, user-facing features: importing the places you chose, deriving evidence-backed memories, refreshing those memories when the source changes, building the focuses and views you request, answering your questions from selected context, and showing the source behind an answer.

If you deliberately contribute a learned detail to a shared space, the preview tells you what other members will receive before you approve it. Membership alone never transfers your private Google source or its raw content. Pryveo does not use Google content for plan enforcement; plan accounting uses content-free counts such as the number of selected places and processing operations.

To turn selected source content into useful memory and answer the questions you ask, Pryveo sends only the context needed for that operation to Anthropic’s commercial API. Pryveo currently uses Claude Haiku 4.5 for extraction and background organization and Claude Sonnet 5 for interactive answers and setup assistance. Anthropic acts as a service provider; under its commercial API terms, API inputs and outputs are not used to train generalized models unless the customer explicitly opts in. Pryveo has not opted in and does not submit user feedback containing Google data to Anthropic.

Anthropic’s standard API may retain inputs and outputs for up to 30 days for trust, safety, and legal purposes. Pryveo does not route Google Workspace data to a model connection whose no-generalized-training treatment it cannot establish. A model key a user adds does not override this restriction.

Amazon Web Services hosts Pryveo’s application, encrypted database, encrypted source storage, secrets, and operational logs. Vercel hosts the web interface. Razorpay processes checkout and subscription information but does not receive connected-source content. Google, Slack, and Notion process authorization and source requests under their own terms when you choose those integrations. Providers receive only information needed for the user-facing service described here and are not permitted by Pryveo to sell it or use it for advertising, credit decisions, or generalized model training.

Pryveo uses PostHog to understand whether product journeys work and where people encounter operational failures. Events contain pseudonymous identifiers and limited milestones such as starting a trial, connecting a source, receiving a first memory, completing an answer, accepting a shared-space invitation, or finishing checkout. They include deployment and release labels so failures can be diagnosed.

Pryveo does not send PostHog email addresses, source content, file or message names, memory text, questions, answers, OAuth credentials, payment details, or arbitrary page addresses. Person profiles and automatic content capture are disabled. You can stop new product analytics at any time from Privacy & data. Account closure also severs the pseudonymous identifier that linked earlier events to your Pryveo account.

Pryveo’s use and transfer of raw or derived information received from Google Workspace APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Pryveo does not sell Google user data; use it for advertising, retargeting, lending, or credit-worthiness; or use it to create, train, or improve a foundational or generalized AI model. A person may inspect specific Google data only with your explicit consent for support, when necessary to investigate a security incident or abuse, or when required by law. Such access is limited and logged.

For each selected source you choose whether Pryveo keeps the original so it can be reprocessed as the product improves, or removes the original after learning and retains only the evidence-backed context. Connector credentials are encrypted separately from content. Pausing an email route stops new processing, and closing it revokes the address. Disconnecting a Google account revokes its token and stops future collection; you then choose whether already learned context remains available or is made unavailable.

You can review sources and provenance, correct or forget individual memories, export your Space, and close your account. Account closure schedules removal of private product data and retained source artifacts. Content-free security, billing, and legal records may remain only for the period required for those purposes. To request access or deletion directly, email nikhil@pryveo.com.

Pryveo uses access controls, encryption, and auditable service boundaries to protect account data. No system is risk-free. For a privacy request or security concern, email nikhil@pryveo.com.