← Back home

Privacy.

Effective: 2026-11-20 · Version 0.13

What Blobby sees

On-device only: which monitored app is in the foreground and how long it's been open. That's the trigger signal. The content of your feed is never inspected.

In the browser extension and the Android app, Blobby also keeps the minutes you spent on your watched sites and apps each day, for the last 14 days, to show you your week. It is one number per day, with no site or app name. It stays on the device, unless you count your time across devices with Pro (below).

What leaves your device

Anonymous usage stats are on by default, and you can turn them off any time in Settings (below). App names are normalized to social_app before any network call. No PII. No fingerprinting. No third-party tracker or SDK runs in the apps or on this website, except Apple's and Google's sign-in, and only when you sign in (on this website, see below). Our server forwards the anonymous events, with their random ID, to PostHog in the EU, as our processor.

Anything else leaves only when you use a feature that needs it: Pro, sync once you sign in, counting your time across devices, making your own pack, or sending a correction or a report. Each one is explained below.

The browser extension

The extension watches which of your monitored sites is in the foreground and how long you have been there. That is all. It never reads the page, never looks at your feed, and never sends the name of a site you added. Its time on the seven built-in apps goes only to your own devices, if you count your time across devices with Pro (below).

Settings (your sites, budgets, topics) and each day's spend against them are kept in your browser. If your browser profile syncs extension data, they follow you through that sync, which belongs to your browser's maker, not us; we never see it.

If you buy Pro or redeem a code, the device token it returns is stored locally on that one browser and is deliberately excluded from sync. Free installs never have one.

The extension asks permission for the sites you choose to monitor, so it can show up on them. It also reaches Blobby's own server for Pro: to start a checkout, to check or redeem a code (about once an hour in the background for a browser that has one, and when you open its Pro settings), to link another device, to count your time across devices (at most once a minute while you're on a watched site, and when you open its settings), or to open your subscription page. If you sign in, it opens Google's or Apple's sign-in window, then reaches our server to check the sign-in, to link this browser's Pro to your account and, while it's on free, to ask about once an hour whether your account has Pro. Apart from Pro, it sends a correction to a question or a bug report when you send one (both below), and the anonymous usage stats described below, which are on by default and turn off in its settings. Nothing beyond that.

The iPhone app

On iPhone, you pick the apps in Apple's Screen Time list. Apple gives Blobby an opaque token for each one, not its name, so Blobby never knows which apps you picked and can't send their names anywhere. When the time you set is up, Screen Time tells Blobby, and Blobby covers the app with its question screen. It never sees what's on the screen.

Your picks, budgets and each day's spend stay on your iPhone, and sync leaves them out. Apart from Pro, the app sends a correction or a bug report only when you send one (both below), and anonymous usage stats unless you turn them off (on by default, below).

Anonymous usage stats

Blobby counts how it's used, so we can make it better. In the Android app, the iPhone app and the browser extension, this is on by default, and you can turn it off any time with "Share anonymous usage stats" in Settings. In Firefox it stays off until you turn it on.

Here's what gets counted: that Blobby was installed and opened, with its version and, if you came from an ad or a tagged link, that campaign's tag; each day it's used; the setup steps you finish and how many apps you picked (0, 1, 2, or 3 or more); when Blobby steps in, which kind of break you saw and how that ended (you answered, skipped or got past it), and when it couldn't step in because a permission was lost; when you turn monitoring off; the questions you answer or skip, with the topic, right or wrong and how long you took, and the question's number for the questions that come with Blobby; when the Pro plans come into view and what led there, the plan you tap, how a purchase ended, and whether you're on free, a trial or Pro; and the looks of Blobby you unlock.

Never counted: the name of an app or a site, a web address, anything in your feed, the words of a question or of your answer, the time you spend in your apps, anything from your account. A question from a pack you made yourself never has its number sent.

Stats go with a random ID made on your device, just for this. It's replaced after 13 months. Turn the stats off and the ID and anything waiting to be sent are deleted. Turn them back on and you get a new ID. Our server reads your country from the request. Your IP is never stored raw: only a keyed hash of it, for up to an hour after your last request, to stop abuse.

We also keep one anonymous record per install on our own server, filed under a one-way hash of that ID (PostHog, above, gets the ID itself): the kind of device (browser, Android or iPhone), the campaign tag, the country, the first and last day Blobby was used, whether it stepped in during the first three days, and whether a trial started, a trial turned into a subscription, or a purchase was made. It's deleted at 13 months, it's never joined to an account, a device or a payment, and we only ever read it as totals.

This website

getblobby.com counts its own page views and clicks on its store buttons. That's the page's path, which store, your country from the request and, if the link that brought you here had a campaign tag, that tag. No cookie and no third-party script. Apple's JS and Google's GIS run only on /account/delete and /redeem, when you open them to sign in, and /auth/apple/return runs no third-party script. A random ID ties one visit together: it lives in your browser's session storage and is gone when you close the tab.

To stop it, use "Don't count my visits" at the bottom of any page. It saves one setting in this browser, and nothing is counted until you click "Count my visits again".

When you remove the extension

