Draft for review. This text was written together with the new website. It has not yet been approved by the legal counsel of White Box Technologies. Section 4 describes commitments that are normally set in each client contract; it must be checked against the contracts in use before publication.
1. Which hat we wear
The General Data Protection Regulation (GDPR) gives different duties to whoever decides how data is used and to whoever handles it on someone else's behalf. We are in both positions, for different data.
For our own data
Enquiries sent through this website, job applications, and the contact details of people at our clients and suppliers. We decide why and how this data is used. The Privacy policy has the details.
For our clients' data
The personal data inside the platforms we build and run: customers, employees, patients, payers. Our client decides; we act on the client's written instructions. See section 4.
2. Your rights, in plain words
| Right | What it means | Good to know |
|---|---|---|
| Access | You can ask whether we hold data about you, what it is, and get a copy. | The first copy is free. |
| Correction | You can have wrong or incomplete data put right. | Tell us what is wrong and what is correct. |
| Deletion | You can have your data erased when there is no longer a reason to keep it. | Some records must be kept by law, for example invoices. |
| Restriction | You can ask us to keep your data but stop using it while a question is settled. | Useful while a correction or an objection is being checked. |
| Portability | You can receive the data you gave us in a common format, or have it sent to someone else. | Applies to data handled by automated means on the basis of consent or a contract. |
| Objection | You can object to a use that rests on our legitimate interest. | We stop unless we have compelling reasons, which we will explain. |
| Withdrawing consent | Where we asked for your consent, you can take it back at any time. | For cookies, use Cookie settings. |
| Complaint | You can complain to the data-protection authority. | See section 7. |
If your data sits in a platform we run for one of our clients (for example you are that company's customer), your request goes to that company: it is the controller. If you write to us, we pass the request on to them without delay and tell you that we did.
3. Make a request
Pick what you want to do. The helper shows what we need from you and prepares an email you can send from your own mail program. Nothing is sent from this page and nothing you type here is stored.
4. Client data in our platforms
The systems we build carry the data of millions of people on behalf of our clients. This is how we treat it. The exact terms are in the data-processing agreement signed with each client.
- A written agreement first. We process personal data for a client only under a data-processing agreement that sets the subject, duration, purpose, kinds of data and our obligations.
- Only on instructions. We use client data only to deliver the service the client asked for. Never for our own purposes.
- Hosted where the client decides. Our platforms run on the client's cloud account or servers: AWS, Azure or on-premises. The data stays in the region the client chooses.
- Least access. Engineers get access to production data only when the work needs it, for as long as it needs it, and every access is recorded.
- No real data where it is not needed. Development and test environments use synthetic or anonymised data unless the client decides otherwise in writing.
- Sub-processors by name. If another company helps us with processing, it is named in the agreement and bound by the same obligations.
- Help with requests and assessments. We help our clients answer the people whose data it is, and support them with impact assessments for new processing.
- Return or deletion at the end. When the contract ends we return or delete the data, as the client chooses, and confirm it in writing.
Privacy is designed into the platforms themselves: permissions by role and by business unit, a record of who saw and changed what, and data retention that is set, not left to chance. You can see these mechanisms at work in the Organisation and Stack sections of the home page.
5. Personal data and AI
When we integrate AI agents into a client's systems, the same rules apply, plus four of their own:
- The client chooses the model and where it runs, in the cloud or on its own servers.
- Agents see only what the task needs, within the permissions of the person they work for. Personal fields that the task does not need are masked before anything reaches a language model.
- A person signs off. An agent prepares; it does not take decisions that have legal or similarly significant effects on a person by itself.
- Everything leaves a trace: what was read, which checks ran, who approved, and which model version was used.
These mechanisms are shown step by step in the AI integration section.
6. If something goes wrong
If personal data is lost, changed or seen by someone who should not see it, we act at once to contain it. For our own data, we notify the authority within 72 hours where the law requires it, and the people affected when the risk to them is high. For client data, we inform the client without undue delay so that they can meet their own duties, and we help them do it.
7. The authority and our contact
Data-protection contact at White Box: office@whitebox.tech (to be confirmed: a dedicated address or a named data-protection officer, if one is appointed).
The supervisory authority in Romania is the National Supervisory Authority for Personal Data Processing (ANSPDCP), dataprotection.ro. If you live in another EU country you can also turn to the authority there.
See also: Privacy policy · Cookie policy · Terms of use
