Privacy policy.

This policy covers failure.fail, api.failure.fail, the console and Failure ID accounts, all run by Failure Model Labs, a company based in Singapore ("we", "us"). We handle personal data in line with Singapore's Personal Data Protection Act 2012.

1. What we collect

Your account

• Email address and name.
• A hash of your password (PBKDF2). We never store the password itself.
• Two-factor secrets (TOTP) and hashed recovery codes, if you turn two-factor on.
• Passkey public keys, if you register a passkey. The private key never leaves your device.
• Your GitHub or Google account identifier and email, if you sign in with them.
• Session records: IP address, user agent and timestamps, so you can see and revoke sessions in the console.
• An account audit log of security events, such as sign-ins, key creation and two-factor changes.

Your API use

• If you turn on face check: face templates (sets of 128 numbers for your front, left and right views), encrypted with AES-256-GCM. Camera frames are analysed in memory — face landmarks, head pose, blinks and an anti-spoofing score — and never stored. If you trust a device for face-only sign-in, a random device token (stored hashed) and the device's name. Remove face check in Security to delete the templates and untrust every device.
• Request metadata for billing: which key, which model, token counts, cost and timing.
• Hashed API keys. A key is shown to you once and then stored only as a hash.
• Your monthly spend cap and spend to date.

When you contact us

The name, email, topic and message you send through the contact form or by email.

2. What we do not keep

We do not train on API traffic. We do not store the content of your requests or responses beyond short-lived caches that make the service faster and cheaper for you:

• Response cache: 1 hour.
• Pre-answer brief cache: 24 hours.
• Conversation-prefix hashes, used to bill resent earlier turns at the cached rate: 1 hour.

After those windows, cached entries expire.

3. Upstream model providers

Failure Tempest 1 sends your prompts to the upstream models in its panel (Anthropic, OpenAI and Google) to produce an answer. Those providers process prompts under their own terms and privacy policies. We choose API access that the providers offer to businesses, but we do not control what they do with the data they receive.

4. Why we use it

• To run your account and keep it secure.
• To serve API requests and bill for them accurately.
• To enforce spend caps and our acceptable use policy.
• To answer you when you write to us.

We do not sell personal data and we do not use it for advertising.

5. Where it lives

Our edge runs on Cloudflare Workers and accounts are stored in Cloudflare D1. The model router runs on our own server. Data may therefore be processed outside Singapore; where it is, we take reasonable steps to protect it to a standard comparable to Singapore law.

6. How long we keep it

Account data is kept while your account exists. Billing records are kept as long as we need them for accounting and legal obligations. Session records and audit log entries are kept so you can review account activity, and are removed when the account is deleted unless we must keep them to meet a legal obligation or resolve a dispute.

7. Your choices

• You can see and revoke your sessions and API keys in the console.
• You can ask for a copy of the personal data we hold about you, or ask us to correct it.
• You can ask us to delete your account and its data by writing to hello@failure.fail from the email on the account.

8. Cookies

We use a session cookie to keep you signed in. We do not use advertising or third-party tracking cookies.

9. Security

See our security page for how accounts and keys are protected. If we become aware of a breach that affects your personal data, we will tell you and the relevant authorities as the law requires.

10. Changes

If we change this policy, we will update the date at the top. For material changes we will tell account holders by email.

11. Contact

Failure Model Labs, Singapore. Email hello@failure.fail, or use the contact form.