Read AI
Read AI · Meeting notes · US · www.read.ai
services/read-ai.yamlVendor data-handling terms
The privacy overview page states "Contributing to model improvement is off by default"; the policy itself ties training to account settings.
“Provide, maintain, and improve (consistent with your account settings) our Services, including maintaining user accounts with us and using information to train and improve our models within our Services; / We do not, and do not permit third party AI tools to, use user data collected via Google Workspace APIs to develop, improve, or train generalized/non-personalized AI and/or ML models.”
“If you wish to delete your account, review the “ How to Delete My Account” instruction or email us at privacy@read.ai with your account information, but note that we may retain certain information as required by law or for our legitimate business purposes.”
“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.”
Domains and endpoints
observed means seen in Unseen deployments; vendor-documented means listed by the vendor. Vendors do not publish complete lists.
| Host | Role | Source |
|---|---|---|
| api.read.ai | api | observed |
| read.ai | app | observed |
Assessment
Reasoning: A meeting bot with engagement analytics. Training on meeting content is controlled by an account setting that the vendor says defaults to off, Google data is protected, and participants get notice and an opt-out. US processing and no retention period keep it at medium.
Flags: Training controlled by an account setting · US processing · Retention period not stated · Assessed 2026-09-16. The assessment is Unseen's; the terms above are the vendor's.
Changelog
- 2026-09-16Documented. Training, deletion and transfer terms verified against the Read AI privacy policy.
- 2026-09-15Listed from the Unseen catalogue with observed domains.
Corrections
Pull request on GitHub, or the form below. Changes are reviewed and recorded in the changelog.