Docfeather

Privacy notice

Last updated: 19 November 2026

In short

Your files — PDFs and images — never leave your device. We do not set cookies ourselves (except one if you object to the counting), do not require an account, and do not embed content from other providers — except Paddle's payment window on a checkout page of its own, and only when you choose to buy Docfeather Pro or open a link from one of Paddle's emails. When you open the site, our hosting provider Cloudflare processes technically necessary connection data, and we anonymously count which steps of our tools are used. If you write to us via the contact form, we use your email address and message only to reply. If you buy Pro, Paddle handles the payment. We keep only a key, Paddle's IDs and how many times a day the key is used, not your name or email address; Paddle does show those to us in our Paddle account, and we look at them there in individual cases — for example when you write to us about a lost key or cancel a subscription. Details below.

1. Controller

Andrii Tokar
Tokar IT
Am Reinhardshof 55
97877 Wertheim
Germany
Email: info@tokar-it.de

2. Your files

PDF files and images you work on with our tools (compress, merge, split, delete, rotate and reorder pages, add images to PDF, JPG to PDF, PDF to JPG, ID card copy, passport copy) are processed entirely in your web browser, on your own device. Neither the files nor their names or contents are transmitted to us, to Cloudflare or to any other third party. If a PDF needs font or character tables, the page loads them from our domain like any other file of the site; nothing from your file is transmitted. Likewise, the ID card and passport copies load a model that finds the corners of the card or passport page, with its runtime library (about 10 MB download), from our domain — in the background as soon as the page opens, so that it is ready when you pick a photo (not when your browser reports data saver mode or a very slow connection); it runs on your device, and your photo is not transmitted for it. When you save a result on a phone, your device's share menu opens; where the file goes from there is up to you alone.

3. Delivering the website (hosting by Cloudflare)

This website is delivered by Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA ("Cloudflare"). With every request, Cloudflare processes the data your browser sends automatically: your IP address, the date and time, the requested URL, if applicable the previously visited page (referrer), your browser's user agent, and technical details such as the status code and the amount of data transferred.

Purpose and legal basis: Delivering the site and protecting it against attacks and abuse (Art. 6(1)(f) GDPR). Our legitimate interest is to provide the website reliably, quickly, and securely.

Recipients: Cloudflare processes this data as our processor under a contract pursuant to Art. 28 GDPR (Cloudflare Data Processing Addendum). Processing may also take place in the USA and in other countries where Cloudflare operates data centers.

Transfers to third countries: For the USA, the European Commission has adopted an adequacy decision (EU-U.S. Data Privacy Framework, Implementing Decision (EU) 2023/1795, Art. 45 GDPR), under which Cloudflare, Inc. is certified. In addition, the data processing agreement with Cloudflare provides for the EU Standard Contractual Clauses (Art. 46(2)(c) GDPR).

Retention: We do not keep server log files containing IP addresses ourselves. Cloudflare retains connection data only for as long as necessary to deliver the site and defend against attacks, and deletes it afterwards. More information: cloudflare.com/privacypolicy.

Statistics: Cloudflare also gives us summary statistics derived from this data (number of requests and page views, approximate number of distinct visitors, countries of origin); we do not receive individual IP addresses. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is to know the reach of the website.

To fend off attacks and automated access, Cloudflare may set strictly necessary security cookies, such as "cf_clearance" after you pass a security check, or "__cf_bm".

4. Anonymous usage statistics

To check that our tools work and are used, we count anonymously. When you open a tool page or the home page, our own server (hosted by Cloudflare) counts the visit solely from what your browser sends with that request anyway: which tool (or the home page) and the page's address (such as /compress-pdf/), the page language, where you came from — as one word from a fixed list ("Google", "Bing", "DuckDuckGo", "Ecosia", "Yahoo", "Yandex", "ChatGPT", "Perplexity", "Claude", "Gemini", "Copilot", "DeepSeek", "Grok", "another site", "direct" or "this site") or, if you came from another public website, only its domain (such as forum.example.com), formed only from the name of the previous website or a corresponding marker in the link, never from the rest of its address or your search terms — and the kind of device ("phone", "tablet" or "computer") and its operating system (such as "iOS", "Android", "Windows", "macOS"), one word each from the browser identification (user agent and client hints); not the model, browser version or screen size. Nothing on your device is accessed for this, except that the server checks whether the "nocount" cookie is set (section 7).

