Analytics & cookies
Last updated:
This page explains which cookies DNSPeek sets, what product analytics records and which service providers receive your data when you pay or chat with support. It describes how the site works today; it is not a complete privacy policy.
Cookies needed to run the service
These are set only when you use the feature they belong to and are never used for analytics.
| Name | Purpose | Lifetime |
|---|---|---|
| dp_rt | Keeps you signed in (HttpOnly, sent only to the sign-in API). | 30 days, or until sign-out |
| dp_oauth | Protects Google sign-in against forged requests. | 10 minutes |
| dp_consent | Remembers your analytics choice (granted or denied). | 180 days |
| theme | Remembers your light, dark or system theme on this site and the docs. | 1 year |
Password-protected preview links set their own cookie on the preview domain after you enter the password.
Product analytics (only with your consent)
We use PostHog, hosted in the EU, to understand which pages are visited and which features are used, so we can improve the product. Until you choose “Accept analytics”, the analytics script is not loaded, nothing is sent to PostHog and no analytics cookies are set.
After you accept, we record page paths (without query strings) and named product events such as “preview link created” or “checkout started”. When you are signed in, events are linked to your account id and plan; your email address and name are not sent. Automatic click and form capture is switched off. Session recording is switched off. As with any web request, PostHog receives your IP address and browser details.
If your browser sends Do Not Track or Global Privacy Control, analytics stays off and we do not ask.
| Name | Purpose | Lifetime |
|---|---|---|
| ph_<project>_posthog | PostHog's anonymous visitor and session id (cookie and localStorage). | Up to 1 year |
| dp_utm | The campaign parameters (utm_*, gclid, fbclid, ref) of your first and latest visit, to see which campaigns bring sign-ups. | 90 days |
Website visit statistics
When you open a page of our public website, we record a page view so we can understand how the site is used. We record the page address (without query parameters), the website you came from (its domain only), the campaign tag in the link (utm_source), your country as reported by our network provider Cloudflare, your browser, operating system and device type as stated by your browser, and your IP address.
To count unique visitors per day we compute a one-way hash of your IP address, browser identifier, the date and a secret key; the hash changes every day. We use the IP address to understand where traffic comes from and to protect the website from abuse; only staff with access to the visit statistics can see it. We use no cookies or browser storage for this, and we do not share these records with third parties.
Our legal basis is our legitimate interest in running and improving the website (Art. 6(1)(f) GDPR). Records are deleted automatically after 90 days. Pages of the dashboard and the admin console are not recorded.
Payment processors
We never see or store your full card number. When you pay, you enter your payment details on the page of the payment provider shown at checkout, and that provider processes them. We only offer the providers switched on for this site, so each one below applies if enabled and only when you choose it.
| Provider | Role | What it receives |
|---|---|---|
| Stripe | Card payments and subscriptions (if enabled) | Your email, workspace name and id, the plan and price, and the card or wallet details you enter on its page. |
| Paddle | Merchant of record: sells the plan to you and handles tax (if enabled) | Your email, country and postcode for tax, workspace id and plan, and the payment details you enter on its page. |
| Lemon Squeezy | Merchant of record: sells the plan to you and handles tax (if enabled) | Your email, country for tax, workspace id and plan, and the payment details you enter on its page. |
| WayForPay | Card, Apple Pay and Google Pay payments (if enabled) | Your email, workspace id, the plan and amount, and the card details you enter on its page. |
| Cryptomus | Cryptocurrency payments (if enabled) | The invoice amount and currency, workspace id and plan, and the wallet and transaction details of your payment. |
| AI provider (support chat) | Generates replies in the support chat | Chat messages, the email you gave and, for signed-in users whose identity is verified, the account information needed to answer about their own account: plan, limits and usage, status of preview links and why a link is unavailable, subscription status and, for workspace owners and admins, recent payments (date, amount, status, what the payment was for and whether it was made by card or crypto, never card numbers or wallet addresses), and whether a link is under moderation review. |
The providers send us back what we need to run your plan: payment status, amount, currency, a customer and subscription id and the renewal date. They may also use the data to prevent fraud and meet their legal obligations under their own privacy policies. Refunds go back through the same provider; see our Refund Policy.
Support chat
The “Chat with us” button uses Crisp. Nothing is loaded from Crisp until you open the chat. When you do, Crisp receives your messages and any files you send, your IP address and browser details and, when you are signed in, your name, email, account id and your current workspace, its plan and your role in it, so our team can answer you. Crisp may set its own cookies for the chat session. Conversations are kept so we can follow up on your request.
Our AI support assistant uses a third-party AI provider (as our processor) to answer chat messages: the text of your messages, your email and, for signed-in users whose identity is verified, the account information needed to answer about their own account (plan, limits and usage, status of your preview links and why a link is unavailable, subscription status and, for workspace owners and admins, recent payments (date, amount, status, what the payment was for and whether it was made by card or crypto, never card numbers or wallet addresses), and whether a link is under moderation review) are sent to it to generate a reply, and it does not use this data to train its models. With each chat message we store a log entry for 180 days with the message, the reply, the account information the assistant used (for verified users) and the approximate location (country, region, city), browser, operating system, language and time zone reported by Crisp, plus the name and email you gave. We do not store your IP address.
Change your choice
You can accept or withdraw consent at any time. Withdrawing stops analytics immediately and removes PostHog's visitor id from your browser.