CookieSentry
Data Processing Agreement (DPA)
Agreement on the processing of personal data on behalf of the Customer under Art. 28 GDPR
Version 2026-10 · Published 22 October 2026
1. Parties and scope
- 1.1
This Data Processing Agreement ("DPA") is concluded between the customer named in the acceptance record, acting as controller (the "Customer"), and Mantas Lukošius, a sole proprietor (individuali veikla) registered in Lithuania, VAT number LT100014517418, Liepų g. 71A, Ginduliai, Klaipėdos r., Lithuania, who operates CookieSentry and acts as processor ("CookieSentry" or the "Processor"). Contact for data protection matters: [email protected].
- 1.2
This DPA supplements the Terms of Service at https://cookiesentry.com/terms (the "Terms"), under which CookieSentry provides its service to the Customer (the "Service"). If this DPA and the Terms conflict on the processing of personal data, this DPA prevails.
- 1.3
Terms such as "personal data", "processing", "controller", "processor", "data subject" and "personal data breach" have the meaning given in Regulation (EU) 2016/679 (the "GDPR"). "Customer Data" means the personal data that CookieSentry processes on behalf of the Customer under this DPA, as described in Annex 1.
2. Subject matter, nature, purpose and duration
- 2.1
Subject matter: CookieSentry scans the publicly accessible websites that the Customer adds to its account for cookies and third-party requests, monitors them on the schedule the Customer sets, sends alerts and reports to the recipients the Customer names, and administers the Customer's account.
- 2.2
Nature of the processing: collecting, storing, organising, analysing, displaying, sending by email and deleting Customer Data, as far as needed to provide the Service. The scanner loads the Customer's pages with a headless browser as an anonymous first-time visitor. It does not sign in to the Customer's website, does not submit forms, and has no access to the website's backend, its visitor statistics or the cookies of its real visitors.
- 2.3
Purpose: providing the Service under the Terms, including support and the security of the Service.
- 2.4
Duration: this DPA applies from its acceptance for as long as CookieSentry processes Customer Data for the Customer. It ends when the Customer's account is deleted and the Customer Data has been deleted or returned under section 12.
- 2.5
The types of personal data and the categories of data subjects are listed in Annex 1.
3. Instructions
- 3.1
CookieSentry processes Customer Data only on documented instructions from the Customer, including with regard to transfers to a third country, unless EU or Member State law to which CookieSentry is subject requires otherwise. In that case CookieSentry informs the Customer of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest.
- 3.2
The Terms, this DPA and the Customer's settings and actions in the Service (for example adding a website, choosing a scan schedule, naming alert recipients, sharing a report or deleting data) are the Customer's complete documented instructions at the time of acceptance. The Customer gives further instructions in writing or in text form (email to [email protected]); they must be compatible with the Service. Instructions that change the scope of the Service can be agreed as a change to the Terms.
- 3.3
CookieSentry informs the Customer without undue delay if, in its opinion, an instruction infringes the GDPR or other EU or Member State data protection provisions. CookieSentry may suspend that instruction until the Customer confirms or changes it.
- 3.4
CookieSentry also uses billing and payment data, and the data it needs for its own obligations in accounting, tax, security and abuse prevention, for its own purposes as an independent controller under its Privacy Policy (https://cookiesentry.com/privacy). That use is not covered by this DPA.
4. Obligations of the Customer
- 4.1
The Customer is responsible for the lawfulness of the processing it instructs, in particular for being allowed to scan the websites it adds (Terms, Acceptable Use Policy) and for having a legal basis to name the alert recipients.
- 4.2
The Customer informs CookieSentry without undue delay if it finds errors or irregularities in the processing with regard to data protection.
5. Confidentiality
- 5.1
CookieSentry ensures that persons authorised to process Customer Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality. This obligation continues after this DPA ends.
- 5.2
CookieSentry is run by its owner as a sole proprietorship. Where other persons are given access to Customer Data (for example a contractor for maintenance work), they are bound in writing to confidentiality and to this DPA before they get access.
6. Security of processing
- 6.1
CookieSentry implements the technical and organisational measures described in Annex 2 to ensure a level of security appropriate to the risk (Art. 32 GDPR), taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of the processing.
- 6.2
The measures are subject to technical progress. CookieSentry may replace them with alternative measures that provide at least the same level of security. CookieSentry documents material changes and includes them in Annex 2 with the next version of this DPA.
7. Subprocessors
- 7.1
The Customer gives CookieSentry general authorisation to engage subprocessors. The subprocessors engaged when this version was published are listed in Annex 3. The current list, including changes notified under clause 7.2, is kept at https://cookiesentry.com/legal/hosting.
- 7.2
CookieSentry informs the Customer at least 30 days in advance of any intended addition or replacement of a subprocessor, by email to the account email address and by updating https://cookiesentry.com/legal/hosting.
- 7.3
The Customer may object to the change in writing or in text form within that period on reasonable grounds relating to data protection. The parties then discuss the objection in good faith. If CookieSentry cannot reasonably avoid the change, the Customer may terminate the Service with effect from the date the change takes effect.
- 7.4
CookieSentry imposes on each subprocessor, by contract, data protection obligations that offer at least the level of protection of this DPA, in particular sufficient guarantees for appropriate technical and organisational measures. CookieSentry remains liable to the Customer for the performance of its subprocessors' obligations (Art. 28(4) GDPR).
- 7.5
Ancillary services that CookieSentry uses from third parties, such as telecommunications or postal services, are not subprocessing as long as no Customer Data is processed in them.
8. Data subject rights
- 8.1
Taking into account the nature of the processing, CookieSentry assists the Customer by appropriate technical and organisational measures, insofar as possible, in responding to requests from data subjects exercising their rights under Chapter III GDPR.
- 8.2
Account holders can view, correct and delete most Customer Data themselves in the dashboard (profile, websites, alert recipients, account deletion). Where that is not enough, CookieSentry helps on request.
- 8.3
If a data subject contacts CookieSentry directly about Customer Data, CookieSentry forwards the request to the Customer without undue delay and answers it only on the Customer's instruction.
9. Personal data breaches
- 9.1
CookieSentry notifies the Customer of a personal data breach affecting Customer Data without undue delay, and no later than 48 hours after becoming aware of it. The notice goes to the account email address.
- 9.2
The notice contains, as far as known:
- the nature of the breach, including where possible the categories and approximate number of data subjects and records concerned;
- the likely consequences of the breach;
- the measures taken or proposed to address the breach and to mitigate its possible adverse effects;
- a contact point for further information.
- 9.3
Information that is not yet available is provided as soon as it is.
- 9.4
CookieSentry takes the measures needed to secure the Customer Data and to mitigate possible adverse effects, and documents the breach. Notifying the supervisory authority and the data subjects is the Customer's decision; CookieSentry does so only on the Customer's instruction.
10. Assistance with Art. 32 to 36 GDPR
- 10.1
Taking into account the nature of the processing and the information available to it, CookieSentry assists the Customer in meeting its obligations under Art. 32 to 36 GDPR (security of processing, notification and communication of personal data breaches, data protection impact assessment and prior consultation).
- 10.2
CookieSentry may ask for reimbursement of reasonable costs for assistance that goes beyond the information in this DPA and its annexes, unless the assistance is needed because CookieSentry breached this DPA.
11. International transfers
- 11.1
CookieSentry stores Customer Data in the EU (Frankfurt, Germany). Where an Annex 3 subprocessor is outside the EU/EEA or may access data from there, Annex 3 names the transfer mechanism.
- 11.2
Customer Data is transferred to a country outside the EU/EEA only on the Customer's documented instructions (section 3) and only where the conditions of Chapter V GDPR are met, for example through an adequacy decision or the EU Standard Contractual Clauses. Engaging the subprocessors in Annex 3, including any onward transfer described there, is part of these instructions.
12. Deletion and return at the end of the processing
- 12.1
The Customer can delete individual websites and its whole account at any time in the dashboard. Deleting the account removes the account, its websites, scan results and cookie inventory from the production database straight away.
- 12.2
Before deleting, the Customer can save its reports as PDF. On request made before the account is deleted, CookieSentry provides the Customer Data in a common machine-readable format (JSON or CSV).
- 12.3
On request in writing or in text form, CookieSentry also deletes, within 30 days, the uploaded logo file, the email delivery records and the log entries that relate to the Customer. Data that remains in backups kept by a subprocessor is deleted in that subprocessor's regular backup cycle.
- 12.4
Beyond that, CookieSentry keeps only data that EU or Member State law requires it to store, for example invoices and payment records under tax law (clause 3.4), and the acceptance record of this DPA as proof of the agreement.
- 12.5
On request, CookieSentry confirms the deletion in text form.
13. Information and audits
- 13.1
CookieSentry makes available to the Customer all information necessary to demonstrate compliance with Art. 28 GDPR, in particular this DPA with Annex 2 and Annex 3, and answers reasonable questions in writing (for example a security questionnaire).
- 13.2
Where the written information is not sufficient, the Customer, or an independent auditor bound to confidentiality and mandated by the Customer, may carry out audits, including inspections. Audits require at least 30 days' notice, take place during normal business hours, are limited to once per calendar year unless a supervisory authority requires it or a personal data breach has occurred, and must not disrupt the Service. Each party bears its own costs.
- 13.3
Subprocessors are checked through the information and audit reports they publish or provide, as far as their terms allow.
- 13.4
CookieSentry informs the Customer without undue delay of inspections and measures by a supervisory authority that concern Customer Data.
14. Liability
- 14.1
Liability under this DPA follows the "Limitation of Liability" section of the Terms. This does not apply where mandatory law, in particular Art. 82 GDPR, does not allow a limitation.
15. Term, changes and final provisions
- 15.1
This DPA is concluded in electronic form (Art. 28(9) GDPR) when the Customer accepts it in the account settings. The acceptance record (company, person accepting, version, language, date and time) forms part of this DPA. CookieSentry agrees to this DPA by offering it in the Service.
- 15.2
This DPA runs for as long as the Terms and ends with them. Provisions that by their nature are meant to continue (confidentiality, deletion, information) continue until the Customer Data is deleted.
- 15.3
CookieSentry may update this DPA, for example because of changes in the law or in the Service. A new version is published with a new version number and shown in the account settings; it applies once the Customer accepts it. Until then, the version the Customer accepted continues to apply. Changes of subprocessors follow section 7.
- 15.4
This DPA is governed by the law that governs the Terms (the law of the Republic of Lithuania), without prejudice to the GDPR. The courts named in the Terms have jurisdiction.
- 15.5
This DPA is available in English and German. If the versions differ, the English version prevails.
- 15.6
If a provision of this DPA is invalid, the rest of this DPA remains valid. The invalid provision is replaced by a valid one that comes closest to the intention of the parties and to the requirements of Art. 28 GDPR.
Acceptance record
This record is part of the DPA (clause 15.1).
Customer (controller)
Filled in when the Customer accepts the DPA in the account settings.
CookieSentry (processor)
- Company
- Mantas Lukošius, individuali veikla
- Address
- Liepų g. 71A, Ginduliai, Klaipėdos r., Lithuania
- VAT ID
- LT100014517418
- Contact
- [email protected]
- Form
- Agreed by offering this DPA in the Service (clause 15.1)
Annex 1: Description of the processing
- Subject matter and purpose
- Scanning the Customer's public websites for cookies and trackers, scheduled monitoring, alert and report emails, shared reports and badges that the Customer chooses to publish, and administration of the Customer's account (section 2).
- Nature of the processing
- Automated loading of the Customer's public web pages by a headless browser as an anonymous visitor; recording the cookies set and the third-party requests made; classification and comparison with earlier scans; storage; display in the dashboard; sending emails; deletion.
- Duration
- For the term of this DPA (clause 2.4). Scan history is kept while the account has an active plan; for accounts without an active plan, scans older than 12 months may be deleted, except each website's latest scan and publicly shared reports.
- Frequency
- Continuous, on the schedule the Customer sets (daily, weekly or monthly) and on demand.
Categories of data subjects
- Users of the Customer's account (the Customer's staff or contractors who sign in)
- Alert recipients the Customer names for a website (up to three email addresses per website)
- The Customer's billing contacts
- Persons whose personal data the Customer's websites publish openly to every visitor (for example a name in an imprint), only as far as it appears in the scanned page content or in request URLs
Visitors of the Customer's websites are not data subjects of this processing: the scanner is its own anonymous visitor and receives no data about the real visitors of the website.
Types of personal data
- Account data: name, email address, password hash (scrypt, never the password itself), sign-in method (email or Google), email verification status, uploaded report logo
- Session and security data: session records with IP address and browser user agent; rate-limit counters per IP address (kept briefly in Redis)
- Website configuration: website URLs, display names and descriptions, scan schedule, time zone, alert settings
- Email addresses of alert recipients and email delivery records (recipient, subject, date, delivery status)
- Scan results: scanned and final URL; names, domains and attributes of cookies; a salted SHA-256 hash of each cookie value; origins and script URLs of third parties; compliance result
- Raw scanner response, kept with each scan for troubleshooting: it can contain the cookie values the website set for the scanner's own visit and, for scans by the overflow scanner, the response headers and the first 1,000 characters of the page's HTML
- Billing data: name, billing email, company name, billing address, VAT ID, invoice and payment records (amount, date, invoice link). Card details are entered at Stripe and never reach CookieSentry. CookieSentry also uses this data for its own purposes as a controller (clause 3.4).
- Connection data: IP address and request data of every request, which pass through Cloudflare's network; on the free scan form, Turnstile also checks IP address and browser signals
- Technical logs: application log entries with account ID, request IDs and error details; some entries also contain user and recipient email addresses and email subjects. The logs are sent to Better Stack (Annex 3).
- Error reports: stack traces, URLs and account ID, sent to Sentry (EU region)
- Support chat: every page, including the dashboard, loads the tawk.to widget, which receives IP address, browser and page data; if a user opens the chat, tawk.to (USA) also processes the messages and the name and email entered
Special categories of personal data (Art. 9 GDPR) are not part of the processing. The Customer does not enter such data in the Service, for example in website descriptions.
Annex 2: Technical and organisational measures
CookieSentry implements the following measures. They describe the Service as it runs on the publication date of this version.
Physical access control
- CookieSentry runs no server rooms of its own. The server that runs the application, the PostgreSQL database, Redis and the scanner workers is operated by Hostinger International Ltd. in a data centre in Frankfurt am Main, Germany; Hostinger is responsible for its physical security under its own agreement.
System access control
- Accounts can be used only after the email address is verified; sign-in by password or with Google.
- Passwords are stored only as salted scrypt hashes (better-auth); the password itself is never stored.
- Sessions expire after 7 days; session cookies are HttpOnly, SameSite=Lax and Secure.
- API requests and sign-in attempts are rate-limited per IP address to slow down password guessing and abuse.
- The scanner servers accept scan jobs only with a secret token per server.
Data access control
- Every query for Customer Data is limited to the signed-in account; one customer cannot read another customer's websites or scans.
- The admin area and the admin API are limited to a fixed list of owner accounts, checked on the server for every request.
- Reports are public only when the Customer shares them; links to shared reports and badges use random IDs that cannot be guessed.
Separation control
- Customer records carry the ID of the account they belong to and are kept logically separate in a multi-tenant database.
- Scan workers handle one website per job and never sign in to the Customer's websites.
Pseudonymisation and data minimisation
- Cookie values found by the scanner are stored in the cookie inventory only as salted SHA-256 hashes.
- The scanner acts as an anonymous visitor and collects no data about the real visitors of the Customer's websites.
- Product analytics on cookiesentry.com (Umami, self-hosted by CookieSentry at stats.mantestrategy.com, not a third party) sets no cookies and receives no email addresses, account IDs or IP addresses as event data.
Transfer control
- The application is served over HTTPS; API responses set HSTS for one year.
- API responses carry security headers (Content Security Policy, X-Frame-Options DENY, no MIME sniffing).
- The scanner refuses targets that resolve to private, internal or reserved network addresses.
Input control
- Each scan records when it ran and which scanner and scanner version produced it; every scanner call is logged.
- Admin actions on customer accounts (for example a granted trial) are written to the application log.
Availability and resilience
- Scans run through a job queue with automatic retries; when a scanner fails, another configured scanner or the overflow scanner takes over.
- Scanner health is checked regularly and monitored by the owner.
Control of subprocessors
- Subprocessors are engaged only under agreements according to Art. 28 GDPR and are listed in Annex 3 with their location and, where relevant, the transfer mechanism.
- Persons with access to Customer Data are bound to confidentiality (section 5).
Regular testing and review
- Code changes go through pull requests and a type check before release; production dependencies are checked for known vulnerabilities before each push from the owner's machine.
- Customers can delete websites and their account in the dashboard; deletion removes the data from the production database straight away.
- These measures are reviewed when the Service changes and with every new version of this DPA.
Annex 3: Subprocessors
The Customer authorises the following subprocessors (section 7), as listed on 22 October 2026. Later changes follow section 7 and are shown at https://cookiesentry.com/legal/hosting.
- Hostinger International Ltd.
- VPS: application, PostgreSQL and Redis, scanner workers
- Location: Frankfurt am Main, Germany (EU)
- Data processed: All Customer Data
- Legal basis / transfer: Art. 28 GDPR — Data Processing Agreement
- Hostinger
- Transactional email (SMTP)
- Location: EU
- Data processed: Recipient address, email content
- Legal basis / transfer: Art. 28 GDPR — Data Processing Agreement
- BunnyWay d.o.o. (Bunny CDN)
- Storage and delivery of static assets and uploaded report logos
- Location: Company in Slovenia (EU); storage in Germany (Falkenstein); delivery via global edge
- Data processed: Public assets, customer-uploaded report logos
- Legal basis / transfer: Art. 28 GDPR — Data Processing Agreement
- ScrapingBee
- Overflow scanner (used only when the own scanners are busy or down)
- Location: Paris, France (EU)
- Data processed: Target URL and the public page returned; for non-EU country domains the page is fetched through a proxy in that country
- Legal basis / transfer: Art. 28 GDPR — Data Processing Agreement
- Cloudflare, Inc.
- CDN / reverse proxy and Turnstile (anti-bot check)
- Location: Global edge; USA
- Data processed: All requests in transit, including IP address; Turnstile: IP address and browser signals
- Legal basis / transfer: Art. 28 GDPR; EU–US Data Privacy Framework + SCCs
- Functional Software, Inc. (Sentry)
- Error monitoring
- Location: EU region (Germany)
- Data processed: Stack traces, URLs, account ID
- Legal basis / transfer: Art. 28 GDPR; EU–US Data Privacy Framework + SCCs for access from the USA
- Better Stack, Inc. (Logtail)
- Application logs
- Location: Nuremberg, Germany (EU region)
- Data processed: Account IDs, user and recipient email addresses, email subjects, error details
- Legal basis / transfer: Art. 28 GDPR; SCCs
- tawk.to inc.
- Support chat (widget on every page, including the dashboard)
- Location: USA
- Data processed: Chat messages, name and email entered, IP address, browser and page data
- Legal basis / transfer: Art. 28 GDPR; SCCs
Also listed on https://cookiesentry.com/legal/hosting, but not subprocessors under this DPA, because CookieSentry or the user deals with them as a controller (clause 3.4): Stripe Payments Europe Ltd.: Subscription billing and invoicing (CookieSentry's own processing as controller, DPA clause 3.4); Google (optional Sign in with Google): Sign-in, only when the user chooses it.