Legal

Privacy policy

Last updated November 4, 2026 · California CCPA / CPRA

1. Who we are

Plato is offered by Augmentation Company (“we”, “us”), 95 Minna St, Floor 3, San Francisco, CA 94105, United States (Doppel Labs). This policy describes how we handle personal information when you visit our website, place a US pre-order for Plato Ring, or use the Plato app (the Plato web app, the Plato Mac app, and the Plato Ring companion).

For privacy requests, email support@plato.it.com or write to us at the address above.

2. Scope

This policy covers:

the public website, checkout, order-status pages, and related cookies; and
the Plato app, including information you connect from Google and other services (see sections 3A to 6B and 10A).

Our Terms of sale cover Plato Ring pre-orders. Our Terms of Service cover the Plato app. Both are linked at the bottom of this page.

3. Personal information we collect

Identifiers and contact

Name and email address you provide at checkout
Email for requested Plato updates, with confirmation, consent copy version, signup placement, timestamp, campaign source and subscription state
Shipping address collected through Stripe Checkout
Phone number collected through Stripe Checkout, for delivery

Commercial information

Pre-order details: ring quantity, sizes, finishes, payment and fulfillment status
Returns and support records related to an order
Where your visit came from, if the link you followed named a campaign (for example an ad), saved with your order. We don't send this to ad networks.

Internet and device activity

Essential cookies for checkout continuity and cookie preferences
Aggregate page views (page address without query details, referrer, and coarse device, browser, and country) through Vercel Web Analytics, which sets no cookies and does not identify you
Bot-detection signals from your browser when you submit signup, checkout or staff sign-in, through Vercel BotID, used only to block automated abuse
Optional interaction analytics only after you allow them: signup invitation views, dismissals, attempts and categorized errors, preorder clicks and checkout starts. A random identifier in tab storage deduplicates interactions; emails, form data, private codes and tokens are excluded.

Payment data

Card and wallet payments are processed by Stripe. We do not store full payment card numbers on Plato servers.

3A. The Plato app: information we collect

When you use the Plato app, we collect:

Account

Your email address, and a sign-in session that keeps you signed in on your device.
Your settings, such as whether History is on.

What you say and type to Plato

Your requests and Plato's answers (the chat).
Text you dictate. The words are saved only if History is on (see section 10A). We do not store the audio.
Short facts about you that you ask Plato to remember, or that you let it save (“memories”). You can see, change and delete them.
Files and photos you give Plato, and the passages Plato makes from them so it can find the right part later.

Information from services you connect

Only when you connect a service and then ask Plato for something that needs it. For Google, see section 6B.
Records of what Plato did for you, such as an email you approved and sent, a calendar event you approved, and the time. These let you check what happened.

Your own AI keys (optional)

If you add your own API key for another AI service, we store the key so Plato can use it for you. See section 6A.

Technical information

Basic device, browser and error information needed to run and secure the app.

4. Sources

Directly from you (forms, cookie choices)
Payment and shipping details from Stripe
Our hosting, database, and email providers acting on our instructions
For the Plato app: from you, from the services you connect (for example Google), and from our service providers acting on our instructions

5. How we use information

Process and fulfill pre-orders, including sizing kits and shipping
Send updates you confirm you want: new Plato features and exclusive subscriber offers. Every marketing email has an unsubscribe link. Unsubscribing does not stop necessary order or support messages.
Understand signup and purchase outcomes. We match confirmed subscriber and checkout emails privately on our backend for aggregate 7- and 30-day conversion reports, and use signed email-provider outcomes for delivery and suppression. We do not send email addresses to general analytics.
Provide order status, customer support, and refunds or returns when applicable
Secure the site, prevent fraud, and meet legal obligations
Improve the site with optional analytics only after consent
Send transactional messages when email delivery is configured

5A. How we use Plato app information

We use app information to:

answer your requests and do things you ask for, such as drafting an email, finding a free time, or saving a note;
turn your speech into text when you dictate;
keep you signed in and keep your account secure;
show your History, memories and records of what Plato did;
prevent abuse and fix problems; and
meet legal obligations.

Plato asks before it sends an email, books or changes an event, creates a file, adds a task or posts anything. It acts only when you ask or approve.

We do not sell your information. We do not use it for advertising. We do not use your content to train or improve AI models, ours or anyone else's. Your content is your data, not training data.

6. Sharing

We share personal information with service providers who help us operate the business, including:

Stripe (payments and shipping address collection)
Supabase (order database and related infrastructure)
Vercel (website hosting, aggregate page-view analytics, and bot detection)
Resend for requested subscription confirmations, updates and delivery outcomes, and transactional email when enabled

We do not operate a production advertising tracker on this site. Vercel Web Analytics counts page views in aggregate without cookies; other optional analytics remain off until you opt in. If that ever changes under California “sale” or “sharing” rules, we will update this section and provide an opt-out.

6A. Who receives Plato app information

We share app information with these service providers, only to run Plato for you:

