Privacy

We do not want your data, and the site is built so that we cannot accumulate it.

There is no account to create, so there is no email address, no password and no session. There is no table mapping anybody to the vulnerabilities they have not patched, which is the single most sensitive thing a tool like this could hold and the one thing it must never be breached out of. The way to be certain of that is not to hold it.

Four things a site normally does, that this one does not do at all.

• No accounts. Nothing to sign up for, no email address, no password, no session, no profile. Nothing you do here is attached to an identity, because there is no identity to attach it to, and there is no database behind the site to attach it in.
• No cookies. The site sets no cookie of any kind. There is no consent banner here because there is nothing to consent to. Your browser does keep one thing locally, on your device only, and that has its own section below.
• No analytics. No analytics product, no tag manager, no pixel, no session recorder, no A/B testing, no fingerprinting. We do not measure you.
• No third-party requests. Every page loads from this site alone. No fonts, scripts, images or frames are fetched from anywhere else, and the content security policy restricts those resource requests. The hosting provider still receives the request, and following an external link sends a request to its destination. Typefaces are downloaded when the site is built and served from here.

Links to the upstream catalogs point off site, and following one takes you to somebody else's site under their policies. The site sends only its own address as the referrer when you leave, so the page you were on does not travel with you.

A list you paste is used to answer the question you asked and is then gone.

The list is submitted in the body of the request, never in the web address, so it does not appear in a browser history, in a link you might share, or in a server access log. It is compared against the shipped findings, the answer is rendered, and the request ends. It is not written to a database, not written to a file and not written to a log. The site has nothing to write it to: it reads one dated snapshot file and holds no store of its own.

The same is true of the API. A request to POST /api/v1/check is answered from the same pass the paste box uses, its response is marked not to be cached anywhere, and its body is not retained. When a request fails, the error handler logs the error message only and never a stack trace, because a stack can carry the input that caused it. An error reply to the check API repeats the rejected line so you can find it; nothing is stored.

We ask for record identifiers, package names and version numbers. Do not paste anything else: no names, no email addresses, no hostnames, no credentials and nothing confidential to somebody else. Nothing here needs it, and you are responsible for what you submit.

Saving or importing a review explicitly stores a capsule under pd.desk.baseline.v1 in this browser. It contains the exact inputs and optional watchlist token, source snapshot and coverage, captured evidence, acknowledgments, capture date, and any decision date or private ticket notes you entered.

The token decodes to the list and any versions or filters in it. Refreshing sends the supported identifiers, packages and product lines to this site's check API. Your private notes, decision date and acknowledgments are not sent. Opening or closing a page never marks evidence reviewed.

Use Forget saved review (shown on the landing page once a review is saved) to remove the capsule and the older pd.desk.token, pd.desk.lastVisit and pd.desk.since keys. Clearing site data in your browser also removes it. If storage is blocked, the app reports that it could not save the review. An exported capsule is a separate file: delete or protect your copies.

pd.ticker.paused separately remembers whether you paused the moving strip. Clear site data to remove that display preference. Other sites cannot ordinarily read this site's local storage; anyone using the same browser profile may read it.

On a shared machine: a saved review can expose the list, versions and private notes to the next person using the browser. Forget it or clear site data when finished. Exporting does not encrypt a capsule.

A watchlist has no row in any database: the list is encoded in the link itself, so whoever holds the link holds the list.

The part of the address after /w/ is the list. It is decoded when the page is opened, answered against the same findings the check page uses, and dropped when the answer is written. Nothing about it is stored here, which is also why a lost link cannot be recovered by us: there is no copy.

That trade has a cost and it is yours to weigh. Anyone you send the link to can read it, and so can anything that keeps a copy of a URL: a chat log, a ticket, a bookmark sync, a proxy, a mail scanner. The page asks search engines not to index it and the site never publishes it, but a link is only as private as the places it has been.

Vercel hosts this site and can retain request metadata. The deployed project's exact retention and log-drain configuration have not been verified by us.

Vercel documents request paths, timestamps and status in its runtime logs. Its log-drain schema also supports client IP addresses and query-bearing paths. Retention depends on the plan and configured services. Do not treat this site's lack of application storage as a promise that the hosting platform keeps no request metadata.

Opening a watchlist or record link sends its identifiers in a request URL that the host may log. A watchlist URL encodes the list; a record URL names that record. A paste-box or POST API check sends its input in the request body. Result links do not automatically prefetch the named records, but following a link deliberately makes a separate URL request. A GET API query also places its query parameters in the URL. The app does not write pasted input to its own logs; this is not a claim that the hosting platform retains no request metadata. Share a watchlist only if its contents can be disclosed.

We keep no logs of our own beyond that, and we run no separate tracking, aggregation or reporting on top of the host's.

Nothing is sold, rented, shared or handed to an advertiser, because there is nothing to sell.

We do not sell or share personal information, we run no advertising, and we have no marketing list, no data broker relationship and no tracking partner. The only third party involved in serving this site is the host described above.

If the project were ever transferred to somebody else, there is no store of visitor data to transfer with it. If we were compelled by law to produce something, we could only produce what exists, which is what this page describes.

This is a tool for people who triage vulnerability reports at work, and it is not for children.

The site is not directed at children, has no features aimed at them, and knowingly collects nothing from anybody, of any age. If you believe a child has submitted something to this site, there is nothing stored for us to delete, and you are welcome to contact us about it anyway.

Data protection law gives you rights over personal data held about you. We hold none, so there is nothing to exercise them against.

There is no account to access, correct, export or close, and no profile to object to. The app maintains no account or stored check history to delete. What your own browser keeps is yours: clear it with the control described above. Watchlist links cannot be revoked: deleting your copy does not disable another person's copy. They encode their contents directly.

The host's request logs are the one exception, and they are subject to the host's policies and the project's configuration. You can reach us about any of this through the contact below.

If this notice changes, the date at the top of the page changes with it.

Every claim here is checkable against the code, and a change to the code that made one of these sentences untrue is a change to this page in the same commit. The notice describes how the deployed application handles data.

One channel, and it answers privacy questions as well as disputes.

Contact us → The same page carries the corrections policy for findings and the route for reporting a security issue in the site itself.