Last updated October 24, 2026
Rzume is built by Randes Digital Labs, a sole trader (eenmanszaak) registered with the Dutch Chamber of Commerce under KvK number 99694913 (VAT ID NL005404480B15), at Buikslotermeerplein 431, 1025 WR Amsterdam, the Netherlands. Randes Digital Labs is the controller of your data.
This page describes what happens to the things you give it. It is written to be read, not to be survived.
Your resume. The file you upload and the text extracted from it. We store it so you can come back to it, compare versions, and export it again without uploading twice.
Your career record. The answers you give when Rzume asks what changed, how long something took, or who used it. This is the part that makes the next resume quick.
Your account. An email address and a hashed password. Nothing else is required.
A review you started without an account. You can upload a resume and read the parse and the full review before you create anything. That work is held against a random identifier in a cookie your browser cannot read, and it is not linked to you until you create an account. See "How long we keep it" for how quickly it goes.
Basic usage counts. Which steps of the product you reached, so we can tell a broken step from an unpopular one. This is collected through a self-hosted Plausible instance, without cookies and without cross-site identifiers.
A resume often carries more than a work history. Trade union membership, a religious or political affiliation, a health condition, a disability, a photo: under the GDPR these are special categories of personal data and they need your explicit permission, not just a legitimate reason.
That is what the tick box on the upload screen is for. It is separate from the terms, it is not pre-ticked, and it covers only what your file happens to contain. The rest of the service runs on the ordinary basis of performing the contract you asked for, so withdrawing that permission does not delete your account by surprise.
You can leave those details out. Rzume works fine without them, and for several job markets it will tell you to remove them anyway.
We do not sell your resume. We do not send it to recruiters, job boards or staffing agencies. We do not train models on it.
We do not build an advertising profile of you, and we do not embed third-party tracking pixels.
The companies below handle your data. Each one does only the job listed next to it.
Anthropic (United States). Your resume text is sent to Anthropic's Claude models to be parsed, reviewed and rewritten. That is the core of what the product does, and it cannot happen locally. Anthropic processes the text to return a result and does not use it to train its models. Because Anthropic is in the United States, this is a transfer of personal data outside the European Union. It is covered by the EU Standard Contractual Clauses in Anthropic's data processing addendum.
DigitalOcean (AMS3 datacenter, Amsterdam, the Netherlands). Runs the Rzume API and the database. Your account, your career record, your reviews and the file you upload are stored there. Our self-hosted Plausible analytics runs there too. Your file is held in the database rather than with a separate file-storage provider, so there is one fewer place it can sit and one fewer company that holds it.
Vercel. Hosts the website and serves the pages you see. Requests pass through Vercel on their way to the API.
Stripe. Handles payment for paid plans. Stripe acts as the seller of record: it receives your email address, your payment details and the amount, and it handles invoicing and tax under its own privacy policy. Rzume never sees or stores a card number.
We do not use any other company to process your resume.
With an account: until you delete it. There is no silent expiry, because a career record that vanishes after a year would defeat the point of keeping one.
Without an account: 24 hours. A review you started anonymously is deleted a day after you started it, and the uploaded file is deleted with it. The file is stored inside the review itself, so nothing survives the review it belonged to. We keep it short on purpose: with no account there is no way for us to check that someone asking to see or delete that review is the person who uploaded it, and holding a stranger's resume against an identifier we cannot verify is not something we want to do for longer than the product needs.
If you create an account during that day, the review moves into it and the account rules above take over.
With an account: Settings has a delete button. It removes your account, your resumes and your career record immediately. It is not a request queued for review, and there is no retention email.
Without an account: the result screen has a delete control that drops the review and the identifier with it, straight away. You do not have to wait for the 24 hours, and you do not have to tell us who you are to use it.
Under the GDPR you can ask for a copy of your data, ask for it to be corrected, or ask for it to be erased. Email dev@codingspace.io and you will get a person.
If you think we have handled your data badly, you can complain to the Dutch data protection authority, the Autoriteit Persoonsgegevens.
If this page changes in a way that affects what happens to your data, the date at the top changes and we email account holders. We do not make quiet edits.