← Back to BloomGauge

BLOOMGAUGE / PRIVACY

Your Mac. Your choice.

Updated October 30, 2026.

Apart from detailed usage data, beta usage reporting and phone offline notices, everything BloomGauge sends about your Mac is anonymous, and all of it is optional. Beta usage reporting is off by default; anonymous setup counts and anonymous usage data are on for a new install, and from BloomGauge 1.65 detailed usage data (pseudonymous, below) is on by default for every Mac, new or updated, each easy to turn off. From beta 57 every one of these switches is in one place, More → Settings → Privacy. Saying no does not reduce BloomGauge features. Your balances, payments and Darkbloom account data stay on your Mac. The one exception you can choose is the optional private link (below), which shows today’s earnings and status to anyone who has the link.

If you choose to share beta usage reports

BloomGauge sends a small summary of the day to BloomGauge’s own reporting service a few times a day, at most every six hours (sooner after changes such as setup changes):

This reporting is pseudonymous, not fully anonymous: the random ID connects one Mac’s reports across days. It does not tell us your identity. We do not collect earnings, prompts, account identifiers, licensing IDs, serial numbers, personal names, email addresses, account tokens, passwords, private phone URLs or raw logs through usage reporting.

Control and deletion

Change your choice in BloomGauge on your Mac: “Share beta usage reports” in More → Settings → Privacy (from beta 57; before that in More → About BloomGauge). Turning sharing off immediately stops collection and queues deletion of that reporting ID and its reports from the service. If offline, BloomGauge keeps only the credentials needed to retry deletion and shows that deletion is pending. It confirms removal only after the service responds. A one-way deletion receipt, containing no reports or raw reporting ID, remains for 30 days to prevent delayed requests from recreating deleted reports.

The service keeps a rolling 30-day app-reporting window. Expired records are removed during reporting requests and owner-dashboard refreshes. Separately, it keeps one daily total for 13 months: how many Macs sent their first usage report that day. That total has no reporting IDs or report contents, so turning sharing off deletes your reports but not a daily total that already counted your Mac. It keeps aggregate download counts for up to 90 days under the same cleanup process. Download totals grouped by the referring website’s name (see Anonymous setup and download counts) are kept for 13 months. Reports are visible only in the private owner dashboard; they are not sold or used for advertising.

Optional problem reports

When BloomGauge detects certain interface, connection or control problems, it can offer to send a short report with one tap (“Send report”). You can also open a fully reviewable report from Help & feedback. Detection and dismissal stay on your device. Nothing is uploaded until you choose Send report, or until you turn on “Send these automatically from now on.” That setting is off by default; with it on, BloomGauge sends the same short report without asking each time, and you can turn it off at any time in More → Settings → Privacy (“Send problem reports automatically”). This works independently of usage sharing, and does not turn it on.

A report contains a random per-report ID, time, app version, Mac/phone surface, broad issue category, the screen it was sent from, macOS major version, chip family, memory-size group, and limited connection/Manager status codes. It excludes earnings, raw logs, stack traces, account and license identifiers, credentials and private URLs. Description and reply contact are optional, blank fields that you fill in deliberately. Please avoid sensitive information in them.

Builds with BloomGauge’s reliability test on also add its counts to a report sent from the Mac: how often the test agreed with what BloomGauge did, the reason codes behind any difference and how long its checks take. No model names, identifiers or text.

Newer versions also add the app’s update status: whether an update is waiting, roughly how many hours it has waited, a short code for why it was postponed, and whether the app runs from Applications, a disk image or elsewhere. No file paths, names or other personal data.

From beta 53, on a Mac where BloomGauge can’t read power use, a report also lists which of a fixed set of power sensors answer, their type and their readings, so support for that Mac can be added.

Reports go to BloomGauge’s private owner inbox and remain for up to 30 days; expired reports are removed during submissions and owner reads. Contact Andrew with the report ID to request earlier deletion. Deletion removes the report and contact details; a content-free receipt remains within the same retention window so a delayed retry cannot recreate it. Reports are never joined to app usage IDs. The service uses bounded storage and rate limits, and does not store IP addresses in its reporting database.

