Updated 2026-10-18
Privacy Policy
This explains what information 4AICode collects, how it is used, and the purpose of browser cache.
1. Information We Collect
Account information: email, login method, account identifier returned by third-party login, organization information, and basic profile data.
Usage information: request time, model, token count, HTTP status, cost, organization used, Token, request routing result, and related metadata.
Payment information: order number, payment status, Stripe customer ID, subscription and top-up records. Card information is handled by the payment provider.
Risk control information: request review results, blocking reasons, upstream model reroute signals, account or Token risk levels, sampled audit records, and necessary access audit records.
2. Request Content Processing
Regular request bodies are used for forwarding, content safety review, billing, troubleshooting, and risk control. Streaming responses are used only for forwarding and usage statistics.
When a request is blocked by content safety review, the system retains a redacted and truncated input summary for security audits and appeals.
For high-risk accounts or Tokens with a risk_tier of probation or quarantine, the system may retain redacted and truncated input summaries through low-probability sampling. Default sampling rates are 1% for probation and 10% for quarantine; during extreme anomaly investigations, the sampling rate may be temporarily adjusted for specific Tokens.
Requests from trusted-tier accounts remain at zero sampling. Sampling results are not exposed through response headers, error messages, or other user-visible signals.
3. Protection of Risk Control and Audit Data
Sample summaries automatically remove or replace sensitive information such as API keys, Bearer tokens, emails, private keys, long ciphertexts, and credit card numbers, and limit summary length.
Sample summaries are used only for anti-abuse analysis, rule tuning, upstream warning tracing, appeal handling, and dispute resolution. Standard admin views display only aggregated information and metadata.
Viewing sampling summaries requires a named administrator account. Every view is recorded in the access audit log, including the administrator ID, viewing time, and target Token.
Sample summaries are retained for no more than 30 days by default; content safety interception records and upstream risk-control signals are retained for no more than 90 days by default.
4. Browser Cache
The frontend uses browser local storage to save login status, interface preferences, and update log read status.
The site uses PostHog and random anonymous browser identifiers to measure page visits, referring sites, device and language, visit duration, and completed registration and payment events. Collection stops when Do Not Track is enabled.
This data is stored in your browser. Clearing browser data will reset the related status.
5. Third-Party Services
The service may use upstream AI services, Stripe, email services, GitHub Sign-In, Google Sign-In, Cloudflare, and other infrastructure.
These services process necessary data according to their own policies, such as for payments, login verification, email delivery, and request forwarding.
PostHog processes anonymous visit statistics in its US region. Reports contain sanitized page paths, referring sites, and basic device information. Invitation links use route templates. Collection of page query parameters, form content, account details, and session recordings is disabled.
6. Data Security
We minimize data collection and encrypt sensitive credentials at rest.
Sensitive information such as API Tokens, OAuth tokens, and payment keys is not proactively displayed in logs.
Risk control audit data follows the principle of least-privilege access. Administrator access to sampled summaries is logged for internal auditing.
7. Your Rights and Contact Us
If you want to access, correct, or delete account data, or request deletion of sampled summaries still within the retention period, contact [email protected].
The Privacy Policy may be updated as the product changes. When updated, we will notify you through the website, email, or release notes whenever possible.