Skip to content
Security

Security &
privacy.

How Ablitron handles your keys, your data and your requests.

No prompt or output text stored

Our usage ledger records token counts, costs and request metadata — not the text of your prompts or responses.

Keys stored as hashes

API keys are hashed at rest and can be revoked anytime from the console.

Payments on Stripe

Card details are entered on Stripe's hosted checkout, never in the Ablitron app.

Essential cookies only

The console uses one session cookie for sign-in. No advertising or analytics cookies.

Requests and the inference provider

API requests are forwarded to an external inference provider to generate responses. No end-to-end zero-retention claim is made; don't send secrets or sensitive personal data during the preview. See our privacy information.

Protecting your account

Repeated wrong passwords pause password sign-in for that account from that network for a few minutes, without locking you out on your own networks. We email you when your password changes, when an API key is created and when Ablitron Code is connected, and Settings → Privacy lists your recent security activity. Each API key can have its own request and usage limits.

Responsible disclosure

If you believe you have found a security vulnerability in Ablitron, please tell us privately first. We appreciate reports from researchers and customers and will work with you to understand and fix the problem.

How to report

Email security@ablitron.com in English or Spanish. If you get no reply within a week, write to support@ablitron.com with “Security” in the subject. Include:

  • what you found and the impact you expect;
  • the steps to reproduce it, and the affected URL, endpoint or app version;
  • a request ID or timestamp where possible.

Do not send API keys, passwords or other people's data. Our contact details are also published in security.txt.

Scope

In scope: ablitron.com, the console and chat at ablitron.com/app, the API at ablitron.com/v1 and the Ablitron Code desktop app. Out of scope: services run by third parties (for example Stripe checkout and our email provider), reports without a demonstrated security impact, and denial-of-service, spam or social-engineering findings.

Please

  • Test only with accounts, keys and data that are yours, and stop as soon as you have shown the problem.
  • Do not access, change or delete other people's data, and do not degrade the service for others (no denial-of-service, no high-volume automated scanning).
  • Do not use social engineering, phishing or physical attacks against our staff, customers or providers.
  • Give us a reasonable time to fix the issue (normally up to 90 days) before you disclose it publicly.

What we will do

  • Acknowledge your report within five business days and keep you informed as we investigate.
  • Fix confirmed vulnerabilities as quickly as we can, and tell you when they are fixed.
  • Credit you publicly if you want us to.
  • Not pursue legal action against good-faith research that follows this policy.

We do not run a paid bug bounty at the moment.