Privacy
What Fylane keeps, and for how long
Fylane exists to process files people hand it, so the only honest privacy page is a specific one. This is what is stored, where, for how long, and what never happens. Each line is checked against the code and the infrastructure it describes.
Your files
The same rules apply whether a file arrives through the API, a free tool on this site, the Fix page or the browser extension.
Uploads live one day
A file you upload sits in a private bucket in AWS (us-east-2) while its job runs. A bucket rule deletes it within 24 hours whether or not the job succeeded.
Results live seven days
Converted, compressed or fixed files are kept for seven days so you can download them, then expire on their own. Nothing is kept longer.
Only machines read them
Files are processed by software in a single-use container and are not read by people. They are never used to train anything, and never shared with or sold to anyone.
AI features run in-house
Answering questions about a document, translating it or splitting it by topic runs on models Fylane hosts itself. Your text is not sent to a third-party AI provider.
What leaves for a job you asked for
Capturing a website fetches the address you typed. Signing a PDF with a timestamp sends a hash of the signature, not the document, to the authority you chose (Sectigo or FreeTSA). Nothing else leaves.
Processing is walled off
Each job runs in its own container with no credentials, short-lived links to its one input and output, and outbound network limited to TLS. It cannot reach other files or the database.
Accounts, billing and logs
A console account is an email address and a credential, held by Amazon Cognito; Fylane never sees or stores your password. Alongside it we keep what the product needs to work: your API keys as keyed hashes that cannot be reversed, and for every job its name, size, type, timings, outcome and credit cost. Every record carries your organisation and is isolated from every other organisation at the database level.
Payments are processed by Stripe. Card details go from your browser to Stripe and never touch Fylane; we keep the Stripe customer reference and the invoices it issues.
Server logs record request metadata (route, status, timing, and the calling IP address, which the abuse limits use) for days, not months. They never contain file contents.
Cookies, and the trackers that are not here
fylane_session
Set when you sign in to the console. It holds an encrypted session reference, is HttpOnly, and expires with the session.
fylane_visitor
Set when you use a free tool without signing in. A random token that counts your free monthly allowance; it identifies a browser, not a person, and holds nothing about you. Deleting it resets the count.
The browser extension
Reading a form’s rules and checking your file against them happens on your device, and simple fixes (image convert, resize, compress) run on your device too. The extension makes two kinds of request, and each has a switch in its popup.
Anonymous usage events, on by default
When the extension acts at a file input it records what happened: the kind of field, the file’s type and size bucket, the rule it inferred and where it came from, which fix was offered and whether it ran locally or in the cloud, whether you took or declined it, how long it took, a failure code when it failed, the conversion it could not offer, why it stood down, and a scrubbed error message when its own code failed. Each event carries the extension version, the minute, and a random id replaced every day. The first switch in the popup turns this off and empties the queue.
Site names and rejection sentences, off unless you turn it on
The second switch adds the site’s registered domain (northgate.co.uk, never the page address) and, when a site rejected a file in its own words, that sentence — scrubbed of email addresses, long numbers, paths and URLs and cut at 300 characters — so the next person on that site is not rejected. Both are dropped the moment an event is recorded while the switch is off.
How it travels and how long it stays
Events queue on your device (at most 200) and leave in one batch of at most 50 every five minutes, from the background worker to fylane.dev/api/ext/events with credentials omitted, so the request can never carry a cookie. Nothing is sent while the queue is empty. Raw events are deleted after 90 days; daily totals are kept without any per-user field. Only Fylane’s founder can read the report.
Shared rules come back at release time only
What people who turned on the second switch reported is compiled into a file that ships inside the next version of the extension. The extension never fetches rules while you browse.
The consented cloud fix
When you choose “Fix with Fylane Cloud” on a card that names the file and says it will be uploaded, the file goes to fylane.dev, is processed under the rules above, and the result comes back. No file is read or uploaded on install, while browsing, or when you pick a file.
Never sent: file contents, file names, page text other than the site’s own error sentence (and only with the second switch on), page addresses beyond the registered domain (same), your email, cookies, the free-allowance token, or any identifier that outlives a day. What it stores, on your device only: the rule text sites stated or rejected with, your “don’t offer again” choices per form, the list of sites you armed, the two switches, the event queue, and the in-flight copy of a file being fixed in the cloud, deleted when the result arrives.
Who else touches the data
Amazon Web Services stores and processes files and runs the accounts service, in the US East (Ohio) region. Vercel serves this website. Stripe handles payments. A timestamp authority sees a signature hash only when you ask for a timestamp. That is the whole list; it will be updated here before anyone is added to it.
Your data, your call
Write to security@fylane.dev (opens in a new tab) to ask what we hold about you, to correct it, or to have your account, its keys and its records deleted. Files need no request: they are gone within the windows above regardless.
This page changes when the code does. Last updated 7 September 2026.