Production scaffold

Protocol Entrance

Google-free build
Personal data management

Where your records remember you.

open-record.org is built to help people cover every GDPR data request category. The first production vertical is intentionally narrow: CV to employer extraction, request authorization, manual review, delivery tracking, and secure reply storage.

Initiate DiscoveryAuthorize Identity
Readiness ledger
Prototype UX mappedSource reviewed
Production dependency postureNon-Google
Broad GDPR scopePreserved
Provider decisionPOC required
Outbound sendingManual review only
First vertical loop

Get my employment data back.

  1. 01Upload CV
  2. 02Extract employers
  3. 03Confirm companies
  4. 04Prepare request
  5. 05Authorize
  6. 06Manual review
  7. 07Send and track
GDPR verticals

Careers first, not careers only.

The product architecture must preserve Health, Government, and public benefit / civic evidence as planned GDPR request verticals.

  1. 01Careers
  2. 02Health
  3. 03Government
  4. 04Public benefit / civic evidence
Data Vault

Encrypted request evidence before broad timelines.

The V1 vault is scoped to CV processing artifacts, authorization forms, employer replies, attachments, downloadable exports, and the evidence-pack model that later verticals will reuse.

Billing

Quotas and plans without bulk-send incentives.

Billing stays in the shell for private beta readiness, but every outbound request still requires identity readiness and manual approval.

Chat

Provider-neutral Article 15 guidance.

The assistant can return later behind the LLM abstraction. It must avoid visible Gemini/GCP ties and make only implemented privacy claims.