Provider	What it does for Plato	What it can receive
OpenAI	Runs the AI model that reads your request and writes the answer; turns speech into text; turns file passages into search data	Your messages and recent conversation, memories, what Plato needs from your connected services to answer, passages of files you gave Plato, and the audio of a recording you dictate
Deepgram	Turns your speech into text live while you dictate	The audio of what you dictate, for that recording only. Not your Google data
Supabase	Hosts Plato's database and handles sign-in	Your email, your account data, chat, History, memories, records of what Plato did
Resend	Sends your sign-in code emails	Your email address and the code
Vercel	Hosts the Plato web app and Plato's servers	Requests to the app, which pass through its servers
Nango	Stores the secure access tokens for the services you connect, so Plato can act for you	Tokens and connection details. Not the content of your email, calendar or files
Your own AI provider (only if you add a key)	Answers when you ask Plato to use it, for example “ask Claude”	The request you send to it. Providers you can add: Anthropic (Claude), OpenAI (ChatGPT), Google (Gemini), xAI (Grok), Perplexity, and OpenRouter
Stripe, Resend	As described in section 6, for pre-orders and email	See section 6

OpenAI. We ask OpenAI not to store responses for later retrieval. OpenAI may keep prompts and answers for up to 30 days to monitor for abuse, and then deletes them, unless the law requires longer. OpenAI does not use API data to train its models, and we do not opt in to data sharing. We do not have a zero-data-retention agreement with OpenAI.

Your own AI keys. If you add a key, Plato reads it only for the moment of a request, and sends it only to the provider you chose. It is not shown to the AI model and not written to our logs. Your request goes to that provider under your own account and that provider's terms and privacy policy.

Others. We may disclose information if the law requires it, to protect people's safety or our rights, or in a sale or merger of the company (with notice to you). The people you approve on a card, such as the person you email, get what you approved.

We do not sell personal information and do not share it for cross-context behavioral advertising.

6B. Google user data

If you connect your Google account, Plato asks Google for permission (a “scope”) for each thing it can do. You choose what to allow. You can allow some and decline others. Plato works only with what you allow.

Plato uses Google information only when you ask or approve. It does not look through your Google data in the background.

What Plato asks for and why