So that search engines and other programs do not distort the figures, the server also checks with the same request whether what your browser sends fits together (browser identification, client hints, preferred language) and whether the request comes from a data centre's network; for this it uses the network's number (ASN) that Cloudflare adds to every request. If the check fails, we count only one word for the reason (such as "data centre"); we do not store the network number itself. Once a tool page or the home page has been in view for three seconds in all, it reports this once to the same server, with the word for where you came from; for this the page only reads whether it is in view. The server checks this report and the reports described below in the same way; if the check fails, it does not count them at all (except a purchase).

While you use a tool, the page also sends short reports to the same server: that a file was added, that the result was created or a file could not be made smaller, or that an error occurred (error type "encrypted", "restricted (copying or editing locked)" or "other"), that you started over or cleared the list, that you passed one or more results on to another tool and to which one (not how many), for a finished result roughly how long it took ("under 1 second", "1–3", "3–10", "10–30" or "over 30 seconds") and which result since the page was opened it is ("1" to "5" or "more" — the page counts this only while it is open and stores nothing on your device for it), and, for Docfeather Pro: that the offer was shown, that you opened the Docfeather Pro page (from the offer, on your own, or as your own Pro page), that you opened Paddle's payment window for a plan or closed it without buying, that it could not be loaded, reported an error or no key came after a payment, and that a purchase went through — each with the plan ("monthly", "yearly" or "lifetime") where there is one, and with the country the request came from (the two-letter country code Cloudflare determines from the connection, not your IP address). With these reports we store neither device nor operating system, and we do not link the counts with the purchases in our Paddle account. For "Add image to PDF", also that you put an image on every page (not which one). For the ID card and passport copies, also whether the card or passport page was found in the photo automatically and whether you moved its corners, rotated it, blacked out parts, swapped front and back, tapped "Add another card" or "Add another passport" or added another card or passport — only that it happened, not where or what — how long loading the corner model (reported only after you pick a photo) and the way from picking the photo to placed corners roughly took ("under 0.5 seconds", "0.5–1", "1–2", "2–5", "5–15" or "over 15 seconds"), whether loading worked, and whether the model, the simple detection or the whole picture placed the corners (the latter when the picture has the proportions of the card or passport page, as a scan or a cropped picture does); where the model did not place them, also how sure it was (one of four steps, or "not loaded") and whether the picture has those proportions; also whether you picked both photos at once and, for a finished result, whether the file name was the default or your own, whether you turned the mark on or off against how the page started or changed its text, and whether you wrote a note — never the name, the mark or the note themselves. Each report also includes the tool, the selected or automatically applied setting (compression level, page size, image quality or file format) and the page language; the server adds the device and operating system as above. It also includes the address of the page it was sent from (such as /compress-pdf/) and the word for where you came from when that page was opened (as above: a word from the list or the other website's domain, so "this site" if you got there through our own links); for the steps on the Docfeather Pro page, those of the tool page whose offer you followed, passed along in the offer's link. Nothing about your files — name, contents, size — is transmitted.

We store only one counter per day for each combination of these attributes. We do not store IP addresses, user agents, or any identifiers; we set no cookies and store nothing on your device for these counts (for the cookie set if you object, see section 7). The counters contain nothing we could identify you by; we keep them without a fixed time limit.

When a report is received, Cloudflare — as with every page request — briefly processes your IP address and the other connection data listed in section 3; this data is not included in the statistics. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is to detect errors, improve the tool and the way to Docfeather Pro, and decide which features to build next.

The page creates these reports from how you use the tool; they contain no information previously stored on your device and no identifier. Insofar as this involves access to your terminal device within the meaning of Section 25 TDDDG, we rely on Section 25(2) no. 2 TDDDG: we need the reports to see whether the tool you are using and the payment process work (for example whether the payment window loads and the key arrives) and to fix errors.

If your browser sends the Global Privacy Control signal, nothing is counted. You can also object to the counting at any time at the end of this page ("Don't count my visits in this browser"); page views are then no longer counted and no reports are sent from this browser.

5. Contact form

If you write to us via the contact form, we process your email address, your message and the page language in order to reply, and, to fend off automated spam, the time between opening the page and sending the message; this is only checked, not stored. The message is not stored on our website; Cloudflare (Email Routing, as our processor, see section 3) forwards it by email to our mailbox. Our email provider is mailbox.org, operated by Heinlein Hosting GmbH, Schwedter Straße 8/9A, 10119 Berlin, Germany, also acting as a processor under Art. 28 GDPR.

