Privacy.
Last updated November 11, 2026
Scope and product surfaces
Para has two separate deployment surfaces with different data paths. This page describes the current implementation; it is not a promise that every deployment has the same retention, security, or availability configuration.
- Para Desktop: the Tauri macOS app talks to a local daemon. Mail projections, search indexes, settings, diagnostics, backups, approvals, and connected calendar/contacts data are kept in local app storage by default. Provider, AI, and integration calls send the relevant data to those services when you enable them.
- Para Web: the same workspace served to a browser by a self-hosted Bun host that the operator runs. It uses the same local daemon store on that installation, with one owner, cookie sessions, and no hosted sign-up. Account/session data and synced mailbox projections are kept in that installation's store, logs, and backups, and the operator of the installation is responsible for their retention, security, and backups.
Before handling sensitive information, review the deployment configuration, the connected provider terms, and the operator's retention and access practices.
Google account integration
When you connect a Google Account, Para uses OAuth and the Gmail, People, and Calendar APIs needed by the features you enable on the selected surface. The consent screen is the authoritative list of scopes for your account.
- Google grants access only after you approve the OAuth consent screen
- Para uses the granted data to sync, display, search, and act on requested features
- Token storage follows the selected surface and deployment configuration
- You can revoke our access to your Google account at any time through your Google Account settings
Google's own terms and privacy policy apply to Google-held data. Disconnecting Para does not delete messages or other copies that remain in Google or in a deployment you do not operate.
Data collection and usage
Desktop
- Local mailbox projections, indexes, settings, and diagnostics are stored on the Mac by default.
- Backups and exports are created only when you configure or request them.
- AI, provider, MCP, and other integrations receive the data needed for the action you request.
- Desktop diagnostics are read from local daemon stores; they are not a promise that an enabled third-party integration receives no data.
Hosted web deployments
- The web host processes account, connection, mailbox, and AI data required for its enabled features.
- Synced mail can be persisted in the installation's local daemon store, logs, and backups.
- Hosted deployments may enable product analytics or error monitoring through environment configuration. Error monitoring is off unless the operator configures it, and session recording is additionally opt-in. Product analytics, when enabled, uses an opaque account identifier and event metadata only, never message content.
- Self-hosted operators control their infrastructure, retention, access, backups, and any optional telemetry.
External services
Google, model providers, analytics, hosting, and other services process data under their own terms when you connect or enable them. Check each provider's policy and the deployment configuration before using a service with confidential content.
Data protection and security
What the code provides
- OAuth flows are used for supported Google integrations.
- Desktop local stores, backups, and approvals include application-level controls described in the source.
- Self-hosted installations rely on the access, session, storage, and backup controls that the operator configures.
- The repository is open source and can be reviewed, tested, and hardened by operators and contributors.
What this page does not promise
- Para does not claim end-to-end encryption for every email or integration.
- Para does not claim a particular cloud certification, audit cadence, retention period, or incident-response SLA.
- Para does not claim that every deployment has the same network, backup, access, or monitoring controls.
Your responsibilities
Secure your device, credentials, OAuth applications, deployment infrastructure, and connected providers. Self-hosted operators must set their own access, retention, backup, monitoring, and incident-response policies.
Google user data handling
Data access and usage
- Depending on the features you enable, Para may access the following Google data:
- Email content and attachments
- Email metadata (subject, dates, recipients)
- Labels and folder structure
- Basic profile, calendar, and contact information
- The selected surface uses this data to provide the requested mail, calendar, contacts, search, and AI features.
- Any copy or derived result can follow the storage and retention rules of the selected surface and enabled integration.
- Para's use and transfer of Google data must follow the Google API Services User Data Policy.
Data sharing and transfer
- Google data can be sent to the providers required for an enabled feature, such as Google itself, a configured model provider, or the hosting platform.
- Review the service's own terms and the deployment's environment configuration before enabling an integration.
Data retention and deletion
- Desktop retention follows local settings, backups, exports, and OS storage that you control.
- Web retention follows the operator's local daemon store, log, and backup configuration for that installation.
- Provider-held messages and provider-side backups are not deleted by clearing a Para copy.
- Use the available export and deletion controls for the selected surface, then revoke OAuth access with Google when you no longer need it.
User rights and controls
- Revoke or reconnect provider access from the provider or Para settings.
- Export or delete data where the selected surface and deployment expose those controls.
- Ask the deployment operator about hosted account, backup, and log retention.
- Additional rights may apply under the law where you live.
Limited use disclosure
Our use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Your rights and controls
- Revoke access to your Google account at any time through Google or Para settings.
- Use the available export and deletion controls for the selected surface.
- Ask a hosted deployment operator about account, backup, and log retention.
- Exercise any additional rights provided by the law where you live.
Contact
Use the support channel published by the operator of your Para deployment. Desktop diagnostics can be exported locally from Settings without including credentials.
Updates to this policy
We may update this privacy policy from time to time. We will notify users of any material changes through our application or website.