Privacy

Last updated 25 August 2026.

Most conversions never leave your device. When a file can be converted in your browser — which is the default, and covers images, documents, data files, PDFs and archives — it is read, converted and saved entirely on your own machine. It is never uploaded, so there is nothing for us to store, read, or lose.

When a file is uploaded, and when it is not

A file is only ever sent to our servers in three situations, and the interface tells you which one you are in before it happens:

• Your device cannot do it. Some conversions need more memory than a phone has, or a decoder browsers do not ship.
• You saved it to your library. Storing a file is the point of storing a file.
• It arrived through the API. An automated client has no browser to run the conversion in.

Everything else stays local. If you convert an image and download it, no part of that file ever reaches us.

How long an uploaded file is kept

• Signed out: files are not stored at all.
• Free account: deleted 24 hours after upload.
• Premium: kept until you delete them.

Deletion is done by a scheduled sweep that removes the stored bytes and records that it did. Deleting your account removes your files with it.

What we measure

Analytics are first-party — no Google Analytics, no third-party tracker, nothing sold or shared. What a conversion records is:

• The format converted from and to, as registry identifiers.
• A size bucket, not a size — enough to tell a photo from a video.
• How long it took, and whether it ran locally or on a server.
• An error code when something failed.

Filenames are never recorded, and content is never read. Individual events are aggregated into daily totals and the raw rows are deleted after 90 days.

Your account

If you create one, we store your email address, a hash of your password (never the password), and — if you signed in with Google, Apple or GitHub — the identifier that provider gives us. We do not receive your password from them, and we do not ask them for anything beyond your email address.

Payments

Payments are processed by Stripe. Card details are entered on Stripe's own systems and never reach ours: we store a customer identifier, what you are subscribed to, and whether it is paid. Stripe's handling of your payment data is governed by their privacy policy.

Advertising

The free tier is paid for by advertising, served by Google AdSense. Ads never appear on a paid plan.

Where consent is required by law, it is collected through a Google-certified consent dialog before any personalised advertising is served. Until you consent, and if you decline, ads are non-personalised — they still appear, they are simply not based on a profile of you. Google's use of the data it collects through its ads is described in its own policies.

Cookies and local storage

• Signing in sets a session cookie. Without it we cannot tell it is still you between pages.
• Your preferences — theme, saved presets — are kept in your browser's own storage and never sent to us.
• Advertising and consent cookies are set by Google and by the consent dialog, and are governed by your choice in it.

There is no cookie here that exists to follow you elsewhere.

Automated clients

Files submitted through the API are stored for as long as the plan on the API key allows, and are subject to the same sweep. API request metadata is recorded on the same aggregate basis as everything else.

Your rights

You can export your library, delete individual files, or delete your account and everything attached to it, from your account page. If you would rather ask us to do it, or want a copy of what we hold, get in touch from the support page and we will answer within 30 days.

Changes

If this policy changes in a way that affects what we collect or how long we keep it, the date at the top changes and the change is described here. It will not change retroactively for files already uploaded.