Privacy Policy

Dopple ("Dopple", "we", "us") is an operational AI identity layer: it gives you persistent memory, multi-persona voice, and service agents that act inside the tools you connect — such as Gmail and Google Calendar. This policy explains what data we collect, how we use it, where it is stored, when it is shared, and how you can delete it.

This policy applies to the Dopple web application and the Dopple API. By using Dopple you agree to this policy. If you do not agree, please do not use Dopple.

Account data. When you sign up we collect your name, email address, and profile image through our authentication provider, Clerk.

Conversations and memories. Your chats with Dopple personas, and the memories Dopple extracts from them (facts, preferences, and context you share), including vector embeddings of that content used for retrieval.

Google user data. Only if you explicitly connect a Google product (see section 3).

Other connected services. If you connect services such as Slack, Notion, GitHub, or Linear via API tokens, we store those tokens and the minimum data needed for the relevant agent to act on your behalf.

Technical data. Standard server logs (IP address, request timestamps, error traces) used for security and reliability. We do not use third-party advertising trackers.

Connecting Google is optional and separate from signing in. When you connect Gmail or Google Calendar from the Connections page, Dopple requests the following OAuth scopes:

• gmail.readonly — to read your email threads so Dopple can triage your inbox, summarize threads, surface what needs a reply, and build your daily digest.
• gmail.modify — to send replies you approve, and to archive or label threads when you ask Dopple to.
• calendar.events — to read and create calendar events when you ask Dopple to schedule something.
• openid, userinfo.email, userinfo.profile — to identify which Google account you connected.

What we store. We store your OAuth tokens, your Google account email address, and a synced copy of email thread metadata and message content (sender, recipients, subject, body) so features like inbox triage, summaries, and search work quickly. Calendar events are accessed on demand and are not stored as a synced copy.

Limited Use disclosure. Dopple's 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.

Specifically: we only use Google user data to provide the user-facing features described above. We do not sell Google user data. We do not use Google user data for advertising. We do not transfer Google user data to third parties except as needed to provide these features (see section 5), to comply with law, or as part of a merger or acquisition with prior notice to you. Humans do not read your Google user data except with your explicit permission, when required for security or legal compliance, or when aggregated and anonymized for internal operations.

No AI/ML model training. We do not use Google user data — including any Gmail or Calendar content — to develop, improve, or train generalized artificial intelligence or machine learning models. Google user data is only passed to AI models at your request, to generate the specific output you asked for (for example, summarizing a thread or drafting a reply), and our model providers are contractually prohibited from training on it.

• To provide Dopple's features described above.
• To personalize your personas using the memories you have let Dopple keep.
• To secure, debug, and operate the service.
• To communicate with you about your account.

We do not sell your personal data, and we do not use it for third-party advertising.

Dopple runs on a small set of infrastructure providers that process data on our behalf, under agreements that restrict their use of your data to providing their service to us:

• Clerk — authentication and account management.
• Vercel — hosting for the web application.
• Railway — hosting for the API and the PostgreSQL database where your data is stored.
• AI model providers (Groq, Google Gemini) — process the specific content needed to answer your request (for example, a thread you asked Dopple to summarize). These providers do not retain or train on this data.

We may also disclose data if required by law, or to protect the rights, safety, or security of Dopple or its users.

All data is encrypted in transit using TLS. Data at rest is stored in managed databases with encryption at rest provided by our hosting providers. OAuth tokens are stored server-side and are never exposed to your browser or to other users. Access to production systems is restricted to authorized personnel.

We keep your data for as long as your account is active, so that your memories and connected services keep working.

Disconnecting Google. You can disconnect Gmail or Google Calendar at any time from the Connections page. When you disconnect, Dopple deletes the synced copies of your email data, deletes the stored OAuth tokens, and revokes its access with Google. You can also revoke Dopple's access from your Google Account security settings.

Account deletion. To delete your Dopple account and all associated data — including memories, conversations, and any remaining connected service data — contact us at hello@dopple.app. We complete deletion requests within 30 days.

Depending on where you live, you may have rights to access, correct, export, or delete your personal data, and to object to or restrict certain processing. You can exercise these rights by contacting us at the address below. We do not discriminate against you for exercising them.

Dopple is not directed at children under 16, and we do not knowingly collect data from them.

We may update this policy from time to time. Material changes will be announced in the app or by email before they take effect. The "Last updated" date above reflects the current version.

Questions about this policy or your data: hello@dopple.app.