Naven
Open Naven
Every company that handles personal information for Naven, where it is based, what it does, and exactly what it sees.
Last updated 25 September 2026A sub-processor is a company Naven uses to run the service, which handles personal information on Naven’s behalf and for nothing of its own. None of them buys data from Naven, and Naven sells data to nobody. Data is stored in the United States.
| Company | Where | What it does | What it sees |
|---|---|---|---|
| Cloudflare, Inc. | United States (servers worldwide; the database in western North America) | Hosts the site and API; stores member records, channels, uploads and signed consent forms; runs automated screening models (Workers AI) | Everything Naven stores outside Firebase, and message content at the moment it is screened |
| Google LLC — Firebase | United States (Firestore multi-region nam5) | Sign-in, and the database that holds conversations and profiles | Account records, conversations and messages |
| Groq, Inc. | United States | Automated screening, the policy review of refused messages, and Naven AI | Message content at the moment it is screened or reviewed; Naven AI questions (not for a child under 13 unless a parent allowed Naven AI) |
| OpenAI, L.L.C. | United States | A fallback for screening and Naven AI when Groq is unavailable | The same as Groq, only when it is used |
| Resend, Inc. | United States | Sends Naven’s email | Email addresses and the content of Naven’s emails |
| Agora, Inc. | United States | Carries voice and video calls. Calls are not screened or recorded by Naven | Call audio and video in transit, and connection details |
| Browser push services (Apple, Google, Mozilla, Microsoft) | Varies | Deliver notifications to a device that turned them on | An encrypted notification only the device can read |
| AgeVerif | France | Optional age verification, only for a member who chooses it | The verification itself; Naven receives only a signed yes/no and the age threshold |
| Google LLC — Analytics | United States | Counts visits to the public pages, before sign-in only | Page views and device type; nothing from inside Naven, never a signed-in account |
Changes. A school or organization with a signed agreement is told at least 30 days before a new sub-processor handles its data, and may object. Everybody else sees the change here, and in the Privacy Policy, before it takes effect.
Questions: shervin@shapoury.com.