Your browser opens a goodbye page on getblobby.com. If the stats were on in the extension, that page counts one uninstall, with the extension's version and your country. If they were off, no uninstall is counted. Either way the page still opens and asks why you left, with fixed choices, and a reason is counted only if you tap one. There's nothing to type. It's the website that counts, with a random ID for that visit, not your install's, and like any page here it counts as a page view. "Don't count my visits" on this site stops all of it.

Accounts

Optional. The core product works without one. Sign-in (Apple / Google) powers sync, and lets the Pro you bought follow your account to your other devices. We keep a random account number, the id Apple or Google gives us for you (not your name or your email), and which of your purchases you linked to it. Delete your account any time from the app, or at getblobby.com/account/delete; it erases the account, its sessions and everything synced, on the spot; it unlinks your purchases and asks RevenueCat, our in-app purchase processor, to delete its record of your account. Your purchases stay with the store. Devices that got Pro through your account lose it, and the phone that bought it can get it back with Restore purchases.

Your time across devices

With Pro, the devices linked to one purchase count your time together, so your phone knows about the hour you spent on your computer. Each device sends to that group, and only to it: the minutes it spent on each of the seven built-in apps (TikTok, Instagram, YouTube, X, Reddit, LinkedIn, Threads) each day, with the minutes it earned back, for the last 14 days; its last 300 answers (the question's number, its topic, right or wrong, and when); the name and kind of the device (like "Chrome on Mac"); and the settings the group shares, which are the mode, each built-in's budget and how it's split between devices.

We keep it on our server in the EU as your account data. Only the devices in your group read it. It never goes in our logs or in usage stats. Sites and apps you add yourself never leave the device, by name or by time. On iPhone, Apple's tokens for your apps never leave it either: an app counts only once you tell Blobby which built-in it is.

Erase it any time. "Erase my synced data", in the app or the extension, erases it for every device in the group. Removing a device erases that device's part. Deleting your account erases it too.

Your own packs

In the Android app, you can paste your notes and get a pack of questions made from them. The text goes through our server to Anthropic, whose Claude model writes the questions. We don't keep it: the signed pack comes back to your phone and stays there.

To hold the limit of three packs per install, the app sends a random ID made on your phone. Our server keeps only a one-way hash of it, with how many packs you've made and when. It isn't tied to your account.

Corrections you send

After a question, you can tell us it's wrong and give a link. We get your words, the link, the question's number and pack, its language, and the hour you sent it. Nothing else: no account, no device or install ID, no app or site name. Your IP is checked for a few minutes to stop abuse, then dropped.

We check each one against its source, with help from Anthropic's Claude, which checks sources for us. We delete it once it's been looked at, and within 90 days at most. It isn't tied to you, so we can't find it from your account: to have one deleted sooner, email us its text.

Reports you send

From Settings, you can report a bug. In the Android app, under a question from a pack you made yourself, you can also report that question. We get your words, your email if you give one, which Blobby it came from (Android, iPhone or the browser extension) and its version, your system's version (like Android 15 or iOS 26), your language and the hour you sent it. For a question you report, the question goes with it. Nothing else: no account, no device or install ID, no app or site name. Your IP is checked for a few minutes to stop abuse, then dropped.

We use a report to fix what went wrong and, if you gave your email, to write back. We keep it until it's been read, and 90 days at most; your email goes with it. To have one deleted sooner, email contact@cpnd.xyz.

Money

Subscriptions, or Pro for life in one payment. No ads. Ever. No data sales. Ever.

In the browser extension, payments are handled by Stripe, which acts as the merchant of record: Stripe receives your email and payment details under its own privacy policy, and it is the seller on your receipt. Blobby's server stores your Stripe customer id, your subscription status, and the hashed device tokens that unlock Pro. If you buy Pro for life, it also keeps a record of that purchase: Stripe's reference for the payment, the date, the price paid, whether it was the founding price, and the date of a refund if there is one. We never see your card. If you sign in, we also note which account the purchase is linked to.

In the Android app, you subscribe or buy Pro for life through Google Play Billing, and RevenueCat manages the purchase for us. Google takes the payment under its own privacy policy; RevenueCat gets the receipt from Google Play to check it. Blobby's server stores your RevenueCat customer id, your Pro status and when it ends (Pro for life doesn't), the hashed device tokens if you link another device, and, if a purchase is refunded, which one and when. We never see your card either. If you sign in, we also note which account the purchase is linked to.

In the iPhone app, you subscribe or buy Pro for life through the App Store, and RevenueCat manages the purchase for us. Apple takes the payment under its own privacy policy; RevenueCat gets the receipt from Apple to check it. Blobby's server stores your RevenueCat customer id, your Pro status and when it ends (Pro for life doesn't), the hashed device tokens if you link another device, and, if a purchase is refunded, which one and when. We never see your card there either. If you sign in, we also note which account the purchase is linked to.

To see how the plans are doing, our server also counts, per day, the checkouts started, trials, subscriptions, cancellations (with the reason, if you give one) and refunds. Those are bare numbers: no ID, nothing that leads back to you.

Hosting + region

Backend on Cloudflare, EU region. Marketing site on Cloudflare Pages.

Waitlist

If you leave your email in a waitlist or contact form on this site, we store the address and nothing else. Your IP is checked for a few minutes to stop form abuse, then dropped. We use the address only to write to you once, when there's news. We never share it or sell it.

Questions

Email contact@cpnd.xyz. We answer.