Privacy
Your files never leave this computer — video or image, whichever you brought. They are never uploaded, and there is no server that could receive them; the conversion runs on your own GPU, in this tab.
The hardware report
This site sends two things, and only two. The first is a short report about what your graphics hardware can do. That is the whole of the report, and here is every field; the second thing is an email address, if you type one into the waitlist form, and it has a section of its own below. Beside those two, every request your browser makes to this site, page loads included, carries your IP address and browser details, as a request to any website does, and Vercel, the host that serves the site, receives them. They are processed on the basis of our legitimate interest in serving the site and keeping it secure.
It is sent only from the converter, once per visit, after a notice on that page: when you choose a file, or 20 seconds after the notice appears, whichever comes first. The notice has a “Don’t send” button. Pressing it stores one setting in this browser, acuta.hardware-report, which records only that you said no; while it is there, the report isn’t sent. If that report was sent and you then run an export, one more report with the measured speed is sent when the first export of the visit finishes; later exports in the same visit send nothing. No other page sends a report.
| Field | What it means |
|---|---|
ok | Whether the check passed on this machine |
gpuFailureCode | If it failed, which of four known reasons it was |
webgpu | Whether the browser exposes WebGPU at all |
adapterVendor | Your graphics chip’s maker, e.g. apple, amd, intel |
adapterArchitecture | Its architecture family, e.g. metal-3, rdna-1 |
adapterDescription | The driver’s own description of the chip |
shaderF16 | Whether the chip supports the half-precision maths the model needs |
features | Which optional WebGPU features the chip offers — the whole list your browser reports, which grows as browsers add new ones |
limits | The chip’s size limits, such as the largest buffer it allows — whichever limits your browser reports |
encoders | Which video encoders worked here, and the sizes each was tried at — the whole list, which grows as browsers add codecs |
decoders | Which video decoders worked here — the whole list, which grows as browsers add codecs |
maxSizeClass | The largest output this machine can render |
budgetBytes | How much graphics memory the tile plan was given |
storageQuotaBytes | How much disk the browser allows this site, rounded to the nearest gigabyte |
msPerFrame | How long one frame took, if a conversion was run |
userAgent | Your browser’s version string |
No filenames. No file paths. No frames of your video, and no pixels of your images. No cookies, no login. The report mints no identifier for you — nothing in it is a random value, a timestamp, or a counter added to single you out — and we never join one report to another. An email address is an identifier; that is the one thing here you hand over deliberately, and the section below says where it goes.
That is a claim about what we do, not a claim about what the data allows. The report does carry your graphics chip’s vendor, architecture and driver description, the WebGPU features and limits it exposes, and your browser’s version string, and for an unusual combination of those that tuple can be close to unique — most visitors share theirs with everyone who owns the same hardware and browser, but an unusual machine could be recognisable across two visits a week apart.
Two details are stated plainly because they are true and checked: storageQuotaBytes is rounded to the nearest gigabyte rather than sent exactly, and the one adapter field the probe collects but never sends is dropped before the report leaves your browser. The request itself is sent with credentials omitted, so no cookie rides along with it — verified in a real browser against a cookie planted for the purpose.
Why collect anything at all
The same conversion runs 91 times slower on the slowest machine we have measured than on the fastest, in an eleven-machine sweep dated 2026-09-12/13. Knowing which hardware is which is how the tool learns to tell you the truth about your own.
Not one compatibility failure across those eleven machines: every one of them reported ready and produced correct output. The risk this project has found so far is speed, not support — and some of them are slow enough that “supported” and “usable” are different answers, which is why the converter checks your own machine before you choose a file. The one machine that failed outright had hardware acceleration switched off in the browser, and worked once it was enabled; that is by far the commonest failure, more than missing hardware. Firefox is untested and expected to fail on WebGPU, so none of this generalises to “any browser”.
We send the hardware report on the basis of our legitimate interest in knowing which machines can run the converter, and how fast, so the tool and the hardware page tell people the truth about theirs. We think that interest is fair to you because the report carries no filenames, pixels, cookies or identifier we add, and we never join one report to another. The converter shows a notice before the report is sent, with a “Don’t send” button that stops it from this browser. You can also object by email, and because a report can’t be traced back to you once it is sent, the way we honour that is by the deletion period set out below.
The second thing: your email address, if you type one
There is one form on this site — the extension waitlist. It appears on the home page, on the extension page, and in three places on the converter: the result card, the notice about longer videos, and the page shown when this browser can’t run it. It is the only thing here that asks you for anything. No address is sent unless you type one into it and submit it: leave the form alone and there is nothing to send.
Here is everything that is stored, and there is nothing else: the address itself; one word recording which of those forms you used, one of home, extension, result, cap or blocked; and the time the request arrived. It is written to a private object in Vercel Blob, stored privately rather than at a public URL so it cannot be read by guessing one, and to a contact in a mailing list at Resend, the service that would send the email. The hardware report above carries nothing from this, and this carries nothing from it — separate requests to separate endpoints, separate objects, and no shared identifier in either record.
We keep your address because you asked us to: your consent, given when you submit the form. You can withdraw it at any time by asking us to remove the address, as the section on removing it below explains; that stops us using it from then on.
You will get no confirmation email, and that is a decision rather than an oversight: the only verified sending domain on this account belongs to a different product, and this one has no hostname of its own yet. Sending from another product’s brand, or from a generic provider address, would both be worse than sending nothing. So nothing arrives until there is something to say — one email, when the extension ships.
How long it’s kept
Your address is kept until 30 days after the one email announcing the extension, or until you ask us to remove it, whichever comes first. Hardware reports are kept for 12 months, then deleted. In your own browser, this site keeps four things, none of which is sent anywhere: the setting acuta.hardware-report, only if you press “Don’t send”, until you clear this site’s data or press “Send reports again”; the comparison view you last chose on the converter (acuta.convert.comparator), which the browser discards when the tab closes; an export’s working files, which the converter deletes when the export ends, or the next time you open the converter if the tab was closed first; and the finished file, until you next open the converter or start another export.
Remove your address
Email support@acuta.app from the address you signed up with and ask for it to be removed; we delete it from both places it is stored within 30 days and reply to confirm.
Hardware reports carry nothing that names you or links a report to you, so one person’s report can’t be found to remove it; they are deleted when the period above ends.
Who runs this
This site and the Acuta extension are run by r7ai LLC, doing business as Acuta, who decides what is collected and why. Email support@acuta.app about anything on this page, to ask what is held about you, or for help with the converter or the extension.
Two services handle this data for us, and both are in the United States: Vercel, which hosts the site and stores the hardware reports and waitlist addresses, and Resend, which holds the mailing list. Both are certified under the EU–US Data Privacy Framework and its UK Extension, which is what makes sending your data to them lawful under European and UK law; Resend’s contract with us also includes the European Commission’s standard contractual clauses. We are in the United States too.
If you think your data has been handled wrongly, you can complain to a data-protection authority, such as the one in the country where you live.
The browser extension is different
Nothing you process is ever uploaded — your video, the model and every frame stay on your machine, and it sends no hardware report. The extension makes network requests in exactly three cases: downloading a video you asked it to fetch, from a site you granted access to; fetching the preview image a page shows for a video, while you let Acuta read the pages you visit; and connecting to an agent running on your own computer, only while you have agent access switched on. This page describes the website only.