Legal / Security
Security
Plain-English summary
- Every connection is encrypted, and passwords are stored only as hashes.
- Each shop sees only its own records, and each person only what their role allows — checked on the server, not just hidden on screen.
- Sign-in attempts are limited, and a password reset or a turned-off account signs that person out at once.
- Found a problem? Write to chnailab@gmail.com.
1.How your records are protected
- Encrypted connections. The site is served only over HTTPS, and browsers are told never to use an unencrypted connection to it. The database accepts encrypted connections only and encrypts what it stores (AES-256, per Neon).
- Passwords are stored only as bcrypt hashes. Nobody at PhsarOS can read your password, and we will never ask you for it.
- One shop, one set of records. Every read and every change is limited to the signed-in person's own shop, and automated tests check that one shop cannot reach another's records.
- Roles, enforced on the server. A cashier's session cannot call what only a manager or owner may do, whatever the screen shows.
- Sign-in limits. 10 attempts per email and 30 per network address every 15 minutes, and 5 new accounts per network address an hour. Confirming a deletion with your password is limited the same way.
- Sessions that end. A sign-in ends after 7 days without use and after 30 days in any case. Resetting someone's password, changing their role or turning their account off signs them out on every device.
- An activity log of who changed what in the workspace.
- No card data. PhsarOS takes no payments, so it never sees a card or bank number.
2.What PhsarOS does not have yet
It is a free beta, run on free hosting plans. There is no security certification (SOC 2, ISO 27001), no uptime guarantee, and no dedicated security team. The only backup is the database's own history of up to 6 hours, so a mistake noticed later than that cannot be undone by us. We would rather say so than imply otherwise.
3.If something goes wrong
If we learn that someone reached data they should not have, we will tell the owners of the affected workspaces what happened, what was involved and what we are doing about it, as soon as we know.
4.Reporting a vulnerability
Email chnailab@gmail.com with enough detail to reproduce the problem. Test only against a workspace you created yourself — sign-up is free — and don't read other people's data or slow the service down. We will reply, keep you told while we fix it, and credit you if you would like.
5.Your part
Use a password you use nowhere else, give each person their own account, and turn an account off when someone leaves. See also the Privacy Policy.