Browser-local by default
The current workspace can save drafts in your browser storage without requiring an account.
Trust
Security and Trust
SteadyFile handles sensitive personal records, so the product is explicit about what stays local, what is shared only by user action, and what users should still control themselves.
Translations are provided for accessibility and convenience. If there is any inconsistency, the English version is the reference version unless a reviewed local version is published.
Current security posture
Originals not uploaded by default
The workspace references original records and can compute local SHA-256 hashes. Original evidence files are not uploaded by the browser-local workflow.
Optional accounts
Signing in is optional. An account stores your structured record (entries, people, record references and their fingerprints) and a server-dated entry history, never original files. It is not required to start a private record.
No access for anyone else
The product has no employer or landlord dashboards, no HR integrations, and no way for anyone else to see a user's file.
Transport security
Public routes are served over HTTPS by the hosting provider. Backend traffic should also use encrypted provider-managed connections.
Access controls
Account data is stored per user, and the database returns only the signed-in person's own rows. Structured records only; no access for anyone else.
Data lifecycle
Browser-local drafts remain on the device until the user clears them. Account holders can download everything their account holds or delete the account from the account page.
Report a security concern
Email hello@steadyfile.com with the subject line Security concern. Do not include sensitive personal records in the initial report.