Regixo docs
Get help
EU compliance · optional · walkthrough · the compliance team

The compliance team

An engineer forwarded a draft record built from their real systems. This is the whole compliance-team side, in one sitting: open the link, sign in, add a colleague, make the legal calls, then make the record official under a named person. Reading needs no account — only filling and signing need a session.

Optional · EU compliance module You need this only if your company must keep a GDPR Article 30 RoPA or a DORA register — it is an optional module on top of the free data catalog. If that is not you, you can skip this section.
What you need The claim link and the RoPA_DRAFT.pdf your engineer sent — nothing to install. Screens below are static examples of what you'll see, not live widgets.
1
The email arrives compliance
Your engineer's message carries two things: a RoPA_DRAFT.pdf and a claim link — app.regixo.com/claim/<token>. Open the link.
The PDF opens with no tools and carries a DRAFT stamp; the link opens the same record, live, in your browser. Both point at one record — the PDF is for reading offline, the link is for filling and, later, signing.
Next: land on the record.
2
Land on the record — not signed in
The link drops you straight onto the record. No login to look. Read the header first: it tells you what this is, where it came from, and what is left.
what you'll see — landing on the claimed record, not signed in · the header block: what this is, where it came from, what is left, and what left the engineer's machine
Regixo compliance portal · EU-hosted
Your GDPR Article 30 Record of Processing — drafted from your own systems.
  • 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? →

