Is CiteProof working right now?

Security practices

Stated as facts you can check, not badges you must trust. Previously its own page; it lives here now, beside the live state alongside it.

Transport

TLS terminates at the platform edge; HSTS, a self-only content policy, no-sniff content types, deny framing, and no-referrer are set on responses. Confirm with curl -sI https://getciteproof.com/ and read the Strict-Transport-Security and Content-Security-Policy lines. Product pages load no third-party scripts beyond product analytics, which runs only when configured.

What is stored — and what never is

Brief text never lands in logs: a log filter strips body-shaped content before anything is emitted. Free checks are never stored; paid checks persist 90 days in your history, then age out. Usage metering keeps counts and timestamps only — it cannot express what was checked. Rate limiting hashes addresses and holds them up to 24 hours.

Authentication

Sign-in is magic-link only: single-use links that expire, with uniform responses that never reveal whether an address holds an account. Sessions ride HttpOnly, Secure, SameSite cookies; state changes carry independent CSRF tokens on top of SameSite. Abuse prevention uses a first-party device cookie for the anonymous trial; this product never does browser fingerprinting, full stop.

Secrets at rest

Practice-management tokens and webhook secrets are encrypted before storage; API and operator keys live as digests only, so a database dump alone unlocks nothing. Provider webhooks verify HMAC signatures before any payload is trusted.

Payments

Paddle is the merchant of record (see pricing): card data never touches our servers, and prices live in Paddle, never in the browser.

What we ask of you

Reports verify existence and quote accuracy only — never legal advice, and attorney review is required. If a report contains our material error, the Refund Policy says we investigate first. Questions reach a human at the support chat.

Right now

Live lookups

OK — Live verification on — new citations resolve against the live corpus.

Checkout

OK — Checkout open.

Email notifications

OK — Completion and reply emails sending.

Citation data

OK — Resolving against public records as of 2026-10-06 (11 days old).

Background jobs

Unknown — Not observed yet since deploy.

Recent activity

Unknown — Not enough recent activity to describe — check back later.

Availability, evidenced

Unknown — No completed checks in the window yet.

Records and history

OK — Saved checks persist in your history.

Country screening

Needs attention — Country screening is configured but its database is unreadable — traffic is withheld rather than served unblocked.

Release

OK — Release 1.1.0.

What happens when you verify

Each step names what crosses a boundary. The full checking narrative lives on the how-it-works page; this is the data-flow version: what moves, where it rests, and what never leaves.

1. Paste. Your brief travels to the server inside the verification request. Brief text never lands in logs; free checks are never stored, paid checks persist 90 days in your history.
2. Extract. Citations and quoted passages are found in the document, including footnotes, margin line numbers, and headers. Nothing leaves the server in this step.
3. Resolve. Each citation is checked against the dated snapshot above: court opinions from the public corpus, federal statute sections against the U.S. Code.
4. Look up. Gaps go to live sources when lookups are on. Only the citation itself — volume, reporter, page — leaves the server; brief text never goes upstream.
5. Compare. Paid checks match quoted passages against opinion text and show the closest real passage beside the claim.
6. Record. Per-citation statuses plus a Verification Record (PDF for paid checks). The record verifies existence and quote accuracy only — never legal advice, and attorney review is required.

Money and identity ride side rails, never the checking path: checkout binds your email at payment, sign-in links and notifications travel by email, and country screening runs per request and stores nothing.

Does it work?

Effectiveness numbers live in exactly one place so they cannot rot apart: the accuracy ledger reports the false-clean bound, extraction score, and identity coverage from dated runs, caveats included. Worked examples with full evidence live in the gallery and the public verifications index.

Who runs this

CiteProof is operated under the Terms of Service, Privacy Policy, and Refund Policy. Payments ride Paddle as merchant of record (see pricing). Release 1.1.0 — what changed, newest first, is on the changelog. Questions reach a human at the support chat.