Ambient

Privacy Policy

Effective date: May 10, 2026 Last updated: May 10, 2026

This Privacy Policy explains how Ambient Assistant, Inc. ("Ambient," "we," "us," or "our") collects, uses, shares, and protects information when you use the Ambient website at ambientapp.ai, the Ambient web application, our APIs, and any related services (together, the "Services"). The Ambient browser extension and desktop application described in earlier drafts of this Policy are not yet available; sections that depend on them will become effective when those surfaces ship.

Ambient is an AI assistant — a "digital twin" — that helps you complete work across the tools you already use. To do that, the Services read content from accounts you connect (today, the Google Workspace tools you authorize) and build a memory of your preferences, habits, and workflows so that we can draft, summarize, prepare, and act on your behalf. Because the Services are designed to be useful by knowing a lot about how you work, we ask you to read this Policy carefully.

If you have questions, you can reach us at any time by email at [email protected].

1. The basics

Who we are. Ambient Assistant, Inc. is a Delaware corporation. For users in the European Economic Area, the United Kingdom, and Switzerland, Ambient is the controller of personal data described in this Policy unless we say otherwise (for example, when we act as a processor on behalf of a business customer under a Data Processing Addendum).

Who this Policy covers. Anyone who visits ambientapp.ai, signs up for an Ambient account, connects a third-party account to Ambient, or otherwise interacts with the Services. The Services are offered to adults (18+) globally, including in the EEA and the UK. They are not directed to children under 16.

What this Policy does not cover. This Policy does not cover the practices of third parties whose accounts you connect to Ambient (today, Google) or third-party websites or applications that Ambient interacts with on your behalf. Those services are governed by their own privacy policies and terms.

A note on "no training." We do not use the content you or your connected accounts produce ("Customer Content") to train foundation models or to develop generalized AI models for use by anyone other than you. We contractually require our AI sub-processors to do the same. See Section 5 for details.

2. Information we collect

The categories of information we collect depend on how you use the Services.

2.1 Information you give us directly

Account information. Ambient does not collect or store passwords for your Ambient account. When you sign in with a third-party identity provider (Google today), we receive the basic profile information that provider returns — your name, email address, and a unique identifier — which we use to link your Ambient account, plus any profile photo you upload.

Billing information. If you subscribe to a paid plan, our payment processor (Stripe) collects your payment card or bank details, billing address, and tax identification number where applicable. Ambient itself receives the last four digits of your card, the card brand, the billing zip/postal code, the receipt number, the amount, and the subscription status — not the full card number.

Communications with us. When you email support, fill out a form, respond to a survey, post in our community, or talk with us on a sales or onboarding call, we keep a record of what you tell us, including any attachments, transcripts, or screen recordings you share.

Information from your team or organization. If you are invited to Ambient by a workspace administrator, we may receive your email address, role, and group memberships from that administrator before you sign up.

2.2 Content from your connected accounts ("Connected Account Content")

Ambient is most useful when it can read and act on the things you already work on in other tools. With your explicit authorization via OAuth, the Services connect to third-party accounts and access content from them. The integrations available today are limited to Google Workspace; additional integrations may be added as features ship and this Policy will be updated before they go live. Categories we may access, depending on which scopes you approve:

  • Gmail: message bodies, subjects, headers, senders, recipients, timestamps, threads, labels, drafts, attachments, signatures, and account settings;
  • Google Calendar: event titles, descriptions, attendees, locations, conferencing links, attachments, free/busy data, and scheduling preferences;
  • Google Contacts: contact records you authorize Ambient to access, including names, email addresses, and metadata;
  • Google Drive / Docs / Sheets: the documents and files you authorize Ambient to access, including their text, metadata, comments, and revision history;
  • Google Tasks: task lists, items, due dates, and statuses you authorize Ambient to access.

You decide which scopes to grant. You can revoke access at any time inside Ambient's settings or directly with Google; revocation stops new collection and may break features that depend on that integration.

2.3 Browser and desktop context

Ambient does not yet include a browser extension or desktop application. This section will return — describing what those surfaces capture, retain, and exclude — when they ship.

2.4 Audio and transcripts

Ambient does not currently capture audio, transcribe calls, or record meetings. This section will return when voice features ship, including the recording-consent obligations that apply to you when you record other people.

2.5 Memory

