Legal · Early access
Privacy
1. Website
CodexShare does not use advertising trackers. Account registration, login sessions, password recovery, and account emails are handled by Supabase and our configured email delivery provider.
2. Account and device data
We store your email address, internal user ID, CLI installation metadata, revocation state, and per-process usage records. CLI refresh tokens and Access Bundles are kept in the macOS Keychain when available, or in a private 0600 file on supported systems.
3. Request content
Model request and response content travels through the centrally selected public Provider daemon and the CodexShare Gateway so it can reach the Codex backend. CodexShare does not persist those bodies in product logs, but the Provider machine handles them in memory and the centralized Gateway handles them in transit.
4. Operational metadata
Local logs may include timestamps, lifecycle events, connection identifiers, route names, error summaries, request counts, byte counts, and token counts. Credential fields and enrollment material are redacted.
5. Credits and payments
We store append-only credit ledger entries and source-separated verified-payment and Share-earned balances. For a Stripe Test top-up we also store the payment order ID, payment provider and method, USD credit and charge amounts, payment state, Stripe checkout session, payment intent, charge and refund identifiers, and payment timestamps. Stripe handles checkout and card data under its own privacy terms; CodexShare does not receive the full card number or security code.
6. Contact
Privacy questions can be sent to hello@codexshare.codes.