---
title: "Privacy Policy: how Peekivo handles your data"
description: "What personal data Peekivo holds, why and for how long, who processes it, how analytics consent works by region, and how to ask for deletion."
canonical_url: https://peekivo.com/en/legal/privacy
language: en
last_updated: 2026-10-05
---

# Privacy Policy

Version v1. Last updated: 5 October 2026.

**In short:** Today Peekivo holds only what you give the waitlist: your email address, stored encrypted, the version of the consent you gave, and short-lived abuse-control records that contain no readable IP address or identifier. The website runs on Cloudflare. Google Analytics measures visits: in the European Economic Area, the United Kingdom, Switzerland, Türkiye and associated territories its cookies are set only after you accept them; elsewhere they are on by default and you can turn them off at any time. Turning analytics off stops its cookies and identifiers, but Google still receives cookieless pings that carry no cookie or device identifier, so we can measure the site in aggregate. Advertising signals are never enabled. Cloudflare Web Analytics also measures page views and loading speed for every visitor, without cookies; your cookie choice does not switch it off. We keep a waitlist entry for up to 400 days, and you can ask us to delete it at any time. The second part of this policy describes what will apply once the service itself is offered.

## 1. Who is responsible for your data

Erkam Demirci, Nilüfer, Bursa, Türkiye, is the controller of the personal data described in this policy (in Turkish law, the veri sorumlusu). Contact for every privacy question and request: privacy@peekivo.com. We have not appointed a representative in the European Union or the United Kingdom under Article 27 of the GDPR or the UK GDPR; whether one is required is under review. This policy takes effect on 1 October 2026.

## 2. What this policy covers

Part A (sections 3 to 10) describes what happens today, when you visit peekivo.com or join the waitlist. Part B (sections 11 to 16) describes what will apply once the Peekivo service is offered; until then, none of the processing in Part B takes place. Sections 17 to 26 apply to both. This policy is written to meet the transparency duties of the EU and UK General Data Protection Regulation (GDPR), Turkey's Law No. 6698 on the Protection of Personal Data (KVKK) and United States state privacy laws where they apply.

## 3. Today: visiting the website

The website is hosted on Cloudflare's network. To deliver pages and protect them from attacks, Cloudflare processes connection data such as your IP address, browser user-agent and the page requested. We have not switched on Cloudflare's request logging for the website or the waitlist service. When you submit the waitlist form, the site sets a first-party visitor cookie holding a random identifier that we sign; it lets us apply per-browser limits to waitlist sign-ups. Simply opening a page sets no cookie of ours. Our servers do not store that identifier, only a keyed one-way digest of it. The Cookie Policy lists every cookie.

## 4. Today: joining the waitlist

When you join, we store your email address, encrypted with AES-256-GCM under a key kept separately from the database, together with a keyed one-way digest of the address so that the same address is not stored twice. We also store a record that you agreed, the version of the policy you agreed to and the date. To limit abuse, we keep per-browser and per-connection sign-up counters for 24 hours. They are labelled with keyed one-way digests of the visitor cookie identifier and of your IP address network, never the address itself, and a short technical record of each sign-up, holding only a one-way digest, makes retries safe. We use your email address only to contact you about early access to Peekivo, and nothing else.

## 5. Today: bot protection with Cloudflare Turnstile

The first time you interact with the waitlist form, your browser loads Cloudflare Turnstile from challenges.cloudflare.com. Turnstile processes signals such as your IP address, TLS fingerprint and user-agent to tell people from automated sign-ups. It usually stays invisible, but it may ask you to confirm you are human. Our server checks the resulting single-use token with Cloudflare; it does not send Cloudflare your email address. Cloudflare processes Turnstile signals for us and, as it states in its Turnstile Privacy Addendum, also on its own account to improve bot detection. Cloudflare states that Turnstile does not use cookies. If the check wrongly stops you, contact us.

## 6. Today: analytics and your choices by region

