Privacy

Last updated: 7 September 2026

Narrator provides narration and transcription for Obsidian and API clients. This notice explains what happens to your information when you use the plugin, website or API.

Who operates Narrator

Narrator is operated by Corrin Data and Systems under the Corrin AI brand. Corrin AI is a trademark of Corrin Data and Systems. For privacy questions or requests about your data, email [email protected].

Your notes and audio

Narrator is a cloud service. Text you choose to narrate, including script sections, is sent to our API and speech workers. Microphone audio is streamed to those workers for transcription, and the resulting text is returned to you. The plugin does not upload your entire vault as part of these speech requests.

The Narrator API does not maintain a library of your submitted notes, scripts, recordings, generated audio or transcripts. These are processed to answer your request. The current speech-worker configuration does not enable content recording. Diagnostic errors may contain details returned by an upstream service; this is distinct from deliberately recording speech sessions.

Audio and text saved by the Obsidian plugin remain in your vault. Any backup or sync service you use for your vault has its own data practices.

Account and usage records

We store account identifiers, a hash of your API key, plan and subscription status, billing-period dates, narration word usage, transcription duration and payment-provider references. These records provide access, enforce allowances, recover keys in the original browser and handle billing. We do not store your payment-card details in the Narrator database; Stripe handles payment information.

Free signup also stores a hashed browser-recovery proof and a keyed hash derived from your network address to limit signup abuse. This is a pseudonymous identifier, not anonymous data. If you submit an email address to an interest form or contact us, we receive that information too.

Cookies and local settings

Necessary browser cookies support checkout and same-browser key recovery. The checkout cookie lasts up to 24 hours and the free-account recovery cookie up to one year, unless removed earlier. Removing the recovery cookie can prevent you from retrieving your key, so save it securely. Plugin API keys and preferences are stored in your local Obsidian configuration.

Service providers

• Railway hosts the API and account database and processes hosting and diagnostic data.
• Runpod hosts the speech workers that process narration text and microphone audio.
• Stripe processes payments, subscriptions and billing-portal activity.
• OpenRouter and your selected model provider process text when you use optional AI script generation or formatting. Their handling and retention depend on the provider and settings; using speech alone does not require this feature.

These providers may process information outside your country. Their services, locations and data-protection terms apply to that processing. We do not offer a guarantee that processing stays in one particular country.

The landing page and documentation also load fonts from Google Fonts and styling from the Tailwind CDN. Those services receive ordinary browser connection information when these assets load.

Diagnostics and retention

Operational logs help diagnose failures and measure performance. They can include request paths, timestamps, response codes, durations, connection information, voice/model identifiers and error details. Infrastructure providers may also process network addresses. Narrator redacts API-key query parameters in its Uvicorn access logs, but this does not mean every provider log is anonymous.

Hosting logs follow the providers’ retention settings. Account, billing, signup and usage records do not currently have an automatic deletion schedule. They remain until removed as part of account administration or a deletion request, subject to records needed for payment disputes, abuse prevention or applicable obligations. Deletion from active systems does not necessarily immediately remove provider backups or payment records.

Your choices and requests

You choose which text to send and when to start microphone recording. You can stop recording in the plugin or demo. Contact us to ask about your information or request access, correction or deletion. We may need to verify ownership before acting. Never send your full API key in a public issue or message.

We use service and account information to deliver the service you request, billing information to administer payments, and limited operational information to maintain reliability and prevent abuse. Where applicable, you may also have rights to object, restrict processing or complain to your local data-protection authority. Billing records may need to be retained after cancellation or deletion of other account data.