Privacy policy

This policy describes how Pivot’s desktop Google integrations and this product website handle information. “Pivot” refers to the developer maintaining the Pivot desktop workspace.

中文版本 ↓

1. Information accessed and why

Pivot uses Google OAuth rather than asking for your Google password. It receives your account email address and verified account identity to identify a connection, the permissions you grant, and authorization credentials needed to call Google APIs.

Only the permissions you grant can be used. Declaring a supported permission does not authorize an operation. Sending mail or creating a draft also follows Pivot’s action approval rules.

2. AI services and your choices

When you request an AI workflow, the relevant content and your request may be sent to the model provider configured in your installation. Review that provider’s privacy practices and service terms before enabling it. Do not use a provider for Google-connected content if its terms allow uses inconsistent with Google’s Limited Use requirements.

Continuous new-mail summaries require separate consent to a specific provider, model and API host. After establishing a current mailbox baseline, Pivot retrieves newly arriving mail and sends its sender, subject, body and relevant date information to that approved service to produce a summary. This task does not load previous conversations or scan the older mailbox. A changed destination requires renewed consent. Set notifications to Off to stop this automatic processing.

3. Storage, sharing and retention

OAuth credentials are encrypted in Pivot’s protected local credential store. The local database stores account connection metadata, granted permissions, app selections, notification checkpoints, pending mail metadata and generated summaries. Workflows may store retrieved content and outputs in local conversation history.

Pending notification summaries are retained until delivery. Delivery clears the queue’s duplicate metadata and summary, while message identifiers remain for deduplication. Delivered content may remain in conversation history and replay data until you remove the applicable local data. Removing a connection does not automatically erase all previously saved conversations or outputs.

Pivot does not sell Google account data, use it for advertising, or use it to train general-purpose AI models. Transfers are limited to Google for API operations and the user-selected model service for the requested or separately approved feature. User-managed remote deployments, backups and other configured services may have additional retention practices. The product website does not host your Google credentials or mailbox; hosting providers may process basic request information such as IP addresses for delivery and security.

4. Google API Limited Use

Pivot’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google data is used to provide the visible, user-requested features described here. Pivot does not provide developers with routine human access to your Google content; any exceptional access must meet the policy’s permitted conditions, including your affirmative agreement when required.

5. Security and access controls

Google API calls use HTTPS; desktop OAuth uses a temporary loopback callback and PKCE. Account access is checked against current authorization and granted scopes. Diagnostic logs are designed to omit access tokens, refresh tokens, authorization codes and product secrets. Security depends also on your device, your model provider and any remote deployment you manage.

6. Your controls and deletion

• Choose the account and permissions on Google’s authorization page.
• Disable or remove the connection in Pivot; revoke Google access using your Google Account connections.
• Set email notifications to Off to stop automatic processing, or choose the chat receiving notifications.
• Remove locally saved conversations and outputs using available product controls. For complete local data removal, contact support for guidance and remove user-managed backups separately.

7. Changes and contact

Material changes to how connected data is processed will be described in an updated policy and, when required, an in-product notice or renewed consent.

Support and privacy contact: trueme521@gmail.com.