This site uses Google Analytics 4 on its public pages, never on account pages, with Google Consent Mode. Which rules apply is decided on our server from the country code Cloudflare derives from your IP address; we do not store that country and never accept one supplied by your browser. Opt-in regions are the 27 EU countries, Iceland, Liechtenstein, Norway, the United Kingdom, Switzerland and Türkiye, together with the Åland Islands, Guadeloupe, Martinique, French Guiana, Réunion, Mayotte, Saint Martin, Gibraltar, Guernsey, Jersey and the Isle of Man, and any visitor whose country cannot be determined. There, analytics and all advertising signals start denied and analytics cookies are set only after you accept; accepting grants analytics only. In every other country, analytics is on by default and you can turn it off at any time: the analytics notice and the cookie preferences take effect immediately and expire the analytics cookies. We remember a decision to turn analytics off for 13 months and a decision to keep it on for 180 days. If your browser sends a Global Privacy Control signal, analytics starts off in those countries too, unless you have explicitly turned it on. Google's tag loads on our public pages for every visitor, whatever you choose. Whenever analytics is off, in any region (before you accept, after you reject, after you turn it off, or because of Global Privacy Control), the tag sets no analytics cookie and sends only cookieless pings that carry no cookie or device identifier. A ping contains, for example, the page address and referrer without any query string or fragment, the page title, your browser language, screen resolution, browser and device information such as your browser's user-agent, coarse timing, your consent state, a random number for each page load and whether the address carried an ad-click identifier. Like any request, a ping reaches Google from your IP address, together with your browser's user-agent. Google may use these pings, which carry no cookie or device identifier, to estimate aggregate figures for the site. Turning analytics off therefore stops analytics cookies and identifiers, not every request to Google. Advertising, ad-user-data and ad-personalisation signals and Google signals are denied everywhere. We send no events of our own. Google's tag records a page view for each public page you open, with the page title, language, screen size and your consent state, together with the visit and engagement events Google Analytics collects automatically. We have switched off its enhanced measurement, so it does not record clicks, scrolling, site searches, form use, file downloads or video plays. We never send your email address, form contents or page contents. Google states that Google Analytics 4 does not log or store IP addresses; how Google uses this information is explained at policies.google.com/technologies/partner-sites. Separately, the site uses Cloudflare Web Analytics. Cloudflare, which already delivers every page, adds a small script to our pages that reports each page view and how quickly the page loaded. A report contains, for example, the page address, the referrer, loading and responsiveness timings and the page element those timings relate to. Like any request, a report reaches Cloudflare from your IP address, together with your browser's user-agent, and Cloudflare derives your country, browser and device type from them. Cloudflare states that Web Analytics uses no cookies or other storage in your browser and does not fingerprint visitors through their IP address, user-agent or any other data. This script runs for every visitor in every region and is not controlled by the analytics choice described above, because it sets no cookie; that choice controls Google Analytics only.

## 7. Today: purposes and legal bases

We store and use your waitlist email address because you consented (GDPR Article 6(1)(a); KVKK Article 5(1)), and you can withdraw that consent at any time. We protect the waitlist with Turnstile, the visitor cookie and sign-up counters because of our legitimate interest in keeping the service secure and free of abuse (GDPR Article 6(1)(f); KVKK Article 5(2)(f)). In the European Economic Area, the United Kingdom, Switzerland, Türkiye and associated territories, analytics cookies are used only with your consent (GDPR Article 6(1)(a); KVKK Article 5(1)), which you can withdraw at any time; we do not rely on legitimate interest for them there. The cookieless pings sent whenever analytics is off, in any region (before you choose, after you reject or turn analytics off, or when your browser sends Global Privacy Control), rely on our legitimate interest in basic, aggregate measurement of the site (GDPR Article 6(1)(f); KVKK Article 5(2)(f)). Cloudflare Web Analytics relies on that same legitimate interest in every region. In other regions, we use analytics cookies for that same interest, and you can opt out at any time. We keep the cookie that stores your choice because it is necessary to respect that choice. Giving your email address is voluntary; without it you cannot join the waitlist.

## 8. Today: how long we keep it