A successful send gives you a receipt. Failed sends do not start background retries; you choose whether to retry. A crash that prevents BloomGauge from opening, a dead collector, or loss of internet may require contacting support directly. Unless you have turned on automatic reports, no report is sent automatically, including on your next launch.

To help us sort problem reports, the report text and diagnostic codes are processed by Anthropic’s Claude API. Contact details are never sent.

Website traffic

Public pages send a small page-view count to BloomGauge’s own service. We store aggregate daily counts (US Central days) by page, referring website domain, approximate country and broad device category, and by page together with referring domain or country, for a rolling 30 days, plus totals by US Central hour for 14 days. When a link we post ourselves carries a short campaign tag (for example ?ref=slack-providers), that tag is counted in place of the referring domain; nothing else from the address is sent. On our Darkbloom setup guides (bloomgauge.io/use-darkbloom), clicking the link to Darkbloom’s sign-in also adds 1 to a daily total for that guide’s page, with no referring site, country or device. That link carries our Darkbloom referral code; once you are on Darkbloom, its own practices apply, and if you sign in there through our link it records our code on your account. We do not use analytics cookies, persistent visitor identifiers or fingerprinting, and do not store IP addresses, full user-agent strings, referring URL paths or query strings in these reports. Owner pages are excluded. Browser Do Not Track and Global Privacy Control preferences are respected. Known automated clients are excluded where recognizable; these counts are not unique people. Expired totals are removed during traffic collection and owner-dashboard refreshes.

Anonymous setup and download counts

To see how many new Macs try BloomGauge and where setup gets stuck, BloomGauge can send a few one-time counts. On a new install, setup shows a ticked box, “Send anonymous setup counts”; nothing is sent unless you leave it ticked and continue from that screen. It then sends each of these at most once:

Each count contains only the event name and the BloomGauge version. Our service adds the date (US Central time) when it receives it. When you click Download on this website, the page also sends the name of the website that sent you here (for example reddit.com), without the page address. It skips that step if your browser sends Do Not Track or Global Privacy Control.

These counts never include an account, device or installation ID, your IP address, your Mac’s model, chip, memory or macOS version (a failed requirement check names only which check it missed, for example “chip” or “memory”, not the value), your location, your email, your earnings or a timestamp. A small marker on your Mac stops each count from being sent twice. The service only adds 1 to a daily total, so it cannot tell whether two counts came from the same Mac.

Existing installs are not switched on. To turn the counts off at any time, open More → Settings → Privacy and switch off “Send anonymous setup counts”. BloomGauge then sends nothing more, and any counts it hasn’t sent yet are discarded.

The service stores only daily totals, with no individual records. Totals are kept for 13 months. They are visible only in the private owner dashboard and never sold or used for advertising. This is separate from usage sharing, anonymous usage data and problem reports, and changing it does not change them.

Anonymous usage data

BloomGauge shares anonymous usage data to improve the app and its estimates. It has two parts: from beta 50, a daily total of how often each of its screens and main settings was used; and from beta 52, a weekly summary of how each model’s pay rises with network demand on your Mac, used to improve BloomGauge’s starting estimates for everyone (details below). On a new install both are part of the one agreement on the setup screen. A Mac that updates from an older version is asked once, quietly, and sends nothing before you say yes. If you already said “No thanks” to sharing anonymous usage data, you aren’t asked again. From beta 57, every Mac that shares anonymous usage data also sends the weekly pay summary, unless you said no to the pay summary itself (details below). If you already share beta usage reports (above), the daily totals follow that choice. One switch, Share anonymous usage data in More → Settings → Privacy, turns both parts off at any time. Test builds send neither.

From the developer: this data is anonymous and deleted within 180 days. It helps new Darkbloom and BloomGauge users get better numbers and make better model choices sooner, and improves BloomGauge for everyone already using it. Better data, better results for all.

Daily screen and setting totals

Once a day, after midnight US Central time, BloomGauge sends the previous day’s totals in one short message, separately from the usage summary above and without its reporting ID. This is a complete example:

{
  "version": "1.36.69",
  "counts": {
    "screen.earnings.overview": 12,
    "action.model_switch": 1,
    "task.switch_model.start": 2,
    "task.switch_model.done": 1,
    "task.switch_model.steps_3_4": 1
  }
}