Ambient builds three layers of memory about you over time:

  • Semantic memory — facts about you and your context: your tone, your contacts, your role, your projects, your preferences;
  • Episodic memory — patterns drawn from your activity: when you tend to schedule, how you reply, what you check first;
  • Procedural memory — workflows it has learned: end-to-end sequences it can repeat after watching you do them.

This memory is derived from the categories of data described in Sections 2.1–2.4. You can view, edit, and delete entries in your memory at any time from Ambient's settings. Deleting a memory entry does not delete the underlying source data in the connected account it came from (we do not control that), and may reduce the quality of Ambient's drafts and proactive behavior.

2.6 Usage, device, and log data

When you use the Services, we automatically collect:

  • Device and connection data — IP address, device type, operating system and version, browser type and version, language, time zone, screen resolution, mobile or desktop carrier where relevant, and crash diagnostics;
  • Service usage data — features you use, buttons you click inside Ambient, prompts you submit, sessions, error events, latency, and similar telemetry;
  • Identifiers — Ambient account ID, session identifiers, and cookies or similar technologies described in Section 2.7;
  • Approximate location — derived from IP address (typically city/region) and from time zone.

We do not collect precise GPS location.

2.7 Cookies and similar technologies

We use cookies, local storage, and similar technologies to keep you signed in, remember preferences, secure the Services against abuse, measure usage, and deliver marketing on our own properties. We do not use third-party advertising trackers inside the authenticated Ambient app. On our marketing pages (such as ambientapp.ai), we use a small number of analytics and conversion tools. You can manage cookies through your browser; on EU/UK marketing pages we ask for your consent through a cookie banner.

2.8 Information from third parties

We may receive information about you from sources other than you, including:

  • Identity and authentication providers (such as Google or Apple Sign-In), which return your name, email, and a unique identifier when you log in;
  • Third-party integrations, which return the content, metadata, and account information described in Section 2.2;
  • Workspace administrators, where Ambient is purchased by an organization you belong to;
  • Marketing and analytics providers that help us understand which channels reach the right users;
  • Public sources and enrichment providers (such as LinkedIn) that we use sparingly to improve sales and support quality.

3. How we use information

We use the information described above to:

  • Provide the Services. Authenticate you, run drafts, summaries, agent actions, scheduling, search, and the other features you request; route requests to AI sub-processors; remember your preferences and history.
  • Personalize Ambient to you. Build the semantic, episodic, and procedural memory described in Section 2.5 so the Services improve with use, and tune Ambient's outputs to your tone and habits.
  • Maintain reliability and safety. Detect and prevent abuse, fraud, security incidents, and misuse of the Services; investigate violations of our Terms; protect Ambient and our users.
  • Improve the Services. Diagnose bugs, measure performance, evaluate features, and develop new features. We separate this from training: see Section 5.
  • Communicate with you. Send you transactional emails about your account, security notices, billing notices, and product updates; respond to your support questions; share product news and tips you can opt out of.
  • Sell and market the Services. Identify prospective customers, run advertising on our own marketing properties, measure marketing performance, and understand which channels work.
  • Comply with law. Meet legal, regulatory, tax, audit, accounting, and reporting obligations; respond to lawful requests; enforce our Terms and policies; establish, exercise, or defend legal claims.

4. Legal bases for processing (EEA, UK, Switzerland)

If you are in the European Economic Area, the United Kingdom, or Switzerland, we rely on the following legal bases under the GDPR / UK GDPR / Swiss FADP:

  • Performance of a contract (Art. 6(1)(b)) — to provide the Services you sign up for, including reading and acting on content from your connected accounts.
  • Consent (Art. 6(1)(a)) — for things like marketing emails to non-customers and non-essential cookies. You can withdraw consent at any time without affecting the lawfulness of prior processing.
  • Legitimate interests (Art. 6(1)(f)) — for service security and abuse prevention, product analytics, basic marketing of our own products to existing customers, and corporate transactions. We balance these interests against your rights and freedoms; you can object at any time (see Section 11).
  • Compliance with legal obligations (Art. 6(1)(c)) — for tax, accounting, regulatory, and law-enforcement responses.
  • Vital interests / public interest (Art. 6(1)(d) and (e)) — rarely, where necessary to protect someone's life or in connection with a public-interest task.

We do not knowingly process special categories of data (e.g., health, political opinions, biometric data used for identification). If your messages or documents happen to contain such categories, we process them only because they are part of the content you have asked us to handle, and you should consider whether you want to share that content with the Services in the first place.

