What this page knows about you.
Short version: Fdo. does not send your files anywhere, does not run analytics, does not embed anything from third parties and requires no sign-up. This page explains exactly what gets processed, where and why.
Last reviewed: April 27, 2026.
What Fdo. does with your PDFs
When you drag a PDF in, the file is loaded into the browser's memory. It is processed there — the signature is inserted using libraries that run on your machine — and the result is saved to your disk when you click download. The file never leaves the browser.
When you close the tab, everything in memory is released. There is no database, no cloud storage, no server-side cache.
What is stored in the browser
By default, nothing. If you turn on "remember my signature" for future sessions, the
signature image is stored only in your browser's local storage (localStorage).
That is not sent anywhere: it lives in your browser and only you can clear it (from the
app itself or by clearing site data).
- localStorage
- Signature image, if you choose to remember it. Up to a few MB.
- Cookies
- None.
- sessionStorage
- None.
What the server sees
The server only serves static files: the HTML for each page and the JavaScript for the app. There is no endpoint to send anything to. Standard web server logs (IP, user-agent, requested path, HTTP status code) do exist — that is unavoidable when a browser requests a page — and are kept according to the hosting provider's policy for as long as it takes to detect abuse. They are not joined with anything else, there is no user profile and no cross-page tracking.
What the pages load
- The HTML, CSS and JS, served from Fdo.'s own domain.
- A typeface (Inter) served from the same domain — not from Google Fonts or another CDN.
- Nothing else. No Google Analytics, no Hotjar, no Sentry, no pixels.
If you open the browser's developer tools and look at the network tab, no outbound request is made when signing once the initial page is loaded.
This is not qualified electronic signature
Fdo. places a signature image onto the PDF, which is legally acceptable as a simple signature in many private and commercial contexts. It is not advanced or qualified electronic signature under eIDAS, and it is not the same as using a digital certificate. For interactions with public administrations, use the official tool issued by your country's government.
Changes to this policy
If this policy changes, the new date is noted at the top of the page. We have no way of letting you know personally because we don't know who you are.
Contact
If you have a specific privacy question or notice something this page doesn't cover, write to hola@fdo.app.