How is our data kept apart from other companies?
Every request runs inside a database transaction bound to one company, and row-level security in the database shows only that company's rows.
How HyoNova separates companies, checks every permission on the server, protects sign-in and encrypts data, and how to report a concern.
Every request runs inside a database transaction bound to one company, and row-level security in the database shows only that company's rows.
The platform runs on AWS with its primary deployment in Frankfurt (eu-central-1). The marketing website uses Namecheap hosting and Cloudflare edge services.
Row-level security in the database for every company. The service refuses to start if its database account could bypass those rules.
Five standard roles and custom roles. The server checks every request, and nobody can grant more than they hold.
On the Enterprise plan, members sign in through your company's identity provider with SAML single sign-on, and accounts can be provisioned with SCIM.
Records are public, internal, confidential or restricted, and each role has a clearance. Restricted finance records such as invoices are visible to Owners only by default.
HttpOnly, Secure and SameSite=Strict cookies, an anti-forgery token on every change, sign-out after 7 idle days and 30 days at most.
Salted scrypt hashes, at least 8 characters, and reset links that work once, for 30 minutes.
HTTPS only with a TLS 1.3 policy, TLS to the database, and encrypted database, files, queues and cache.
Guest links expire and can be limited in uses. Guests never get a company session and see one office or one meeting only.
Invitations, role changes, member removal, guest access and company changes are kept in an append-only log.
Provider authorizations and webhook addresses are kept encrypted in a secret store, never shown again and never written to logs.
Use the contact page with the affected public URL and a short description.
Include steps to reproduce without passwords, personal data or customer content.
Stop testing if it could expose another customer's data, disrupt the service or change a live account without permission.
We review the report and coordinate the fix and any notifications that are required.
Protect your devices, keep roles tight, review connected apps and remove members who leave.
Keep company data isolated, enforce permissions on the server, encrypt data and protect the secrets of your connections.
Providers you connect, such as Google, Microsoft or GitHub, process data for their own functions under their own terms.
No. Owners and admins cannot see, reset or change another member's password.
Remove the member and their access ends, because every request is checked on the server. Their personal Drive and OneDrive connections are disconnected within minutes.
No. It does not give permission for intrusive testing and does not promise a reward.
In the privacy policy, the data processing addendum and the subprocessors register.
Sessions, passwords, encryption and guest limits in detail.
How we handle personal data.
Terms for processing your company’s data.
Providers that process data for us.
Architecture, apps and hosting.
Ask our team about security.
Start free and invite your team with the roles that fit them.