The daily message contains only the BloomGauge version and, for each screen or setting on a fixed list, how many times it was used that day (at most 50). The “task” lines show whether a few common tasks, such as switching models, were finished, and roughly how many steps they took. Use of the phone dashboard is included in the same daily message from your Mac.

The daily message never includes an account, device or installation ID, your Mac’s model, chip, memory or macOS version, your location, your email, your earnings, model names, anything you type, or when you did something. Like any request to a website, it arrives from your network’s IP address; the service uses that only for Cloudflare’s short-lived rate limiting and never stores it, or anything else about your Mac or network, with the counts.

The service doesn’t keep the message itself. It only adds it to daily totals per BloomGauge version: how many Macs used each screen or setting that day, and how many times. Because each Mac sends at most one message a day, no ID is needed, and the totals can’t be traced back to a Mac or followed across days. Totals are kept for 180 days, visible only in the private owner dashboard, and never sold or used for advertising.

Weekly pay summary for better estimates

BloomGauge ships with starting estimates of what each model pays, so it can make reasonable choices on a new Mac. They are built from Andrew’s own Macs and from this weekly summary from other Macs. From beta 52 the summary is part of anonymous usage data; before that it was an option in More → About BloomGauge. It is sent to bloomformac.com at most once a week, and only once your Mac has at least one model with 2 hours or more of steady data; each summary replaces the previous one.

For each model with at least 2 hours of steady paid or ready work in the last 30 days, it holds the model’s name, two numbers describing how its pay rose with network demand (level and exponent), the typical spread, and the hours and half-hour periods measured. From BloomGauge 1.63 it also holds, for each of eight bands of network demand, the hours measured at that demand and the average pay per hour there (a band with under half an hour is left out); no times or individual payments. From BloomGauge 1.64, a Mac signed in to the Darkbloom console in BloomGauge also adds, for each of those models, how long its first reply token took: the median and the 90th percentile in milliseconds, and the hours behind them. Only time when that model was the only one loaded on your Mac counts, and without the sign-in this is left out. Only time when the model was loaded and serving counts. It also holds your Mac’s chip family (for example M4 Max), memory range (for example 33–64 GB), the BloomGauge version, and, from 1.63, whether Darkbloom’s own records were used to leave out minutes with no work (so figures can be compared like with like) and the Darkbloom version on your Mac (its pay rules change by version). It also holds a random ID with its own secret, used only to replace or delete this Mac’s summary and separate from every other BloomGauge ID.

It never includes Darkbloom account or device IDs, balances, individual payments, times, prompts or anything that names you. The service keeps summaries for up to 45 days (at most 5,000 at a time). Only Andrew sees individual summaries, in the private owner dashboard. They are combined across Macs into the starting estimates shipped with BloomGauge versions. When at least 5 Macs with the same chip family and memory range report the same model (8 if Darkbloom’s public data has nothing to check the group against), the combined group figures (a typical level and exponent and their spread, and that at least 5, 10, 20 or 50 Macs stand behind them, never any one Mac’s summary or ID) are also published in the public network file at bloomformac.com/api/network/v1, which BloomGauge reads for starting estimates between versions. Before a group is published, the top and bottom 20% of its Macs are left out, each Mac counts for at most 24 hours and needs at least 2, the group’s pay must sit within 0.4 to 2.5 times Darkbloom’s public figure, and a published figure moves at most 15% a day. Andrew can switch publishing off. First-token figures are not part of that file. If combined first-token figures are ever shown back to other people, they will come only from groups of at least 3 Macs with the same chip family and memory range reporting the same model. Summaries are never sold or used for advertising. From beta 57 the summary comes with Share anonymous usage data on every Mac that hasn’t made its own choice about it, including Macs that turned on usage sharing before beta 52. If you said no to it (answered No thanks when asked, said Not now to the earlier Improve starting estimates card, or turned it off), it stays off, and the switch in More → Settings → Privacy says “Pooled pay summaries are off on this Mac.” To turn it back on, turn Share anonymous usage data off and on again in More → Settings → Privacy on your Mac.

