Legal # Privacy Policy Last updated: 13 September 2026 Blocker is built so that we don’t have your data. We don’t run any servers that hold your blocklist, schedules, or browsing activity, and we never see the sites or apps you block. The app does send anonymous, privacy-respecting product analytics so we can understand how Blocker is used; this page explains exactly what that means, alongside the data we receive when you buy a licence, join a waitlist, or write to us. ## 01The app Your blocklist, schedules, and settings live in the app’s local store on your Mac. They never leave your computer. The app doesn’t talk to any server we run to decide what to block, and it doesn’t sync your data anywhere. Blocker does send anonymous product analytics and crash reports to [PostHog Cloud (EU region)](https://posthog.com/) , so we can understand how the app is used and catch bugs. On first launch, the app generates a random per-install identifier (a “machine ID”) that is the only thing tying events together; it isn’t linked to your name, email, or device until you activate a licence, at which point your licence email becomes the identifier so we can support you. The events tell us _that_ something happened, not _what_: for example, “a domain was added” or “a schedule was created with N days enabled”, but never the domain itself, the app identifier, the URL, the schedule name, or anything you type. Page views, autocapture, and session recording are disabled. Unhandled exceptions are captured with their stack traces so we can fix crashes; we don’t capture console logs. Analytics are also gated on a build-time key, so self-built or development builds send nothing. To enforce your site blocklist, Blocker runs a small proxy on your Mac, on the loopback address `127.0.0.1` (reachable only from your own machine), and routes your Mac’s HTTP and HTTPS traffic through it. For each connection, the proxy checks the destination hostname against your local blocklist. The optional local certificate allows Blocker to display its blocked page for HTTPS sites on that list. Sites outside your blocklist are never decrypted, read, or logged. Blocker does not keep a browsing history or send the sites you visit to us. Allowed connections are forwarded to their original server. To enforce your app blocklist, Blocker runs a small helper on your Mac that watches which apps launch, using macOS’s public `NSWorkspace` APIs (the same ones the Dock uses). When an app on your blocklist tries to open, the helper hides it and closes it. The helper only checks app identifiers (bundle IDs) against your local blocklist; it doesn’t read documents, windows, keystrokes, or anything inside the app, and it doesn’t send anything to us or anyone else. Blocker does not install a system extension. To display its blocked page for HTTPS sites, it can install a local certificate with a one-time Mac approval using Touch ID or your password. Blocking still works if you skip that step. It may also request notification permission to tell you when a schedule starts or ends. Your previous network settings are saved locally and restored when blocking stops. ## 02This website `getblocker.app` uses [PostHog Cloud (EU region)](https://posthog.com/) for audience measurement: page views and a few interaction events, for example when you click a “Get Blocker” or “Buy a licence” button. The setup is cookieless and stores nothing on your device beyond the lifetime of the tab: no persistent cookies, no fingerprinting, and no cross-site tracking. Your IP address is **not** collected and we honour the “Do Not Track” browser setting. All website analytics data is hosted in the EU. Waitlist signups also generate identified server-side events, as described below. If you reach our checkout through a marketing link, the URL parameters that identify the campaign (`utm_source`, `utm_medium`, `utm_campaign`, etc.) are forwarded to Polar so we can understand which campaigns lead to purchases. They are not tied to any account or user identity. Our hosting provider keeps short-lived access logs (IP address, user-agent, requested URL) for security and abuse prevention; we don’t use them for anything else. ## 03Platform waitlists When you join a waitlist, we store your email address, chosen platform, signup time and position, form location, browser user-agent, and any campaign parameters, referring URL or landing path supplied with your signup in Upstash Redis. We also retain any analytics identifier available with the request and delivery records used to retry incomplete email or contact synchronization. IP addresses are used for signup rate limiting and abuse prevention. We use Resend to send a confirmation and a launch announcement. Resend receives your address, platform, waitlist position, signup location, and any campaign source and name supplied, to manage the launch segment. We send signup events, email addresses, waitlist status, and attribution to PostHog, linked to an available visitor identifier or to your email address, to measure the signup funnel. Joining requests these waitlist messages; it does not subscribe you to a newsletter. You can unsubscribe from the launch email or request removal at [support@getblocker.app](mailto:support@getblocker.app) . ## 04Buying a licence When you buy Blocker, the transaction is processed by [Polar](https://polar.sh/) , our merchant of record. Polar collects what they need to charge you, apply the right tax, and send you a receipt: your name, email, billing address, and payment details. We never see your payment details. Polar shares your name and email with us so we can deliver your licence and reply if you contact us. Polar’s [privacy policy](https://polar.sh/legal/privacy) governs how they handle the rest. ## 05Email to support If you write to [support@getblocker.app](mailto:support@getblocker.app) , we receive your email address and whatever you put in the message. We use it only to reply to you and to handle your request. ## 06How we use this data The little data we do hold is used to: - Deliver your licence after purchase. - Reply to support requests. - Manage requested waitlist confirmations and launch announcements. - Meet legal obligations, for example keeping tax records (handled by Polar) and detecting fraudulent payments. We don’t sell your data. Waitlist email is limited to the confirmation and the requested platform launch announcement. ## 07Who we share it with We share data only with the providers that help us run the service, and only what each one needs: - **Polar**: payment processing and merchant of record. - **PostHog (EU region)**: anonymous app and website analytics, plus crash reports and identified waitlist signup events. - **Upstash Redis**: waitlist records, delivery state, and rate limiting. - **Resend**: waitlist email delivery and launch contacts. - **Our email provider**: for sending and receiving messages to and from `support@getblocker.app`. - **Our hosting provider**: for serving this website. That’s the whole list. We don’t sell or rent personal data. ## 08How long we keep it - Purchase and tax records: kept by Polar for as long as French and EU law require, typically ten years for accounting purposes. - Waitlist records and delivery state: stored without an automatic expiry while we manage the platform waitlist. You can request deletion by emailing support, including removal from Resend and identified waitlist analytics in PostHog. - Support emails: kept while the conversation is useful, then deleted. - Server access logs: rotated and deleted by our hosting provider on a short cycle. ## 09Your rights If the GDPR or a similar law applies to you, you have the right to access the personal data we hold about you, correct it, delete it, export it, or object to how we use it. To exercise any of these, write to [support@getblocker.app](mailto:support@getblocker.app) . You can also complain to your local data-protection authority. In France, that’s the [CNIL](https://www.cnil.fr/) . ## 10International transfers Polar and our other providers may be located outside the European Economic Area. When personal data is transferred out of the EEA, the transfer is covered by appropriate safeguards, typically the European Commission’s Standard Contractual Clauses. ## 11Children Blocker is not directed at children under 16, and we don’t knowingly collect their personal data. If you believe a child has sent us personal data, write to us and we’ll delete it. ## 12Changes to this policy If this policy changes, we’ll update the “Last updated” date above. Material changes will be flagged at the top of the page. ## 13Contact Questions about your data, or the [terms](https://getblocker.app/terms) : [support@getblocker.app](mailto:support@getblocker.app) . --- Source: https://getblocker.app/privacy