A waitlist entry is erased 400 days after you join, or sooner if you ask. A deletion request marks the entry for erasure immediately, and the daily cleanup run then removes it. Sign-up counters are removed by the same cleanup once their 24-hour window has passed, and the technical sign-up records are deleted 30 days after the sign-up. Our database provider keeps point-in-time recovery copies for up to 30 days, so a deleted entry can remain in those copies for up to 30 days after deletion. Google Analytics keeps event data for the retention period we set, which is at most 14 months. Your cookie choice is kept in your browser for 13 months if you refuse or turn off analytics and for 180 days if you allow it; the visitor cookie is kept for 30 days.

## 9. Today: who receives it

Today, personal data from the website and waitlist reaches only Cloudflare, Inc., which hosts the site and its database and runs Turnstile and Cloudflare Web Analytics, and Google LLC for analytics, as described in section 6. Section 18 lists our service providers. We do not sell your personal information or share it for cross-context behavioural advertising, and we do not use it to make decisions with legal or similarly significant effects on you. Turnstile is an automated check; if it wrongly stops you, contact us.

## 10. Today: notice at collection for US residents

If you live in California or another US state with a consumer privacy law: we collect identifiers (your email address if you join the waitlist, and cookie and online identifiers) and internet activity on this site (pages viewed and the events listed in section 6), for contacting you about early access, protecting the site from abuse and measuring its use. We keep them for the periods in section 8. We do not sell your personal information or share it for cross-context behavioural advertising, and advertising signals are always denied in Google Analytics. You can opt out of analytics at any time with the analytics notice or the cookie preferences, and we treat a Global Privacy Control signal as an opt-out. Opting out stops analytics cookies and identifiers; the site still sends Google the cookieless pings described in section 6, which carry no cookie or device identifier and are used only for aggregate measurement of the site. You can also use the rights in section 20.

## 11. Once the service opens: your account and workspace

When the service opens, we will process the details you use to create and run an account: your name, email address and either a securely hashed password or, if you sign in with Google, the name, email address and profile identifier Google provides. We will also process your workspace, its members and their roles, invitations, settings, and the security records needed to protect sign-ins. We use this to provide the service under our contract with you, to keep it secure and to meet legal obligations such as keeping billing records.

## 12. Once the service opens: watches, captures and evidence

The service stores the page addresses, rules and schedules you set, the content Peekivo reads from those pages (text, structured fields and screenshots), the changes it finds, health records and your team's notes and outcomes. Pages you choose to watch may themselves contain personal data about other people; Peekivo reads them only because you asked it to. For workspaces used by a business, we process this content on the customer's behalf, and a data processing agreement is available on request.

## 13. Once the service opens: describing a watch in your own words

If you use the feature that sets up a watch from a sentence, we process what you write in order to understand it, find a candidate source and propose a watch for your approval. Your messages are content of your workspace; they are not used for analytics or advertising. To find a source, a web search provider receives only search text derived from your request, never your account details. Language models may interpret the request or answer narrow questions about a change, with only the minimum text needed. Before any such provider receives content from your workspace, it will be listed in section 18 with its location and how long it keeps data.

## 14. Once the service opens: payments

Web subscriptions will be sold through Polar, which processes your payment details itself; we receive your subscription status, plan, amounts, dates and billing country, not your full card number. In-app purchases are processed by Apple or Google; RevenueCat tells us which subscription is active on your account, using your Peekivo account identifier. We keep billing records for as long as tax and accounting law requires.

## 15. Once the service opens: notifications

To notify you, the service will send email through Cloudflare's email service and, in the mobile app, push notifications through Apple Push Notification service and Firebase Cloud Messaging, using a device token you can revoke by turning notifications off. If you connect Slack, Telegram or a webhook, the notifications you configure are sent there under that service's terms.

## 16. Once the service opens: retention and deletion

Before the service opens, this policy will state how long captures, change history, delivery records and account data are kept, by plan. You will be able to export or delete your watches and their evidence, and to delete your account from the app or the website. Deleting an account removes its personal data except what we must keep by law, such as billing records, and copies in backups expire on their normal schedule.

## 17. International transfers