Permission (scope)	What Plato does with it	When	Stored?
Sign-in and email address (openid, userinfo.email)	Shows which Google account is connected, and stops two different Google accounts being mixed in one workspace	When you connect	Your Google email address is stored with the connection
Send email (gmail.send)	Sends an email from your own Gmail, after you approve the exact From, To, Cc, subject and words on a card. Plato cannot read your mail with this permission	Only when you tap Send	The email you approved and the time it was sent are kept as a record of what Plato did, in your history for the retention period in section 10A
Calendar free/busy (calendar.freebusy)	Checks when you are free or busy. Shows busy times only, never event titles	When you ask, for example “when am I free Thursday?”	The answer is kept in your chat history. Plato does not keep a copy of your calendar
Colleagues' availability (calendar.events.freebusy)	Finds a time that works for you and a colleague who has shared their calendar with you, from busy times only	When you ask	Same as above
Your calendar events (calendar.events.owned)	Lists events on calendars you own, and adds, changes or cancels an event (optionally with a Meet link and guests) after you approve the exact card	When you ask or approve	The answer and the event you approved are kept in your chat history and action record. Plato does not keep a copy of your calendar
Google Meet links (meetings.space.created)	Creates a Meet link when you ask for one, after you approve. Plato can read only the meeting spaces it created	When you ask and approve	The link is kept in your chat history
Google Drive files you pick (drive.file)	Reads only the files you choose with the Google file picker, and creates a new Google Doc, Sheet or Slides file you ask for, after you approve. Plato cannot see any other file in your Drive	When you pick a file or approve a new one	Plato keeps the answer in chat history. If you add a file to Plato's library, Plato keeps passages of it until you remove it. A file Plato creates stays in your own Drive
Google Tasks (tasks)	Reads your task lists and open tasks when you ask, and adds a task after you approve	When you ask or approve	Answers are kept in your chat history. Plato does not keep a copy of your tasks
Google Contacts (contacts.readonly)	Looks up a name you typed (for example “email Sara”) in your contacts, and shows the address on the card for you to confirm before anything is sent	When you ask	The address you confirmed appears in the card record. Plato does not keep a copy of your contacts
Other contacts (contacts.other.readonly)	Same lookup, also among people you have emailed before (Google's “Other contacts”)	When you ask	Same as above
Read your Gmail (gmail.readonly)	Searches your mail and reads a message you ask about, for example “has Sam replied?”. Attachments are named, never opened. Plato does not use Gmail content to write to anyone you did not name	Only when you turn on Gmail reading and ask. This is a separate permission you choose	Plato does not save the email's text. It keeps only the answer it gave you in chat history
Read your Drive files (drive.readonly)	Reads Drive files you ask about, so it can answer from them	Only when you turn it on and ask. This is a separate permission you choose	Plato does not keep a copy of the file. It keeps the answer in chat history

Plato asks for Gmail reading and Drive reading as separate, optional permissions. They are not part of the first connection.

Who Google user data is shared with

Plato shares Google user data only with the service providers in section 6A that are needed to give you the feature you asked for:

OpenAI receives the part of your Google data that is needed to answer a request (for example your free times, an event, or text of a file you picked), for that request.
Your own AI provider, only if you added your own key and asked Plato to use it (for example “ask Claude”): the request you send, which can include Google data you asked about, goes to that provider under your own account.
Nango holds your Google access token. It does not receive the content of your email, calendar or files.
Supabase and Vercel host the database and the app that store and carry the answers and records described above.

We also send an email or calendar invitation to the people you approve on a card, from your own Google account.

We do not share Google user data with anyone else, except if the law requires it, for security, or with your consent.

Limited Use

Plato's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

In plain words:

We use Google user data only to provide and improve the features you asked for in Plato.
We do not sell Google user data.
We do not use Google user data for advertising, including retargeting or interest-based ads.
We do not use Google user data to train or improve generalized AI or machine-learning models, ours or anyone else's. Our AI provider does not use it for training either.
People at Plato do not read your Google data, except with your consent, to keep Plato secure or investigate abuse, or to follow the law.

Protecting Google user data

Google data moves over encrypted connections (HTTPS). Access tokens are held by Nango, not in Plato's database, and Plato's database limits each person to their own data. We keep a Google connection only as long as you leave it connected.

Disconnect and delete

Disconnect: In Plato, go to Connectors and choose Disconnect for any Google service. Plato stops using it at once, then revokes the access at Google.
Revoke at Google: You can also remove Plato at any time at myaccount.google.com/permissions.
Delete what Plato kept: You can delete History items and memories in the app. To delete anything else, or your account, email support@plato.it.com.

7. Your California privacy rights

If you are a California resident, you may have the right to:

Know what personal information we collect, use, and disclose
Request deletion of personal information, subject to legal exceptions
Correct inaccurate personal information
Opt out of sale or sharing of personal information, if we engage in those activities
Limit use and disclosure of sensitive personal information, where applicable
Not be discriminated against for exercising these rights

To exercise these rights, contact us using the details in this policy. We will verify requests as required by law and respond within applicable California timelines.

For Plato app information, you can make these requests by emailing support@plato.it.com from the email address of your account. You can already see, change and delete your memories and History in the app. We will verify requests as required by law.

Do Not Sell or Share My Personal Information

8. Do not sell or share

Based on how the site and the Plato app work today, we do not sell personal information or share it for cross-context behavioral advertising. We do not use Google user data for advertising. If that changes, California residents will be able to opt out through a clear link or request process on this page.

9. Cookies and similar technologies

We use a first-party consent cookie to remember your analytics preference, an order-status cookie after checkout in this browser, and admin session cookies for the operations portal. Use Cookie preferences on consumer pages to change optional analytics. Optional measurement uses a random tab identifier only after consent; withdrawing consent stops events and clears that identifier. Signup prompt preference storage remembers a successful signup for a year, without an email address, so the invitation stops showing.

10. Retention

We keep personal information as long as needed to fulfill your pre-order, provide support, meet legal and accounting requirements, and resolve disputes. Unconfirmed signup addresses expire from our system after 30 days. We retain confirmed subscriptions until withdrawal and keep minimal consent and suppression records to honor opt-outs and prevent unwanted re-enrollment; contact us to request deletion. Optional interaction records are retained for up to 90 days. When information is no longer needed, we delete or de-identify it where practical.

10A. Retention for the Plato app

Chat: Your chat messages are deleted after 90 days by default.
History (your dictations, notes and edits): kept until you delete them, or you turn History off. When History is off, nothing new is saved. Items saved earlier stay until you delete them. You can delete one item or all.
Audio: We do not store audio. A recording is used once to turn it into text.
Memories: kept until you delete them.
Files you add: kept until you remove them.
Connections to Google and other services: kept until you disconnect. On disconnect, Plato stops using the access at once and then revokes it.
Records of actions (for example, that an email you approved was sent): kept in a record of what Plato did for you, as described in section 3A.
OpenAI may keep prompts and answers for up to 30 days to monitor for abuse, then deletes them (section 6A).
Account deletion: To delete your account, email support@plato.it.com from your account's address; we delete your data within 30 days, except what the law requires us to keep.
Backups: deleted data may remain in database backups for a short time before it is overwritten.
Legal: we may keep information longer if the law requires it.

11. Security

We use administrative and technical measures appropriate to an e-commerce pre-order site, including restricted server access to order data. No method of transmission or storage is fully secure.

12. Children

The site is not directed to children under 18. We do not knowingly collect personal information from children for pre-orders.

13. International visitors

Pre-orders are offered for US shipping only, and Plato is offered to people in the United States. If you access the site or app from elsewhere, your information may be processed in the United States.

14. Changes

We may update this policy. When we do, we will revise the date above. Material changes will be highlighted on this page or communicated by other reasonable notice.

15. Contact

Augmentation Company
95 Minna St, Floor 3
San Francisco, CA 94105
United States
support@plato.it.com

Terms of sale (pre-orders)Terms of Service (Plato app)Preorder