Private by default, with extra protection when you want it
Files stored in Convert and Store start private by default. You decide when a file or folder is shared, whether you want public access, and whether you want stored files protected with optional encrypted storage from your profile settings.
What that means in day-to-day use
- Validated uploads and careful file handling before anything is processed or stored
- Private storage with controlled delivery paths instead of direct open-directory access
- Optional encrypted storage for people who want another layer of protection for saved files
- Public share pages that can show your public username and avatar instead of exposing your full name
- Secure sessions, CSRF protection, and rate limiting on login, reset, upload, contact, and API flows
- Clear separation between public pages, user workspaces, and admin tools
Sharing stays deliberate
Public links are created intentionally from the file manager, and you can revoke them later. When someone saves a shared file to their own account, that copy becomes theirs and counts against their own storage, which keeps ownership and usage clearer for everyone involved.
Operational trust matters too
Security is also about product honesty. We do not want tools pretending to be live when they are not, or public pages exposing more than they should. That is why support detection, file moderation behavior, protected routes, and public identity controls are treated as part of the product experience, not background details.