About this notice
This notice describes the Trackex website, Windows app and license delivery service. The public project/business name is Trackex. Trackex is independently developed and is not an OpenAI product. Purchases are made through Whop; eligible buyers retrieve their key and installer on the authenticated Trackex account page.
Live purchase and buyer identity
Whop processes purchases and order-confirmation email. The Trackex key page requests openid and profile when you sign in with Whop, to match the verified buyer to a paid purchase and show a friendly username or display name; it does not request email permission. The service retains the Whop user ID, payment identifier, encrypted license key and key hash, status and device allocations. Separately, Whop supplies the buyer name/username and purchase contact email with the payment record. These are retained in the private license registry for purchase and activation support, and cached in the owner's Windows-encrypted Keys tool. They are not shown to other buyers and are not used for marketing or automatic email. A username or display name is retained in the buyer session for up to one hour. Whop access/refresh tokens are not retained. Temporary sign-in state lasts up to ten minutes and a hashed buyer session up to one hour.
Ineligible purchases cannot retrieve keys or obtain new activation receipts. Completed full refunds revoke the corresponding production license. Trackex 0.19.3 and later enforce verified signed revocations and a bounded offline certificate. Earlier permanent-offline builds cannot be remotely forced to upgrade. This technical policy does not override mandatory consumer rights.
Usage information stays local
The desktop widget requests account status, rate-limit percentages and reset timestamps from the locally installed Codex app or CLI. Usage readings are displayed locally, not sent to the Trackex activation service. The widget does not ask you to provide a Codex password or payment details. It does not intentionally collect prompts, responses, source code or project contents.
Codex handles its own account authentication and may communicate with OpenAI under OpenAI’s policies. Live quota refresh is not an offline feature.
Activation and daily verification
The Windows app sends a license key, device public key and signed proof over HTTPS for activation. Production licensing verification then sends the license ID, device public key and signed timestamp/nonce proof once every 24 hours while the app is running. It does not send Codex credentials, quota readings, prompts or project contents. The service stores license status, device allocations and activation records; short-lived nonces prevent request replay.
Device identity is a per-Windows-user credential, not a hardware serial number. A signed certificate, non-exportable device credential and Windows-account-encrypted clock checkpoint are kept locally. The current production certificate allows up to 7 days offline after successful verification. Connection/server errors do not revoke a valid certificate or extend its expiry. Reconnect after expiry. A verified signed revocation disables the app without deleting files. Separate sandbox activation tests keep their own existing policy.
Local preferences and updates
Widget size, position, appearance, companion settings and the companion visit count are saved locally. Optional update checks and downloads contact the update source only when requested. That source may receive ordinary connection metadata; Codex credentials, quota values and project content are not sent by the updater. If you copy diagnostics and choose to share them, review the text first.
Website, cookies and messages
The informational website has no email signup, card-entry form, advertising trackers or analytics integration. Images, fonts and demo video are served as site assets. The separate key/download and sandbox routes use essential secure cookies, not advertising cookies: the live buyer session lasts up to one hour; sandbox retrieval sessions can last seven days. Hosting and security infrastructure may process ordinary connection/request metadata.
Support for buyers uses the seller-contact option in their Whop purchase. No contact form or support upload is active here. Whop handles its own messages under its policies; Trackex uses a received message to answer the request. Never send a Codex password, account token or payment-card details in support messages.
Service providers and location
Cloudflare provides the separate sandbox and live license/delivery services and databases. Website hosting: Cloudflare Pages. Whop handles live payments and confirmation emails. Providers may operate internationally. Providers handle their services under their own applicable policies.
Purpose and retention
License records are used to issue and verify licenses, enforce the device allowance and handle activation support. They are retained while needed to maintain the corresponding license and device allocation; they are not periodically erased by the license service. Local preferences and receipts remain until removed locally. Support messages, if received, are retained as needed to resolve the request and any applicable record-keeping obligations.
Contact Trackex through Whop for questions about your purchase records or privacy requests.
Questions and privacy requests
Depending on your location, you may have rights to access, correct or delete information or other applicable privacy rights. Rights and exemptions depend on your location. Buyers can use Whop’s seller-contact option in their purchase; invited testers can also use their existing developer contact channel. See Contact & Support. No payment-card details or Codex credentials should be sent to Trackex.