Privacy Policy

Last updated: May 31, 2026

aloud is built to be private, and to give you a choice about where your data goes. You can run it locally with your own providers, so nothing touches us at all; or you can use aloud server, our optional hosted service that connects you to AI and voice providers without us keeping your sessions. This policy explains, plainly, what happens to your data in each case.

The short version

Two ways to use aloud

What aloud processes, and where it goes

Your voice

Your microphone audio is used to transcribe what you say into text. In local mode, transcription runs on your device where supported and the audio is not sent anywhere. With aloud server, your audio is relayed through our service to a speech-to-text provider to transcribe it, then discarded. We don't record your audio, and we don't store it.

Your words and the AI facilitator

To generate responses, aloud sends your transcribed messages and the conversation so far to a language-model provider:

Spoken responses

Facilitator responses are turned into speech. Depending on your setup this happens on your device (system voices), via a cloud voice service you connect, or via aloud server, which relays the response text to a text-to-speech provider. We don't store the audio or text.

Saved sessions

aloud can save your session transcripts and a short summary locally on your device so you can revisit them. They stay on your device unless you choose to export or share them. There is no cloud sync, and aloud server does not store your transcripts or summaries.

App updates

aloud may check for new versions (a basic network request that does not include your session content).

aloud server: accounts, credits, and what we keep

If you use aloud server, we process a limited amount of information to run the service. None of it includes the content of your sessions.

We don't retain the content of your sessions on aloud server. None of it. Your audio, your words, and the AI's responses pass through only to reach the providers that fulfill them; nothing is stored on our side afterward.

Your own API keys

On some platforms you can supply your own provider API keys instead of using credits. On local platforms those keys stay on your device. On the web app, where requests must be relayed through aloud server, your key is sent to our server and used only transiently, in memory, to make the request to your provider. We don't store it, and we don't log it.

What we don't do

Third-party services

Whenever your content is processed by an AI or voice provider, whether you connect it yourself or aloud server relays to it, that provider handles your data under its own privacy policy and terms. Please review the policy of whichever provider applies; aloud is not responsible for how third parties handle data sent to them.

When you use aloud server, we aim to be transparent about which providers we rely on. We currently use providers such as Anthropic, OpenAI, OpenRouter, Venice, and Groq for language models, and dedicated speech-to-text and text-to-speech providers for transcription and voice; payments are handled by a third-party payment processor. We'll keep this list current as our providers change.

Your control

Children's privacy

aloud is not directed to children under 13 (or the minimum age in your jurisdiction), and we do not knowingly collect information from them.

Changes to this policy

We may update this policy from time to time; the "last updated" date above will change. Significant changes will be reflected here.

Contact

Questions about privacy, or want your account data deleted? Email lexkrusz@gmail.com.