Transparency

What we keep. What we’re asked. Signed.

Exactly what is stored and for how long, every request from authorities, and a signed statement you can check yourself — updated every month.

Signed 8 October 2026next update by 8 November 2026

What we keep

Exactly what is stored, why, and for how long. Nothing else.

What
Why
How long
Account numberPlus a one-way fingerprint of your login key — never the key itself
Signing you in
While your account exists
Balance and planAnd a record of your top-ups and charges
Billing
While your account exists
Usage countsTime, model, tokens and cost of each request — never what you wrote or what the model answered
Billing
While your account exists
Network at sign-upThe network you connect from — never your IP address, country or city
Fraud prevention
Deleted right after payment
Top-up amountThe US$ amount credited to your balance, and the date
Your balance and our accounts
While your account exists
Payment detailsCoin, exact amount, receiving address and blockchain transaction ID. Only a one-way fingerprint is kept, so the same payment can never be credited twice. A payment we can’t match to an order is kept only until we resolve it with you
Crediting your payment
Deleted right after payment
API keysA one-way fingerprint, the name you give the key and its last 4 characters
Managing your keys
While your account exists
ContactA Telegram handle or email — only if you choose to add one
Support
Until you remove it
Published sitesSites you choose to publish from your workspace
Serving them publicly
Until you delete them
Contact-form messagesWhat you send us through the contact form
Replying to you
Deleted once your issue is resolved
Request logsTechnical request logs for the API — switched off
Running the service
Not stored

What we never keep

Your conversations

Your prompts and the model’s replies. They are processed to produce the answer and never written to our database. Your chat history stays in your own browser.

Your keys

Your login key or API keys in readable form.

Your identity

Your name, email address, phone number, IP address, country or city. A contact is kept only if you add one yourself.

Your card or bank

Card or bank details. We don’t accept cards or bank transfers.

Requests from authorities

Counted every quarter. If we are ever legally forbidden to publish a number, the statement below stops being updated.

Q4 2026 (from launch on 6 October)
Requests received
0
Data handed over
0
Accounts affected
0
Warrant canary

Our monthly promise

In some countries the authorities can secretly order a company to hand over data and forbid it from telling anyone. We can be forced to stay silent, but never to lie. So every month we publish this statement — in the industry it is called a warrant canary. If a month ever passes without it, take that as the sign.

It is signed with a key only we hold, so nobody can fake it. The Bitcoin block number proves the date: nobody can know it in advance.

Signed

Key fingerprint: SHA256:PjmNz0nCW/lyEWLdBvSFfA4vKwTea0EXZX9/BBO1X7w

canary.txtcanary.txt.sigPublic key
Always Yes — warrant canary
Date: 8 October 2026

1. Always Yes has not received any national security letter, gag order or other secret order requiring us to hand over user data or to stay silent about it.
2. Always Yes has not been required to change its systems to collect, keep or disclose user data.
3. Always Yes has not handed any user data to any government or authority.

Latest Bitcoin block when this was written:
  height 970510
  hash   00000000000000000001d475a45969bf4991e5351185e475b52a5f523be8aa80

The next update will be published by 8 November 2026.
If it is not, assume something has changed.
Signature verification

For technical readers

You don’t need to do this. But anyone can confirm the statement really came from us and was not changed, by running these commands. A genuine one prints Good "alwaysyes-canary" signature.

# on a Mac or Linux computer, in Terminal
curl -sO https://status.alwaysyes.net/canary/canary.txt
curl -sO https://status.alwaysyes.net/canary/canary.txt.sig
curl -sO https://status.alwaysyes.net/canary/allowed_signers
ssh-keygen -Y verify -f allowed_signers \
  -I canary@alwaysyes.net -n alwaysyes-canary \
  -s canary.txt.sig < canary.txt

Ready to get a straight yes?

Start using Developer API