Privacy — xades-open

Your files never leave your device

The signed files you open are read, checked and turned into a PDF by code running in your browser. They are not uploaded — not to us, not to anyone — and nothing read from them is sent: not their content, their names, their size, who signed them, or a fingerprint of them.

The page's own Content-Security-Policy allows it to send requests only to this site, so it could not send a file elsewhere even by mistake, and every request it does make is listed below.

Who holds what little there is

It is held by TrainedBooks, an independent software business in California, United States, which operates the agentwares products. Questions and deletions: https://agentwares.vercel.app/contact.

It is stored in the United States. If you are in the EEA or the UK, that is a transfer outside your region, and using the site is you asking us to provide it from there.

What it counts

The beacon, and nothing else, counts how the site is used. Each count goes to this site's own collector and identifies nobody — no cookie, no fingerprint, no network address:

• A page view for each page you open: this site's host, the page's path (never its query string), the host of the page that linked you here if there was one, and two yes-or-no flags — whether the browser looks like a crawler and whether it is one of our own scripts. The browser's user-agent is read to set those flags and then discarded.
• file_opened: one row per file opened, holding one word naming the file's format and the result of the check (such as asice_intact or xades_broken), and whether the caller was one of our own scripts — never the file, its name, its size, who signed it or a fingerprint of it.

If you buy an export

The checkout page is Stripe's. Stripe collects what it needs to take the payment — your email address and card or bank details — under its own privacy policy; we never see your card number.

Your browser also sends:

• Which export you chose, and the language of the page.
• For a one-document export, a 64-character code your browser derives from the document together with a random secret that never leaves the browser. Without that secret the code cannot be matched to the document — not by us, not by Stripe, not by someone who holds the same file.
• After paying, the Checkout Session id Stripe returns you with, so this site can confirm the payment and issue the token; and the token itself before each export.

We keep no purchase records of our own beyond what Stripe holds for us.

What your browser keeps

Nothing, unless you buy. After a purchase, your browser keeps the unlock token in its own local storage — and, for a one-document export, the secret salt and code that let it recognise that document. Clear the site's data and they are gone; we hold no copy.

It sets no cookie and does not follow you to other sites.

Who else touches it

• Vercel, which hosts the site in the United States. Vercel keeps its own log of each request — its path and query string (which, on the page you return to after paying, includes the Stripe Checkout Session id), the requesting network address and the user-agent — for one day on our plan, and we read it only to fix faults.
• Neon, which holds the counted rows, in the United States.
• Stripe, which takes payments.

How long we keep it

• Counted rows identify nobody, so they are kept without an expiry date, as the running tally of how the site is used.
• Vercel's request log: one day.
• Payment records: as long as Stripe and tax law require.

If you write to us through the contact form, that message is covered by the privacy note at https://agentwares.vercel.app/privacy.

What we do not do

We do not receive your files, sell data, set cookies, build profiles, or use anything you send to train models.

Your rights

Ask and you get a copy of anything we hold about you, a correction, or its deletion — whether or not the law where you live requires it of us. Ask at https://agentwares.vercel.app/contact. We aim to answer within 30 days.