- Deployment
- hosted
- Hq Country
- United States
- Hq City
- Seattle
- Ownership
- private
- Founded
- 2021
- Training Default
- trains-deidentified
- Residency Options
- United States and other countries
- Gov Access Exposure
- us-cloud-act
- Eu Ai Act Role
- provider
- DPA available
- yes
- Retention Default
- "Read AI is based in the United States, and we and our service providers process and store personal information on servers located in the United States and other countries." Information is kept as long as necessary for the purposes it was collected for and for other legitimate business purposes.
- Retention Exceptions
- The ingestion surface is the widest in this batch. With the Google integration enabled, Read may collect Google account information, Calendar data including titles, descriptions and guest lists, Gmail message bodies and metadata, Google Docs content, Google Drive content more broadly, and Google Chat messages. It states it will not use Workspace API data to train generalized or non-personalized models — a carve-out that leaves personalized models in scope — while separately saying it uses information "to train and improve our models within our Services", consistent with account settings.
- Subprocessors
- not published as an entity list; the privacy policy describes categories of recipient
- Subprocessor Count
- 0
- Transfer Mechanism
- none-stated
- Eu Procurement Ready
- fail
- Eu Procurement Reason
- The widest data ingestion in the batch paired with the thinnest disclosure. With the Google integration on, Read AI's own privacy policy lists Gmail message bodies, Google Docs content, Drive content "more broadly" and Google Chat messages alongside the meeting recording — an ingestion surface no other row here approaches. Against that: US servers with no EU option, no published sub-processor entity list, no Chapter V transfer mechanism named, no certification found on a first-party page, and training of its own models subject to account settings. The Workspace carve-out is worth reading precisely: it excludes generalized and non-personalized models, which is not the same as excluding training. Two navigation notes for anyone re-verifying this row — read.ai/privacy is a marketing page and the actual policy is at read.ai/pp.
- Training Claim Basis
- stated
- Training Confidence
- high
- Residency Claim Basis
- stated
- Residency Confidence
- high
- Retention Claim Basis
- stated
- Retention Confidence
- medium
- Subprocessors Claim Basis
- stated
- Subprocessors Confidence
- medium
- Residency Class
- non-eu-only
- Portability / Exit Path
- proprietary-only
- Subprocessor Jurisdiction
- undisclosed
- Underlying model providers
- Read AI's own models
