Claro for IT and security
For administrators who received a request to approve Claro
Someone at your organization wants to sign in to Claro with their work account. Claro draws diagrams (architecture, process, data flow, decisions) live during meetings. This page has what a review usually starts with.
What Claro asks for
| Sign-in | Permissions |
|---|---|
| Microsoft Entra ID | openid, profile, email: sign-in and basic profile only. No access to mail, files, calendars or the directory. |
openid, email, profile | |
| GitHub | read:user, user:email; no repository or organization access |
openid, profile, email |
Claro keeps no provider tokens: it only learns who signed in. A Microsoft sign-in is identified by its tenant and object id, never by email address.
Approving it for Microsoft Entra ID
An administrator grants tenant-wide consent once, with the link in the request your colleague sent, which opens Microsoft's own consent screen (login.microsoftonline.com/<your domain>/adminconsent). You can also find Claro under Enterprise applications after anyone in your tenant has tried to sign in, and assign it to a group if you want to limit who can use it.
What is stored
- Per person: name, email address, the sign-in's id, and for Microsoft the tenant id. Usage counts (tokens, seconds, cost) per call.
- Never stored on Claro's server: meeting audio. Audio and text pass through to be processed and are not logged.
- Stored only when the user saves it: a session saved to their account (Session › Save to my account), with its transcript and diagrams, encrypted (AES-256-GCM, a key kept apart from the database, per account), until the user deletes it or their account. Otherwise diagrams and transcripts live in the user's browser.
Where it runs, and who is involved
| Company | Role | Location |
|---|---|---|
| Microsoft Azure | Hosting | West Europe |
| Turso | Database (accounts and usage) | EU |
| Anthropic | Language model (Claude) that turns the conversation into diagrams; API data not used for training, deleted within 30 days (up to 2 years if flagged by Anthropic's safety systems) | United States |
| AssemblyAI | Speech to text, when the microphone is used or a call's sound is shared; its EU data zone, whose servers aren't used for model training | European Union |
| Deepgram | Speech to text when AssemblyAI can't be reached; opted out of Deepgram's model improvement programme (audio kept only while processed) | United States |
| Stripe | Payments | EU and United States |
Traffic is HTTPS throughout. Sessions are server-side, in HttpOnly, Secure cookies.
Who makes it
Den Ouden Consultancy, Winklerlaan 363-37, 3571 KE Utrecht, the Netherlands (KvK 96007737). Questions, security reports and requests for a data processing agreement: support@denoudenconsultancy.com. Plans are personal, paid by the user. See also Privacy and Terms.