Clearance Check

Privacy

Last updated: September 29, 2026

Who operates this site

Clearance Check is operated by Coder Crew LLC, 137 Riverview Ave, Annapolis, MD 21401. Contact: hello@clearancecheck.co.

This website

The public pages have no forms. They run two analytics tools and nothing else. Vercel Web Analytics counts page views without cookies and without following anyone between sites. Google Analytics sets two first-party cookies, _ga and _ga_VLJLPFHBJJ, so we can see which pages get read and how many visits are returning ones; that data is retained for two months, and Google Signals and ads personalization are off, so nothing here feeds an advertising profile. Neither tool runs on the sign-in page or anywhere inside the client tool. Our hosting provider, Vercel, may keep standard server logs of requests.

The client tool

The tool behind the login is used only by clients working with us under a signed engagement. Accounts are created by Coder Crew for named engagement users only; there is no self-service signup. Its sign-in page has a form and sets a sign-in cookie, which can last up to 400 days. Documents a client uploads are processed in US-hosted systems:

  • Vercel, for hosting.
  • Supabase, in its US region, for storing the uploaded PDFs and the text and results extracted from them.
  • Anthropic, for reading the documents. Client data is not used to train its models.

Content we refuse to store

The tool scans the text of every upload before anything is saved. It refuses a PDF whose text matches the patterns it checks for (wire instructions, account numbers, routing numbers and Social Security numbers) and does not save it. We keep only a log entry of the refusal (file name, page numbers, match type, and the signed-in user and time), never the matched text. The scan reads a PDF’s text layer and is a backstop to the client’s own redaction, not a substitute for it, so clients send anonymized files. A page with no text layer, such as a scanned image, is refused for the same reason: the scan cannot read it.

Deletion

Engagement data is deleted at the end of the engagement: the stored files and the database. Sign-in accounts are not part of that deletion. When that runs, the tool records one deletion entry — the engagement name, the date, who requested it, and the number of files, documents and stored objects removed, with no document content — and we then confirm the deletion to the client in writing from that entry. Copies our providers keep under their own retention terms, such as backups and logs, are outside it.

Email

We send business email from this domain. Every commercial message carries our postal address and a way to stop further email, which we honor within ten business days.

Requests

For any privacy request, including stopping email, write to hello@clearancecheck.co.