Cloudflare serves the website from data centres around the world, and our waitlist database is held in the European Union. Cloudflare and Google are based in the United States. For transfers from the EU, UK and Switzerland we rely on their certification under the EU-U.S. Data Privacy Framework and its UK and Swiss extensions, and on the European Commission's standard contractual clauses in their data processing terms. For data subject to Turkish law, we transfer data abroad only on a basis allowed by Article 9 of Law No. 6698, such as standard contracts notified to the Personal Data Protection Authority. You can ask us for a copy of the safeguards that apply.

## 18. Service providers in use today

Cloudflare, Inc. (United States; worldwide network): website hosting and delivery, the waitlist database (Cloudflare D1), Turnstile bot protection, attack protection and Cloudflare Web Analytics. Google LLC (United States) and Google Ireland Limited (Ireland): Google Analytics, under the regional consent rules in section 6. No other provider receives personal data from the website or the waitlist.

## 19. Service providers planned for the service

None of these receives personal data today. When the service opens, we expect to use: Cloudflare, Inc. for application hosting, databases, file storage and email; Convex, Inc. (United States) as a database during our move to Cloudflare; Hetzner Online GmbH for the servers that read web pages, at a location we will state here; Polar for web payments; RevenueCat, Inc. (United States), Apple Inc. and Google LLC for in-app purchases, push notifications and Google sign-in; Tavily for web search during source discovery; Anthropic, PBC (United States) for language-model features; and TypeSafe AI, Inc. (United States) for narrow automated judgments about changes. TypeSafe hosts in the United States and has not stated a retention period, so we will not send it content from your workspace until we have its written retention terms and a lawful transfer basis. We will update this list, with each provider's location, before any of them receives your data.

## 20. Your rights

Depending on where you live, you can ask us to tell you whether we hold your data and give you a copy; to correct it; to delete it; to restrict or object to its use; to receive it in a portable format; and to withdraw consent at any time, without affecting earlier processing. Under KVKK Article 11 you can also ask how your data was processed, to whom it was transferred, and for compensation for unlawful processing. Residents of California and other US states with privacy laws can ask to know, correct and delete their data, and will not be treated differently for using these rights. You can complain to the data protection authority where you live or work; in Turkey this is the Personal Data Protection Authority (KVKK), and in the UK the Information Commissioner's Office.

## 21. How to make a request or leave the waitlist

Email privacy@peekivo.com from the address your request is about and say what you want, for example "delete my waitlist entry". We store your address only in encrypted form and can find it only from the exact address, so please write from it or include it. We may ask you to confirm the request from that mailbox, and we never ask for a password. We reply within one month, or within 30 days where Turkish law applies; if a request is complex we may extend the GDPR period by up to two further months and will tell you why. A deletion request takes effect immediately and the entry is erased at the next daily cleanup run, with recovery copies expiring within 30 days. Requests are free unless they are manifestly unfounded or excessive. An authorised agent may act for you with your signed permission.

## 22. Children

Peekivo is not directed at children. Do not join the waitlist or use the service if you are under 16. If we learn that we hold personal data of someone under 16, we will delete it.

## 23. How we protect it

Connections to the site use HTTPS. Waitlist email addresses are encrypted at rest with keys kept outside the database, abuse-control records use keyed one-way digests instead of raw IP addresses or identifiers, and access to production systems is limited to the people who run Peekivo. No system is completely secure. If a breach affects your personal data, we will notify you and the authorities as the law requires.

## 24. Cookie preferences

The cookies this site uses, what each is for and how long it lasts are listed in the Cookie Policy, where you can also change your choice at any time.

[Review your cookie preferences](https://peekivo.com/en/legal/cookies)

## 25. Changes to this policy

We will update this policy when our processing changes, for example before the service opens. The version and date at the top of the page identify the current text. If a change needs your consent again, we will ask for it; otherwise the new version applies from its effective date.

## 26. Contact

Erkam Demirci, Nilüfer, Bursa, Türkiye. Privacy contact: privacy@peekivo.com.

Questions: Questions about these documents: hello@peekivo.com. Privacy and deletion requests: privacy@peekivo.com.