Privacy / data minimization

Less data. Fewer questions.

SafeAPI is designed around generated credentials and operational metadata rather than identity profiles.

Account data

We do not require an email address, name, phone number, or password. We store a keyed hash of your generated account key, hashed API keys, session records, balance, settings, and operational timestamps. Plaintext generated keys are shown only at creation and are not stored by the application.

Prompts and responses

SafeAPI does not write prompt or completion content to application logs. Requests pass through upstream AI providers, whose own data policies apply. Do not submit secrets or unnecessary personal data. Usage records contain model, token counts, cost, timing, status, and request IDs.

Technical and payment data

Cloudflare and SafeAPI can process IP addresses, user agents, security events, and rate-limit data. Our payment processor receives invoice details and blockchain transaction metadata. Account-less checkout does not prevent a payment provider from requesting additional information under its compliance rules.

Cookies and analytics

SafeAPI uses a secure session cookie for login and essential security controls. The initial service does not use advertising cookies or third-party behavioral analytics.

Retention and deletion

Usage and ledger records are retained as needed for accounting, fraud prevention, security, and legal obligations. Session tokens expire automatically. You can revoke API keys at any time. Contact support to review account deletion; required financial records can persist after access ends.

Security and contact

We use encryption in transit, hashed credentials, encrypted upstream credentials, restricted infrastructure access, and minimal logging. No system is guaranteed secure. Privacy questions can be sent to [email protected].