Small data. Short life. Strong controls.
A practical overview of the safeguards around file jobs, developer credentials, and anonymous service data.
Last updated 19 October 2026
Security by design
Sada Files minimises collection, separates browser and assisted workflows, validates formats, applies fair-use limits, and uses short retention windows. Temporary file keys and objects have matching expiries.
Credentials
Developer passwords use a one-way password hash. API keys are shown once and stored as token hashes with a visible prefix, scopes, expiry, revocation state, and last-used timestamp.
File controls
Assisted jobs use encrypted temporary storage, expire within 24 hours, and expose Delete now. Keep original files, inspect important outputs, and avoid submitting unnecessary sensitive information.
Report a vulnerability
Email support@sadafiles.com with reproducible steps and impact. Do not access other people’s data, disrupt service, or publish exploitable details before we can investigate.

