Last updated 22 August 2026
Sub-processors
Roger is run by a small team, with a small number of service providers doing the specialised parts. These are all of them, what each one does, and where it operates.
Each is engaged under contract to process data only on our instructions. They are service providers, not partners we sell data to — we do not sell your data and do not use it for advertising.
| Purpose | Provider | Where |
|---|---|---|
| Account, database, audio storageHolds your account, transcripts and encrypted audio. | Supabase | India (Mumbai) |
| Application serversRuns the API that processes a recording. | Render | Singapore |
| Speech-to-textThe primary transcription path. Indian languages included. | Sarvam AI | India |
| Speech-to-text (fallback only)Used only when the primary provider is unavailable. | AssemblyAI | United States |
| Summaries, to-dos, Ask AIRoutes the transcript to the language model that writes your summary. | OpenRouter | United States |
| Push notificationsDelivers notifications. Carries no transcript content. | Firebase (Google) | United States |
Processing outside India
As the table shows, some processing happens outside India — application servers in Singapore, and the AI summarisation and push-notification providers in the United States. Your audio and transcripts are therefore processed outside India in some circumstances. If that is not acceptable to you, please do not use Roger.
The primary speech-to-text path runs in India. The United States fallback is used only when the primary provider is unavailable.
Changes to this list
We update this page when a provider changes, and the date at the top reflects the last change. If a change materially affects how your data is handled, we will also tell you in the app before it takes effect, as described in section 10 of the privacy policy.
Questions
Email neel@miraiminds.co — for a question about any provider here, or to exercise any right in section 8 of the privacy policy.
← Back to the privacy policy