Answer your part & forward the draft
The map is built and the record is drafted. Two things are left before it leaves your hands: answer the three fields only your side knows, then forward the draft to your compliance team. This is the hand-off — the moment your part ends and theirs begins. Do it well and the draft arrives trusted; rush it and it arrives with a question mark.
Land here from: Enrich & share (the map is as complete as you can make it), or straight from first run if you just want to hand it over. New to how the two roles split? Understand the record shows the whole picture.
1 · Answer your part — three facts only you know
Open the record and Regixo puts your three questions in one place, called Your part: who receives this data, whose data it is, and how it is protected. Your compliance team cannot answer these — they are facts about your systems. Leave them blank and they reach the compliance team as gaps, whose only fix is an email back to you. Answering takes about a minute.
$ regixo open # then Record → Your part
Run this one yourself, not through your agent — regixo open is a server that keeps running until you press Ctrl+C, so give it a terminal of its own. Then pick your answers and Save.
Three quick facts only you can give
Your compliance team can’t answer these — they’re facts about your systems, and you know them. About a minute, then they travel with the record.
Why is this mine, not my compliance team’s?
Regixo’s record captures ten things per activity. Seven are legal calls your compliance team makes — Regixo never makes one. Three are facts only your engineering team knows:
- which outside services get a copy?
- whose data is it?
- how is the data protected?
Leave them blank and they reach your compliance team as gaps — and the only way to close one is an email back to you.
Who receives this data?
Needs youOutside services that get a copy of personal data. Regixo found no outside services among your connected sources, so name anyone outside your company who receives a copy.
One answer fills all 4 blank activities at once.
Answer once — set an exception only where an activity differs
Each question is answered once and applied to every activity still blank — “One answer fills all 4 blank activities at once”, as the card says. A general answer is all Article 30(1)(g) asks for, not a per-table one. Where one activity genuinely differs — say only your payments activity shares with Stripe — open Set an exception under the shared answer and scope that one recipient to that one activity. Everything else keeps the answer above; nothing is hidden — every activity is listed, so you can see what you set and what you didn’t.
These three are yours to set, not your agent’s — a record field is only ever set by a
person (Hard Rule #4). Pick them in the portal — pick, don’t
type — and Save. Prefer the terminal? regixo annotate set writes the same answer, one
field at a time.
$ regixo annotate set <activity> recipients "Stripe" $ regixo annotate set <activity> dataSubjects "Customers" $ regixo annotate set <activity> securityMeasures "Encrypted at rest and in transit; access controls"
Run this one yourself — setting a record field is a person’s act, so there is no “say it to your agent” form. It writes your answer as provided, never confirmed: the free portal has no confirm control, so it cannot cross that line. Check it with regixo annotate list.
2 · Forward the draft — the warm way
Your compliance team meets Regixo for the first time through what you send. A bare
localhost link and the word “sign” can read like phishing to someone who did not
install anything. So send it in two moves: a briefing they can read with no account and no risk,
then the claim link that lets them act.
First, the briefing (optional, but it converts)
regixo share writes a single self-contained HTML file — no server, no link, nothing
to trust — that explains what Regixo is, what left your machine (nothing but structure), and what
the record is. It answers the “can I trust a machine-made record?” question before the ask arrives.
“Use Regixo to write my data map to a single HTML file I can send to my team.”
Show the commandHide the commandShow the sentenceHide the sentence
$ regixo shareThen, the claim link — and exactly what leaves your machine
regixo invite is the upload that starts the hand-off (watch, push and
start also upload, and only when you run them on a paired machine). Before anything moves it
shows you the exact payload — the same list, word for word, that your compliance team sees on the
other side. It is metadata only: counts and table paths, never a row, never a column name,
never a value.
Before this leaves your machine
Making an invitation is the only upload you start by hand. Nothing moves until you press the button at the bottom.
What goes
- Table names7
The full path of each table that looks like it holds personal data — source, schema, table. For example
app-db/public/event_logs. - The kinds of personal data found
The categories the classifier worked out from your column names —
Email,Name— listed per activity. Never the column name itself. - The drafted record Activity titles and Regixo’s suggested legal fields, and your organisation’s registered name.
- The address you type belowif you fill it in Exactly as you type it — not hashed, not masked, because that is what binds the record to that person. Leave it blank and no personal data goes at all.
What never goes
- Your dataNot one row, not one value, not ever — Regixo has never read one.
- Your column namesThey do not leave the machine at all. The portal learns a column looks like an email address without learning what it is called.
- Credentials & connection detailsThey stay in your environment. Regixo never puts a secret in anything it uploads.
- Column typesThe portal never learns whether a column is text, a date or a number.
- Table ownersThe catalog records who owns each table. None of that is in the upload.
Apart from that address, everything else is a count, not a name — 2 sources · 7 datasets · 12 columns that look like personal data.
“Forward my Regixo draft record to our compliance team. Show me what would be uploaded before you send it.”
Show the commandHide the commandShow the sentenceHide the sentence
$ regixo inviteYour agent prints the exact payload, then asks before uploading. It uploads the
metadata-only snapshot and writes RoPA_DRAFT.pdf (with the claim link inside it) and
snapshot.json. Name a recipient with --email and it also writes
email.txt and invite.eml (the PDF already attached); leave it out and it does not.
Check it worked:
show the checkhide
This forwards a copy of your one compliance record — forward it to your compliance team (no account needed from you):
DRAFT PDF: .regixo/invite/RoPA_DRAFT.pdf (forward it today — it carries the claim link)
claim link: https://app.regixo.com/claim/clm_… (uploaded — this link now works; your compliance team opens it and unlocks there)
Regixo emails nobody — you forward it yourself.REGIXO_PORTAL_URL and the link
lands there, so it opens off your machine. The default host, app.regixo.com, is wired and
offline-tested but not switched on yet.
Either way the preview shows the real destination so you never paste a dead
localhost link into a chat. If an upload is declined or fails, Regixo still writes a
link but marks it plainly as not a working hand-off — it will not offer a dead link as if it
were live.What it will cost them — so you can answer
Reading and sharing the draft is free forever. The paid step is your compliance team’s: unlocking the signed, defensible, kept-current version. So you can answer “what does signing cost?”, the published prices are €6,000 / year for the RoPA, €12,000 / year with the DORA register, and from €18,000 for larger organisations. They see the exact figure on their own unlock screen; you never handle a payment or a key. (The full pricing and what paid adds →)
How you know your part is done
You are finished when both are true: your three answers are saved (the record shows no open Your part gaps), and the claim link is with your compliance team (your Overview card reads “✓ Forwarded — now it's with your compliance team”). That is your whole part — the legal calls and the signing are theirs. The only thing left for you is to keep the record fresh as your schema changes (the next page).
You send: the briefing (optional) and the claim link. They receive: a link that needs no account and no install — they open it, sign in with a one-time email link, and see a finished-looking record built from their own systems, with your three answers already in it and the gaps you left clearly marked as “waiting on your engineering team”. They do next: make the seven legal calls, then sign. What you don’t do: make any legal call, or pay — those are theirs. If they need a system you couldn’t reach re-scanned, that request comes back to you (keep it current covers re-scans).