Information We Process
The information processed depends on how you use the service and which platform features are enabled.
- Account information such as email address, profile details, authentication state and account status.
- API key names, group assignments, quotas, access restrictions and other key metadata.
- API usage metadata such as request identifiers, selected models, token counts, timing, cost and status.
- Network and device information such as IP address, user agent and request context.
- Billing, payment order, subscription and refund-request metadata when payment features are used.
- Security, administrative audit, content moderation and prompt audit information when those controls are enabled.
How We Use Information
We use information to provide accounts and API access, authenticate requests, calculate usage and charges, operate support, diagnose failures, prevent abuse, enforce applicable policies and maintain service security.
API & Usage Data
API request content must be processed to route requests to the selected model provider and return results. Usage records may include model, token, timing, cost and request metadata.
When configured security controls are active, the system may create content excerpts, redacted previews, prompt hashes, risk results or full prompt audit events for review. Administrative audit records use masking and redaction for configured sensitive fields, but customers should avoid sending secrets that are not required for a request.
Security
The platform includes access controls, API key restrictions, credential masking, audit records and optional security review features. No online service can eliminate every risk, and customers remain responsible for protecting their credentials and client systems.
Data Retention
Information is retained for operational, billing, security, support and legal purposes as reasonably necessary. Retention may vary by record type, enabled settings and administrative cleanup configuration. We do not promise a fixed retention period in this policy.
Third-Party Services
Requests may be transmitted to selected upstream model providers and infrastructure or payment providers needed to deliver the service. Those providers process information under their own terms and privacy practices.
Your Choices
You can manage account details and API keys through available account controls, limit the data included in requests, and contact support about account or privacy questions. Requests may be subject to identity verification, security needs, legal obligations and record-keeping requirements.
Contact
Use the support channel published in the current Gengxi API public settings for privacy questions or requests.
Contact Support