Skip to content
EditFlip

Privacy Policy

Last updated November 16, 2026

This policy explains what EditFlip stores, why, where, and for how long. The short version: the files you open are processed by your own browser and are never uploaded to us. An account is optional; if you make one, we keep your email address, your favourite tools and a list of what you did with the tools (never your files or their names). Every finished result is also counted in anonymous daily statistics. There are no advertising cookies and no trackers. The controller is the person named in the legal notice; write to hello@editflip.com for anything in this policy.

Your files stay on your device

When you open a PDF, a Word document, a spreadsheet or a photo, your browser reads it from your device and every tool works on it there: merging, compressing, converting, editing, removing a background, reading text from a scan. The website never sends your files, their contents or their names to our servers or to anyone else, whether you are signed in or not. The pages download what the tools need from editflip.com itself (fonts, the PDF and OCR engines, and small AI models); the only other requests are the small messages described below (sign-in, your account and the statistics), Google’s sign-in when you use it, and, if it is switched on, Cloudflare Web Analytics. The site’s security policy tells your browser to refuse any other destination.

The Scan tool uses your camera only while the scanner is open and only after your browser asks you for permission; the frames and the pages it makes stay on your device.

If you make an account

You can use every tool without an account. If you sign in, with Google or with a one-time code sent to your email address, we keep:

  • Your sign-in, in Firebase Authentication: an account id, your email address and, with Google, your Google account id, name and profile photo as Google provides them, the way you signed in, and when the account was made and last signed in to. With an email code the account is made for the mailbox’s own address (for example without a “+tag”). We never receive your Google password.
  • Your profile: your email address, name and photo (from Google), when the account was made and last used, how many results you have made, and the tools you starred as favourites, so they are shown first.
  • Your tool history: your last 100 results, each with the action (for example “Merge PDF” or “Convert PDF → Word”), the kind of file that went in and came out (PDF, JPG, Word…), how many files, their total size in bytes, how long it took and when. Never a file name, never anything from inside a file. You see it under Tool history in the menu.
  • Sign-in codes: when you ask for a code we send it by email and keep, for its 10 minutes, a keyed hash of the code (never the code itself), an encrypted sign-in ticket for that address and a keyed hash of your IP address, so a code can only be replaced from the connection that asked for it. The record is deleted as soon as the code is used or has been entered wrongly five times.

We, as operator, can see the accounts and their tool history in order to run the Service and handle misuse; if an account breaks the Terms we may suspend it and keep the reason with it. You can delete your account at any time from the account menu (Delete account): that deletes your sign-in, your profile, your favourites and your tool history at once and for good. Only the anonymous daily counters below stay, because they hold nothing about you.

Statistics

Every time a tool finishes a result (a save from the editor, a conversion, a merge…), the page sends us a short message with the action, the kinds of file in and out, how many files, their total size in bytes and how long it took. This happens for everyone, signed in or not. We add it to counters per day and per action (for example “Compress PDF: 120 results, 340 files, 1.2 GB today”), which also count how many results came from signed-in and from anonymous visitors, and how many accounts were made that day. For a signed-in visitor the same result goes into their own tool history, as described above. For an anonymous visitor nothing is kept that could tell who they are: no account, no device id, no cookie. To stop floods, each message is counted against a short-lived rate-limit counter whose name is a hash of your IP address (the address itself is not stored); it only counts within its hour.

The site may also use Cloudflare Web Analytics to count how many pages are viewed. It sets no cookies, builds no profile of anyone and gives us only aggregated figures: page views and, in total, the visitors’ countries, device types and the sites they came from. Neither of these ever sees your files.

Cookies and what is kept in your browser

EditFlip sets no cookies of its own and uses no advertising or analytics cookies, so there is no cookie banner. Your browser keeps a few things on this device, all needed for features you use:

  • Your sign-in, if you sign in: Firebase Authentication keeps it in your browser’s IndexedDB storage (or, where that is not available, in local or session storage), so you stay signed in; signing out removes it. A copy of your profile photo address and initial is kept in local storage so the header shows it at once. When you ask for an email code, the address it went to is kept in local storage for the code’s 10 minutes, so a page that reloads while you read the email still knows it. If Google’s window has to take the whole tab, a one-word flag is kept in session storage until you come back. Signing in with Google opens Google’s own window, where Google may use its cookies on google.com, under Google’s privacy policy.
  • Unfinished work, in your browser’s IndexedDB storage: the step you were on and the files you had open, and what you changed in the editor but did not save yet, so a refresh or coming back later finds them. Each tool page keeps its own. They never leave your device and are not part of your account. After 24 hours they are no longer offered; they are replaced by your next work on that page, removed when you close the file with ✕ or delete it, and you can remove them at any time by clearing this site’s data in your browser. In a private window they go when the window closes.
  • Small settings, in local storage: light or dark theme, the last pen and text style you used in the editor, and whether you have already seen the scanner’s tips.
  • One flag for a few seconds, in session storage, when a page fails to load, so it is reloaded once and not in a loop.