To prevent abuse, Cloudflare limits the number of messages per IP address; the IP address serves only as a counting key for a one-minute window and is then discarded, not stored (Art. 6(1)(f) GDPR; legitimate interest: preventing abuse).

Legal basis: Art. 6(1)(b) GDPR where your request relates to a contract or to steps prior to entering into one, otherwise Art. 6(1)(f) GDPR; our legitimate interest is to answer inquiries. Retention: We delete your message once the inquiry has been fully resolved, unless statutory retention obligations apply.

6. Docfeather Pro: purchase, key and cancellation

Docfeather Pro is sold by Paddle, our reseller and merchant of record: Paddle.com Market Limited, 30 Old Bailey, London EC4M 7AU, United Kingdom; for buyers in the USA, Paddle.com Inc., 3811 Ditmars Blvd #1071, Astoria, NY 11105-1803, USA; for buyers in Canada, Paddle.com (Canada) Ltd., 22 Adelaide Street West, Suite 3400, Toronto, Ontario M5H 4E3, Canada (each "Paddle"). Paddle processes the data of the purchase as an independent controller to carry out the purchase, pay taxes, prevent fraud and send you receipts and subscription emails; see Paddle's privacy notice: paddle.com/legal/privacy. For the United Kingdom, the European Commission has found an adequate level of data protection (Implementing Decision (EU) 2021/1772, renewed by Implementing Decision (EU) 2025/2574; Art. 45 GDPR). Paddle may also transfer data to other Paddle group companies, such as Paddle.com Inc. in the USA, and to service providers outside the EU; Paddle is responsible for this and, by its own account, relies on the EU Standard Contractual Clauses (Art. 46(2)(c) GDPR).

Prices: When the Pro offer or the Docfeather Pro page opens, or Compress PDF shows the price next to the day's free file, our server asks Paddle for the prices in your country; it sends Paddle only the two-letter country code that Cloudflare derives from your connection, not your IP address. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is to show you the correct price for your country, including taxes, before you buy.

Checkout page and payment window: Paddle's payment window runs on a page of its own, docfeather.com/pro/ (in other languages /<language>/pro/), which opens in a new tab when you pick a plan — not on the pages where you work on your files. Only on that page does your browser load Paddle's script (Paddle.js from cdn.paddle.com) and its payment form (from buy.paddle.com), and only once you pick a plan — or, if you open the page through a link in one of Paddle's emails (for example to renew a payment method), as soon as it opens; not before. This gives Paddle your IP address and your browser's details. The legal basis is Art. 6(1)(b) GDPR: loading the payment window is a step you ask for before entering into a contract. Within its payment window — a frame of its own on Paddle's domain — Paddle may store and read information on your device as far as needed for the payment and to prevent fraud; Paddle is responsible for this, see its privacy notice and cookie notice. The page passes Paddle's window the page language and whether your device is set to light or dark, so that it matches.

What Paddle shows us: You enter your email address, payment details and, where needed, your country and postcode directly with Paddle. We never receive payment details such as your card number. As the seller, we can see in our Paddle account (its dashboard and interface) your email address, your name if you gave one, your country and postcode, and your purchases and subscriptions. We do not copy these details into our own storage and look at them only in individual cases: when you ask us for help (a lost key, a refund, a cancellation), when you cancel with our cancellation form (below), or to resolve payment problems, chargebacks or abuse (Art. 6(1)(b) and (f) GDPR; our legitimate interest is to handle such cases properly).

Your key: After the payment — or later, if you enter the transaction ID from Paddle's email to find a lost key — your browser sends us the ID of the purchase. Our server asks Paddle whether it has been paid and for which plan, and stores, for your key: the key itself (generated at random), Paddle's IDs of the purchase and the subscription (strings such as "txn_…" and "sub_…" that contain neither your name nor your email address), the plan, the end of the paid period, the status, the time the key was created, the time of Paddle's last notification about it, and the time our server last asked Paddle about the subscription, for a cancelled subscription the date it ends, and whether a subscription is still in its free trial. Paddle tells our server when a subscription renews, ends or is refunded, so the key follows; from these notifications we take only the status and dates and store nothing else. "Card and invoices at Paddle" on the Docfeather Pro page opens Paddle's own page, where you sign in with your email address; we do not open it for you with the key. Legal basis: Art. 6(1)(b) GDPR (performing the contract for Pro). Retention: as long as the key is valid — for "Lifetime", as long as Docfeather Pro exists, for a paused subscription, as long as it is paused — and for six months after, to answer questions about it; then we delete the entry. The entries are kept in a database at Cloudflare (D1, as our processor, see section 3); Cloudflare keeps a restore history of the database for 30 days, so a deleted entry disappears from it 30 days after deletion at the latest.

