This guide is the checklist, plus an honest description of how an EU-based setup answers it.
What happens to your CV in an AI tool
Many AI resume products follow some version of this pipeline: your file is uploaded to the product's servers, parsed into structured data, sent to a language-model provider for the AI steps (rewriting, tailoring, scoring), and the results are stored with your account. Each step is a place where jurisdiction, retention, and access rules apply.
None of this is sinister; it's how the products work. The difference between tools is whether they tell you clearly where the servers stand and what rights you keep. Parsing is also where layouts break, which how to pass an ATS in 2026 covers.
The five questions to ask any resume tool
- Where is my data hosted? A concrete country beats "the cloud". Hosting location is one of the things that shapes which rules and authorities apply.
- Who are the processors? The AI step usually involves a third-party model provider. A trustworthy tool names its processors in the privacy policy instead of hiding them behind "trusted partners".
- What is stored, and for how long? Especially for free/guest features: does a quick check mean your resume now lives on their servers indefinitely?
- Can I actually delete everything? Account deletion should remove your documents and data, and deactivating a login does not do that.
- Which rights do I have by law? Under the GDPR: access to your data, correction, erasure, export, and objection. These are enforceable rights, not policy promises.
If a tool's website can't answer these in plain language, that's the answer.
Why EU hosting changes the defaults
The GDPR can also reach non-EU services that offer goods or services to people in the EU (Article 3(2)), but enforcement and defaults can differ with geography. A tool built and hosted in the EU starts inside the framework: EU data-protection law is the home jurisdiction, the supervisory authority is European, and GDPR rights are the product's native language rather than a compliance retrofit.
For a document as personal as a resume, and for EU job seekers whose applications already live under European rules, that is a structural difference and more than a marketing sticker. The same logic applies to what goes on the page: see a photo on a German or EU resume and the GDPR clause on a Polish CV.
Want to see this on your own resume? Check it against a job posting, free and with no account.
How CVder is set up
CVder's setup, point by point:
- Hosting is in Germany. CVder's cloud hosting and database are with Hetzner in Germany, and the privacy policy says so.
- Processors are named. The AI processing step uses a named AI processor (OpenAI, USA, under a Data Processing Agreement), listed in the privacy policy.
- The free check doesn't keep your resume. The no-signup ATS resume check is paste-only, with no file upload. The text you paste is sent to OpenAI to be analyzed, for the duration of the request, and we do not store it beyond generating your result. We do keep one record of the check itself, including the score; after 30 days an automatic job removes the identifier and those details. If you leave your email for the full report, that email and your consent choice are kept until you unsubscribe or ask us to delete them.
- GDPR rights are supported: access, correction, deletion and export, and you can delete your account from Profile. Some data is kept for a limited time and the policy lists it: billing records for 7 years under Polish tax law, audit logs for 12 months, and encrypted database backups for up to 14 days.
- The privacy policy is written in plain language, and its complaint route is the Polish Office for Personal Data Protection (UODO).
What we deliberately don't claim: that data never touches a non-EU processor (the AI step uses a named US provider, OpenAI, and we say so), or that "EU-based" alone makes a tool trustworthy. It sets better defaults; the policy and the practice have to do the rest.