Privacy
Privacy and ZWAF
What personal data ZWAF processes, where, for how long and who answers for it. Your applications' traffic stays on your appliance.
Last updated on 19 November 2026.
This notice covers ZWAF: the appliance and ZWAF VE, ZWAF Cloud (the service that activates appliances, sends them updates and feeds, and hosts the customer portal) and this site. How Zero Day Technologies handles personal data as a company, for example through its own website and contact forms, is in the company's privacy policy.
1. Who we are
ZERODAY TECHNOLOGIES S.R.L., București, Sector 6, Str. Apusului nr. 26-28, Bl. N29, Sc. A, Et. 3, Ap. 14, J2024037823005, CUI 50822407, VAT number RO50822407. For anything about your data, write to office@zer0day.ro or to the address above.
2. Your traffic stays on your appliance
ZWAF inspects the traffic of your applications on your appliance, in your network. Requests, responses, URLs, cookies, headers, form fields, the sign-ins of your users and the logs of all this stay there. We never see them, unless you choose to send us some of it for support (section 5). For that traffic your organisation is the controller. When we do handle part of it, in support, we act as your processor, under the data processing agreement in your contract.
Your appliance also talks only to the servers you set: DNS, NTP, syslog, SNMP, e-mail, identity providers. To check your certificates it asks the certificate authorities that issued them (OCSP). None of this goes through us.
3. What the appliance sends to ZWAF Cloud
The appliance always opens the connection; ZWAF Cloud never connects to it. Nothing is sent until an administrator activates the appliance online or sets up the update service, and activation can be done offline.
| What | What is sent | When |
|---|---|---|
| Activation | the serial number, a hash of the TPM key, the model, the software version, the licence installed and the platform's maker and product name (for a virtual machine, its hypervisor) | when an administrator activates the appliance online |
| Updates and feeds | the appliance's certificate, which names its serial number, and the versions it asks for | every few minutes for the IP reputation feed, less often for signatures and software |
| Telemetry, level minimal (the default) | counts of security events: the signature, the campaign, the action taken, and the target as a hash of its host and path | every 5 minutes |
| Telemetry, level full | the same, with the address of the attacker | every 5 minutes |
| Telemetry, level off | nothing |
Telemetry never carries URLs, request bodies, cookies, parameters, headers or the data of your users: ZWAF Cloud refuses a batch that holds anything more, and keeps nothing of it. You choose the level on the appliance and can change it at any time; IP Intelligence and Threat Campaigns keep working on any level. There is no other check-in: the appliance sends no health data, no host name, no addresses of its own and no accounts. ZWAF Cloud records each activation and each software download with the IP address it came from, in its audit log.
In ZWAF Cloud a device's telemetry is stored under a pseudonym (a keyed hash of its serial number). We use the attackers' addresses from full telemetry, with those our own sensors see, to build the IP reputation feed that every ZWAF appliance receives. For this use we are the controller, on our legitimate interest in the security of networks and information.
4. Leaked and compromised passwords
Your users' passwords. A WAF policy can check the passwords your users sign in with against known leaked ones. By default the check runs on the appliance, against a list in the IP Intelligence feed, and nothing leaves it. If you choose the online check, the appliance sends only the first 20 bits of a SHA-256 hash of the password, or of the user name and password together. Many different passwords share those 20 bits; ZWAF Cloud answers with the list for that prefix, the comparison happens on the appliance, and the cloud keeps nothing of the request.
The appliance's own accounts (Blacklight). Off until an administrator turns it on, for the administrators and for the access users separately. A check sends the account's e-mail address, the salt and cost settings of its password hash and the first 64 bits of that hash; never the password and never the whole hash. ZWAF Cloud passes only the e-mail address to Blacklight, our own leaked credentials service, compares what Blacklight returns with the 64 bits, and answers "found" or "not found". Nothing leaves the European Economic Area. A check is deleted a day after the appliance takes its answer and after a week at most; the lookup is deleted after 7 days, in ZWAF Cloud and in Blacklight. An appliance can check at most 50 addresses a day.
5. Support
Diagnostic bundles and captures. The appliance builds a diagnostic bundle only when an administrator asks for one, and never sends it by itself: a person uploads it to a support case in the portal. Passwords, keys, tokens and cookies are removed on the appliance before you download it. A bundle still holds logs with IP addresses, the user names of administrators and the addresses they signed in from, and the configuration. A traffic capture you attach holds what the traffic held: send only what the case needs. Each file is encrypted with a key of its own and deleted, with its key, 30 days after the case is closed.
Remote support. We have no access to your appliance by default and no key to it. If you want an engineer to look, an administrator creates a temporary support account, read-only unless you decide otherwise, for 24 hours at most, and gives us its credentials. The engineer then sees what that account shows, logs included; the appliance records everything the account does.
E-mail. Support notices and the messages we exchange by e-mail go through our e-mail provider, Namecheap Private Email, whose servers are in the United States. That transfer relies on the European Commission's standard contractual clauses. We keep technical data out of e-mail: files, captures, configurations and telemetry go through the portal only.
6. The ZWAF Cloud portal
For each account we keep the name, the e-mail address, the organisation, the role, the password (as a hash) and the secret of its second factor (encrypted). Every sign-in, failed sign-in, second factor refused, password change, case read and file download is written to an audit log with the time and the IP address it came from. Sessions are kept in the database with the IP address and the browser.
We need this to give your organisation its licences, updates and support (the contract) and to keep the portal secure (our legitimate interest). For portal accounts we are the controller. An account that is no longer needed is disabled; the audit log keeps the entries that name it, and the application never changes or deletes an entry.
7. This site
zwaf.zer0day.ro sets one cookie of its own, which keeps your choice about cookies, and loads Google Analytics and Google's marketing tags only if you allow them. The cookie policy lists every cookie, how long it is kept and how to change your choice. The site has no forms: contact goes to the company site. Like every web server, ours records the IP address, the time, the address asked for and the browser of each request, to keep the service secure and to find faults.
8. Where the data is and who else handles it
ZWAF Cloud and this site run on a server of Cyber_Folks SRL in Romania. The backups stay in Romania and no third party receives them; data deleted in ZWAF Cloud leaves the backups as they are replaced by newer ones. Cyber_Folks hosts the data, Namecheap carries our e-mail (section 5), and Google receives data from this site only with your consent (section 7). Connections are encrypted (TLS), appliances prove who they are with their own certificate, and every portal account signs in with a password and a second factor.
9. How long we keep it
| Data | Kept |
|---|---|
| Telemetry events | 90 days, then deleted by a daily job |
| Attacker addresses in the reputation feed, from telemetry | 90 days at most |
| Blacklight checks and lookups | 7 days at most |
| Support case files | until 30 days after the case is closed |
| Portal accounts | while the account exists |
| Licences, support cases and the audit log | for the contract and the archiving period the law sets after it |
| Your choice about cookies on this site | 6 months |
10. Your rights
You may ask us for access to your personal data, its rectification or erasure, the restriction of its use, a copy in a portable form, and you may object to a use based on our legitimate interest. Where you gave consent, you may withdraw it at any time. Write to office@zer0day.ro. Where we act as the processor of your organisation, we pass your request to it and help it answer. You may also complain to the Romanian data protection authority, ANSPDCP.
Next step
See ZWAF in front of your applications
Tell us what you run and how your traffic looks. We will show you how ZWAF would protect it and answer your questions about licensing and support. Resellers and integrators are welcome too: we are building our partner network and would like to hear from you.