Privacy

Routed API prompts and responses are processed transiently and are not stored by our platform after the API request completes. This commitment applies to routed API request and response bodies in platform storage.

The boundary does not cover content a customer chooses to put into support tickets, customer-side logs, screenshots, or documentation, and it does not prevent upstream AI model providers from processing request content needed to serve each API call under their own terms, retention settings, and data controls.

• Account identity, workspace membership, authentication state, and role metadata.
• API key metadata, delivery lane preferences, model preference settings, and key lifecycle records.
• Usage metadata such as token counts, request time, success or failure status, latency, public model id, delivery lane, and charge details.
• Billing records, credits, refunds, disputes, receipts, support tickets, and security signals.

We use data to provide the service, authenticate users, meter usage, calculate credits, create billing records, prevent fraud and abuse, debug incidents, answer support requests, maintain auditability, provide archive downloads, and meet legal or payment obligations.

Sign-in, payments, hosting, database, email, security, analytics, and AI model providers may process data for their parts of the service. We do not sell customer prompts, responses, usage, or billing data.

AI model providers receive the request content needed to serve each routed API call. Their API terms, retention settings, abuse controls, and data processing behavior apply to that provider-side processing.

Routed API prompts and responses

Processed transiently and not stored by our platform after the routed request completes.

Hot API metadata

Generally available for about 90-120 days for billing, audit, support, and abuse prevention.

Cold archive metadata

Eligible API metadata is archived in monthly batches after day 90, retained for 2 years, and downloadable by users with required workspace permissions.

Account, billing, support, and security records

Retained as needed to operate the service, resolve disputes, meet legal obligations, and protect the platform.

Platform cold archives exclude raw request and response bodies, messages, tool payloads, and file contents.

We use authentication, security, session, preference, and product analytics tools to operate and improve the service. These tools should be used for account, security, and product diagnostics, not for selling customer API content or billing data.

Depending on where you live, you may have rights to access, correct, export, delete, object to, or restrict certain personal data. Some records may need to be retained for billing, fraud prevention, legal, security, audit, or dispute reasons.

For privacy questions, email privacy@1api.club or open a support ticket from the dashboard. These privacy terms work together with the Terms and Refunds.