Privacy Policy

Last updated: 2026-06-06.

What we collect

  • Registration data: the wording you submit, your display name, email, optional context note, optional source URL, claim type. All of this except email is intentionally public on the verification page.
  • Payment data: handled by Stripe. We store the Stripe payment intent / session IDs and the SKU you bought, never card numbers.
  • Telemetry: scan timing, IP-based rate-limit counters, and moderation verdicts. IP addresses are not stored long-term — they live in the rate-limit bucket until it expires.
  • Cookies: a session cookie if you sign in, an admin-session cookie for curators. No third-party tracking or advertising cookies.

What we don't do

  • We don't sell your data.
  • We don't use your registered text to train models without your explicit opt-in.
  • We don't scan your email or content for advertising.

Right to export (GDPR Article 20)

POST /api/user/export with your email triggers a verification flow. After you click the link in the email, you get a JSON dump of every submission, record, payment, entitlement, and source report tied to your email.

Right to be forgotten (GDPR Article 17)

POST /api/user/delete with your email + an emailed verification step erases your identity from every table we control. Concretely:

  • Removed: your name, email address, social handle, source links, and usage context across registrations and submissions; your email on any older-source or misattribution reports you filed; contact details on figure-quote suggestions; creator-verification rows (including any identity-evidence links) are deleted outright; the stored timestamp payload that named you is cleared.
  • Anonymized, not deleted: each registration survives as a tombstone. Its registration ID, content hash, registered-at time, collision lineage, and OpenTimestamps digest/proof stay public so the registry's timestamp chain remains verifiable — but the wording is withdrawn and nothing links the row to a person. Our ledger of your erasure request is kept with the email replaced by a one-way hash, so we can prove we processed it.
  • Retained for legal compliance: payment records (pseudonymous Stripe IDs and amounts — bookkeeping obligations, Art. 17(3)(b)) and DMCA takedown notices (defense of legal claims, Art. 17(3)(e)).

Data residency

Application data: Neon Postgres (US/EU regions, you can request migration). Hosting: Vercel (multi-region edge). Payments: Stripe (US/EU). All providers are GDPR-compliant.

Contact

Privacy questions, DPA requests, or data subject requests: psigho.business@gmail.com. We respond within 14 days.