Legal

Privacy Policy

Effective date: September 30, 2026 · twoplus11 LLC · Blockr for Windows

The short version

Blockr watches network connections entirely on your PC. What it sees (which app connected, to which host and port) is recorded only on your machine and is never uploaded.
No usage analytics, no accounts. The app never reports what you do with it, and never sends your traffic anywhere.
Blockr does not read the contents of your traffic. It decides at the moment a connection is seen, based on the app, the host and the port, and it never inspects, decrypts or proxies what flows through. After the verdict, the data path is untouched.
An optional reverse-DNS lookup asks your normal DNS resolver (not us) for the hostname of an address you're already connecting to; you can turn it off in Settings.
Blockr checks for a new version about once a week; that check reaches our server and we count it, described in full in section 5.
If you switch on a blocklist, Blockr downloads that list straight from the people who publish it, at most once a day and only while it is switched on. The download carries nothing about your rules or your traffic, and never passes through us (section 4).
Network profiles recognize a network from details Windows already has (its own ID for the network and your router's addresses). They are saved with your rules and never leave your PC.
If a Windows security-audit policy is switched on, Blockr can read the matching entries from the Windows Security event log as confirmation of what it blocked. Blockr never turns that policy on for you, and what it reads stays on your PC.
If you buy a business license, that purchase happens here on the website (payment handled by Stripe), not in the app.

1. Who We Are

Blockr is made by twoplus11 LLC, a Missouri limited liability company (twoplus11.com). When this policy says "we," "us," or "our," it means twoplus11 LLC.

Questions about this policy? Email us at jeremy@twoplus11.com.

2. Data We Do Not Collect

Blockr sees a great deal about your PC by design (its whole job is watching outbound connections), so it is worth being precise about where that stays:

Nothing is uploaded, ever. The record of which apps connected where lives only on your PC. It is never sent to us or to anyone else, and Blockr has no code path that transmits it.
Blockr does not read the contents of your traffic. It makes its decision when a connection is first seen, based on the app, the host and the port, and it never decrypts, records, or proxies what flows through afterward.
No usage analytics. Blockr does not report what you do in the app, what rules you write, or what connections it sees. The only thing it sends us is the weekly update check described in section 5, and that carries none of the above.
No accounts at all. Blockr needs no sign-up and no key for personal use: there is no login screen and no activation step.
Nothing Blockr records can be uploaded. The log, the per-app totals and your rules stay on your PC; the app has no feature that transmits them.

3. Data We Do Collect

Business-license purchases. If you buy a Business License, you enter your company name, work email, and number of computers in our checkout form on this website. We receive your company name and email so we can deliver your license key and keep a record of the purchase. Payment is processed by Stripe: your card details go straight to Stripe, and we never see or store them.

License validation. When you activate a business license key, Blockr sends the license key and a one-way hash of a Windows machine identifier (a truncated SHA-256 that cannot be reversed) to our licensing server to verify the license. It also sends the app version and the device name you choose to show, so you can tell your own computers apart when managing seats. We never receive anything about your rules, your traffic, or the connections Blockr has seen. These requests are hosted on Microsoft Azure, which may keep standard server access logs (such as IP address) for security and operational purposes. Blockr only makes these requests once a business key has been entered.

Update checks. Blockr checks whether a newer version exists: automatically about once a week, or when you check manually. This is an ordinary HTTPS request, to a small fixed list of twoplus11 hosts, for the current version number; it carries no account and nothing about your rules, your traffic, or the connections Blockr has seen. Our web host may log the request the way it logs any page view. If you then choose to install the update, Blockr downloads the installer from a twoplus11 host, follows every redirect through the same allow-list, and verifies the file's Authenticode signature and version before running it. A download that fails any of those checks is deleted rather than run.

4. Where Blockr Stores Things on Your PC

Everything Blockr saves stays on your PC, and none of it is transmitted:

Your connection log, per-app totals and rules: history.json, stats.json and rules.json in %ProgramData%\Blockr, which only Windows itself and the PC's administrators can open. Rules apply to the whole PC. Each account's connection log is kept apart from every other account's, and Blockr's window shows each person only their own.
The window's own preferences (theme, language, notifications, opening at sign-in): prefs.json in %APPDATA%\Blockr.
Your business license key and its cached validation result, if you have one, in your user profile folder. The cache exists so the app keeps working for a period without a network connection.
The application itself, Blockr's window and its service, in C:\Program Files\Blockr.

Hostname lookups. To show a hostname instead of a raw IP address, Blockr can perform a reverse-DNS lookup for addresses that appear in the log. That query goes to whichever DNS resolver your PC is already configured to use (not to us), and only for addresses your PC was already connecting to. Results are cached, and the feature can be switched off from the connection-log settings.

Blocklists. Only while you have switched a list on (Blockr ▸ Blocklists), Blockr downloads that list directly from its publisher: raw.githubusercontent.com for HaGeZi, 1Hosts and StevenBlack, and small.oisd.nl, big.oisd.nl or nsfw.oisd.nl for oisd. It checks for a new copy at most once a day, and at most once an hour when you press Refresh, and it asks the publisher whether the list has changed so an unchanged list is not downloaded again. The request is an ordinary HTTPS download whose User-Agent header names Blockr and its version, so the publisher (and GitHub, which hosts three of them) sees your IP address the way any download does. It carries nothing about your rules, your traffic, or the connections Blockr has seen, and it never goes through us. With no list switched on, Blockr makes none of these requests. The downloaded copies are kept in %ProgramData%\Blockr\Blocklists, and matching a connection against them happens entirely on your PC, using the names Windows has already looked up.

Network profiles. To tell which network your PC is on, Blockr reads, on your PC, Windows' own identifier and name for that network, your router's address and your router's hardware address. It reads them from Windows (the Network List Manager and the routing and neighbor tables), sends no packet to learn them and never asks for your location. If you create a network profile, those details are saved with your rules in rules.json so Blockr can recognize the network again. None of it is transmitted.

Windows Security event log. If you (or your IT administrator) have switched on the "Filtering Platform Connection" audit policy in Windows, Blockr can read the matching 5156/5157 entries from the Windows Security event log as independent confirmation of what it blocked. Blockr never enables that policy itself, only reads events that already exist on your PC because the policy was on, and what it reads is used only to annotate your own local connection log. None of it is transmitted.

Uninstalling removes the application, Blockr's service and the Windows Firewall rules it created (see the Terms of Service). Your rules and connection logs stay in %ProgramData%\Blockr so that reinstalling picks up where you left off. If you want every trace gone, also delete the two folders above.

5. If You Contact Us

If you email us (for support, beta feedback, or a question about your business license), we receive your email address and whatever you choose to put in your message. If you submit our report form and attach a screenshot, we receive that too. We use this information only to reply to you and to fix the problem. We do not sell or share it.

6. Downloading the App

Blockr is downloaded from our website, which is hosted by a third-party web host. Like any website, the host may keep standard server access logs (such as IP address) for security and operational purposes. This happens at the web-server level when you visit the download page. The Blockr application itself does not transmit anything at install time.

7. Children's Privacy

Blockr is not directed at children under 13, and we do not knowingly collect personal information from children under 13.

8. Your Rights

If you are in the European Union, United Kingdom, or California, you may have the right to access, correct, or delete personal data we hold about you. The only personal data we hold is what you send us by email and, for business-license holders, the company name and email tied to your purchase. You can exercise these rights by contacting jeremy@twoplus11.com. We will respond within 30 days. Deleting your business-license record will deactivate the license.

9. Changes to This Policy

We may update this Privacy Policy from time to time. We will update the "Effective date" at the top of this page when we do. We encourage you to review this page periodically.

10. Contact

Questions or concerns about this Privacy Policy? Contact us at:

twoplus11 LLC
jeremy@twoplus11.com