Privacy

Moonlight Reader is privacy-first. We store voices, not texts.

What we store

• Anonymous session cookie (signed, HttpOnly).
• Voice metadata (provider, provider_voice_id, optional display name).
• TTL-bound audio outputs for temporary download.

What we do not store

• No input text in our database, storage, or logs.
• No source upload files after a provider voice is created.

Text handling

Your text is processed in-memory only to synthesize audio. Logs redact text and only keep counts and timings.

Uploads and outputs

Uploads are stored in an uploads/ bucket with 1–24h TTL and deleted after voice creation. Outputs are delivered via pre-signed URLs with short expiries and auto-purged lifecycle rules.

Consent and revocation

Creating a voice requires explicit consent. You can revoke a voice at any time, which disables further TTS and revokes it with the provider.