We don't keep your images.
Images are processed in memory, results are returned, bytes are discarded. The only thing we store is a one-way cryptographic hash for abuse detection.
Privacy FAQ.
Where are my images?+
Your images are processed in memory and never written to disk, stored in any database, or used for training. We store only a SHA-256 hash of uploaded bytes in usage_log for abuse detection — this hash is irreversible.
Is the /try endpoint different from /predict?+
Same model, same in-memory processing. The only difference is that /try is identified by hashed IP address instead of a user account, and is rate-limited to 1 check per IP per 24 hours.
Do you use my images to train the model?+
No. Images are processed in memory and garbage-collected when the request ends. We have no training pipeline that touches your data.
What we store and why.
We collect
- Account email — required to sign in. Provided by you via Supabase Auth.
- Credit balance and usage records — to bill you and prevent abuse.
- SHA-256 hash of uploaded image bytes — one-way; not reversible to the image.
- API request metadata — timestamps, response codes, processing time.
We do NOT collect
- The actual image bytes (no disk, no S3, no backups).
- EXIF metadata from your images.
- Any information about who is in the image.
Why we store a SHA-256 hash.
A SHA-256 hash lets us detect abuse patterns (one user calling our API repeatedly with the same image) without keeping the image. The hash is a one-way function: knowing the hash does not let us — or anyone — recover the original image.
Account deletion.
You can delete your account at any time from the dashboard. Deletion removes your profile, API keys, and usage records — including the hashed records of your prior usage.
Privacy contact: privacy@airegco.com