Turning it off

Open More → Settings → Privacy and switch off “Share anonymous usage data”. That turns off all of it, including the weekly pay summary and the daily reliability counts, even if you share beta usage reports. BloomGauge first asks the service to delete your weekly summary, then sends nothing more and deletes what it hasn’t sent yet. If the service can’t confirm the deletion, nothing changes and you can try again in a moment. The phone dashboard can turn the switch off, but only the Mac can turn it on. Daily totals already added to a day can’t be removed, because they aren’t linked to your Mac.

Anonymous usage data is separate from anonymous setup counts and problem reports, and changing those doesn’t change it.

From beta 55: if you share anonymous usage data, BloomGauge also sends once a day how many 10-minute windows that day your Mac was online, available and serving each model, by model name, with its chip type, memory range and whether BloomGauge manages its models. It’s added into daily totals and kept 180 days. To stop a retried send from counting twice, the message carries a code the Mac derives from that day’s update-check code (see App updates); the service keeps a one-way hash of it for 48 hours and never joins it with update checks. “Never model names” above applies to the daily screen and setting totals; the weekly pay summary and these reliability counts do name models.

Detailed usage data (pseudonymous)

From BloomGauge 1.65, “Share detailed usage data” sends a detailed log of what BloomGauge does on your Mac, and an hourly summary of its work and pay, to BloomGauge’s own service at bloomformac.com about once an hour. It makes expected-pay forecasts, and so switching decisions, better for every BloomGauge and Darkbloom user. It is on by default. On a new install it is part of the agreement on the setup screen. A Mac that updates from an older version turns it on with the update and shows a one-time notice on Overview with a Turn off button. From BloomGauge 1.65.2, turning it on (on a new install, with an update or with the switch) also sends the hourly summaries of the 7 days before, never from before October 25, 2026; the log of actions starts when it is turned on. Earlier versions sent only what happened from then on; a Mac that was already sharing sends the hourly summaries of the 7 days before its update to 1.65.2 once, with the same limits. If you had turned off another kind of BloomGauge sharing before (anonymous usage data, the pay summary or beta usage reports), your Mac sends nothing until that notice has been on screen, then only what happens from then on, and the notice says plainly that something changed. Turn it on or off at any time in More → Settings → Privacy; the phone dashboard can turn it off, but only the Mac can turn it on. Test builds send it too, marked as a test.

It contains:

It never includes your name, email, Darkbloom account or device ID, balances, the Mac’s name or serial number, prompts or replies, file paths, request IDs or anything you type. The service stores no IP address; like any request, a batch arrives from your network’s address, used only for Cloudflare’s short-lived rate limiting (see Downloads and hosting).

This is pseudonymous, not anonymous. The random ID links one Mac’s log over time, and Darkbloom publishes each Mac’s chip, memory and current model, so someone with both could match a log to a public Darkbloom listing. That listing has no name, email or account. Only Andrew can see individual logs, in the private owner dashboard, and he may analyze them with the help of Anthropic’s Claude. Nothing shown to other people has an ID. BloomGauge publishes, in a public file at bloomformac.com/api/activity/v1/pay, what Macs were paid per loaded hour on each model in each of the last 26 hours, and how many Macs and hours stand behind each figure, for each chip, memory size and model and for each chip and model, any memory size. From BloomGauge 1.65.4 it also shows the same from each Mac’s latest 60-minute summary when it is under 15 minutes old, with the figure again without each Mac’s largest single job, by chip, memory size and model and by chip and model. From October 30, 2026, a group can be a single Mac, so a figure can be what one Mac was paid in an hour, listed by its chip, memory size and model. Since Darkbloom publishes each Mac’s chip, memory and current model, someone could sometimes match such a figure to a Darkbloom listing, which has no name, email or account. Hours before that keep the earlier rules: groups of at least 5 Macs by chip, memory and model, or at least 3 by chip and model (from October 28), and a figure is left out when, set beside another one, it would show what fewer Macs than that were paid. Once a day the file also gives, for each chip and model that at least 5 Macs ran for 40 or more hours over the 3 days before, one rounded number: how far a single Mac’s hourly pay usually strayed from that figure. It is the same for every Mac in the group and can’t be turned back into what any one Mac was paid. BloomGauge reads it to estimate what each model would pay on your Mac. The same file counts, over the last 24 hours, for each chip and for each chip and memory size, how many Macs shared paid hours and how many Macs’ estimates used one of these shared figures; BloomGauge shows those counts in the app and on the What Macs earn page. A count under 3 is left out, and so is one that, set beside the others, would show a count under 3. It has no IDs and leaves test builds out.

