How PageDog handles your data.

Who you can contact

PageDog is responsible for the data described here. If you have a question, an objection, or a privacy request, email support@pagedog.app.

What we measure on this website

We use PostHog Cloud EU for a simple picture of how the site is used: which pages are visited, whether someone follows a product link from a public article or free tool, and whether someone starts checkout, completes it, or downloads PageDog. PostHog runs in cookieless mode, so it does not place analytics cookies or save analytics IDs in your browser.

Automatic click and form capture, session replay, heatmaps, surveys, performance tracking, automatic error capture, and visitor profiles are all switched off in PostHog. We remove query strings and URL fragments before an event is sent. Content attribution contains only a public PageDog article or base-tool path and stays in memory during navigation in the current tab; it is not written to browser storage. Checkout IDs, payment session IDs, email addresses, watched URLs, page content, screenshots, and unlisted tool-result paths do not go into website analytics.

PostHog can still estimate daily unique visits by creating a temporary identifier on its EU servers. It resets each day, so it cannot be used to recognise the same browser from one day to the next. The IP address is not kept as an analytics event property. We keep analytics only while it helps us compare broad trends or diagnose a website problem, then delete or aggregate it.

Our legal basis is legitimate interests: understanding how the website is used, making PageDog better, and spotting checkout problems. You can object by emailing us. Because there is no persistent browser ID, we may not be able to connect a particular cookieless event back to you.

When you publish a tool result

The free tools keep text, screenshots, and generated GIFs in your browser while you edit. If you deliberately choose Share or Publish, PageDog uploads only the result needed for the unlisted link. Shared text and link records are stored in Supabase Postgres; shared screenshots and GIFs are stored in Cloudflare R2.

An unlisted link is not access-controlled: anyone who receives or discovers its long random URL can view it. Remove secrets and blur sensitive areas before publishing. Shared-result and embed routes are excluded from website analytics so their unlisted identifiers are not sent to PostHog.

To limit automated publishing abuse, PageDog stores a keyed, non-reversible value derived from the request IP address and browser agent; the raw values are not stored in the shared-result record. Published files and records may remain available until PageDog removes them during maintenance or handles a deletion request sent to support.

When something goes wrong

We use Sentry to help us find crashes and errors—one project for the website and another for the desktop app. A report contains only what we need to investigate: a shortened technical trail showing where the code failed, the app or website release, basic system details, the process name, and a few predefined product steps leading up to the error.

Sentry does not automatically log clicks, typing, forms, console messages, navigation, or network requests. Public builds do not use Session Replay, screenshots, attachments, performance tracing, session tracking, or persistent Sentry user IDs.

Things that matter to your watches stay out of Sentry: page content, watched URLs, watch names, selectors, screenshots, AI inputs or outputs, alert recipients, email addresses, licence credentials, request or response bodies, headers, cookies, and URL query parameters. File paths and error text are scrubbed before anything is sent.

Sentry stores error reports in its EU data region in Germany. We prevent it from keeping IP addresses or derived locations, and we do not attach a PageDog account, installation, or analytics ID. Reports are deleted after the retention period we set in Sentry.

Our legal basis is legitimate interests: keeping PageDog secure, reliable, and working correctly. You can object by contacting us. Because reports have no persistent user ID, we may not be able to connect a particular error report back to you.

When you pay

If you start checkout, we send your chosen plan and basic checkout context to Polar, our merchant of record and payment provider. Polar handles payment, tax, and billing details under its own privacy terms. PageDog records only broad checkout events in PostHog; transaction IDs are not sent to website analytics.

What stays on your Mac

Your watched URLs, browser sessions, full captures, and change history stay on your Mac. When an AI evaluation is needed, PageDog sends only what the evaluation needs: crops of the area you selected, its visible text, and a small structural summary. Optional PostHog product analytics have their own control inside the app. The limited Sentry error reports described above never include monitoring data or a recording of the app.

Who helps us run PageDog

We use a small number of service providers to operate PageDog: PostHog for analytics hosted in the EU, Sentry for error reports stored in Germany, Polar for checkout, Supabase for shared-tool database records, and Cloudflare R2 for shared screenshots and GIFs. We do not sell personal data or use it for behavioural advertising. A provider may process data outside your country, with the contractual safeguards required by law.

Your privacy rights

Depending on where you live, you may have the right to access, correct, delete, restrict, or receive a copy of your personal data, and to object to how it is used. Email support@pagedog.app to make a request. You can also complain to your local data-protection authority.

If this policy changes

We will update this page and the effective date above whenever our data practices change.