Privacy

Last updated October 2026.

This page is short because the honest answer is short: this site is built so that we handle as little of your data as possible.

Your files

Your files are never uploaded — everything runs on your device. Every tool reads and processes your audio, video, images, documents and text entirely inside your browser. They are not sent to us or to anyone else, and we could not access them if we wanted to. Results exist only in your browser tab and in files you choose to download.

Accounts

There are no accounts and no passwords.

Reports, feedback and requests

Your files are never uploaded. Every tool runs on your device, and nothing in this section changes that. What follows is the small amount of information you can choose to send us when you rate a result, report a problem, vote or suggest a tool — and only when you press the button that sends it.

We never collect your files, your results, file names, or any text, audio or image from them. A report form never asks for them. If you want to send us a file that fails, email it — that is a separate, deliberate choice.
A rating Exactly which fields The tool, the site build and your answer (Great). The server answers with a random ID for that one vote, kept only in your open tab, so the vote can be undone. Why To see which tools work well and which don’t. How long 12 months, then counted totals only.
Run details Exactly which fields Only if “Attach” is on — exactly the fields shown before you send: model and version, the engine used and any fallback, GPU vendor and architecture, number of cores, device memory as the browser reports it, browser and operating system family, timings and how much of the media was processed, the input’s kind, length band, format, file size and file type, your settings (for a cloned voice: how long your recording was, as a band like 10–20 seconds — never the recording), the error type, the step it happened in and the error’s name (never its message), and the last 20 lines of the tool’s log. Why To reproduce a problem on similar hardware and fix it. How long 12 months, then combined into counts per tool, engine and GPU family.
Your note Exactly which fields Up to 500 characters. Email addresses, phone numbers, web addresses and long numbers are removed in your browser before sending, and again on our server. Why To understand what the fields can’t say. How long 12 months, or 90 days after the fix is in the changelog, whichever comes first.
Requests and votes Exactly which fields The request text, public once we have checked it. A vote is a random ID kept in your browser, so you can vote once per browser; we store it only scrambled together with the request, so your votes on different requests cannot be linked. Why To decide what to build next. How long For as long as the request is listed. A suggestion that never makes the list is deleted after 12 months.
IP address Exactly which fields Passes through Cloudflare and Turnstile while a form is sent. We do not store it. Why To stop spam and abuse. How long Not stored by us.

Where it’s kept, and who handles it

Reports, ratings, requests and votes are stored in a Cloudflare D1 database located in the EU. Cloudflare also hosts the site and runs Turnstile, the check that keeps bots off the forms. There are no accounts and no tracking cookies in any of this.

Your choices

Run details are attached only while Attach is switched on, and you see every field before you send. To have a report deleted, email hello@yourdevice.app with its code (for example YD-7K3Q) and we remove it within 30 days.

The legal part

We rely on your consent — given by pressing Send, Great or Vote — for everything above, and on our legitimate interest in stopping abuse for the IP address passing through. You can withdraw consent at any time, as easily as you gave it. You also have the right to see, correct and delete what we hold, and to complain to the Danish Data Protection Agency (Datatilsynet).

Model downloads

A tool's model is fetched once and cached by your browser. Like any file download, that request exposes your IP address to the server that serves the model files — nothing about your files is included in it.

Analytics

We use Cloudflare Web Analytics to see aggregate traffic — page views, referrers, rough location and device type. It is cookieless, collects no personal data, and does not track you across sites or build a profile. It never sees the contents of your files, which are processed entirely in your browser and never uploaded. If we ever add another analytics or advertising tool, we will name it here before it ships.

Run outcomes

When a tool with a run receipt finishes, your browser sends us one line saying how the run ended. It has exactly four fields: the tool, the site build, the outcome (for example ok or decode_failed_empty) and the backend it ran on (WebGPU, WebNN or WASM). Nothing else: no file, file name or text, no device details, no timings, and no ID that links one run to another or to you. We use it to see whether a fix worked, because problem reports alone are too rare to tell. The lines are kept in Cloudflare Workers Analytics Engine for three months. Sending one passes your IP address through Cloudflare, as loading a page does, but it is not written down. If your browser sends Global Privacy Control, the line is not sent. We rely on our legitimate interest in keeping the tools working.

Advertising

The site is planned to be ad-supported — that is what keeps the tool free. Ads may involve third-party cookies and their own data practices; when ads ship, this page will describe the provider and a consent banner will be in place where the law requires one. Whatever the ad setup, it never touches your files: those stay on your device, full stop.

Questions

Ask us — contact details are on the about page.