Privacy Policy — Uttir
Skip to main content
Uttir

Privacy Policy

Last updated: November 20, 2026

Uttir is built to be private by default. This policy explains what data we do and don't handle.

Your files and text stay on your device

Our tools process your input — text, files, images, and documents — entirely in your browser using JavaScript in your browser. There is no backend that receives, stores, or inspects what you type or upload, because nothing is uploaded. Closing the tab removes the data.

What we collect

We collect no usage statistics. There is no analytics script on this site, and nothing you do with a tool is measured, counted or sampled — not which tool you opened, and not how often an error happened. We do not collect file contents or tool inputs.

If you use a form — the contact page, report a bug, request a tool, or the newsletter — we keep what you typed, including your email address, so that we can reply to you and send the newsletter. Those records stay in our own storage, and the newsletter address is used for the newsletter and nothing else.

Cookies and local storage

We use your browser's local storage to remember preferences such as your theme choice, and to remember that you have already subscribed to the newsletter so the form does not ask again. These values never leave your device. We do not use tracking cookies. If advertising or analytics providers are added in the future, they will only load after consent where consent is legally required.

Third parties

The site is served through Cloudflare's content delivery network, which processes standard request metadata (such as IP addresses) as part of delivering any website. If we display ads in the future, ad providers may set their own cookies subject to your consent.

Account emails — the confirmation link when you create an API account, and the link when you ask to reset a password — are sent from our server by an email provider: Resend, or Cloudflare's own email service, whichever this account is configured with. It delivers them, and it sees the recipient address and the contents of those two messages. Nothing else is sent: your API requests, your keys and anything you type into the browser tools never go to it, or to anyone else. The email is sent from our server, so your browser does not load a script from anywhere else.

The API itself runs on Cloudflare, which is who serves this site, so nothing new sees your requests. The AI families — sentiment, similarity, transcription and background removal — are the exception worth naming: their input is sent to Cloudflare's own inference to be read. It is processed and not kept: Cloudflare does not retain it once the answer is ready, does not use it to train a model, and does not make it available to anyone else. The image-to-text family is the exception to that: it runs its engine in our own Function, so an image never leaves this server at all.

The forward family is different again: it sends your request to the provider you name — the list of providers is published in the API reference — using your own key for that provider. Whatever you send goes to them, under their privacy policy, and not to us. We add the routing and the bill. The key you send us for that provider is used for the one call and is never stored or logged.

Buying points is handled by Paddle. If you buy a balance, they are the merchant of record: their payment form takes the payment details, they issue the receipt, and they see your email address and what you bought. Your card details never reach our server — the form is theirs, and it opens on our account page only when you choose to buy: their payment script loads at that moment and nowhere else, and the browser tools load no third-party script at all. We are told which price was bought and which account to credit, and nothing else.

Contact

Questions about this policy? Contact us.