Each Mac’s log and hourly summaries are kept for 90 days, its 60-minute summaries for 7 days. Each hour, once it can no longer change (after about a day), is also added to totals by chip, memory and model with no ID, and each day’s actions to daily counts by chip and memory, kept for 13 months (test builds left out). Typical pay per hour for each chip, memory and model is worked out from groups of at least 5 Macs. The What Macs earn page also shows, for a chip and memory size with no such group, what at least 3 Macs of it were paid across all the models they ran on the last whole day (UTC), never next to a figure it could be subtracted from. You can save your own copy of the hourly snapshots and the log with Export my data in More → Help. Turning the switch off stops sending at once, even offline, and BloomGauge then asks the service to delete this Mac’s log and summaries, within a minute or so when online and retried until the service confirms. A content-free, one-way deletion receipt remains for 30 days so a delayed batch can’t recreate them. Totals already made can’t be removed, because they aren’t linked to your Mac. Turning it on again starts a new random ID. Detailed usage data is never sold or used for advertising, and it is separate from anonymous usage data, beta usage reports and problem reports.

App updates (beta builds)

BloomGauge checks for updates at bloomformac.com about every hour while it’s running (every six hours before beta 48). When there is a new version, it downloads it and installs it while you’re away from the Mac. The request sends only the app version (in the updater’s User-Agent) and never a system profile, account or analytics ID. From beta 51, each update check also includes a random code that the app makes new every day, so we can count Macs exactly. It isn’t tied to your Mac, account or any ID, changes daily, and the service keeps only the day’s total. If you share anonymous usage data, the reliability counts derive their retry code from it (see Anonymous usage data); that hash is kept 48 hours and never joined with update checks. If an update check fails, macOS may note the request’s address, including that day’s code, in the Mac’s own system log; that stays on your Mac. You can turn automatic updates off in More → Help (“Update BloomGauge automatically”). BloomGauge then checks only when you choose Check for Updates.

Downloads and hosting

The website counts installer requests by day (US Central time), version and whether the request came from BloomGauge’s updater (an automatic update) or a browser, without a cookie or device identifier for that count; only that yes/no is kept, never the request’s user agent. The website also counts how many Macs check for updates each day (US Central time), per app version, whether or not you share usage. To count each Mac once a day, it keeps a one-way hash of the request’s network address and the app’s update-check name (which includes the app version from 1.36.56) under a random key for that day; it also keeps a second hash the same way with the version numbers left out, so a Mac that updates during the day counts once in that day’s total, and, from beta 51, a third: a hash of that day’s random update-check code under the same key. The key and all three hashes are deleted when the day ends, so no address can be recovered or linked across days. Only the daily counts (per version, and the day’s total) are kept, for 13 months. Repeat downloads can be counted more than once. These totals do not tell us how many people installed or used BloomGauge.

Hosting and network providers necessarily process IP addresses and other request metadata to deliver and secure the website. BloomGauge’s app-reporting database does not store IP addresses. To stop abuse, Cloudflare briefly counts requests from each IP address to BloomGauge’s service; those counts are not stored with anything you send. The private owner dashboard is limited to Andrew through Cloudflare Access; downloading BloomGauge or using the beta needs no account.

Contact details

From version 1.36.35, More → About BloomGauge had an optional “Stay in touch” field for an email address or Slack handle. Beta 57 (1.36.76) removes it. Versions with the field could save what you typed on BloomGauge’s service, kept for up to a year after it was last saved. From beta 57 the app asks the service to delete it when it starts, and from October 27, 2026 the service accepts no new contact details. To reach Andrew, message him on the Darkbloom Slack.

Optional offline notices