We do not use the Services to make solely automated decisions that produce legal or similarly significant effects on you.

5. AI models, training, and sub-processors

Ambient uses both AI models we run ourselves and third-party large language model providers ("AI sub-processors") to deliver features.

No training on Customer Content. We do not use Customer Content — your prompts, your connected-account content, your memory, or your outputs — to train, fine-tune, or evaluate foundation models for general use, and we contractually require our AI sub-processors not to do so either. We may use aggregated, de-identified telemetry that cannot reasonably be linked back to you to evaluate quality and safety. Where we develop personalization that improves your own Ambient (for example, models that fit your tone), the resulting personalization is scoped to your account and is not shared with other users.

Sub-processors. We rely on a small set of vendors to deliver the Services, including AI model providers (e.g., Anthropic, OpenAI, Google), cloud infrastructure providers (e.g., Amazon Web Services, Google Cloud, Cloudflare), payments (Stripe), email delivery and customer support tooling, telemetry and error reporting, and analytics. We maintain a current sub-processor list at ambientapp.ai/sub-processors and notify business customers under our DPA before adding new sub-processors as required by that DPA.

Outputs may be wrong. AI outputs can be inaccurate, incomplete, biased, or fabricated ("hallucinated"). Review important outputs before relying on them, and especially before letting Ambient send messages, schedule meetings, sign documents, or take other actions that affect other people.

6. How we share information

We share information only as described below.

With your direction. When you tell Ambient to send an email, post a message, schedule a meeting, share a document, or take any other action that involves a third party, we transmit the information needed for that action to the relevant service.

With AI sub-processors and other service providers. We share Customer Content and other information with the categories of providers described in Section 5, under contracts that restrict their use of the data to providing services to us.

With your workspace administrator. If you use Ambient through an organization, the administrator may have access to your account, usage data, and Customer Content stored in Ambient. Talk to your administrator about their internal policies.

With participants in a transaction. In connection with a merger, acquisition, financing, reorganization, bankruptcy, or sale of all or part of our business, we may share information with the counterparties and their advisors, subject to confidentiality. If a transaction would change who controls your data, we will tell you.

For legal reasons. We may disclose information to comply with applicable law, lawful requests from public authorities, valid subpoenas or court orders, or to protect the safety, rights, or property of Ambient, our users, or the public. We push back on overbroad requests and aim to publish a transparency report.

With your consent. For anything else we describe to you and you say yes to.

We do not "sell" personal information for money, and we do not "share" it for cross-context behavioral advertising as those terms are defined under California law.

7. Connected accounts and Google API Services

When you connect a third-party account to Ambient, you authorize Ambient to access information from that account on your behalf. The scopes we request are listed in the consent screen at the time of authorization and explained in our integration documentation.

Google API Services User Data Policy. Ambient's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use Google user data only to provide the user-facing features of Ambient, do not transfer it except as necessary to provide those features or as required by law, and do not use it for advertising. We do not allow humans to read Google user data except (a) with your explicit consent for specific messages, (b) for security investigations, (c) to comply with applicable law, or (d) where the data has been aggregated and anonymized.

We follow analogous "limited use" practices for other connected providers (e.g., Microsoft Graph, Slack, Notion, Apple).

You can revoke Ambient's access to a connected account at any time from Ambient's settings or directly with the provider. Revocation stops new collection but does not by itself delete what was already retrieved; see Section 9 on retention and Section 11 on deletion rights.

8. International data transfers

Ambient is headquartered in the United States. We process information in the United States and in other countries where our service providers operate. When we transfer personal data out of the EEA, the UK, or Switzerland, we rely on:

  • the European Commission's Standard Contractual Clauses (SCCs) (Module 1 or 2 as applicable);
  • the UK International Data Transfer Addendum to the SCCs, or the UK IDTA;
  • the Swiss FDPIC-recognized SCCs;
  • adequacy decisions, where they apply (for example, we participate in the EU–U.S. Data Privacy Framework where required); and
  • supplementary technical and organizational measures (encryption in transit and at rest, access controls, vendor due diligence).

You can request a copy of the relevant transfer mechanism at [email protected].

9. How long we keep information

