Legal
Privacy policy
Short version: this website sets no cookies and collects nothing unless you send us a request for access. If you do, here is exactly what happens to it.
Scope
This policy covers the websitezarx.ai. It does not cover the Zarx API service: data processed through the API (prompts, outputs, fine-tuning data) is governed by the processing terms agreed with each customer, which describe the processing on NPAW's own servers in Spain.
Who is responsible
The data controller is NicePeopleAtWork, S.L. (NPAW), the company that operates Zarx.
- Address: Calle Roc Boronat 23, 08005 Barcelona, Spain
- Privacy contact:contact@zarx.ai
- Data protection officer: dataprotection@nicepeopleatwork.com
What this site does without your input
Browsing zarx.ai creates no account and sets no cookies. The pages are static files served from a content delivery network; like any web server, it receives your IP address and browser headers to deliver the page, and keeps standard, short-lived access logs for security and capacity purposes. We do not use those logs to identify you. We do not embed third-party trackers, advertising pixels or social-media widgets. If we add audience analytics, we will use a cookie-less, aggregate-only measurement and update this page and the cookies page first.
Access requests
When you submit the request access form we collect the data below, only to answer your request and, if you want, to set up an evaluation with you.
| Field | Why we ask for it |
|---|---|
name | To address you when we reply. |
email | To reply to your request. |
company | To understand the context of your workload. |
role | Optional. To route your request to the right person. |
stack | What you run inference on today; helps us prepare a relevant evaluation. |
message | Optional. Anything you want to tell us about your workload. |
consent | Your agreement to this policy. |
source | The page the request was sent from (always this site). |
Legal basis. Your consent (Article 6(1)(a) GDPR), which you give by ticking the box on the form, and our legitimate interest in responding to a request you initiated (Article 6(1)(f)). You can withdraw consent at any time by writing to us; we will then stop and delete the request unless a contract or a legal obligation requires us to keep it.
Retention. We keep requests for up to 24 monthsfrom the last contact. If an evaluation, partnership or commercial relationship follows, the data moves to the records of that relationship and is governed by its own terms.
No profiling, no selling. We do not make automated decisions about you, we do not build profiles, and we never sell or rent your data.
Who processes the data
For this website we use a small number of service providers that process data on our behalf under a data processing agreement:
| Provider | Role | Location and safeguards |
|---|---|---|
| Google Cloud (Firebase Hosting, Cloud Firestore) | Serves this website and stores early-access requests sent through the form. | European Union (multi-region eur3) for stored requests; Firebase Hosting uses a global CDN. Google Cloud Data Processing Addendum, EU Standard Contractual Clauses where applicable. |
Your request may also be read by the NPAW team members who handle access requests. We do not transfer data to other third parties except where the law requires it. These processors serve the website only; they are not in the data path of the Zarx API.
Your rights
Under the GDPR you can ask us to access, correct, delete or export your data, to restrict or object to its processing, and you can withdraw consent at any time. Write to contact@zarx.ai; we answer within one month. You also have the right to lodge a complaint with a supervisory authority; in Spain, the Agencia Española de Protección de Datos.
Security
Requests are transmitted over TLS and stored in a database that only allows the website to create records: nothing on the public site can read, list or modify them. Access on our side is restricted to the people who handle access requests.
Changes
If we change how we handle data, we update this page and the date below. Material changes that affect requests already submitted will be communicated to the email you gave us.
Last updated: September 4, 2026