Off by default. If you turn on offline notices in BloomGauge on your Mac (from beta 57: Control → Now → Notifications, called Models → Now before 1.61; also shown in More → Settings → Privacy), the app checks in with BloomGauge’s service about every 5 minutes, and also when the Mac is about to sleep, restart, shut down or update.

A check-in contains:

A few times a day, and when the Mac is about to sleep, restart or update, a check-in also carries the notice your phone would show, plus your phone’s push address issued by Apple, Google or Mozilla. The notice is encrypted on your Mac with your phone’s own notification keys. The service can deliver it through that push service but cannot read or change it, and the notice stops working within 22 hours unless your Mac renews it.

If check-ins stop when none was expected, the service sends that notice to your phone. When the Mac is back, the app itself tells you what happened.

The status word shows whether the Mac was earning at that moment (yes or no), never how much. Like any request to a website, each check-in arrives from your network’s IP address; the service uses it only for Cloudflare’s short-lived rate limiting and never stores it with your check-in.

Check-ins never include earnings, balances, Darkbloom account or device IDs, model names, hardware details or logs. This ID is not linked to usage sharing, anonymous usage data or problem reports.

The service keeps only the latest check-in (with its sequence number, when it arrived and the BloomGauge version) and the current notice’s status (times, delivery counts and the push service’s response codes), never a history. Turning offline notices off deletes them right away. A setup with no check-in for 30 days is deleted automatically. A content-free, one-way deletion receipt remains for 30 days so a delayed check-in can’t recreate deleted data.

The service also keeps daily totals for 30 days, such as how many notices were sent. Andrew sees only totals in the private owner dashboard, used to spot problems such as an update that stops Macs from checking in.

If you delete BloomGauge without turning offline notices off, your phone may get one last notice.

Off by default, and only the Mac can turn it on. If you turn on “View from any browser” in BloomGauge on your Mac (More → Settings, or from the “Set up on your phone” step and button), the Mac makes a long random link and sends a small read-only snapshot to BloomGauge’s service about every 2 minutes. The page at that link shows the latest snapshot in any browser. It has no controls, and your Mac takes no orders from it.

A snapshot contains:

It never includes the Mac’s name, hostname or address, Darkbloom account or device IDs, balances, individual payments, prompts or logs.

Anyone who has the link can see the page, so treat it like a password and share it only with yourself. The service keeps only the latest snapshot and a one-way hash of the link’s secret, not the link. It deletes the snapshot when you turn the link off or press “New link” (which also stops the old link working), or after 48 hours without an update: an older snapshot is never shown, and it is deleted the next time any Mac sends a snapshot, usually within minutes. To turn it off, open More → Settings → View from any browser on your Mac. The phone dashboard shows whether it is on, but cannot turn it on or off. This is separate from usage sharing and every other setting here; like any request to a website, an update arrives from your network’s IP address (see Downloads and hosting).

Optional survey

bloomgauge.io/feedback is an optional, anonymous survey. Each answer is stored with the date (US Central), the app version and which link brought you there (for example the app or Slack), in its own table, apart from problem reports and usage data. The survey sets no cookies and loads no third-party scripts, and its database stores no IP address or anything derived from one (Cloudflare’s short-lived abuse limit, described under Downloads and hosting, is separate). Answers are kept for 12 months and are visible only to BloomGauge’s owner, in the private owner dashboard and its export. Because they are anonymous, we can find and delete one only if you tell us something you wrote. To help us read and summarize the answers, their text is processed by Anthropic’s Claude API.

The last screen is optional. If you say we may contact you or quote you, we also store the contact you typed, whether we may quote you and the name to show, in a separate list linked to your answers. Contact details are kept out of the feed we use to read and summarize the answers. We remove your contact after we follow up, or after 90 days; if you agreed to be quoted, we keep your name and that permission with your answer.

Free Manager access and feedback

Manager access is free with no scheduled expiration. It does not depend on usage sharing. Updating does not enable automation or resume a paused plan. Existing local access records remain unchanged.

Information you voluntarily send in Slack or by email is separate from optional app reporting. Please review diagnostics and screenshots before sharing them. For privacy questions, contact Andrew on Slack or by email.