Updated 13 October 2026
Privacy
& your data.
The Mac app reads provider usage through local integrations. The website demo uses example data. Here is what each part stores and connects to.
Browsing this website
The interactive notch on the homepage uses fixed example readings. It does not connect to your AI accounts or read credentials. Fonts, icons and the background image are served with the site.
Public pages use a small first-party analytics script to count page visits and checkout clicks. It sends the public page path, a fixed traffic-source category and random event and visit identifiers to this website. It does not send complete page URLs, query strings, referrer URLs, email addresses, AI account details or payment details. The tracking records are kept in private Vercel storage and do not store IP addresses or browser request headers. Ordinary hosting logs can still contain network request information.
The visit identifier is saved in this tab’s session storage and is replaced after thirty minutes of inactivity. It is not a persistent cross-site identifier. The script respects Do Not Track and Global Privacy Control signals by skipping visit and checkout tracking. Closing the tab or clearing this site’s browser data removes the saved visit. No advertising tracker is included.
Stripe-confirmed purchases are counted separately, including purchases with a full discount. A non-secret checkout reference lets us connect a purchase to its public checkout page and temporary visit when available. Free orders are separated from paid sales. Conversion records use a hashed purchase identifier and do not include the private purchase credential, customer email or card information. The private download page does not load the analytics script.
Reset countdowns and browser storage
The Codex reset tracker saves your chosen usage window, reset timestamp and display timezone in this browser's local storage. It also caches successful public-feed responses so saved posts remain available if the feed cannot be reached. These saved values are not sent to an AI Usage Tracker account service.
Use the countdown's clear control to remove your saved timer. Clearing this site's browser data also removes the timer, timezone preference and cached announcements. A timer in one browser is not automatically shared with another browser or device.
Public feeds and external links
While the reset page is open, your browser requests public announcements from willreset.com and service status from status.openai.com, initially and every five minutes while the tab is visible. Those services receive ordinary network request information. The requests do not send your AI account credentials or your saved personal countdown.
Links to original posts open X. Documentation links open their respective providers. Those sites handle visits under their own policies. AI Usage Tracker is independent of OpenAI, Anthropic and Cursor; displaying a provider's name or linking a post does not imply endorsement.
Provider access in the Mac app
Depending on the integration, the app reads compatible local sign-in files, keychain entries, cached usage, a local runtime or a provider's usage endpoint. Requests to a provider use the credentials required for that integration. Some providers require a key entered in Settings or an explicit sign-in inside the app.
Read the Claude, Codex and Cursor pages for their specific data sources and limitations. Provider access is separate from the website's example demo.
Data kept on your Mac
The app saves preferences and recent usage readings locally so it can restore its display after a restart. Provider integrations can also use local credentials and account information needed to identify the connected account.
Switching a provider off stops its polling and forgets its tracker readings. It does not sign you out of the source application. Optional local-model measurements process runtime activity to calculate counts and timings. The local-model monitoring features do not save prompts, reasoning or replies.
If you enable phone pairing, the companion receives display readings over the local network. The pairing protocol does not send provider tokens, credentials or raw provider responses. Removing a paired phone revokes that device's access.
Purchases
Payments are processed by Stripe Managed Payments on Stripe's checkout. Stripe collects the information needed to process your purchase, including payment and billing details. The AI Usage Tracker website does not receive or store your full card number. See Stripe's Privacy Policy.
The download service checks your payment status with Stripe and stores a fulfillment record in private Vercel storage, including the product, price, purchase time and a hashed purchase identifier. It does not store your email address in that fulfillment record. The service checks for refunds and disputes before issuing a download link.
Your private purchase-page link grants access to your download. Keep it private. Installer links expire after ten minutes; your purchase page can generate a new link while your purchase remains eligible. The purchase identifier is moved out of the page's query string into its URL fragment after the page loads. Hosting systems can still receive the initial redirect URL. The download page does not load third-party analytics. Vercel hosts the website, delivery service and private installer storage; see Vercel's Privacy Policy.
Activation and private app updates
Activate this Mac connects your purchase to the installed app. The browser receives a temporary code that expires after ten minutes and can be redeemed once. The activation service keeps the associated Stripe checkout identifier, a randomly generated installation identifier and activation time in private Vercel storage. It does not use a hardware fingerprint.
The app saves its update credential in your Mac's Keychain. Update checks send that credential to AI Usage Tracker's server so it can verify current purchase eligibility with Stripe. Knowing the feed URL alone does not grant download access. Activation and update requests do not send your AI provider credentials, usage readings, prompts or conversation content to this service.
Questions about data
See the support page for setup guidance and the information needed to investigate an issue. Do not send credentials or private conversation content in a support request.
For privacy or data requests, email tom@aiusagetracker.dev.