How we protect your uploads, your keys, and the files you serve.
Tonta handles other people's files for a living, so security isn't a bolt-on. Below is a plain-English summary of how the platform is built and the controls you have. If you have a question this page doesn't answer, email hello@tonta.io.
Files live in a private object-storage bucket that is never publicly listable. Nothing is served straight from the origin bucket — all delivery is brokered through an edge layer that enforces access rules on every request.
Every uploader has its own key, and you decide where that key is allowed to be used. Keys are domain-restricted, so an exposed front-end key can't be reused from a site you don't own.
Uploads are validated server-side, not just in the browser. Images are re-processed during resizing and conversion, which strips the original file down to clean output rather than passing untrusted bytes straight through.
POSTYou own your files. You can delete any file or uploader at any time, and deletions remove the object from storage. For details on what we collect and retain, see our Privacy Policy; for the rules of use, see our Terms of Service.
If you believe you've found a security issue, please email hello@tonta.io with the details and steps to reproduce. We take reports seriously, will acknowledge them, and ask that you give us a reasonable window to investigate and fix before any public disclosure.