Data processing agreement
Version 2, 2026-11-16.
Parties
The controller is the customer that signs this agreement when signing up for Quota: the organisation named at sign-up, or the person signing in their own name.
The processor is Pasqual Peñalver Collado, a natural person trading as Syrakon, Tax ID (NIF) 47194112K, Carretera de la Marina, 45-47, Local 8, 08820 El Prat de Llobregat (Barcelona), Spain ("we", "us"). Contact: help@quota.at.
If you use Quota for personal data you process on behalf of your own customers, you are their processor and we are your sub-processor. You confirm that their authorisation covers using Quota and you pass their instructions on to us; this agreement sets the duties Article 28(4) GDPR requires of us towards you.
This agreement is part of the terms of service (quota.at/terms) and meets Article 28 of the General Data Protection Regulation (GDPR). Where the two differ on personal data, this agreement wins.
Subject and duration
We process personal data on your behalf to run your Quota nodes. This agreement lasts as long as you use Quota, and its duties on return, deletion and confidentiality continue after.
Nature and purpose
Your node sits in front of your API. It receives each request, counts it, limits and filters it, records it, and shows you what happened: logs, reports, Realtime, alerts and the defence mode. We process the data only for that, and never to advertise, profile, sell or combine it across customers.
Data and data subjects
Data subjects: the individuals whose personal data reach your API through your node (your end users, visitors and clients). Machines and scripts also send requests, but only people are data subjects.
Categories of data, per request:
- IP address of the client making the request
- Request method, path and query string. Before the query string is stored, the values of parameters that usually carry secrets or personal data (such as token, key, secret, password, auth, signature, session, code and email) are replaced with ***.
- Status code, latency and bytes in and out
- User agent and referer
- Visitor identifier (computed from the IP with a secret key of your node)
- Country and city derived from the IP
- What the protection layer decided for the request
No special categories of data are needed to run the service. Do not put them, secrets or other personal data in paths or query strings: paths are recorded as they arrive, and the masking only catches the parameter names above.
Instructions
We process the data only on your documented instructions: this agreement, the terms, and what you set up in your panel (limits, rules, blocks, retention by plan). If we think an instruction breaks data protection law, we tell you. If the law requires us to process the data for something else, we tell you first, unless the law forbids it.
Confidentiality
Everyone who can access the data is bound by confidentiality, by contract or by law, and accesses it only when running the service needs it.
Security measures
We apply technical and organisational measures appropriate to the risk (Article 32 GDPR). They are listed here and explained on the security page (quota.at/security):
- Each customer gets their own edge node and their own database file. There is no shared table that could return another customer's rows.
- Traffic is encrypted in transit with TLS up to the edge node.
- Nodes and databases run in the European Union (Gravelines, France).
- Request bodies and response payloads are never stored.
- Query string values that look like secrets are masked before they are stored.
- Nobody sees client IP addresses in the Realtime view; visitors appear as per-node identifiers.
- Request data is deleted when the periods in Retention end.
- Access to the panel is by passkey or single-use email link, with roles inside each organisation.
- Access to production systems is limited to the people who run Quota, bound by confidentiality.
Disks are not encrypted at rest, and request data is not backed up. We say so plainly so you can weigh the risk: protection rests on the isolation, access and retention measures above, and as no copies are made, none outlives the retention periods.
We review these measures when the service or the risks change. A change that lowers the protection is made only through a new version of this agreement.
Retention
We keep the data from your nodes for these periods and then delete it:
- Individual requests: 4 hours.
- Hour-by-hour breakdown: 7 days.
- Daily totals: 90 days.
- Blocks you or the defence mode set on a visitor, with its IP address: while the block lasts. A permanent block lasts until you remove it.
If we shorten a period, we tell you at least 30 days in advance by email. A longer period needs a new version of this agreement.
Sub-processors
You give us general authorisation to use sub-processors. Today they are:
- OVH: servers and databases where your nodes and their data live. Gravelines, France.
- Resend: email to you and your team about your nodes (alerts and reports). These emails carry the node name and aggregate figures, such as times, request peaks and the number of blocked IPs; they never carry IP addresses, paths, user agents or other data from your end users' requests. Resend is based in the United States. Its data processing agreement incorporates the Standard Contractual Clauses of Commission Decision (EU) 2021/914 and states that it is certified under the EU-U.S. Data Privacy Framework.
Each one is bound by data protection terms at least as strict as these. Before adding or replacing one, we email you at least 30 days in advance; you can object, and if we cannot meet your objection you can cancel before the change. We remain responsible for what our sub-processors do.
Assistance
If one of your end users asks us about their data, we pass the request to you and do not answer it ourselves.
Taking into account the nature of the processing and the information available to us, we help you answer requests to exercise data subject rights (Articles 12 to 22 GDPR) and meet your duties under Articles 32 to 36 GDPR: security of processing, notifying and communicating personal data breaches, data protection impact assessments and prior consultations with the supervisory authority.
Personal data breaches
If we become aware of a breach affecting your data, we notify you without undue delay, with what we know: what happened, what data and how many people may be affected, its likely consequences, and what we have done and will do. We add details as we learn them.
We cooperate with you so you can document the breach (Article 33(5) GDPR) and decide whether to notify the supervisory authority and the people affected (Articles 33 and 34). We do not notify them on your behalf unless you ask us to.
End of the service
When the service ends, you choose whether we return or delete the personal data your nodes hold.
Return: ask us at help@quota.at before you close your account. Within 30 days we send you the request records your nodes still hold, in CSV, together with your monthly reports. Then we delete them.
Deletion: closing your account in the panel deletes your nodes and their data straight away, so ask for the return first if you want it. If the service ends in any other way, the same choice applies to what your nodes still hold when you ask.
No copies remain, as there are no backups of request data. We keep nothing from your nodes unless EU or Spanish law requires it; if it does, we tell you what and why.
Audits
We make available the information needed to show we meet this agreement. If that is not enough, you can audit us, yourself or through an independent auditor bound by confidentiality, with 30 days' notice, at your own cost, and no more than once a year unless a breach or an authority requires it.
Versions
This is version 2. Your account shows the version you signed and when. A new version applies to you once you sign it in your account; until then, the version you signed applies.
Law
This agreement is governed by Spanish law. If you sign it as a business, disputes go to the courts of Barcelona. If you sign it as a consumer, you keep the protection of the law where you live and can bring a claim in your own courts.