What happens to your data

No EchoScribe backend for AI data

There are no EchoScribe servers that receive, store, review, train on, or forward your recordings, prompts, API keys, transcripts, summaries, translations, generated images, or TTS text/audio. The public website only serves the static landing page; it is not an AI request backend.

Direct provider requests

When you choose OpenAI, Google Gemini, Anthropic Claude, xAI Grok, or ElevenLabs, EchoScribe sends the required request directly from your end device to that provider's API. When you choose Local AI, supported text and STT requests go to the endpoint you configured. The selected destination receives only the content needed for the feature you started.

Data used only for the feature you request

• Audio is used for recording, transcription, summaries, and optional dictation workflows.
• Text, shared messages, extracted webpage text, and custom prompts are used for summaries, translation, and re-processing.
• Image prompts are used to generate images through the selected image provider.
• TTS text is used to generate playable audio through the selected speech provider.

Local storage and deletion

API keys are stored locally using platform secure storage such as Android Keystore. History, transcripts, summaries, generated media, cached TTS audio, settings, and debug information are stored locally on your device so you can reuse them. You can delete history, clear app data, remove API keys, or uninstall the app to remove local EchoScribe data. Provider-side retention must be managed in the account or dashboard of the provider you used.

Recipients and third parties

EchoScribe does not sell data, use ad networks, embed tracking SDKs, or share app content with data brokers. AI content is disclosed only to the provider you selected for the action you started. Those providers process the request under their own terms, privacy policies, abuse monitoring, retention rules, and billing settings. EchoScribe cannot delete or change provider-side logs after a direct API call has been made.

Permissions and Android Accessibility

Microphone access is used only when you record. File/media access is used only for saving or sharing results where your platform requires it. The optional Android Floating Dictation feature uses Accessibility only to detect editable fields, show the floating microphone, and insert text after your approval. Password, PIN, payment, banking, credit-card, and phone fields are blocked.

Website and technical access logs

Visiting the EchoScribe website creates normal technical webserver and Cloudflare delivery/security data, such as IP address, timestamp, requested URL, user agent, TLS/security metadata, and error status. These logs are used for secure delivery, troubleshooting, abuse prevention, and server operation. Current nginx logs rotate daily and are kept for up to 14 rotations. Website logs do not contain your EchoScribe API keys or AI request contents.

Your controls and rights

You decide which provider receives a request, which API key is used, whether Pro mode is enabled, whether history/debug logging is kept locally, and when local data is deleted. Where data protection law such as the GDPR applies, you may request access, correction, deletion, restriction, portability, or objection regarding data controlled by the EchoScribe project. For data processed by OpenAI, Google, Anthropic, xAI, or ElevenLabs through their API, please contact that provider directly. For EchoScribe project and privacy questions, contact the developer using the support contact on Google Play.