How often a key is used: For each key we count how many times a day it is checked or retrieved with its transaction ID — only this number per day, without IP address and without anything else about who asked. A browser asks about once a day; very many requests show that a key has been published. We then replace it with a new one: the old key no longer turns Pro on, and you get the new one by entering the transaction ID from Paddle's email. We keep the old key so that the page can tell you it was replaced. Legal basis: Art. 6(1)(f) GDPR; our legitimate interest is to detect and stop keys being shared with the public. Retention: the counts for 30 days, replaced keys for six months.

To stop anyone from trying out keys or transaction IDs and to protect Paddle's interface from overload, Cloudflare limits the number of requests for prices, purchases, keys and cancellations per IP address (for IPv6, per address block); the IP address serves only as a counting key for a one-minute window and is then discarded, not stored (Art. 6(1)(f) GDPR; legitimate interest: preventing abuse).

Storage in your browser: The page keeps the key and its state in your browser's local storage ("df-pro") so that Pro is on next time; once a day it sends the key to our server to check that it is still valid. The Docfeather Pro page shows your plan and key from it, and the cancellation form fills in the key from there; "Turn off Pro in this browser" deletes the entry. From the moment Paddle reports a payment until its key has arrived, it also keeps the transaction ID ("df-pro-pending"), so that a key is not lost if the tab closes; it is deleted as soon as the key has arrived, and if the key never comes, the first time you open Compress PDF, ID Card Copy, Passport Copy or the Docfeather Pro page after seven days. Right after a purchase it also briefly keeps the new key ("df-pro-welcome"), so that Compress PDF, ID Card Copy or Passport Copy shows it to you once to keep; the entry is deleted as soon as it has been shown, at the latest the first time you open one of them after one day. If you turn Pro off on the Docfeather Pro page, it sets a marker for the current session ("df-pro-off", session storage) so the next page can confirm it; that page deletes it at once. Without Pro, the page keeps there only the date on which you used the day's free file for "Fit a size" ("df-fit"); it does not leave your device. Storing and reading these entries is strictly necessary to provide the service you explicitly ask for — Pro, or the free file a day (Section 25(2) no. 2 TDDDG). You can delete them by clearing this site's data in your browser; your key turns Pro on again.

If you lose your key and write to us, we use your email address to look up your purchase in our Paddle account and send you the key (Art. 6(1)(b) GDPR); section 5 applies to your message.

Cancelling without signing in: With "Cancel contracts here" at the bottom of every page (docfeather.com/cancel/, in German docfeather.com/de/kuendigen/), you can cancel a subscription without signing in. The form sends our server the email address you used for the purchase, the transaction ID (txn_…) from Paddle's email or your key (DF-…) if you give one, and what you state about the cancellation. With a transaction ID or key, our server asks Paddle for this purchase, checks that it was made with that email address and, if so, instructs Paddle to cancel the subscription. If you give only the email address, our server looks up the running Docfeather Pro subscriptions for that address at Paddle and has them cancelled; the answer on screen is then the same whether a subscription was found or not, so that nobody learns through the form who has bought. To fend off automated access, our server also checks how much time passed between opening and sending the form, and counts cancellations with only an email address per hour for the whole website (only the number, no address and no connection); the time is not stored and the counts are deleted after two days (Art. 6(1)(f) GDPR; legitimate interest: preventing abuse). The confirmation with date and time appears on your screen at once; Paddle records the cancellation with the subscription and confirms it to you by email. We do not store what you enter in the form in our database. For a cancellation for good cause, we send your email address, the subscription's ID and the reason as an email to our own mailbox, to look into the reason and reply to you (section 5 applies to it). If you choose a date after the end of the current billing period, we likewise send your email address, the subscription's ID and the date to our mailbox, to carry out the cancellation at Paddle then; we delete the email once that is done. The entry for your key follows the cancellation as described above. The legal basis is Art. 6(1)(c) GDPR in conjunction with Section 312k of the German Civil Code (BGB), which requires this way of cancelling, and Art. 6(1)(b) GDPR (ending the contract). Section 3 applies to the connection data; Cloudflare limits the number of cancellation requests as described above (per IP address, for IPv6 per address block).

