Legal
Sub-processors
The third-party providers Breviya relies on to run the service, what each one does, the data it handles, and where it is located.
Operator
Breviya is operated by Nimavera Inc. (in formation) This page lists the third-party providers (“sub-processors”) that process personal data on our behalf to deliver Breviya. It complements the Privacy Policy and the AI Disclosure.
What a sub-processor is
A sub-processor is a company we engage to process personal data as part of running Breviya — for example to host the service, take payments, send email, or power an AI feature. We share only the data each provider needs for its specific task, under that provider's data-processing terms, and (where their API terms allow) we opt out of having your data used to train their models.
Current sub-processors
Payments and subscription billing.
Data: Name, email, billing and subscription identifiers, and transaction / entitlement events. Breviya does not store full card numbers.
AI text generation and safety moderation. Whisper is an OpenAI-created model, but Breviya routes all speech-to-text through OpenRouter, not a direct OpenAI transcription connection.
Data: Text derived from your prompts and activity; message text for crisis screening, when an OpenAI-hosted model is used.
AI gateway for configured text models and all voice-to-text transcription, including primary and fallback models. Requests also reach the selected downstream model host.
Data: Text prompts and responses; audio and transcripts for voice reflections, Companion voice turns and separately opted-in Voice Anchor transcription. Turning off voice transcription in Privacy blocks new transcription requests, not deletion of existing recordings.
Runs the selected speech model. Current defaults: OpenAI-created Whisper large-v3-turbo (available through Groq and DeepInfra), with xAI Grok STT as the availability fallback. Groq and Grok are different services. OpenRouter selects the model host; its transcription endpoint does not support pinning a host with per-request routing controls.
Data: The audio submitted for transcription and its resulting text. Processing and retention depend on the selected host and applicable account terms; Breviya does not promise zero third-party retention for transcription.
Image generation for illustrated storyboard scenes.
Data: Only the short text prompt for a scene. Your journal or reflection content is not sent.
Transactional and digest email delivery.
Data: Your email address and the content of the emails we send you.
Hosting infrastructure — runs the Breviya application servers, database, object storage, and job queues (VPS).
Data: All account data, at rest on Breviya-managed servers, plus the standard connection and access logs generated by serving requests, which include IP addresses.
The database, object storage, in-memory cache, and text-to-speech narration run on Breviya's own infrastructure rather than a separate third party. Push notifications, when you enable them, are delivered through your browser's own push service (operated by your browser or device vendor), which is not a contracted sub-processor.
International transfers
Most sub-processors above are established in the United States. For transfers of personal data from the EEA, the United Kingdom, or Switzerland, we rely on the European Commission's Standard Contractual Clauses (SCCs), the UK Addendum, and the EU-U.S. Data Privacy Framework where the provider is certified, supplemented by appropriate technical and organisational safeguards. See the Privacy Policy for detail.
Changes and notice
We may add or replace sub-processors as the product evolves. When we do, we will update this page and its “Last updated” date. If you would like to be notified in advance of a new sub-processor that handles your personal data, or to raise an objection, contact privacy@breviya.com.
On this page
Last updated September 4, 2026