2
sources connected · 2 unreachable
4
datasets mapped
4
hold personal data
10
legal calls still blank — yours to fill
A finished-looking document built from your engineer's real tables — not a blank form — with a provenance line that states plainly what was uploaded: metadata only, no row values.
Full detail: Claim & review →
3
Sign in to fill
Reading the record never needs an account. To change or confirm anything, press Email me a sign-in link and enter your work email. Regixo sends a one-time link — no password to set. Opening that link does not sign you in on its own: it lands on the small page below, which names the address you are signing in as and waits for you to press Continue to sign in →. That extra press is deliberate — corporate mail scanners follow links, and a scanner must not be able to consume your sign-in by opening the mail.
what you'll see — verify it's you (the one-time email link's confirm page)
Regixo compliance portal

Confirm it’s you

You’re signing in as d•••@acme.eu. One click and you’re back on your record.

Didn’t request this sign-in? Close this tab — the link works once and expires 15 minutes after it was requested; nothing has happened yet.

Corporate mail scanners open links, so a click lands first on a Confirm it's you page — pressing Continue to sign in → is what actually signs you in. The first person to sign in on a claim becomes its admin.
Next: bring in a colleague.
4
Add a colleague
From the Team card, press Send invite (they join as a viewer by default), enter their email, and set their role to preparer so they can fill the draft.
Roles are per record, never global: a viewer reads · a preparer fills · an approver confirms and signs · an admin manages the team. A preparer's work saves as provided by you, never as a confirmation.
Full detail: The compliance portal — team & roles →
5
A preparer fills a legal call compliance
Open an activity, check the Still needs you index, and on the lawful-basis row click + Fill this. Pick a ground, or type your own.
what you'll see — the compliance portal · the claimed record: a preparer fills a legal call
Regixo compliance portal · EU-hosted

Record of Processing Activities

DRAFT · not yet defensible
  • Marketing & email outreachusers
    Regixo found: contact, account, consent · suggested basis Art. 6(1)(a) consent suggested
    ✓ Mapped — review the suggested legal calls before signing.
    Activity detail & gaps
    PurposeSend product and marketing email to customers who opted in. suggested
    + Fill this

    Saves as provided — your approver confirms it (a person, never Regixo).

    Personal datacontact, account, consent found
    Data subjectsCustomers suggested
    + Fill this

    Saves as provided — your approver confirms it (a person, never Regixo).

    RecipientsStripe found
    + Fill this

    Saves as provided — your approver confirms it (a person, never Regixo).

    Lawful basisThe person agreed to it.Art. 6(1)(a) consent suggested
    + Fill this

    Saves as provided — your approver confirms it (a person, never Regixo).

    Retention2 years suggested
    + Fill this

    Saves as provided — your approver confirms it (a person, never Regixo).

    A person confirms legal fields — not Regixo. Purpose, lawful basis, retention and recipients are legal calls only your compliance owner makes. Regixo drafts them from your data; a person reviews and signs. This part isn’t yours to finish.
The value is filled, badged provided by you, and the activity leaves the Still needs you list. Special-category rows also ask for an Art. 9(2) ground.
Full detail: Fill the RoPA →
6
The gaps shrink
Work down the Still needs you index — every activity with an open field is listed, so nothing is missed.
As the calls get filled and confirmed, the index heading moves through three honest states: Still needs you → Awaiting confirmation → Nothing still needs you. You always know exactly where the record stands.
Next: an approver confirms.
7
An approver confirms compliance
An approver opens each filled row and ticks the confirm checkbox: Confirm as legally reviewed — your act as approver; Regixo never confirms a legal field for you.
A confirmed field records who confirmed it and when. If your organisation isn't named yet, you're asked for the controller's registered legal name — a record of processing must identify the controller (GDPR Art. 30(1)(a)), and Regixo never guesses it.
Machines suggest, humans confirm Regixo never sets a legal field to “confirmed” on its own. Purpose, lawful basis, retention and transfers are legal judgments — the tool suggests and sanity-checks; a named human confirms. A confirmation must carry the name of the person who made it (REGIXO_SIGNER_EMAIL; without it you get SIGNER_REQUIRED), and a confirmed answer that names nobody is refused outright — ROPA_CONFIRM_UNATTRIBUTED — even on import. No agent may confirm on your behalf: the read-only MCP server has no tool that could, and no agent sentence is offered for the command that does.
8
Make it official
Open Make this record official. It runs in four steps — Review & fill, Choose your plan, Verify it's you, Sign & seal. Step 1 shows how many calls are confirmed; Step 2 asks two questions to set your price.
what you'll see — Make this record official · the four steps (close-up)

Review & fill the legal calls

1 of 16 confirmed — 10 blank · 5 awaiting confirmation. Review & fill →

You can seal with open calls — they seal as flagged gaps, clearly listed before you sign.

Choose your plan

Your plan is set by the licence on this record — nothing to choose or pay. Verify and sign below to apply it.

Verify it’s you

Signing is a legal act under your name, so we confirm your identity once — with a one-time email link. Reading this record never needs an account.

Works once, for 15 minutes — no password, no account form.

Sign & seal

Verify your email in step 3 first — the seal records who signed.

Nothing new leaves your systems when you sign — signing only seals what you already see on this page.

The published price appears from your two answers — never guessed from your scanned data. Yes to the financial-firm question adds the DORA register (€12,000/yr); More than 250 routes to Enterprise — from €18,000/yr, invoiced, price published.
Next: pay.
9
Pay
Press Continue to payment (card, via Stripe). A leave page explains you'll enter your card on Stripe's secure page — Regixo never sees or stores them — and come straight back.
illustration — back from Stripe · payment received & receipt (this one screen is drawn from the spec, not captured from the product: it exists only after a real card payment returns from Stripe)
Regixo compliance portal · EU-hostedDana Kessler · approver · sign out
PlanRoPA · Article 30 official record
Billed yearly€6,000 / year
✓ Payment received. Your licence is active until 5 July 2027.

The DRAFT stamp comes off when you sign. A receipt is on its way to dana.kessler@acme.eu.

Receipt

PlanRoPA · Article 30 official record
Billed€6,000 / year
Licence valid until5 July 2027
Charged€6,000.00 · VAT €0.00 (reverse charge)
RecordAcme Europe BV · a1f3c9e2b7d4…
↓ Download invoice (PDF)Invoice & VAT receipt issued by Stripe.
On return you see ✓ Payment received — activating your licence…, then a receipt with a downloadable invoice. The €6,000 and €12,000 tiers close with a card, no salesperson.
What works today Stripe checkout is wired and offline-tested; the live card-payment run is a launch gate. Until it runs, a licence is provided by Regixo on invoice — the sign & seal path below is the same either way.
10
Verify & sign
Step 3 is Verify it's you; Step 4 is Sign & seal. Press 🔓 Sign & seal this record as <name> and read the Before you sign page.
what you'll see — Before you sign (the confirm-before-irreversible page)
Regixo compliance portal · EU-hosted

Before you sign

You are about to sign and seal this record as dana@acme.eu (dana@acme.eu). This removes the DRAFT stamp and records a simple electronic signature (eIDAS Art. 25(1)) under your name.

What kind of signature is this?
  1. It is a simple electronic signature. Under EU law (eIDAS Art. 25(1)) it cannot be denied legal effect, or refused as evidence, solely because it is electronic. It is not a qualified electronic signature — that needs a government-issued certificate Regixo does not require.
  2. The time comes from our server's clock. That records when you signed. On its own it is not an independent timestamp.
  3. An independent counter-stamp adds more. Where one is configured, a third-party timestamp authority stamps the signature, proving it existed no later than that moment — still not an eIDAS qualified timestamp, but no longer resting on our clock alone. Your sealed record names which one it carries.
You are RE-sealing — 1 activity changed since the seal of 2026-03-14:
  • Marketing & email outreach — personal data categories

The previous seal stays in the version history; re-signing seals the record as it stands now.

Regixo could suggest a value for every legal entry — review them before you seal; they record as suggestions for your confirmation, and the seal never confirms a legal entry for you (a person must).

Nothing new leaves your systems when you sign — signing only seals what you already see.

Controller: Acme Europe BV (GDPR Art. 30(1)(a))

Go back and keep reviewing
Records render in English; a localized render is on the roadmap where a supervisory authority expects it.
The page states exactly what signing does: it removes the DRAFT stamp and records a simple electronic signature (eIDAS Art. 25(1)) under your name. It is not a qualified electronic signature. Confirm, and the record flips to OFFICIAL. Only an approver or admin can sign.
Next: the sealed record.
11
It's OFFICIAL
The record is signed. The DRAFT stamp is gone, and a seal block lays out the signature facts.
what you'll see — the OFFICIAL seal on the signed record (close-up)

✓ Audit-ready · sealed 2026-03-14

● OFFICIAL — signed & sealed

  • Who signed — dana@acme.eu (dana@acme.eu), on 2026-03-14T00:00:00Z. Identity verified by email sign-in link (magic link).
  • Timestamp — vendor clock only — n.
  • What kind of signature — A simple electronic signature. Under eIDAS (Art. 25(1)) it cannot be denied legal effect solely because it is electronic. It is not a qualified electronic signature.
  • Tamper-proof seal — Locked: any later edit re-opens the signature. Anyone can check it’s genuine offline, without contacting us — see “Technical details”.
  • Your record — Plan ropa · valid until 2027-06-01. Manage billing →
Technical details (for your auditor)

Content seal sha256:h — any later edit re-opens the signature.

Attestation att_bbbbbbbbbbbbbbbbbbbbbbbb · key k · tenant t1.

Verifiable offline: run node verify-attestation.mjs next to the exported attestation.json (key published in ATTESTATION_KEYS.md).

This attestation states a mechanical fact: the auto-filled fields were sourced from the connected systems as of 2026-03-14. The legal fields (purpose, lawful basis, retention, transfers) carry the judgment of the named signatory, who confirmed and signed them. This document is not legal advice.

Download the official PDF
The seal names who signed in full capacity — name, role, organisation — carries a content seal over the exact record bytes, and ships with an offline verifier so anyone can check it without Regixo. That is the defensible record.
Full detail: Unlock, sign & maintain →
Honest about what's live Reading is free and account-free; only filling and signing need a session. The fully hosted portal at app.regixo.com and live card payment are launch gates, not yet switched on — but the forwardable DRAFT PDF and claim link work today, and the fill, confirm, sign and seal path is built. Where a licence is needed before the live-Stripe run, Regixo mints one on invoice.
← Back
Your first session