Privacy and measurement choices
For how login tokens are stored and used, and how to revoke access, read account connection security. Storage encryption is server-side, not end-to-end encryption.
Daily usage history (Pro, optional)
If you switch on daily tracking, we store, for each connected account and calendar day in your time zone, the share of its weekly limit used, the highest session and weekly readings, the number of readings and their first and last times. We do not store prompts, conversations, files, account names or emails in this history. Days older than 35 days, and days for accounts you remove, are deleted automatically. You can turn tracking off or delete all saved days from the dashboard at any time.
Android and iPhone apps
HMU, the How Much Usage Android app (package com.howmuchusage.widget), opens the howmuchusage.ai dashboard full screen in a Trusted Web Activity, using Google's android-browser-helper library, or in a Custom Tab where the browser has no Trusted Web Activity support. You sign in inside the app with the website's own sign-in, so the dashboard and everything on this page work as they do on the web. Add widgets pairs the phone with a one-time code that works once, for five minutes, and only together with a secret the app keeps. The app creates a random install id, not linked to the phone's hardware or to advertising ids, and sends it when it pairs, so pairing the same phone again replaces its earlier key.
The read-only device key the app receives is encrypted with Android Keystore and sent over HTTPS only to the How Much Usage server, to download your saved usage readings for the widgets. The readings (account display names, plans, limit labels, percentages and reset and reading times) are stored only on the phone and are excluded from device backups. Widgets can hide account names. The app contains no ads or analytics SDKs, asks for no location, contacts or files, and never contacts Anthropic, OpenAI or any other provider. No advertising measurement runs inside the app: the website shows no measurement prompt there and sends OpenAI no measurement events from it. Forget saved key in the app deletes the key and the saved readings from the phone, and uninstalling does the same. Device keys expire after 180 days, you can revoke one in Widget studio at any time, and the server keeps only a hash of each key.
HMU for iPhone, the How Much Usage iPhone app, signs you in on howmuchusage.ai inside Apple's sign-in sheet, which shares Safari's cookies, with the website's own sign-in. Add widgets then pairs the iPhone with a one-time code that works once, for five minutes, and only together with a secret the app keeps in memory. The app creates a random install id, not linked to the phone's hardware or to advertising ids, keeps it in the iPhone Keychain on this device only, and sends it when it pairs, so signing in again replaces the iPhone's earlier key. The read-only device key it receives stays in the iPhone Keychain, shared only with its own widgets, readable after the phone is first unlocked and never synced to other devices, and the saved readings stay in the app's own container on the phone. The camera is used only to scan a pairing code from Widget studio. The app contains no ads, analytics or third-party SDKs, does not track you, and never contacts Anthropic, OpenAI or any other provider. No advertising measurement runs in its sign-in sheet either. Disconnect in the app turns the key off on the server and deletes it and the saved readings from the phone. Deleting HMU does not turn the key off. iOS keeps Keychain items after an app is deleted, so the install id and the device key can remain on the phone. The key stays valid on the server until it expires after 180 days or you remove it in Widget studio. To turn it off first, use Disconnect before you delete HMU. Installing HMU again and signing in replaces that key. Settings > Account > Delete account opens the page where you delete your account.
First-party statistics
We count signed-out homepage visits and clicks on sign-in and demo controls on our own server. A secure 24-hour cookie groups repeated visits into one observed landing session. We store a keyed hash of its random identifier, the event type and time for up to 90 days. We do not store full URLs, referrers, IP addresses, email addresses or connected-account details in these traffic events, and do not link them to your identity. Do Not Track and Global Privacy Control disable this collection. Browser restrictions and automated traffic can affect these counts.
The owner-only business dashboard shows registration email, registration and last sign-in times, plan entitlement, linked-account count and supported campaign attribution. Checkout and verified payment records are stored privately for business reporting. Provider credentials and usage contents are never displayed there. These first-party records are separate from the retired ChatGPT advertising measurement.
Connection steps
On the signed-in dashboard we also record first-party account-connection milestones: dashboard visits, connection/provider choices, starting sign-in, copying a code (not the code itself), opening the provider, returning to the app, submitting credentials (not their contents), cancellation, and safe failure categories. Our server separately confirms code issuance, approval, verification and successful encrypted storage. An opaque random connection-attempt identifier groups these steps with your account for the owner-only dashboard. Only broad phone/computer categories and first/last times and bounded repeat counts are stored. We do not record keystrokes, screens, raw errors, codes, credentials, provider account identities, usage contents or AI conversations. No connection-step events go to advertisers. Do Not Track and Global Privacy Control disable collection. Events are retained for up to 90 days; older rows are removed when new events arrive, so dormant sites may retain rows until the next event. Missing events are not proof of abandonment. Deleting your account deletes these records.
Campaign links
Supported Google and X campaign links use a secure, signed 24-hour first-party cookie. For a new registration within that period, we store the campaign name and visit and signup times in private account metadata with our sign-in provider, Clerk. This first-party record is not sent to Google, X or OpenAI. We no longer collect new ChatGPT campaign attribution. Earlier campaign records remain in account metadata until that account is deleted. This collection respects Do Not Track and Global Privacy Control and does not record ad click IDs, arbitrary URL values or returning users as new signups.
Advertising measurement
ChatGPT advertising measurement is off. The website no longer asks for ad measurement consent, loads the OpenAI ad SDK, or sends registration, checkout or purchase events to OpenAI. This also applies if you previously allowed measurement. The change does not affect your access, pricing or connected accounts. Events sent before the change cannot be recalled from OpenAI.
Cookies
The retired ad preference used a first-party browser cookie for up to 30 days. Earlier choices and optional click references may remain in our private database, but are no longer used for advertising measurement. Account-associated records are deleted with the account. The old OpenAI browser SDK may have set __oppref for 30 days or __obref for 365 days on a device that opted in. We no longer load that SDK or use those cookies; existing cookies expire according to their previous lifetimes.
For events sent before measurement stopped, see OpenAI’s privacy policy.
Deleting your account
You can delete your account yourself. In the dashboard or the Android HMU app, open the menu at the top right, choose Delete account and type DELETE to confirm. In HMU for iPhone, Settings > Account > Delete account opens the deletion page in your browser, where you confirm the same way. How to delete your account lists what is deleted and what is kept. We keep two records after a deletion. Payment records (amount, currency, date and the Stripe reference, with your account id replaced by a one-way code) are kept for 10 years after the end of the year of the payment, because tax and accounting rules require them, then deleted. A deletion record with your account id and the time is kept for 90 days, so a late payment message cannot bring the account back, then deleted. Stripe, which processes payments for us, keeps its own records of past payments, as payment processors must: invoices, charges, the email used to pay, and the card brand and last four digits. If you cannot sign in, email karim@brandgrowthos.ai from the address on your account and we will delete it.
Contact and support
For help with the dashboard, the apps or your data, including a copy of your data, email karim@brandgrowthos.ai.