Headroom Privacy Policy
Prepared on November 1, 2026
Headroom is an AI subscription usage utility operated by Donghyun Nam. For privacy questions, contact namudongs@gmail.com. Headroom is independent of, and is not affiliated with or operated by, the AI service providers you connect.
Information stored on your devices
Authentication tokens and API keys for connected services are stored in the operating system's secure storage. Account identifiers, email addresses, plans, usage, reset times, settings and recent provider responses are stored in the app's on-device storage. Observed usage history is trimmed to a maximum recent 35-day range when updated. The latest responses and account details can remain until replaced or the account is disconnected. We do not send these account details or usage records to our server.
Communication with connected providers
When you choose to connect a service, Headroom uses that provider's authentication page in the system browser or accepts an API key. Authentication, token refresh, account and usage requests go directly from your device to the provider. The provider receives the authentication and network information needed to handle the request, subject to its own terms and privacy policy. Headroom does not send prompts to generate AI conversations. For supported accounts, after your confirmation, it can send a request to use a quota-reset entitlement supplied by your provider. Granted permissions can be broader than the app's usage-query features; the in-app privacy information describes the connection scopes.
iOS background refresh
The background refresh setting is on by default. On iOS, when a connected account is present and the setting is on, Headroom sends an Apple push notification token and the development or production environment to a Cloudflare-hosted server to request background refresh. The database stores only the push token, environment and registration/update timestamps. We do not combine this registration with your name, email, provider account or usage. The server sends content-free background notifications through Apple Push Notification service. The operating system decides when, or whether, refresh runs. This registration is separate from permission for visible notifications.
Cloudflare provides the server and database, and Apple provides push delivery. These providers can process network information such as IP addresses as part of providing those services. Headroom's server code does not store IP addresses in its database, and Worker request logging and observability are disabled. Push registrations have no fixed expiration period. Tokens are removed when Apple reports a permanent invalidation.
Widgets, Apple Watch and notifications
Widgets receive display data, including usage and account labels, through an App Group. Display-only account names, plans and usage are sent to your paired Apple Watch for its app and complications. Authentication tokens, API keys and raw provider responses are not sent to the Watch. Widgets, Watch displays and notifications may be visible to others who can see your device.
Analytics, diagnostics and support
Headroom does not use advertising, tracking, analytics SDKs or an automatic remote crash reporter. Recent diagnostic responses remain on your device. The Copy action places the selected response on the system clipboard. Support emails do not automatically include diagnostics. If you send a support request or attachments, we use your sender address and the information you choose to send to respond. Do not send authentication secrets. Support information is kept only as needed to handle the request and meet applicable legal obligations; deletion requests can be sent to our contact address.
Disconnecting and deleting information
Choose Disconnect in an account's detail screen to remove its on-device credentials and account/usage cache. This does not delete your account with the provider. To revoke the provider's authorization completely, also review that provider's account settings. Copies already shared to other devices, the clipboard or email need to be managed separately.
Turning background refresh off in Settings requests deletion of the server's push registration. Disconnecting all accounts also requests deletion of that registration. A network failure may require reconnecting to complete deletion. Turning the setting back on with a connected account can register the device again. Uninstalling the app alone does not immediately delete the server's push registration. Turn the setting off or disconnect all accounts before uninstalling. Contact namudongs@gmail.com about server-held information or deletion. Because push registrations are not linked to provider accounts, an email address alone may not identify a registration.
Headroom does not create its own user accounts. We will update this page if this policy or our data practices change.