Data Processing Agreement
Version 1. This agreement is part of every agreement for the 3DAY Agent between the client (the "Controller") and Ad Astra Tech s.r.o. (the "Processor", "we"). It sets out how we process personal data for the Controller under Article 28 of the GDPR. If it conflicts with the main agreement on data protection, this agreement wins.
1. What we process and why
- Purpose: reading the Controller's tools to write a weekly report with improvements, posting it to the Controller's Slack, and watching the Controller's website for problems.
- Data: what the connected tools hold, such as website analytics and visit recordings (with typed text hidden), search and ad data, payment records, email delivery data and emails in a connected inbox. This can include names, emails, IP addresses and order details.
- People: the Controller's website visitors, customers, leads and contacts, and the Controller's staff.
- Duration: as long as the main agreement runs, then section 7 applies.
2. Our obligations
- We process the data only on the Controller's documented instructions, which are the main agreement, this agreement and the project settings agreed in writing. If an instruction would break the law, we say so.
- Everyone who can see the data is bound to confidentiality.
- We read with read-only access and change nothing in the Controller's tools without the Controller's approval.
- Before an AI model sees the data, names, emails and phone numbers are removed.
- We help the Controller answer requests from data subjects and meet its duties on security, breaches and impact assessments, as far as our part allows.
- We give the Controller what it needs to show compliance, and allow an audit on reasonable notice, at most once a year unless there was a breach.
3. Security
Every connection is encrypted. Keys the Controller gives us are sealed so only the agent can read them, and the admin cannot read them back. Each client's rows are separated in the database by row-level security. Access is limited to the people who need it, each with their own account, and changes are recorded. The data is stored in the EU (Neon, Frankfurt).
4. Sub-processors
The Controller allows us to use the providers listed in our privacy policy (section 6) for the 3DAY Agent. We tell the Controller at least 14 days before adding or replacing one; the Controller can object, and if we cannot meet the objection, it can end the service. Each sub-processor is bound by data protection terms at least as strict as these.
5. Transfers outside the EU
Where a sub-processor is outside the EU, the transfer relies on the EU-US Data Privacy Framework or the EU's standard contractual clauses.
6. Breaches
We tell the Controller without undue delay, and within 48 hours of learning of a breach that affects its data, with what we know: what happened, which data and people, the likely effect and what we are doing about it. We then keep the Controller informed.
7. At the end
When the service ends, we delete the data read from the Controller's tools within 30 days, or return it first if the Controller asks, except where the law requires us to keep it. Raw data from the tools is deleted after 90 days during the service as well.
8. Liability and law
Liability follows the main agreement. This agreement is governed by Czech law. Questions: info@3day.studio.
Ad Astra Tech s.r.o.
Varsavska 715/36, Vinohrady, 120 00 Praha 2
ICO: 245 40 544
Tax ID: CZ24540544