Privacy,
in plain language.

This policy describes AIUsageWatch and this website, provided by Guiix. Updated 4 October 2026.

Settings and readings on your Mac

The app stores account configuration, display preferences and the last good usage readings in ~/Library/Application Support/AiUsageWatch/. These files can include account labels, provider names, directories, colours, usage information and reading times. The app has no Guiix account system, advertising, app analytics or cloud synchronisation.

Provider credentials and network requests

Usage monitoring can require access to your provider’s existing authenticated session or local CLI login. The default Claude connection and Cursor connection read the Safari cookie file after you grant access. Other Claude directories use their .credentials.json. Codex uses the local CLI app-server and can fall back to local session transcripts. Grok reads usage information from its local unified log.

The app does not directly read the macOS Keychain. Provider CLIs have their own credential handling. Live readers contact the relevant provider using your existing authentication; these are not anonymous or entirely offline operations. Providers process those requests under their own policies. AIUsageWatch does not send account readings or credentials to a Guiix usage service.

Codex starter requests

At a live weekly reading of 100% remaining, the app can send a small Codex request to start the weekly window. This uses the configured directory’s saved CLI login and a small amount of its allowance. The attempt is remembered in memory; relaunching can allow another attempt. See the full starter behaviour. Historical fallback does not send such a request.

The website

The marketing pages have no advertising, analytics scripts, external fonts or embedded trackers. The interactive preview uses synthetic data and does not connect to provider accounts. Ordinary server access logs may record an IP address, requested URL, browser information and time, depending on the hosting configuration.

Contact messages

If you send the contact form, we receive your optional name, email address, topic and message, together with your IP address, browser information, UTC submission time and approximate city, region and country from a local GeoIP database when available. No precise device location permission or remote location lookup is used.

The form uses an essential session cookie to protect submissions. Rate-limit records contain a hashed IP filename and submission attempt times and are stored outside the public document root. The limit counts attempts within the previous hour. Messages go to our support inbox and may be processed by the relevant mail providers. We retain messages as needed to handle your request and meet legal obligations; information may also be disclosed when legally required.

Your choices

Remove configured accounts or quit the app to stop its usage monitoring. You can revoke the Safari cookie-file grant and remove the app’s local configuration and cache after quitting. Removing the app does not cancel a provider plan or delete that provider’s data. Use the contact form to request access, correction or deletion of information you have sent Guiix, or raise a privacy concern. Do not include passwords, cookie values or credential files in support messages.