What a saved file carries

When you save a PDF or a photo from the editor, and the file you started from is 10 MB or smaller, EditFlip puts that starting file and the things you added (text, drawings, lines) inside the saved file, so that opening it again in EditFlip lets you move or change them. Other programs do not show this part. If you covered or changed anything in the file (white-out or blur, a changed line of the file’s own text, a filled shape or a picture placed on top), the file is saved flat instead: the starting version is not kept, so what you covered cannot be taken back out of it. The other tools (merge, split, compress, convert, page numbers, watermark, password) do not add anything of this kind.

Providers and data processing agreements

We run on these providers, each bound by a data processing agreement that meets GDPR requirements:

  • Cloudflare (Cloudflare, Inc.) serves the website and passes the small requests above to our server. Like any web host it handles your IP address and browser details to deliver the pages and protect the site from attacks, and may keep short technical logs. Cloudflare acts as our processor under the Cloudflare Customer DPA.
  • Google Firebase / Google Cloud (Google LLC) runs our server (a Cloud Function in europe-west1, Belgium), stores the account data, tool history and counters (Firestore, europe-west1, Belgium), handles sign-in (Firebase Authentication, Google sign-in and the email-code accounts) and keeps the server’s technical logs (time, address of the request, errors) for up to 30 days. Google acts as our processor under the Google Cloud Data Processing Addendum.
  • Resend (Resend, Inc.) delivers the sign-in code emails, from hello@editflip.com. It sees the address and the text of each message, under the Resend Data Processing Agreement.

No other third party receives your data, except that your Google profile photo is shown to you from Google’s servers, and that mail you write to our contact address is handled by our email provider.

Where your data goes

Cloudflare, Inc., Google LLC and Resend, Inc. are US companies. Your account data, tool history and the statistics are stored in the European Union (Belgium), but support and some account services can involve access from the United States. Cloudflare and Google are certified under the EU-US Data Privacy Framework, and their data processing agreements also include the EU Standard Contractual Clauses; access by Resend from the United States is covered by the Standard Contractual Clauses in its data processing agreement.

Email

If you write to us, we receive your email address and what you wrote, and use them only to answer you. We keep the conversation for as long as it is useful to answer you, and delete it on request. The only email EditFlip itself sends is the sign-in code you ask for.

Retention

Your account, profile, favourites and tool history are kept until you delete the account; the tool history holds only your last 100 results, older ones drop off as new ones come. Sign-in codes last 10 minutes. Rate-limit counters only count within their hour or day. The daily statistics hold no personal data and are kept. Server logs are kept for up to 30 days.

Why we may process this (legal bases)

Delivering the website and the account you asked for, and answering your messages (GDPR Art. 6(1)(b)), and our legitimate interest in keeping the site secure and knowing, in aggregate, which tools are used and how much (Art. 6(1)(f)). Keeping your sign-in in your browser is strictly necessary for the account you asked for. We make no automated decisions about you and do no profiling.

What we do not do

  • We do not upload, see, store or analyse your files, and we never record their names.
  • We do not use advertising networks, tracking pixels or analytics that set cookies or follow you from site to site.
  • We do not sell or share data, and we do not use anything you open to train AI models.
  • We do not send you newsletters or marketing emails.

Your rights

You can ask us to access, correct, delete or export the personal data we hold about you (your account, profile, favourites, tool history and emails you sent us), and to restrict or object to its processing. You can see your tool history yourself under Tool history and delete everything with Delete account. What is kept in your browser is under your control: sign out, or clear this site’s data in your browser settings, to remove it. Write to hello@editflip.com and we answer within one month. You can also complain to the Romanian supervisory authority, ANSPDCP (Autoritatea Națională de Supraveghere a Prelucrării Datelor cu Caracter Personal), B-dul G-ral. Gheorghe Magheru 28-30, Bucharest, anspdcp@dataprotection.ro, dataprotection.ro, or to the authority of the country where you live.

Children

The tools need no account and collect no personal data, from children or anyone else. Creating an account (with Google or by email code) requires confirming that you are 16 or older. If you believe a child under 16 has made an account or written to us, tell us and we delete it.

Changes

We will update this page if our practices change, for example if anything new is ever kept or leaves your device, and the date at the top will show it.