Data processing agreement
Last updated September 30, 2026
This data processing agreement ("DPA") is part of our terms of service between you, the customer, and Levan Tchubabria, Individual Entrepreneur, Mirian Mepe Str. #80, Tbilisi, Georgia ("Peekbird", "we"). It applies whenever Peekbird processes personal data on your behalf, and takes effect when you accept the terms: nothing needs signing. If you need a signed copy for your records, write to [email protected].
1. Words used here
- Data protection law: the EU General Data Protection Regulation (GDPR), the UK GDPR and Data Protection Act 2018, the Swiss Federal Act on Data Protection, the Law of Georgia on Personal Data Protection, and any other law on personal data that applies to the processing.
- Your personal data: personal data about visitors to your websites that Peekbird processes on your behalf, as Annex 1 describes.
- Subprocessor: a company we engage to process your personal data.
- Other terms, such as controller, processor, personal data breach and supervisory authority, mean what they mean in the GDPR.
2. Roles
For your personal data, you are the controller and we are your processor. Data about you and your team as our customers (your account, billing and support) is ours as controller, under our privacy policy, and isn't covered by this DPA.
3. Your instructions
We process your personal data only on your documented instructions: these terms and this DPA, the settings you choose in Peekbird (what is collected, sampling, masking, consent and how long data is kept), and how you use the service. If the law requires other processing, we'll tell you first, unless the law forbids that. If we believe an instruction breaks data protection law, we'll tell you.
4. Your responsibilities
You are responsible for having a lawful basis for the data collected on your websites, for telling your visitors and asking for their consent where the law requires, and for the instructions you give. You won't send us special categories of personal data, payment card numbers or passwords, and you'll mark any page parts that show such data to be left out of recordings.
5. Confidentiality and security
Everyone we authorize to process your personal data is bound to confidentiality. We apply the technical and organizational measures in Annex 2, and may update them as long as the overall protection doesn't fall.
6. Subprocessors
- You authorize the subprocessors listed on our subprocessors page. Each is bound by a written contract with data protection obligations at least as protective as this DPA, and we remain responsible to you for them.
- Before adding or replacing a subprocessor of your personal data, we update that page and email your workspace's owners at least 30 days ahead.
- You may object on reasonable data protection grounds within those 30 days. We'll work with you in good faith to resolve it; if we can't, you may end the affected service, and we'll refund what you prepaid for the time after it ends.
7. Where data is processed, and transfers
Your personal data is stored in the European Union (see the subprocessors page). We are established in Georgia, which the European Commission hasn't recognized as providing adequate protection, so when you are subject to the GDPR and our processing involves a transfer of your personal data to us, the standard contractual clauses adopted by Commission Implementing Decision (EU) 2021/914 ("SCCs"), Module Two (controller to processor), apply and are part of this DPA:
- Clause 7 (docking) applies. Under Clause 9, option 2 (general written authorization) applies, with the notice in section 6. The optional wording in Clause 11 doesn't apply.
- Clause 13: the supervisory authority is the one competent for you under Clause 13. Clauses 17 and 18: the SCCs are governed by the law of Ireland, and disputes go to the courts of Ireland.
- Annexes I, II and III of the SCCs are Annexes 1, 2 and 3 of this DPA.
- For transfers under the UK GDPR, the International Data Transfer Addendum issued by the UK Information Commissioner (version B1.0) applies with the SCCs as above; in its Table 4, neither party may end it. For transfers under Swiss law, the SCCs apply with references to the GDPR read as the Swiss Federal Act on Data Protection, and the Federal Data Protection and Information Commissioner as the competent authority.
If the SCCs and this DPA conflict, the SCCs win. Our own transfers to subprocessors outside the European Economic Area rely on the SCCs or on an adequacy decision, such as the EU-US Data Privacy Framework.
8. Helping you
- Visitors' requests. If a visitor asks us directly about data we hold for you, we'll pass the request to you and not answer it ourselves. Peekbird lets you find and erase a visitor's data; for anything more, we'll help within reason.
- Assessments. We'll give you reasonable help with data protection impact assessments and consultations with supervisory authorities, using the information we have.
9. Personal data breaches
We'll tell you without undue delay, and within 48 hours of becoming aware, of a personal data breach affecting your personal data, with what we know: its nature, the categories and approximate number of people and records concerned, its likely consequences, and what we've done or propose to do. We'll add to it as we learn more, and help you meet your own obligations.
10. Deleting data
- You can delete your personal data at any time: a visitor's data, a site with everything it collected, and recordings, which are also deleted when they pass the retention you set.
- When you delete a site, or ask us to close your account, we delete your personal data within 30 days, unless the law requires us to keep it. Copies in our encrypted off-site backups expire on their own schedule: within 5 weeks for recordings and analytics, and within 12 months for backups of our account database, which can hold references such as shared recording links.
11. Audits
We'll make available the information needed to show we meet this DPA, including answers to a reasonable security questionnaire once a year. If that isn't enough, you or an independent auditor bound by confidentiality may audit us once a year, or after a breach or when a supervisory authority requires it, with 30 days' notice, during business hours, at your cost, and in a way that doesn't expose other customers' data.
12. Duration, liability and order
This DPA lasts as long as we process your personal data. Each party's liability under it is subject to the limits in the terms, except where data protection law doesn't allow that. If documents conflict, the SCCs come first, then this DPA, then the terms.
Annex 1: Description of the processing
- Controller (data exporter): the customer, as named in its Peekbird account; contact: its workspace owners' email addresses. Activities: running websites that use Peekbird.
- Processor (data importer): Levan Tchubabria, Individual Entrepreneur, Mirian Mepe Str. #80, Tbilisi, Georgia; contact: [email protected]. Activities: providing Peekbird.
- People concerned: visitors to the customer's websites, including users the customer identifies to Peekbird.
- Personal data: random browser and visit identifiers (cookies); pages viewed, where visits came from, device, browser, operating system and approximate location (country, region and city, worked out from the connection; IP addresses aren't stored); clicks, scrolling, errors and page speed; experiment variations shown; recordings of pages and what happened on them, with typed input masked; goals, orders and events the website sends, with order values; and, only if the website sends them, a user ID, name, email address and other attributes.
- Special categories: none; the customer must not send them.
- Frequency: continuous, while Peekbird is installed and collecting.
- Nature and purpose: collecting, storing, analyzing, showing and deleting the data, to provide the customer with A/B testing, session recordings, analytics and heatmaps.
- How long: recordings as the customer sets for each site, within its plan (30 days on Free, up to 13 months on paid plans); other data while the site exists, unless the customer erases it sooner; then as section 10 describes.
- Subprocessors: as listed on the subprocessors page, for hosting and storage in the EU.
Annex 2: Technical and organizational measures
- Encryption: every connection uses TLS; recordings and backups are stored encrypted at rest in object storage.
- Where data lives: servers in Germany and storage in the EU, in providers' data centers with physical access control.
- Network: traffic reaches Peekbird through Cloudflare; the servers' firewall allows only the web server and key-based administrator access; databases have no public access.
- Access: customers sign in with hashed passwords and optional two-factor authentication, which a workspace can require; roles limit what each member can do. Peekbird staff need two-factor authentication; when they view an account to help its owner, they can only look, and every view is logged.
- Collecting less: IP addresses aren't stored; what visitors type is masked in recordings; customers can leave page parts out, sample which visits are recorded, choose how long recordings are kept, and wait for consent; bots are filtered out.
- Separation: each customer's data is kept apart by workspace and site, and every request is checked against them.
- Availability: nightly off-site backups, with restores tested.
- Deletion: tools to erase a visitor and delete a site with all it collected; automatic deletion of recordings past their retention.
- Change and incidents: changes are tested before release; staff actions in the admin area are logged; personal data breaches are handled as section 9 describes.
Annex 3: Subprocessors
The subprocessors page lists them, with what each does and where.
