Security & data handling
What passes through Byesu, what we keep, for how long, and how we protect it. Plain facts, updated whenever the setup changes.
Last updated: November 16, 2026
What we keep
Everything we store about you and your requests, and how long it stays.
| Data | What it contains | How long |
|---|---|---|
| Prompts, files and outputs | Forwarded to the upstream service for the model you chose, so it can answer. Not written to our database or logs, and never used for training. | Not stored |
| Usage records | Time, model, token counts, charge, key name and client IP for each request. You see the same records in your usage logs. | 60 days |
| Error records | The same fields plus the error message returned upstream, used to diagnose failures. | 14 days |
| Web access logs | Request path, status code, IP address and user agent. API keys are masked before they are written. | Rotated by size; old files are overwritten |
| Account | Email, sign-in identifiers if you use GitHub, Google or Telegram, and a hashed password. | Until you delete the account |
| Payments | Order amount, currency and status. Card and wallet details stay with the payment processor. For USDT we keep the transaction hash. | As long as accounting and the law require |
| Backups | Encrypted copies of the database, so data you delete can remain in a backup for a while. | Hourly copies 48 hours, daily copies 30 days |
How we protect it
In transit and at rest
All traffic to byesu.com and its API uses HTTPS. Backups are encrypted with AES-256 before they leave the server, and are stored with a separate provider in the EU.
Accounts
Passwords are stored as salted hashes (bcrypt). New sign-ups verify their email. Repeated failed sign-ins from one address are blocked automatically.
API keys
Keys are masked in our logs. In the console you can give each key a spending limit, an expiry date, a model allowlist and an IP allowlist, and revoke it at any time.
Servers
Server access is by SSH key only, behind a firewall. Admin interfaces are not exposed to the public internet. Production access is limited to the core team.
Upstream providers
To answer a request we have to send its content to the upstream service that serves the model you picked. That service processes it under its own terms and privacy policy. If your input is sensitive, read those terms first and remove anything the model does not need.
Cookies and scripts
The console uses only the cookies needed for sign-in and security. We do not run advertising or analytics scripts in the console. One exception: visitors who arrive from one of our ad campaigns load the X (Twitter) conversion pixel, which tells us whether the campaign led to a sign-up.
Your rights
- Delete an API key at any time in the console; it stops working immediately.
- To get a copy of your data, correct it or delete your account, email legal@byesu.com from the address on your account.
- The full legal text is in the Privacy Policy.
Report a security issue
- Email security@byesu.com with the affected URL or endpoint, steps to reproduce and the expected impact.
- We aim to acknowledge reports within 3 working days.
- Testing rules are on the contact page; machine-readable contact at /.well-known/security.txt.