We keep personal data for as long as we need it to provide the Services and for the legitimate business and legal purposes described in this Policy. In practice:

  • Account information — for as long as your account is active, plus up to 30 days after deletion in our primary systems and up to 90 days in encrypted backups.
  • Connected Account Content — only what is needed to perform the workflows you have asked for, and otherwise according to your settings. You can disconnect an integration to stop new collection, and you can ask us to delete previously retrieved content from Ambient at any time.
  • Memory — until you delete the memory entry or your account.
  • Logs, telemetry, and security records — typically up to 13 months.
  • Billing, tax, and audit records — for as long as required by applicable law (commonly 7 years).
  • Marketing data — until you unsubscribe or object, plus a short suppression window so we don't email you again.

We may keep information longer if we are required to (for example, to comply with a legal hold) or if it has been aggregated and de-identified.

10. Security

We protect personal data with administrative, technical, and physical safeguards designed for the sensitivity of the data, including encryption in transit (TLS) and at rest, access controls based on least privilege, single sign-on and multi-factor authentication for our staff, network segmentation, vendor due diligence, audit logging, secure development practices, and an incident-response program. We test our defenses regularly.

No system is perfectly secure. If we learn of a personal data breach that affects you, we will notify you and the appropriate regulators as required by law.

You also play a role: secure your Google account with multi-factor authentication or a passkey, keep your devices patched, and be careful about which integrations and scopes you grant.

11. Your privacy rights

Depending on where you live, you may have some or all of the following rights. We honor these rights regardless of where you live, to the extent we can verify your identity.

Access — to request a copy of the personal data we hold about you. Correction — to ask us to fix inaccurate or incomplete data. Deletion — to ask us to delete your personal data, subject to legal exceptions. Portability — to receive certain data in a structured, commonly used, machine-readable format and have it transmitted to another controller where technically feasible. Restriction — to ask us to limit how we process your data. Objection — to object to processing based on our legitimate interests, including direct marketing (which we will always honor). Withdraw consent — to withdraw any consent you have given. Automated decisions — not to be subject to a decision based solely on automated processing that produces legal or similarly significant effects on you. We do not make such decisions. Complain to a regulator — to lodge a complaint with your local data protection authority. We would appreciate the chance to address your concern first.

To exercise any of these rights, email [email protected] or use the in-product privacy controls. We may need to verify your identity. We respond within 30 days where required (longer for complex requests, with notice). You can authorize an agent to make a request on your behalf.

11.1 California residents (CCPA/CPRA)

In the last 12 months, we have collected the following categories of personal information described under the CCPA: identifiers; customer-records information; commercial information; internet or other electronic network activity; geolocation (approximate); professional or employment-related information; and inferences drawn from the above. We collect this information from the sources, for the purposes, and share it with the categories of recipients described in Sections 2, 3, 5, and 6.

We do not sell or share personal information for cross-context behavioral advertising as defined under the CCPA, and we do not knowingly sell or share personal information of consumers under 16. We do not use or disclose sensitive personal information for purposes other than those permitted under §7027 of the CCPA Regulations, so a "Limit the Use of My Sensitive Personal Information" link is not required.

You have the right to know, delete, correct, and to non-discrimination. To exercise these rights, email [email protected]. We will verify your request using information already associated with your account.

11.2 Other U.S. state rights

Residents of states with comprehensive privacy laws (including Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, Iowa, Indiana, Tennessee, Florida, New Jersey, Delaware, New Hampshire, Minnesota, and Maryland) have rights similar to those listed above and the right to appeal a denial of a request. To appeal, reply to our denial email or write to [email protected] with "Appeal" in the subject.

11.3 EEA, UK, and Switzerland

If you are in the EEA, the UK, or Switzerland, you can contact our EU/UK representative arrangements by writing to [email protected]. We will publish formal Article 27 GDPR / UK GDPR representative details on our Sub-Processors and Compliance page.

12. Children

The Services are not directed to children under 16 and we do not knowingly collect personal data from them. If you believe a child has given us their data, contact us and we will delete it.

13. Changes to this Policy

We update this Policy from time to time. If we make a material change, we will post the updated Policy at ambientapp.ai/privacy-policy and let you know in the Services or by email at least 30 days before it takes effect, unless the change is required to take effect sooner by law. The "Last updated" date at the top of this Policy tells you when the latest version was published.

14. Contact us

Ambient Assistant, Inc.

Email: [email protected]

For privacy questions specifically, write to us at [email protected] with "Privacy" in the subject line and we will route your request to the right team. We will publish our registered-agent mailing address as part of our Sub-Processors and Compliance page.