Is this a certification?
No. It describes how the product works. Ask sales for the details your security review needs.
Isolation between companies enforced by the database, permissions checked on the server for every request, protected sessions and encryption in transit and at rest.
No. It describes how the product works. Ask sales for the details your security review needs.
Every request runs inside a database transaction bound to one company, with row-level security.
Every action is checked on the server, and removing a permission takes effect at once.
Records are public, internal, confidential or restricted, and each role has a clearance.
HttpOnly, Secure and SameSite=Strict cookies, anti-forgery tokens, and sessions that end after 7 days idle or 30 days at most.
On Enterprise: sign-in through your identity provider and member provisioning with SCIM.
Only salted scrypt hashes are stored, and reset links work once, for 30 minutes.
Stricter limits on sign-in, password and invitation actions.
HTTPS with TLS 1.3 at service endpoints, TLS to the database, and encrypted storage, files and queues.
Guests never get a company session and see only what their link allows.
Invitations, role changes, guest access and company changes in an append-only log.
An admin invites a new member by email and chooses their role.
The member sets a password of at least 8 characters, or signs in with SAML SSO on Enterprise; the session is protected and time-limited.
The server checks every action against the role and the record’s clearance.
Guests enter with an expiring link and, when required, the host’s approval.
When the person is removed, they are signed out at once and the change is recorded in the audit log.
Every plan includes these controls. Enterprise adds SAML SSO, SCIM provisioning, a custom SLA and dedicated onboarding.
Runs the platform, isolates companies, encrypts data and checks every permission.
Give the right roles, control guest access and remove people who leave.
Uses a strong password, signs out on shared devices and protects their computer.
No. Database row-level security binds every request to one company, and the service refuses to start if it could bypass those rules.
No. HyoNova stores only a salted hash, and owners and admins cannot see or change another member’s password.
Yes, on Enterprise, through SAML SSO and SCIM provisioning.
Yes. Uploaded files are kept in encrypted storage, and the database is encrypted at rest.
Through the contact page, with the affected URL and short, non-sensitive steps to reproduce.
Contact sales for the details your review needs, or start free and see the controls yourself.