Privacy policy
Your CV is personal. Here is what Umon holds, why, for how long, and what you can ask of us.
Last updated 20 September 2026
Umon is made by 99six. Legal entity: Dryn B.V., KVK 97899321, Oude Haagweg 46 E, 2552 EP Den Haag, BTW NL868281104B01. Contact [email protected].
What this page covers
This page explains what happens to your personal data at Umon. It covers two things, and they are very different in size.
- This website. Reading umon.io collects nothing about you. Section 3 has the detail, and it is short.
- Your Umon account. Once you build a profile, Umon holds your CV and your career history. Sections 4 onwards cover that in full.
Throughout, “personal data” means any information that identifies you, and “processing” means anything we do with it: collecting it, storing it, using it, sharing it or deleting it.
Who we are
Umon decides why and how your personal data is used, which under Article 4(7) GDPR makes Umon the controller of it. That is the registered company named in the imprint at the top of this page, not the Umon brand on its own. If you want to know what we hold, change it or have it deleted, we are who you ask.
Umon is the product. 99six is another name the same team trades under, used for its wider development work, so a message from us can arrive from either name. It is a trading name rather than a separate company, so your data stays with the controller named in the imprint and goes nowhere else.
Privacy questions and data requests: [email protected]
Everything else: [email protected]
Reading this website
You can read every page on umon.io without telling us anything. This website has no account, no contact form and no newsletter sign-up. It sets no cookies, runs no analytics, and loads no fonts, scripts, images or embeds from anyone else, so no third party sees your visit either.
Our web host records the usual server logs, which include the IP address a request came from. Those exist to keep the site up and to spot abuse, and we use them for nothing else. The cookie notice sets this out in full.
The moment you choose to start a CV, you move to the Umon product and create an account. From there on, the rest of this page applies.
What your account holds
We collect what the service needs to work and stop there, which is the data minimisation principle in Article 5(1)(c) GDPR. In practice that is:
- You. Name and email address. Optionally a phone number, date of birth and a profile photo, if you add them.
- Sign-in. Your password, kept only as a bcrypt hash. Session and refresh tokens. Google account identifiers, if you sign in with Google.
- Your CV. Employment history, education, skills, certifications, languages and achievements. Uploaded CV files and supporting documents. Salary details, if you choose to enter them.
- Your search. Applications you track, vacancies you save, match results, and interview practice sessions you record.
- Your device. IP address, browser and device information, sign-in timestamps, and a log of actions taken in your account. This is what lets us spot someone else using it.
- What Umon works out. Skills read from your CV, learning suggestions, and the numerical representations used to compare your profile with vacancies.
- Billing. Your plan, your Stripe customer reference, billing email and country. Card numbers are collected and held by Stripe in their PCI DSS certified environment, and never reach us.
- Organisations. Which organisations you belong to, your role in them, and invitations you sent or accepted.
Why we hold it, and the legal basis
Article 6 GDPR says personal data can only be processed on one of a fixed list of legal bases. Here is the purpose and the basis for each thing we do.
- Running the service (your CV, exports, applications): performance of a contract, Art. 6(1)(b).
- Signing you in and keeping the account safe: performance of a contract, Art. 6(1)(b), and our legitimate interest in account security, Art. 6(1)(f).
- AI features (CV tailoring, interview practice, learning suggestions): performance of a contract, Art. 6(1)(b). They are part of the service you sign up for.
- Service email (verification, password reset, receipts): performance of a contract, Art. 6(1)(b).
- Marketing email: your consent, Art. 6(1)(a). Withdraw it at any time from the unsubscribe link or your account settings.
- Product analytics: your consent, Art. 6(1)(a), asked for before any analytics cookie is set. It stays off until you turn it on in your account settings, and you can withdraw that consent there at any time.
- Preventing fraud and abuse: our legitimate interest in protecting the service and the people on it, Art. 6(1)(f).
- Legal obligations (tax records, court orders, regulator requests): compliance with a legal obligation, Art. 6(1)(c).
AI, and the decisions that stay yours
Umon uses AI to write and score CV content, suggest learning paths, prepare interview questions and rank vacancies against your profile. Everything it produces is a suggestion for you to read, edit, accept or throw away.
No decision with a legal or similarly significant effect on you is taken by automated means alone, in the sense of Article 22 GDPR. Hiring decisions are taken by employers. Career decisions are taken by you.
AI can get things wrong and can invent detail that was never in your CV. Read anything it writes before you send it to an employer. Your CV and your profile are never used to train third party AI models without your separate, explicit consent; the terms say the same. You can object to AI based processing at any time by emailing [email protected].
Who else sees your data
Your data is shared only with the companies below. Most work under a written data processing agreement as required by Article 28 GDPR. Two do not: Telegram, which only receives an alert when something in the service fails, and Google Fonts, which only serves typefaces inside the Umon product, never this website. We name them anyway, because Article 28(2) means you can only object to a sub-processor you can see. Your data is never sold, rented or traded, and CV content is never shared for advertising.
| Company | What it does | What reaches it | Where |
|---|---|---|---|
| Neon | The database that holds accounts, CVs and workspace records | Everything an account or workspace stores | EU |
| Oracle Cloud | The servers the Umon application runs on | Everything, while the service runs | EU |
| Cloudflare | The network edge: TLS, protection against attacks, content delivery | Every request, including the IP address it came from | Worldwide, handled at the nearest location |
| Stripe | Payments and subscriptions | Email, name and billing details; card numbers stay with Stripe | EU and US |
| Resend | Service email, and marketing email where you have consented | Email address, name and the message itself | EU and US |
| PostHog | Product analytics, switchable off in account settings | Usage events and the account identifier | EU |
| OpenAI | The language model behind CV writing, tailoring, interview practice and voice transcription | CV text, prompts and interview audio | US |
| Google (Gemini) | The language model behind skill extraction, matching and learning suggestions | CV and vacancy text | US |
| Anthropic | An alternative language model provider | The same CV and profile text | US |
| Google (sign-in) | Signing in with a Google accountOnly if you choose to sign in with Google | Name, email and Google account ID | US |
| Google Calendar | Creating interview events in a connected calendarOnly if an organisation connects its calendar | Event details and attendee email addresses | US |
| Microsoft 365 | The same, for a Microsoft calendarOnly if an organisation connects its calendar | Event details and attendee email addresses | US |
| Telegram | Alerts to our own operators when something in the service failsOnly while operator alerting is switched on in our deployment | Your email address and name, inside the alert text | Outside the EU |
| Google Fonts | Delivers the typefaces the Umon app usesEvery visit to the Umon app, never this website, which serves its own fonts | Your IP address and browser details, when a page loads | US |
Authorities are the one thing that table leaves out. Tax authorities, courts and law enforcement can receive personal data where the law requires us to hand it over. They receive it as authorities, which is a different thing from a company processing data on our instructions.
Data that travels outside the EEA
The companies in the table above that process personal data outside the European Economic Area are Cloudflare, Stripe, Resend, OpenAI, Google (Gemini), Anthropic, Google (sign-in), Google Calendar, Microsoft 365, Telegram and Google Fonts. When personal data leaves the EEA we rely on one of the safeguards in Chapter V GDPR:
- the European Commission’s Standard Contractual Clauses, Module Two, controller to processor;
- the EU US Data Privacy Framework, where the company is certified under it;
- any other safeguard recognised under Art. 46 GDPR.
Ask us for a copy of the safeguards that apply and we will send them. Email [email protected].
How long we keep it
Data is kept for as long as the purpose it was collected for lasts, and then it goes.
- Your account and CV content: for as long as your account exists.
- After you delete your account: 30 days, during which you can change your mind and restore it. After that it is permanently deleted and cannot be recovered.
- Activity and session logs: 13 months, for security and fraud prevention.
- Record of the terms you accepted: 6 years, as evidence of consent.
- Billing and invoices: 7 years, which Dutch tax law requires (Algemene wet inzake rijksbelastingen, Art. 52).
- Support conversations: 24 months from the last message.
- Backups: overwritten on a rolling cycle, and never restored to bring deleted data back.
Your rights, and how to use them
Under the GDPR you have all of the following, free of charge.
- Access. Get a copy of the data we hold about you. Art. 15.
- Rectification. Correct anything inaccurate or incomplete. Art. 16.
- Erasure. Have your data deleted, subject to the retention periods the law requires of us. Art. 17.
- Restriction. Have us pause what we do with it, in certain situations. Art. 18.
- Data portability. Receive your data in a structured, machine readable file. Art. 20.
- Objection. Object to processing based on legitimate interests, including profiling. Art. 21.
- Withdraw consent. Where we rely on consent, withdraw it at any time. Anything done beforehand stays lawful. Art. 7(3).
- Complain to a regulator. In the Netherlands that is the Autoriteit Persoonsgegevens, autoriteitpersoonsgegevens.nl. You can also go to the authority in the country you live in. Art. 77.
Two of these are buttons rather than emails: you can export everything you have, and delete your account, from your account settings whenever you like. For anything else, email [email protected] and we reply within one month, which is the deadline Art. 12(3) GDPR sets.
How your data is protected
We apply technical and organisational measures in line with Article 32 GDPR. The main ones are worth naming.
- TLS 1.2 or better for everything in transit, so traffic is encrypted end to end.
- Passwords stored only as bcrypt hashes, never as text anyone could read.
- Parameterised database queries, which close off SQL injection.
- Authentication cookies marked HttpOnly, Secure and SameSite.
- Strict separation between organisations, so every query is scoped to yours.
- Signature checks on every incoming webhook.
- Rate limiting on sign-in and registration.
- Continuous dependency and security scanning, reviewed regularly.
- Internal tools locked down by role, on a need to know basis.
If a breach ever happens and it is likely to put your rights at risk, we notify the supervisory authority within 72 hours as Art. 33 requires, and tell you without undue delay where Art. 34 applies.
Where the data comes from
Almost all of it comes straight from you, when you create an account, build your CV or use the service. Sign in with Google and we also receive your name, email and Google account ID from Google. Accept an invitation from an organisation and we receive your email address and role from the account that invited you.
One small set of data has a different origin, and section 14 sets it out in full because Article 14 GDPR requires that.
Recruiter contact details from public job adverts
This section is for recruiters and recruitment agencies. It covers a separate, small set of contact details that did not come from you. If you use Umon for your own CV, it does not apply to you.
What we hold, and where it came from
Umon reads job advertisements that have been published in public. Where an advert carries a recruiter’s own contact block, we keep that contact in a separate internal list. The source is the advert itself, and we store only what it already showed in public: name, business email address, business phone number, employer name, job title, and the web address of the advert. Where an advert lists neither an email address nor a phone number, we store nothing. We buy no contact data and add nothing from data brokers.
Why we hold it, and our lawful basis
We use this list to contact recruiters and agencies about Umon’s recruitment product. Our lawful basis is legitimate interests, Art. 6(1)(f) GDPR: the interest is identifying the people who publish job listings so we can offer them a product built for that work. We carried out and wrote down a balancing test against the privacy of the people concerned before relying on it, and you can ask us for it at any time at [email protected].
Who can see it
The list stays inside Umon. Job seekers never see it, it never appears in our public job feed, and the details are kept out of our system logs. It is never sold, rented or traded. Access is limited to administrators and to our own outreach tooling, which reads it and writes nothing. Outreach may reach you from an address branded 99six, the name the same team uses for its wider development work, and whichever name it arrives under it identifies Umon as the controller.
How long we keep it
A contact is kept for 365 days from the last time it appeared in a public advert. Once the advert stops appearing and the same details are not published again, the record is deleted. A job runs once a day to clear anything past that point.
How to be removed
There are two routes, both free and both immediate.
- Every outreach email carries a one click unsubscribe link. Clicking it removes you.
- Or email [email protected] and ask. You do not need an account with us to do this.
Either route deletes the record and stops us collecting you again. To make that second part work, we keep the address on a suppression list that is checked before anything is ever stored. A phone number is kept there only as a one way fingerprint. That list is used for this and nothing else, and never to contact you.
Your rights over it
Everything in section 10 applies here too. Two are worth calling out. Because this data is used for direct marketing, your right to object under Art. 21 is unconditional: no reason is needed, and we stop and delete the record. And you can complain under Art. 77 to the Autoriteit Persoonsgegevens or to the authority where you live. We carry out no profiling and no automated decision making on this data.
People under 16
Umon is built for people aged 16 and over, and we do not knowingly process the personal data of anyone younger. If we find that we have, the account and everything attached to it is deleted without undue delay. If you think a child has registered, tell us at [email protected].
Changes to this policy
This policy changes when the service changes, when the companies we work with change, or when the law does. The date at the top of this page always shows the current version. Where a change is material, account holders are told in the app and asked to acknowledge the new policy before carrying on.
Contact and complaints
For privacy questions, data requests or a complaint, email [email protected]. We reply within one month.
You can also complain to the Dutch supervisory authority, the Autoriteit Persoonsgegevens, at autoriteitpersoonsgegevens.nl, or to the supervisory authority in the country where you live.
