Last updated: 13 September 2026
Who answers, and how fast
A person. Register Radar is operated by its founder, an individual based in Spain, and the founder is who reads and answers — at contact@registerradar.com or through the contact form. The legal notice is where the operator is identified, and the name, tax ID and address lines there are still to be completed.
The written promise is the one on the contact page: a real reply within one business day. Our own working rule is tighter — a customer's message is answered within two hours of being read, any day of the week — but that is a rule we hold ourselves to, not a term you can invoke, and we publish the rule rather than a measured average because we have no measurement we could honestly name. There is no overnight desk, and the terms say plainly that there is no promised service level.
Where your data lives
| What | Where | Detail you can check |
|---|---|---|
| Database and sign-in | Supabase (Postgres), region eu-west-3 — Paris, EU | Row-level security is on with no public policies: without the server key, nothing is readable. That key lives only in the server's environment and never reaches a browser. |
| Website and API functions | Vercel — functions run in Sydney (region syd1) as of today | That is where your requests are served and where our API functions read the national register when you use the site. It is a project setting, not a commitment: if it ever changes, this line changes with it. |
| Zoho Mail, EU data centre | The emails our own code sends — scope alerts, confirmations, the deletion receipt — leave from mail.zoho.eu. The sign-in code is the exception: it is sent by our sign-in provider, Supabase Auth, not by our code. | |
| Billing | Stripe | Card details never touch us; the billing portal in your account is Stripe's own. |
Inside the database, these fields are encrypted with AES-256-GCM using a key held only in the server's environment: the unit-by-unit detail behind each per-learner result, the validation report of each upload, the notes you record against a learner, and the messages you send us from your account together with our replies. Those fields, in a copy of the database taken without that key, are bytes. Learner references, verdicts, counts, file fingerprints and account details are stored readable — we add no encryption of our own around them beyond the database provider's encryption at rest. It is real protection against a database leak; it is not absolute protection, and the privacy policy says where its limits are. The full table of what is stored, where, and for how long is there too.
What we hold about learners — and what we refuse
The paid engine takes a de-identified file, and the de-identification happens in your browser. You drop the export your student management system already produces; the browser keeps five columns at most — an opaque reference, the unit code, the outcome, the completion date and, when your export carries it, the qualification code — shows you exactly what will be sent, and sends nothing else. If the export has names but no reference, the browser makes references and offers you the name-to-reference map as a local download that never leaves your machine. A file that still carries a name, an email, a phone number, a date of birth, a USI or an address is rejected, and the message says which column.
If you drop the whole AVETMISS ZIP, only the NAT00120 is opened. The NAT00120 carries no learner name by design of the national standard; the files that do (NAT00080, NAT00085) are never decompressed — the ZIP's directory is read, the one entry is inflated, and the rest stay as they were.
The uploaded file itself is never stored: it is processed in memory and discarded when the request finishes. What is stored is each reference's computed result, with the file's SHA-256 fingerprint so you can prove which file produced which report.
How you take your work out
- The typing-order worksheet (CSV) — the result re-ordered the way it is keyed into a student management system.
- The SMS import (CSV) — the same rows with the AVETMISS national outcome code on each, ready for your system's import.
- The full record (CSV) — every learner reference with its verdict and its unit-by-unit detail.
- The dated, printable record at
/report/run— the document you hand an auditor: file fingerprint, when it ran, against which reading of the register, the verdict per learner and the log of decisions with their dates. - Your own de-identified file and, when the browser had to make references from names, the local reference map — both offered at upload time, before anything is sent.
Each CSV is generated in your browser from the report you are looking at — the server hands you the report, your browser writes the file, and the file is yours from that moment. There is no single "export everything" button today; files are downloaded one at a time, from the account or from a report. The terms put it in one line: your data stays yours — the file, every result computed from it, every action you record against it.
If you stop paying
- You cancel from the billing portal in your account at any time: the subscription stops renewing and runs to the end of the period you paid for, which is how the terms put it — either side ends a monthly arrangement at the end of the period. Within the first 30 days the terms let you ask for those days back.
- New uploads close. Everything you already generated stays in your account and stays downloadable — the dated working and the CSVs. Nothing is deleted because a subscription ended; a report is deleted when you delete it, or when you delete the account.
To delete your account, press the button in Settings. The endpoint behind it first tries to cancel any live subscription with our payment provider, then deletes your rows — watches, preferences, uploads and their results, your questions, your contact-form messages — then asks our sign-in provider to remove the login, and confirms by email. If that cancellation could not be completed, the confirmation email tells you so and what happens next. One declared exception: paid review documents stay as an accounting record, and the deletion email says so at the moment you delete. If you turn on the optional two-step verification, the code is asked for exactly where it matters: opening or downloading a student file, deleting the account, and creating an evidence link.
If Register Radar stops operating
Honestly: this is a service run by one person, and we would rather you plan around that than around a promise. What holds without any promise from us is the shape of the thing. Register Radar is never your system of record — the input is the export your student management system already produces plus the public national register, and the output is files you download. Nothing you need exists only here. The terms say your data stays yours, and the files on your machine do not depend on us being there.
Two things we do not promise, so that you do not assume them: we do not promise off-site backups of the database today, and we do not promise a notice period before a shutdown. The practical advice is the one we would give a friend: download the worksheet, the SMS import and the printable record when you produce them, and keep them with the evidence they belong to.
What this page does not claim
- No 24-hour desk, and no service-level agreement.
- No published availability figure — we do not measure one we could stand behind.
- No security certification of any kind.
- No claim here about the operator's legal form: it is operated by an individual; the legal notice is where the operator is identified, with its name, tax ID and address lines still to be completed.
If any of this changes, the date at the top changes with it. A test in our codebase checks that the files cited behind each line still say what this page says — a check on the citations, not a proof of the product.