01
Trace
Build your private data map.
Add services and accounts you recognize. Review every suggested relationship before it becomes part of your map.
Private beta
Find where your personal data lives. Decide what happens next.
open-record.org helps you map likely data holders, review a scoped rights request, and organize what comes back—without turning your legal power into hidden automation.
Review comes first. Requests are not sent without your approval and operator review during the private beta.
Your data map4 to review
Apps & platformsRetail & servicesFinance & public bodiesWork & organizations
Before anything is sentYou review the exact action
Built for people—not privacy departments.
- You confirm every relationship
- You review every request
- Returned files stay private
Trace · Mandate · Reveal
One understandable step at a time.
Start with what you know. Build confidence before taking action. Keep the result useful after the legal request is over.
02
Mandate
Choose one clear action.
See the organization, route, scope, and exact request. Decide whether to approve it or leave it alone.
03
Reveal
Make sense of what returns.
Keep the evidence, returned files, deadlines, and next steps together in a private, reviewable workspace.
Inbox access is not required to start. The beta begins with services, domains, and account details you choose to add or confirm.
A real first journey
From one remembered account to one reviewed request.
The beta is designed around a deliberate first success—not a wall of accounts or a burst of legal emails.
- 1Add what you already know
Start with a service, account email, or domain. Inbox access is not required to begin.
- 2Confirm the relationship
See why an organization appears and decide whether it really belongs in your data map.
- 3Review the request
See the holder, route, wording, and scope. Nothing is sent until you have reviewed and approved the exact action.
- 4Follow the response
Track replies, proof requests, portal steps, deadlines, and returned records without losing the evidence trail.
Request previewTravel serviceYour review
What you are asking forAccess to account and travel records
RouteVerified privacy email
Identity evidenceNot included
Next actionReview wording and approve
Example interface. Approval is scoped to one holder and one request.
Your control
A legal right should not require blind trust.
Every screen should make four things clear: what is happening, why it matters, what is uncertain, and what you can safely do next.
You confirm the map
A suggestion is not treated as truth. You decide which relationships are real and worth acting on.
The request stays available
You can open the case text and delivery details before choosing. A single confirmation surface is still being refined during the beta.
Proof should be explained
The current beta uses a manual identity check before supported sends. Identity documents are kept out of request emails by default while route-specific proof is developed.
You keep the evidence
Requests, replies, delivery events, files, and decisions remain connected to one understandable case history.
Privacy boundaries
Useful enough to act. Restrained enough to trust.
open-record.org is built to coordinate your rights—not to create another invisible profile about you.
Read the privacy notice- Your data map starts with relationships you add or confirm.
- Requests are reviewed before they are sent.
- Raw identity documents are not attached to requests by default.
- Returned records are not used for advertising.
Private beta, honestly
What the product helps with—and what it does not pretend.
Personal-data rights are real, but the routes are messy. The product should remove effort without hiding that reality.
Carefully reviewed betaLimited access while routes and safeguards are proven
Different organizations use different routes.
Some reply by email. Others require an account portal, a direct confirmation, or delivery to you instead of open-record.org.
A mandate is scoped authority—not a master key.
An organization may still ask to verify you or open-record.org before it releases sensitive information.
Returned data comes before clever insights.
The first job is to preserve what arrived, organize it safely, and show what is missing or uncertain.
The first beta promise
One person. One reviewed action. One visible evidence trail.
No bulk-send incentives. No guarantee that a holder will comply. No suggestion that open-record.org replaces legal advice or an organization's secure delivery process.
Research & perspective
The 168-Account Citizen
A visual essay about the ordinary digital relationships that leave fragments of a person's life across apps, institutions, services, and archives.
“168” is an illustrative lens for thinking about a scattered footprint—not a promise that every person has the same number of accounts.
Read the visual essayQuestions
The useful details, without the legal fog.
If something feels unclear, the product should say so before asking you to act.
Is open-record.org only for employer data?
No. Employers are one kind of data holder. The broader goal is to help you understand and act across platforms, services, brokers, financial providers, public bodies, retailers, former accounts, and other organizations that may hold or infer information about you.
Does open-record.org send requests automatically?
No. The private beta is built around review. You should be able to see the holder, route, request, scope, and any proof involved before an action is approved. Bulk or hidden sending is not the product model.
Will I always need an identity document?
In the current private beta, an identity document is required before a supported request can proceed. It is not emailed to data holders by default. The intended proof ladder is route-specific and starts with less intrusive options where a holder can accept them.
Where is my information stored?
Account, request, reply, and returned-file storage is configured for EU residency. The current private beta uses a controlled US-based subprocessor for identity-document field extraction if you upload an ID. The privacy notice explains each provider and data location.
What if an organization will not send data to open-record.org?
That can be a valid security decision. The workflow should support delivery to your own account, a secure organization portal, or another route you approve. open-record.org coordinates the process; it does not claim every organization must deliver into its vault.
Is this legal advice?
No. open-record.org helps make personal-data-rights workflows understandable and reviewable. It does not replace independent legal advice, and it cannot guarantee how an organization will respond.
Private beta
Start with one relationship you want to understand.
Help shape a calmer, more trustworthy way to exercise personal-data rights across the internet.