7. Cookies and storage on your device

Apart from the special case mentioned in section 3, this website sets a cookie only if you object to the counting at the end of this page: "nocount", valid for two years. It holds only the value "1", no identifier; your browser sends it with each request; our server and the page itself only check whether it is set — the page so that it then sends no reports from the tools either. Storing and reading it is strictly necessary to honour the objection you explicitly asked for (Section 25(2) no. 2 TDDDG); unticking the box deletes it.

Only when you pass results on to another tool with a button named after that tool (such as "Compress PDF", "Merge PDF (3)" or one in the "Continue with…" menu) does the page keep the file or files — with the name of the tool they come from and, for compressed PDFs, their size before, so the next tool can show this — briefly in your browser's storage (IndexedDB) and set a marker for the current session (session storage). This can include a copy of your ID card or passport made with "ID Card Copy" or "Passport Copy". The next page reads the files at once and deletes both. If they are not picked up, for example because you close the tab, they stay in this browser until you next open any page of docfeather.com, which then deletes them, or until you clear this site's data in your browser. On a shared or someone else's device, it is better to save an ID card copy directly than to pass it on. The files do not leave your device. This storage is strictly necessary for the function you explicitly asked for (Section 25(2) no. 2 TDDDG).

As with any website, your browser keeps files of the site — including the corner model from section 2 — in its cache so they need not be loaded again. The page also checks a few properties of your browser locally to adapt to it (such as touch input, share function, screen size, data saver mode and connection type, supported features, Global Privacy Control); this information does not leave your device. Both are necessary to provide the site (Section 25(2) no. 2 TDDDG). On computers, the page downloads a finished result to your downloads folder automatically — several files picked together as one ZIP file — as long as "Download automatically" is ticked; this setting is not stored. When you open the full-screen view of your files, the page adds an entry to the tab's history (without file names or contents) so that Back closes the view. Beyond that, we store nothing on your device, except the Pro key ("df-pro"), a paid purchase's transaction ID until its key arrives ("df-pro-pending") and the date of the day's free "Fit a size" ("df-fit"), each under Section 25(2) no. 2 TDDDG (section 6). Scripts, fonts and libraries are loaded exclusively from our own domain — except Paddle's payment window on the checkout page, which may itself store information on your device within its own frame; Paddle is responsible for this (section 6).

8. Obligation to provide data, automated decisions

You are not legally or contractually required to provide any data. Without the connection data described in section 3, however, the website cannot be displayed, without an email address we cannot reply to a message sent via the contact form, you can buy Pro only if you give Paddle the details its payment window asks for, and the cancellation form can find your subscription only if you give the email address of the purchase (you can also cancel in the other ways listed in our terms). We do not use automated decision-making, including profiling (Art. 22 GDPR).

9. Your rights

Subject to the legal requirements, you have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18) and data portability (Art. 20). Because we do not store any data about page requests that would allow us to identify you, we are generally unable to attribute individual requests to a person (Art. 11 GDPR). For Docfeather Pro, we give you access to the entry for your key, correct it or delete it if you tell us the key (DF-…) or the transaction ID (txn_…); if you give us only your email address, we look up your purchase in our Paddle account (as for a lost key); deleting the entry ends Pro for that key. For the data Paddle processes as controller, you can contact Paddle (paddle.com/legal/privacy) or us; we then pass your request on. You can reach us at info@tokar-it.de for any request.

You also have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR), in particular in the Member State of your habitual residence. The authority competent for us is the State Commissioner for Data Protection and Freedom of Information of Baden-Württemberg (Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg), Heilbronner Straße 35, 70191 Stuttgart, Germany (postal address: Postfach 10 29 32, 70025 Stuttgart), email: poststelle@lfdi.bwl.de, www.baden-wuerttemberg.datenschutz.de.

10. Right to object under Art. 21 GDPR

You have the right to object at any time, on grounds relating to your particular situation, to the processing of personal data concerning you that is based on Art. 6(1)(f) GDPR (sections 3, 4, 5 and 6). We will then no longer process this data unless we can demonstrate compelling legitimate grounds for the processing that override your interests, rights and freedoms, or the processing serves the establishment, exercise or defense of legal claims. You can object informally, for example by email to info@tokar-it.de; you can object to the counting (section 4) right here as well:

Saves a cookie "nocount" in this browser, nothing else.