Data processing agreement
The Article 28 agreement for your team’s data: what Umon may do with it, who else touches it, and how it is deleted.
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].
Who this agreement is for
This page is for organisations. If your workspace holds records about your employees, your consultants or candidates you are recruiting, this is what Umon may do with those records and what we owe you in return.
Your organisation decides why those records exist and what happens to them, which under Article 4(7) GDPR makes it the controller. Umon holds and processes them on your instructions, which under Article 4(8) makes us the processor. Article 28 requires that split to be written down, and this is where it is written down.
It does not cover people who sign up to Umon for themselves. Umon is the controller for them, and our privacy policy is the document that applies. The two groups are held separately in the product, so nothing here changes what a personal account holder was promised.
This agreement forms part of the terms of service for an organisation account, and it applies from the first record you upload. For a countersigned copy naming your organisation, email [email protected], the same address every other request under this agreement goes to.
We act on your instructions, and nothing else
We process your data only on your documented instructions, including any instruction to send it outside the EEA, unless EU or Dutch law requires something else of us. Where a law does, we tell you before we act on it, unless that law forbids us from telling you. Art. 28(3)(a).
Your instructions are:
- this agreement, and the terms of service it forms part of;
- your team using the product’s features in the ordinary way;
- the settings you choose in your workspace, including the one in health and accessibility notes.
An instruction given any other way, in a call or a support ticket, becomes binding on us once it is confirmed in writing.
If we think an instruction breaks the GDPR, we tell you straight away. Article 28(3) requires that of us, and it is worth knowing we will use it.
We use your data for no purpose of our own. It is never sold, never rented, and never used to train an AI model, ours or anyone else’s. That is a stronger limit than the privacy policy and the terms set for an individual account, which allow training a model with that person’s own separate, explicit consent.
Health and accessibility notes
Every employee and candidate record has a free text field called Considerations. Teams use it for accessibility needs, physical limitations and health related accommodations. Anything of that kind is data concerning health, which Article 9(1) GDPR treats as a special category and protects more strictly than the rest.
AI analysis of that field is off in every workspace until you switch it on. While it is off, the field is stored, visible to your own team, and reaches no AI provider at all, not even as an empty label. Matching still scores and ranks every candidate without it.
Switching it on is your documented instruction to include the field in the matching feature, which sends it to the AI providers in the table below. Switching it off again withdraws that instruction from the next matching run onwards.
Before you switch it on, you confirm that:
- you have a condition under Article 9(2) for the processing and can demonstrate it. In an employment context that is usually Art. 9(2)(b) read with Dutch employment law, or the explicit consent of the person under Art. 9(2)(a);
- you have given the people concerned the information Articles 13 and 14 require, including that an AI assisted assessment happens and why;
- you have carried out a data protection impact assessment where Article 35 calls for one, which health data combined with systematic evaluation of people usually does;
- you will switch it off again if that condition stops applying, for example where someone withdraws consent.
We do not check your Article 9(2) condition, decide who gets assessed, or take any decision about any individual. What we do, whichever way you set it, is this:
- the analysis stays off until you turn it on, so a workspace that has never seen the setting has instructed nothing;
- the prompt may only report a conflict where a vacancy states the requirement it conflicts with, and a score never drops because a note exists;
- the field is left out entirely while the setting is off, rather than sent as a placeholder, because the label alone would tell the model that something had been withheld;
- one row goes into our AI decision log for every person assessed, including people filtered off a shortlist.
Please do not upload special category data of any other kind (racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data, or data about sex life or sexual orientation), or criminal offence data under Article 10, without agreeing it with us in writing first. The product has no field designed to hold it and no controls specific to it.
Who at Umon can see it
Everyone at Umon who can reach your data is under a confidentiality obligation, in their contract or in law. Access is limited to what running the service, supporting you and investigating an incident actually require. Art. 28(3)(b).
The companies that process it for us
You give us general written authorisation to use the companies below, which is what Article 28(2) GDPR provides for. Most work under a written data processing agreement carrying obligations that match the ones on this page, and we stay fully liable to you for what they do with your data. Art. 28(4). Two do not carry that agreement: Telegram, reached only when something in the service fails, and Google Fonts, reached only inside the Umon product, never this website. We still name them, because Article 28(2) only works if you can see everyone who receives your data.
| 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 |
This list is published at umon.io/dpa. Before we add or replace one of them, we announce it here at least 30 days beforehand. You can object on reasonable data protection grounds. If we cannot agree a way forward, you can end the affected part of the service without penalty.
Helping you answer a request from a person
When someone exercises a right under Chapter III GDPR, answering is your obligation as controller. We help you meet it, as Article 28(3)(e) requires. Here is what the product does today, stated precisely, because a promise that overstates this is worse than none:
- Access, Art. 15. An administrator can view every employee and candidate record in the workspace, and export CV data and documents. There is no single one click export of everything the product holds about one person, so a full access request is work we do together by hand.
- Rectification, Art. 16. An administrator can edit any field on an employee or candidate record.
- Erasure, Art. 17. Deleting an employee record is immediate and permanent, and the CV exports, documents, assignments, sessions, learning suggestions and match data attached to that record go with it. Where the same person is also a candidate in a hiring pipeline, that is a second record and deleting the employee does not reach it. Tell us and we remove it.
- Restriction, Art. 18. No dedicated switch. In practice you remove the data, or stop using the feature the person objects to.
- Portability, Art. 20. CV data and documents export from the workspace. Anything beyond that we prepare by hand on request.
- Objection, Art. 21. Yours to handle as controller. For the AI analysis in health and accessibility notes, switching the setting off stops it.
We answer a request for help under this section within five working days.
If a person contacts us directly about data in your workspace, we do not answer the substance of it. We pass it to you without undue delay, and we tell the person we have done so.
If there is a breach
If a personal data breach affects your data, we tell you without undue delay and in any event within 48 hours of becoming aware of it. Art. 28(3)(f) and Art. 33(2). That is ahead of the 72 hours Article 33 gives you for the regulator, so you have time to assess it.
What we send you, as far as we know it at the time:
- what happened;
- roughly how many people and how many records are affected, and what kinds of data;
- the likely consequences;
- what we have done about it and what we plan to do;
- who at Umon to talk to.
Where we do not have all of that at once, we send what we have and follow it with the rest as soon as we can.
We do not notify a supervisory authority or the people affected about a breach in your workspace without your agreement, unless the law requires us to. We help you meet Articles 32 to 36 throughout.
Getting your data back, or deleted
When the contract ends, you choose: we return your data, or we delete it. Either way our copies go. Art. 28(3)(g). Tell us which within 30 days of the end. If you tell us nothing, we delete.
Deleting a workspace starts a 30 day grace period in which it can still be restored. After that a scheduled job removes it permanently, and the employee records attached to the workspace go with it.
Deleting a single employee record works differently. It is immediate and permanent, with no grace period, and helping you answer a request from a person says exactly how far it reaches.
Backups are overwritten on a rolling cycle and are never restored to bring deleted data back, which is what the privacy policy says too.
Where EU or Dutch law requires us to keep something, we keep that and nothing besides it.
Auditing us
You can audit this processing, and we contribute to it, as Article 28(3)(h) requires. The practical terms: once in any twelve months, on 30 days’ written notice, during business hours, at your own cost, and whoever carries it out is bound by confidentiality. After a breach affecting your data you can audit sooner than that.
Umon holds no SOC 2 report and no ISO 27001 certification today. We would rather say that plainly than point you at a report that does not exist. What we can do is answer a security questionnaire about any of the measures in how your data is protected, and show you how they work.
Data that travels outside the EEA
We send your data outside the European Economic Area only in line with Chapter V GDPR. The companies in the table above that process it outside the EEA are Cloudflare, Stripe, Resend, OpenAI, Google (Gemini), Anthropic, Google (sign-in), Google Calendar, Microsoft 365, Telegram and Google Fonts.
For each of those transfers we rely on one of:
- the European Commission’s Standard Contractual Clauses;
- 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 to your workspace and we will send them. Email [email protected].
How your data is protected
We apply technical and organisational measures appropriate to the risk, which is what Article 32 GDPR asks for. The ones 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.
- Every query scoped to one organisation, so one workspace cannot reach another’s records.
- Signature checks on every incoming webhook.
- Rate limiting on sign-in and registration.
- Uploaded files checked for their real file type and capped in size, so a renamed file cannot slip through.
- Your text fenced inside marked blocks in every AI prompt, so a line inside a CV cannot act as an instruction to the model.
- Continuous dependency and security scanning, reviewed regularly.
- Internal tools locked down by role, on a need to know basis.
We improve these over time. We will not make a change that reduces the protection they give you.
Dutch law, and where a dispute goes
This agreement is governed by the law of the Netherlands, and a dispute about it goes to the competent court in Den Haag. That is the same law and the same court as the terms of service it forms part of.
Nothing here takes away a person’s rights under the GDPR or a supervisory authority’s powers.
Contact
Everything under this agreement goes to [email protected]: a data subject request you need help with, a breach question, an audit request, or a countersigned copy for your records.
Umon has not appointed a data protection officer. We say so rather than leave you guessing at an Art. 37 appointment. The address above reaches the people who handle all of this.
