01
Your key, hashed
API keys are stored as one-way hashes. Platform staff, exports and logs never contain a complete key. The owner can retrieve the value when needed.
Security
What happens to your data?
Here is what we store, what we never store, and what you can control.
02
Prompts are not stored
Request and response bodies are not written to the platform database. Call records retain metadata such as model, token counts, cost, status and latency.
03
Revoke access immediately
Resetting a key generates a new value and invalidates the old one immediately. Disabling a key takes effect on the next request. Both actions are audited.
04
Staff and customer accounts are separate
Customer accounts and staff accounts are isolated. Admin screens never expose a complete customer key. Team members only see keys assigned to them.
05
Limits on every key
Per-key scopes, team roles, concurrency limits and IP rate limits reduce the impact of a leaked credential or a runaway client.
06
Admin actions leave a record
Dangerous actions such as key resets, risk actions and platform-side changes require confirmation and produce an audit record with actor, time and reason.
Report a security issue
Report what you found.
Email support@models.seedone.ai with the details and a request id if available. Do not include live API keys.
Security contact
support@models.seedone.ai For account or billing issues, the console support desk is faster. Security reports are read by the platform team.