Data & Security
Last updated: November 15, 2026
Plot connects to the tools where your work happens: your email, your calendar, your team chat. That means we hold data worth protecting, and we treat that as part of the product. This page explains who can see your data, where it lives, what AI does with it, and what happens when you delete it.
This page covers all three Plot products: Plot Traction, Plot Dispatch and Plot Pulse. Where a practice differs by product it says so. The legal commitments live elsewhere: Dispatch and Traction share the terms and privacy policy, and Pulse has its own terms and privacy policy because it calls, records and transcribes people who have no Plot account.
The short version
- People at Plot can't browse your conversations. They're encrypted with a key that belongs to your account alone, and no person here has permission to use it.
- Nothing is sold, and nothing trains AI. We don't sell your data or show ads. The AI providers we use are barred from training on it, and from keeping it after they respond.
- You choose what connects. You sign in with the provider directly, so Plot never sees your password. Remove a connection and what it brought into Plot Dispatch is deleted.
- Deleting means gone. Delete your Plot account and we destroy your key. Once it's gone, nothing encrypted with it can be read again, backups included.
- There are limits, and we list them. This is not end-to-end encryption: our services open your content to do the work you asked for. See what it doesn't cover.
Your content stays private
The people who work at Plot have no way to browse what we store for you. Everything your connections bring into Plot is encrypted before it's stored, with a key that belongs to your account alone. That covers your messages and chats, documents and comments, calendar events, the names in your contacts, and attachments. In Plot Dispatch it also covers what you write there: your notes and replies, thread titles, the names and notes you keep about people, and the files you attach.
Only Plot's own services can use your key. They open your content to do what you asked for: sync it to your devices, send your reply, write a summary. Our staff have no access to the keys, so the copies in our database, our backups and our file storage are unreadable to the people who work here.
How it works
- Your content is encrypted with AES-256-GCM, using a data key created for your account and used for nothing else.
- That data key is only ever stored wrapped: encrypted by a second key, one per account, held in Google Cloud Key Management Service in Toronto. That second key never leaves Google's service.
- The keys sit in a Google Cloud project of their own, where no person holds permission to use them. The only identity that does is the service that runs our sync.
- Google records every use of a key, and every change to who may use one, in audit logs we can read but can't edit.
- Our services keep an opened key in memory for at most 15 minutes. It's never written to a database, a disk, a cache or a log.
What it doesn't cover
We'd rather you hear the limits from us.
- This is not end-to-end encryption. Our services work with your content in memory to sync it, send it and summarize it. What account keys remove is standing access: nobody can browse what we store. You are still trusting the code we run.
- Addresses and routing details stay readable to our systems. Email addresses, phone numbers, links, dates and IDs aren't encrypted with your key, because we need them to deliver and match your messages. They're encrypted at rest by our infrastructure providers like everything else, and left out of the tools our staff use.
- Shared Dispatch threads use a shared key. A thread you start in Plot Dispatch and share belongs to everyone on it, so it's encrypted with a key held for Dispatch as a whole, protected the same way, and not with any one person's key.
- Notifications leave our servers readable. A push notification or an email summary carries the sender, title and preview you see, and passes through Apple, Google or our email provider to reach you.
- Not every product is covered yet. Account keys protect what your connections bring in and everything in Plot Dispatch. Plot Pulse recordings and transcripts, and what you write in Plot Traction, rely on the infrastructure encryption described below.
Who can see your work
Your threads are visible to you and the people you've shared them with, directly or through a group. What a connection brings in is yours alone, even on a thread you share. Drafts stay private until you send them. These rules are enforced on our servers, on every request, not just in the app.
People at Plot don't read your content. The tools we use to run and debug Plot show counts, dates and IDs, with content left out. If you ask us to look at something specific, we need your written permission naming the threads or messages. Reading them then takes a temporary grant on your key alone, made by a named person and removed afterwards. The grant, each use of the key, and the read itself are all recorded. There is no quieter way in: the narrow exceptions in our privacy policy, investigating abuse and legal requirements, take the same recorded steps.
Where your data lives
Plot keeps a copy of your data on your device, so it works offline and stays fast. That copy is protected by your device's own storage encryption.
Your data syncs to our servers for backup, for your other devices, and for sharing with the people you choose. Our database and our encryption keys are on Google Cloud in Toronto, Canada. The database is backed up every day, and backups are kept for seven days in Google Cloud's United States region. A backup holds exactly what the database holds, so your content is encrypted there too. Our API and file storage run on Cloudflare's network.
Protected on the way and in storage
Everything moving between your device and our servers is encrypted in transit with TLS. Everything stored on our servers is encrypted at rest by our infrastructure providers, underneath the account encryption described above.
The tokens that link your connected accounts are encrypted separately with AES-256-GCM, under a key that only our sync service holds and that is never stored in the database.
Your connected accounts
Connections use OAuth: you sign in with the provider directly, and Plot receives a scoped token, never your password. Each connection asks only for the access its features need. You can remove a connection at any time, which revokes Plot's access, deletes its token, and deletes what it brought into Plot Dispatch.
Plot's use of information received from Google Workspace APIs adheres to the Google User Data Policy, including the Limited Use requirements. Because Plot can access Gmail, we also pass an annual independent security assessment (CASA) that Google requires for that access.
AI
AI in Plot does things you can see: rank what needs you, write a title, summarize a thread, tidy up dictation. We send only what a feature needs to our AI providers, under agreements that prohibit them from training on your data or keeping it beyond the response. Plot Dispatch uses models from Google and Cloudflare; across all Plot products the providers are Anthropic, Cloudflare, Google and OpenAI. Requests go through a gateway we run on Cloudflare, set to keep no record of what was sent. We never use your data to train models either. Any personalization is specific to your own account and applied when a feature runs, not used to train a shared model.
AI is assistive: it suggests, and you decide. Plot doesn't let AI take consequential actions on its own. You stay in control of what gets sent, moved, or changed. As with any AI, its output can be incomplete or wrong, so review anything important before you act on it.
Deleting your data
You can delete your Plot Dispatch account from the app at any time. We hold your data for 14 days in case you change your mind. Then your connections are removed, and your threads, notes, files and settings are deleted, automatically and permanently. Notes you wrote on threads you shared stay with the people you shared them with.
You can also delete your whole Plot account. After the same 14 days, each product deletes your data and we destroy your account's encryption key. Google completes the destruction seven days later. From then on, anything that was encrypted with your key can no longer be read by anyone, including any copy still sitting in a backup.
Payments
Payments are handled by Stripe. Your card details go to Stripe directly and never touch our servers.
The services we rely on
Plot runs on a small set of providers, each doing one job:
- Cloudflare: API hosting, networking, file storage, and some AI features
- Google Cloud: database hosting and key management (Toronto, Canada), and database backups (United States)
- Clerk: sign-in and authentication
- Stripe: payments
- Anthropic, Google, and OpenAI: AI features (never used for training)
- Unipile: powers the LinkedIn, WhatsApp, and Instagram connections, and holds those sessions for us
- PostHog: product analytics and error tracking, with no message content
- Resend: email notifications
- Firebase and Apple Push: notifications to your devices
We don't sell your data, and we don't show ads.
If you find a security issue
Email security@useplot.com. It reaches us directly, and we respond quickly. We also publish security.txt for automated discovery.
Where we are
We're a small team, and we don't have a SOC 2 report yet. What we do have: the controls on this page, an independent security assessment every year, and a design where reading your content takes a deliberate, recorded act rather than a database login. If you're evaluating Plot for your business and need more than this page, write to security@useplot.com. A person will answer.