Sell or share your profile
Not to recruiters, not to data brokers, not anonymised-and-aggregated.
SECURITY & PRIVACY
Your CV is the most
personal file you own.
It has your address, your salary history and every place you have worked. Here is exactly where it lives, who can see it, and how to make it disappear.
EU-only data residency GDPR · DPA on request Row-level isolation per account Deletion revokes shares immediately
WHAT WE NEVER DO
Four of them, and none are aspirational.
Press submit for you
The candidate reviews every field and submits on the employer's site.
Train a public model on your CV
Your history supports candidate-approved matching, drafting and interview coaching. It is not used to train a public model.
Let one account see another
Isolation is enforced in the database, not in the application layer.
SUB-PROCESSORS
Four, and where they are.
Customers are told before a fifth is added. The current list is here rather than behind a form.
EUWhere the data sits, not where the company is registered.
SupabaseDatabase, auth and private file storage
VercelApplication hosting and edge routing
Model providerCandidate-approved matching, drafting and coaching context
EU and USOne processor, one purpose, and only if you choose to pay.
StripePayments. It never sees your CV or your history
Grouped by region rather than listed alphabetically, because where the data sits is the only thing on this page a reader cannot work out for themselves. Names and purposes are in the DPA.
APPROVAL
Break it yourself.
Review Mode binds your approval to one exact version. Change a word and the approval is void and has to be given again, which is the only thing that makes a receipt worth anything.
31 · REVIEW-SEALApproval binds to one exact version
COVER LETTER · V4UNCHANGED
Six years in payments, most of it on the checkout itself. The line I would defend in the room is the drop-off rebuild.
Not approved. Nothing has been sealed or made available for candidate-operated autofill.
Approve the version on the left, then change one word in it. The seal breaks, and it breaks the same way every time — there is no setting that keeps an approval alive across an edit, because an approval that survives an edit is not an approval.
This is the version you approved. Nothing has changed since.
The processing terms live in the DPA, and the candidate-facing version is on Privacy.
THE RECEIPT ITSELF
Computed, not decorative.
A hash is the one claim on this page that does not need you to trust us. Anyone you hand it to can check it against the document.
12 · HASH-FORMINGComputed, not decorative
sha 4c1f…8ab2SEALED 07:48
Computed over the exact version you approved. Characters landing one by one is the difference between a receipt and a badge — a badge asserts, and a hash can be checked by anyone you hand it to.
Every approved packet carries one. It is computed over the exact bytes you approved, stored against your account, and shown to anyone you choose — a hiring manager, a recruiter, or nobody.
- Computed at approval, over that version only
- Checkable by whoever you hand it to
- Not a badge, and not issued by us as a verdict