Privacy

Short version: your audio stays on your device. We don’t have accounts, and we can’t see your files.

Your files

Converting, trimming, joining, compressing, editing, boosting, reversing and recording all happen inside your browser, using ffmpeg compiled to WebAssembly and the Web Audio API. Files are read into the page’s memory and never sent to our servers or anyone else’s. Closing the tab frees that memory.

The one exception: AI transcription

The transcribe audio to text tool can’t run a speech model in your browser, so when you press Transcribe it sends a compressed, mono copy of your audio (maximum 10 minutes) to our server, which passes it to a speech-recognition model through Vercel AI Gateway (Google Gemini transcription). The text summary feature sends the transcript text to an OpenAI model the same way. We don’t store the audio or the text, and nothing is sent until you press the button. Don’t use it for recordings you aren’t allowed to share with a third-party processor.

What’s stored in your browser

• Settings: your last output format and bitrate in the converter (localStorage key ak:convert).
• Offline cache: the audio engine and site files, so tools load instantly and work offline.

Clear AudioKit settings and offline cache

Analytics

We use Ahrefs Web Analytics to count page views. It doesn’t use cookies and doesn’t collect personal data or anything about your files.

Contact

Questions about privacy: open an issue on the project’s GitHub repository.