Claim & review
An engineer has forwarded you a draft record built from their real systems — the structure, never the rows. This page is how you open it, sign in, and get your bearings — what the record shows, which calls are already made, and which are waiting for you. Reviewing needs no account; signing does.
What the engineer forwards
The engineer runs regixo invite on their machine. That produces two things they send
you, and nothing else leaves their machine but metadata:
- A draft PDF —
RoPA_DRAFT.pdf, a readable Record of Processing Activities you can open with no tools. It carries the DRAFT stamp and a “claim this in the portal” link. - A claim link — the same link, on its own, so you can open the live record in your browser:
https://app.regixo.com/claim/clm_<token>. The token in the link is the credential; whoever holds it can open the record.
Both point at the same record. The PDF is for forwarding and reading offline; the link is for filling and, later, signing. The engineer never had to create an account to send them.
Open the link and sign in
Opening the claim link lands you straight on the record — no login to look. When you are ready to change or confirm anything, you sign in with a one-time email link (a “magic link”):
How your team works this record: a viewer reads · a preparer fills · an approver confirms & signs · an admin manages the team.
Reading the draft needs no account — the claim link is enough. To change or confirm anything, press Email me a sign-in link: Regixo sends a one-time link, good for 15 minutes. Corporate mail scanners often open links first, so it lands on a Confirm it’s you page — press Continue to sign in → and you are in, with no password to set. The first person to sign in on a claim becomes the record’s admin. A tour: the compliance portal tour.
Signing in is a portal act — no terminal command signs a person in. The engineer’s side is
regixo invite to send the claim, and later regixo seal pull to bring
the sealed copy home.
An agent can read the draft over the read-only API, but it never signs in and never signs — signing names a verified person.
- Enter your work email. Regixo sends you a single-use sign-in link.
- Open the email, click the link, and you are signed in — no password to set or remember.
- Signing in creates your account, so the record you later sign carries a verified identity — the signature can name who you are.
What the record shows
The record opens as a finished-looking document built from the engineer’s real tables — not a blank form. Three things orient you:
- The activities — each thing done with personal data, grouped from the scanned tables, with the Article 30 fields. (What each field means: Understand the record.)
- A coverage meter — how much of the estate the draft is built on, stated plainly (for example, “18 of 22 datasets mapped · 5 of 6 sources reached”). A partial scan is honest about what it missed, never silent.
- Per-field badges — every field shows its state: auto-filled (Regixo measured it), suggested (a starting point to confirm), or needs you (only you can supply it). Special-category data is marked ⚠ Art. 9.
A short orientation block sits at the top of the claimed record, above the activities: what it is, where it came from, what is done and what is still blank — with a provenance line stating exactly what left the engineer’s machine, a coverage banner when a source could not be reached, and the counts:
- What this is — the list of how your company uses people’s personal data — the “Record of Processing” most EU organisations must keep.
- Where it came from — your engineering team mapped your real database with Regixo, which drafted this from your actual tables.
- What’s done — the data inventory is mapped for you.
- What needs you — 10 legal calls are still blank — security measures, recipients, purpose, your lawful basis and more. Your team fills them below; then you sign.
- Your privacy — metadata only (names, types, owners). No row values ever left your team’s machine.
- What’s not covered —
snowflake-dwh,stripe(unreachable at the last scan).
Forwarded draft — received 2026-07-10 · what left their machine: metadata only — 4 dataset names and types + 9 personal-data flags. No row values, ever. No account needed to review. · what changed → · who is Regixo? →
The same summary, as plain text:
Record of Processing Activities — DRAFT GDPR Article 30 · not defensible until your team confirms the legal calls and signs Coverage 18 of 22 datasets · 5 of 6 sources reached Auto-filled 23 mechanical fields Needs you 14 legal fields across 6 activities Special category 2 activities carry Art. 9 data
What to look for on first review
You do not need to read every field to know where you stand. On a first pass, check three things:
- The activities are right — the tables were grouped into activities that match how you actually work. Any grouping tagged “best guess — review” is one to confirm or split first.
- The outstanding legal calls — scan for needs you: the purposes, lawful bases, retention periods, recipients and security measures that are yours to make. These are the work of the next page.
- The sensitive data — any ⚠ Art. 9 or criminal-offence (Art. 10) activity needs a specific ground before the record can be signed. Start there; those are the strictest calls.