Privacy policy

Effective from 5 November 2026.

Who controls your data

The controller of your personal data is Matěj Wernisch, registered office Sokolská 1883/8, Prague 2, Czech Republic, company ID 29519641, registered in the Czech trade register. For anything about your data, write to hello@anyutil.io.

Files and text you put into the tools

Most tools work entirely in your browser: the file is never uploaded and we never learn what is in it. That holds for the calculators, QR codes, text work and most PDF and image editing.

With the tools that have to compute on the server (PDF compression, conversion to Word, background removal, transcription, the AI tools), we process the file or text and delete it immediately. We do not store it, do not back it up and do not use it to train models. On every such tool this is stated next to the button.

The tools that use a language model send the entered text through our server to the API of Anthropic (USA, under standard contractual clauses). Anthropic does not use the text to train its models and keeps it only briefly, for at most 30 days, to detect abuse; longer only if its checks flag the text as a breach of its usage policies.

The server voices of the Text to speech tool and the voice-over in the video editor are computed by Microsoft's Azure AI Speech in a data centre in the EU, as our processor under a data processing agreement. Microsoft stores neither the text nor the resulting audio and does not use them to train models. The Piper voices run entirely in your browser; the first time, they only download the voice model from Hugging Face (USA), which thereby sees your IP address and browser details, but not the text.

What stays with us when you ask for it

Some features store data on our server because you ask them to:

Projects and sharing: documents saved from the editors and their versions. A shared document can be seen by anyone who has the link.
Forms: the forms you create and the answers people submit. The form's author is responsible for the answers; we only keep them on their behalf.
Invoicing: your billing details, client list and invoices. We process your clients' details on your behalf, as a processor.
Secret messages: only the encrypted content. The key sits in the part of the link after the # sign, which is never sent to the server, so we cannot read the message. It is deleted once read or when it expires.
Dynamic QR codes: the target address and the daily number of scans, with nothing about who scanned the code.
Teams: the emails of invited people and who is on the team.
Tool ratings: the stars and a comment, if you write one.

You can delete all of it yourself, and it goes when the account is deleted too.

Operational record of tool usage

So we know which tools are worth developing, we keep one row per use of a tool: which tool it was, when, which of our two sites it came from, how long you had it open and a two-letter country code. We do not store IP addresses.

For people without an account the row carries the random identifier from a cookie (see below), which daily limits are counted by. After 60 days we remove it from the row and only an anonymous record for totals remains. For signed-in people the row is tied to the account, because the account's limits are counted from it. Deleting the account deletes these records too.

Account

When you create an account we keep your name, email, chosen plan, favourite tools, saved presets and records of using tools that have a daily limit. All of it is in your account overview, and from there the account and all its data can be deleted for good at any time. We may close an account that has been unused for more than two years and has no subscription; we email you first.

If you sign in with Google or Microsoft, all we receive from them is your name, email and profile picture address; no password is ever created with us in that case. Their sign-in page loads only after you click the button; they learn that you are signing in to us and follow their own privacy policies.

Payments

Subscriptions and day passes are handled by Stripe. Card numbers never reach us; we only know that a payment went through and the details needed to issue a document. Stripe also processes some of the data as an independent controller, for example to prevent fraud. Tax documents have to be kept for 10 years by law, including after an account is deleted.

Contact form and emails

A message from the contact form (name, email and text) reaches us by email, and we keep it for as long as it takes to deal with the request and any follow-up. The form is protected from bots by Cloudflare's Turnstile, which loads only on the contact page and processes the IP address and technical browser data when the form is submitted (USA, standard contractual clauses). It is used only to tell a person from a bot.

We only send operational emails: address verification, password resets, order confirmations, team invitations and replies to your messages. We send no marketing newsletters.

Analytics without a cookie banner

We measure traffic with our own Umami running on our server. It stores no cookies or other data on your device, builds no profiles and does not follow you across sites. All it keeps from a visit is an anonymous summary: the page address without parameters, where you came from, the device type and the country. It uses the IP address only at the moment of the visit, to work out the country and to tell visits apart, and does not store it.

There are no third-party advertising or tracking scripts here, and we pass the measurement data to nobody.

Server logs

Like any web server, ours keeps a log of requests: IP address, time, page address and browser details. It is used only for security and fixing errors, contains no file content, and we delete it after 30 days at the latest.

Cookies and browser storage

Under the ePrivacy rules, consent is required for storing or reading data on your device unless it is necessary for a service you asked for yourself. We only store such data:

The sign-in cookie: only for signed-in users, it holds the session.
The XSRF-TOKEN security cookie: it protects forms against forged requests from other sites.
A signed cookie with a random identifier: it counts daily limits for people without an account. It contains no name or other detail about you.
Browser storage: the site's appearance, tool presets and models the tools download (such as the Piper voices), so they need not download again.

None of it is used for tracking or advertising, so neither consent nor a cookie banner is needed.

Why we process data

Performance of a contract (Art. 6(1)(b) GDPR): the account, the tools you run, saved projects, forms and invoices, subscriptions and the emails that go with them.
Legal obligation (Art. 6(1)(c)): keeping tax documents, handling complaints and withdrawals, handling notices of illegal content under the Digital Services Act.
Legitimate interest (Art. 6(1)(f)): analytics, the operational record and limits against abuse, server logs, protecting the contact form from bots and replying to your messages.

An account cannot be created without an email, because we use it to verify the account and reset the password. Otherwise you do not have to give us any data; most tools work without an account. We carry out no automated decision-making or profiling.

How long we keep data

The account and everything saved in it: until you delete it; an unused account for at most two years.
The guest identifier in the operational record: 60 days.
Server logs: 30 days at most.
Tax documents: 10 years, including after the account is deleted.
Contact form messages: for as long as the request and follow-up take.
Notices of illegal content (including the notifier's email) and decisions on them: until handled, then six more months for any complaint against the decision.

Who receives data

Hostinger International Ltd.: server, database and backups in Germany.
Spacemail (Hostinger): sending emails, EU.
Stripe Payments Europe, Ltd.: payments, Ireland, with part of the processing in the USA under standard contractual clauses.
Anthropic, PBC: text from the tools that use a language model, USA, standard contractual clauses.
Microsoft Ireland Operations Ltd.: the server voices (Azure AI Speech, EU) as a processor; sign-in with Microsoft if you choose it.
Google: sign-in with Google if you choose it.
Cloudflare, Inc.: protecting the contact form, USA, standard contractual clauses.
Hugging Face, Inc.: Piper voice models downloaded straight to your browser, USA.

Otherwise we pass data only to authorities where the law requires it.

Your rights

You have the right to access your data, correct it, delete it, restrict its processing and port it. Most of this you can do yourself in the account overview; otherwise write to us and we will reply within 30 days.

The right to object. You can object at any time to processing based on legitimate interest (analytics, the operational record, server logs). We then stop it unless we have compelling grounds, such as protecting the service from an attack.

You can lodge a complaint with the Czech Office for Personal Data Protection (uoou.gov.cz) or with the supervisory authority in your country of residence.

Details for businesses

The exact list of tools that compute on the server is on where your data is processed. If you process your clients' data through the tools, the data processing agreement with its list of sub-processors belongs with it. The technical measures are described on Security.