Data processing agreement
How we handle the addresses you send us to verify, as your processor under Article 28 of the GDPR. Last updated: 17 November 2026.
1. Parties and scope
This agreement is between you, the customer (the controller, or a processor acting for your own clients), and ZENIFICA, S.L., tax ID B16783052, C/ Virgen de las Nieves 33, Oficina 1, 29569 Pizarra, Málaga, Spain (the processor, “we”).
It is part of the terms of service and you accept it when you create your account; no signature is needed. We keep the date and the version you accept. If you need a signed copy, write to hola@zenifica.com.
It covers only the personal data you send us to be verified. For your account and billing data we are the controller; see the privacy policy. We have not appointed a data protection officer because the law does not require us to; for any privacy matter, write to the same email.
2. What the processing is
- Subject matter and purpose: checking whether email addresses look deliverable and returning the result to you.
- Nature: receiving the addresses by API, panel or file; checking syntax and DNS records; where your plan includes it, opening a connection to the mail server that hosts the address to ask whether it accepts mail for it, without sending any message; storing the results; deleting them.
- Data: email addresses, the verification result for each one, the mail server's technical answer and the date. From the files you upload we keep only the email column. The service is not meant for special categories of data: do not send them.
- Data subjects: the people behind the addresses: your customers, users, subscribers or contacts.
- Duration: while your account is open, plus the deletion periods in section 11.
3. Your instructions
We process the data only on your documented instructions: this agreement, the terms and what you ask for through the API and the panel. In particular:
- We do not send email to the addresses, sell them, share them or publish them.
- We do not use them for our own purposes or for other customers, except as section 4 describes and limits.
- If we think an instruction breaks data protection law, we will tell you and can stop following it.
- If the law of the European Union or of a member state obliges us to process the data in another way, we will tell you first unless that law forbids it.
4. Cache, statistics, calibration and our own uses
Verifying well takes more than answering each request on its own. This is everything we do with the data besides returning the result to you, and its limits.
- 24-hour technical cache. We keep the answer a mail server gave about an address for at most 24 hours. If within that time you or another customer ask to verify that same address, we reuse the answer instead of asking again. This puts less load on mail servers. The other customer only gets what they would have got by asking themselves: they do not learn who verified the address before, and they never receive addresses they did not send us. You instruct us to work this way.
- Anonymous statistics. You instruct us to aggregate the results into statistics that do not identify any person, address or customer: for example, how often a type of mail server gives each kind of answer. We count by class of infrastructure, never by address. We name a mail provider only when it serves a very large number of people. We do not use or publish any figure drawn from fewer than 50 addresses or fewer than 3 customers. We do not try to re-identify anyone. Those statistics are no longer personal data: they are ours, and we can use them to run, measure and improve the service, and publish them.
- Calibration with outcomes (optional). This applies to you only if you choose to upload or connect the bounces from your sends. In that case you instruct us to match them with the verifications you ran before and to add the result to the counters of the previous point, under the same rules. We delete the raw bounces within 30 days at most. We do not keep the outcome of an address to give it to another customer.
- Our own uses, as a controller. There are a few purposes we decide ourselves and answer for as a controller, on the basis of legitimate interest or a legal obligation: protecting the service and third parties (detecting uses the acceptable use policy forbids, applying query limits to each mail server and honouring exclusion requests from operators and from individuals), answering requests from authorities and defending ourselves in claims. For this we use the minimum data, for the periods in section 11; if a specific investigation needs it, for as long as it lasts.
- What we never do. Build lists or databases of addresses, profile people, tell one customer what another has verified, or train models on addresses: statistical models are fed only by the anonymous statistics.
If your own obligations do not let you accept the cache or the statistics, write to us before using mailbox verification.
5. Your obligations
You make sure you have a legal basis for the addresses, that the data subjects have been informed as the law requires (including that you use providers to check their data), and that you follow the acceptable use policy. If you act as a processor for your clients, you confirm they have authorised you to use us and you pass on to us only instructions they have given you.
6. Confidentiality
Only the people who need the data to run the service can access it, and they are bound by a duty of confidentiality that continues after they stop working with us.
7. Security
We apply technical and organisational measures appropriate to the risk (Article 32 GDPR), including:
- encrypted connections (TLS) between you and the service, and encryption with mail servers when they offer it;
- servers for the application, the database and the verification engines located in the European Union;
- encrypted backups stored in the European Union;
- a private network, encrypted end to end, between our servers;
- access limited to the few people who operate the service, with individual credentials;
- API keys stored only as hashes, and separation of each customer's data;
- usage and activity logs that contain no addresses in clear text;
- automatic deletion of results (section 11) and security updates of systems.
We hold no security certification. We can update these measures as long as the level of protection does not go down.
8. Subprocessors
You give us general authorisation to use subprocessors. Today they are:
- Hetzner Online GmbH (Germany): servers for the application, the database and the verification engines, in the EU.
- Cloudflare, Inc. (United States): network, protection against attacks and edge delivery in front of the panel and the API. It handles the traffic in transit.
- Amazon Web Services EMEA SARL (Luxembourg): storage of the encrypted database backups, in the Frankfurt region (Germany). Each backup is deleted automatically after 30 days.
The private network that links our mailbox verification server with the application server is provided by Tailscale Inc. (United States). Data travels over it encrypted end to end with keys held only on our servers, so Tailscale cannot read it: that is why it is not a subprocessor. If that changed, we would add it to the list with the advance notice set out in this section.
Stripe (payments), Resend (account emails, sent from its Ireland region) and Google and GitHub (sign-in) work with your account data, not with the addresses you send to verify, so they are listed in the privacy policy and not here.
We sign with each subprocessor a contract with data protection obligations equivalent to these, and we remain responsible to you for what they do. We will announce any addition or replacement on this page and by email at least 30 days ahead. You can object within that period on reasonable data protection grounds; if we cannot offer an alternative, you can end the contract and we refund the unused part of what you prepaid.
9. International transfers
We store the data in the EU: the servers are in Germany and the backups in Frankfurt. Cloudflare can handle traffic at network locations outside the European Economic Area, and the parent company of Amazon Web Services is in the United States; this is covered by their data processing addenda, which include the European Commission's standard contractual clauses, and by the EU–US Data Privacy Framework where it applies. We will not make any other transfer outside the EEA without your instruction and without one of the safeguards of Chapter V of the GDPR.
Checking a mailbox means asking the mail server that the address's domain has designated to receive its mail, wherever it is. You instruct us to do so. We send it only the address being checked, as any server about to deliver a message to it would, and no other data. That server is not our subprocessor.
10. Help with your obligations
- Data subjects' rights. If someone writes to us to exercise their rights over data you sent and we can tell that you are the one who sent it, we pass the request on to you without undue delay and do not answer it ourselves. The panel lets you download and delete your data; if you need more, we will help within reason.
- Security, impact assessments and prior consultations. We give you the information we have that you need to meet those obligations.
- Personal data breaches. If we become aware of a breach affecting your data, we will notify you without undue delay and at most within 48 hours, at your account email, with what we know: what happened, what data and roughly how many addresses are affected, likely consequences, and what we have done or propose to do. We will complete the information as we learn more.
11. Return and deletion
- Results stay available for you to download for 30 days after each batch job finishes. After that we delete them automatically. You can delete them earlier from the panel.
- The verification engines keep their own technical copy of each check for at most 30 days; that copy cannot be deleted earlier.
- For single verifications the application does not store the address (except for 24 hours if you use an idempotency key): only an irreversible code, for 30 days, so that we do not charge you twice for the same address.
- When your account is closed, we delete whatever is left within 30 days. Until then you can download it.
- Copies in backups disappear as the backups rotate, at most 30 days later.
- We keep only what the law requires and usage counts for billing, which contain no addresses.
12. Audit
We give you the information needed to show that we comply with this agreement. Once a year, and after any breach affecting your data, you can send us a written questionnaire and we will answer it within 30 days. If that is not enough, or an authority requires it, you can carry out an audit yourself or through an independent auditor bound by confidentiality, with at least 30 days' notice, during working hours, at your cost, without access to other customers' data and without disrupting the service.
13. Customers outside the European Economic Area
- Countries without an adequacy decision. If you are established in a country the European Commission has not found adequate, returning the results to you is an international transfer. In that case the standard contractual clauses of Implementing Decision (EU) 2021/914, module four (processor to controller), form part of this agreement: we are the exporter and you the importer, the description of the transfer is the one in section 2, and Spanish law and courts apply.
- United Kingdom and Switzerland. This agreement also covers the equivalent obligations of the UK GDPR and of the Swiss data protection act.
- United States. If California privacy law or a similar state law applies to you, we act as your service provider: we do not sell or share the personal information, and we do not retain, use or disclose it outside the purposes of this agreement and those such laws allow a service provider. We will tell you if we can no longer meet this.
14. Liability, duration and law
Between you and us, the liability limits of the terms of service apply to this agreement. Nothing here limits what either party owes to data subjects or to authorities under the GDPR.
This agreement lasts as long as we process data for you. If it conflicts with the terms on a data protection matter, this agreement prevails. It is governed by Spanish law and by the courts named in the terms. If the English and Spanish versions differ, the Spanish version prevails.