Your voice is not our library

Dictando is operated by HolaAI. This policy covers the Dictando website, public voice demo, current iOS app, Dictando keyboard, and account features.

Privacy contact: contact@dictando.app

Audio input in the app

When you start dictation, Dictando records audio on your device and sends it through the Dictando service to Groq for transcription. If Background Voice Mode is enabled, the host app keeps the microphone ready, but audio is uploaded only after you start dictation.

Dictando does not intentionally persist raw audio on its own servers after the active request completes.

Transcript and cleaned text

Dictando sends transcript text to Groq for cleanup and formatting. Dictando does not intentionally persist the transcript or cleaned result on its own servers after returning the response. If you use in-app history, the transcript and result remain on your device until you clear them or remove the app data.

Public website voice demo

The demo records audio in your browser only after you press the recording control. It sends the recording, selected input language, and selected output language to a same-origin Dictando endpoint. Dictando sends the audio to Groq for transcription and sends the resulting transcript to Groq for cleanup or translation.

The demo processes audio and text for the active request and does not intentionally save either as a user history. It temporarily holds a network address in server memory for up to 10 minutes to enforce the demo rate limit. Hosting and security providers may also create ordinary request logs containing technical request metadata.

Account and local device data

Sign in with Apple or Google is backed by Supabase. We store authentication data needed to run your account, such as an email address, profile details provided by your sign-in method, user ID, and sessions. Dictando also stores settings, custom dictionary entries, usage stats, onboarding state, consent state, and optional dictation history on your device.

Diagnostics and service records

The current iOS build does not include a dedicated third-party advertising SDK, mobile analytics SDK, or crash-reporting SDK. Dictando and its infrastructure providers may create limited operational logs needed for security, rate limiting, debugging, and service reliability.

• Authenticate your account and keep you signed in.
• Transcribe speech, clean dictation, and provide a requested demo translation.
• Operate the keyboard companion flow and Background Voice Mode.
• Store your preferences and optional history locally on your device.
• Answer support, deletion, and data access requests.
• Secure the service, limit demo abuse, and investigate failures.

• Groq: receives audio and transcript text for transcription, cleanup, and requested demo translation.
• Supabase: handles authentication and stores account records.
• Apple and Google: provide available sign-in methods.
• Vercel: hosts the website and server endpoints and may process request metadata.
• Resend: may deliver waitlist or support-related email.

• Raw audio on Dictando systems: not intentionally retained after the active request completes.
• Transcript and result on Dictando systems: not intentionally retained after the active request completes.
• Demo rate-limit address: held in server memory for up to 10 minutes.
• Local history, dictionary, and stats: remain on your device until cleared or the app data is removed.
• Account records: remain until account deletion, subject to legal, security, billing, and fraud-prevention needs.
• Processor and infrastructure records: follow the provider terms and configurations applicable to the service.

• Revoke AI Processing Consent in the Dictando Account tab.
• Revoke microphone access in iOS Settings.
• Disable keyboard Full Access in iOS Settings.
• Clear local history and dictionary data from the app.
• Delete your account in the app or request deletion by email.
• Request access, correction, or a copy of account data by email.

See the Privacy Choices page for direct instructions.

In-app deletion starts after you confirm. It removes the server-side account and clears local dictation history, custom dictionary entries, and stats from the device where deletion was started.

If you cannot use the app, email contact@dictando.app from the address connected to the account. Limited records may remain where required for legal, security, billing, or fraud-prevention purposes.