Security

Security and access protection

How HyoNova separates companies, checks every permission on the server, protects sign-in and encrypts data, and how to report a concern.

  • Company isolation enforced by the database
  • Every permission checked on the server
  • Encrypted in transit and at rest
A shield with a lock protecting an office desk, beside a completed checklist.

At a glance

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.

Where is it hosted?

The platform runs on AWS with its primary deployment in Frankfurt (eu-central-1). The marketing website uses Namecheap hosting and Cloudflare edge services.

Controls in HyoNova today

Company isolation

Row-level security in the database for every company. The service refuses to start if its database account could bypass those rules.

Server-side permissions

Five standard roles and custom roles. The server checks every request, and nobody can grant more than they hold.

SAML SSO and SCIM

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.

Data classification

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.

Secure sessions

HttpOnly, Secure and SameSite=Strict cookies, an anti-forgery token on every change, sign-out after 7 idle days and 30 days at most.

Protected passwords

Salted scrypt hashes, at least 8 characters, and reset links that work once, for 30 minutes.

Encryption

HTTPS only with a TLS 1.3 policy, TLS to the database, and encrypted database, files, queues and cache.

Limited guest access

Guest links expire and can be limited in uses. Guests never get a company session and see one office or one meeting only.

Audit log

Invitations, role changes, member removal, guest access and company changes are kept in an append-only log.

Protected connections

Provider authorizations and webhook addresses are kept encrypted in a secret store, never shown again and never written to logs.

Report a security concern

Contact us

Use the contact page with the affected public URL and a short description.

Share safe steps

Include steps to reproduce without passwords, personal data or customer content.

Stop if others could be harmed

Stop testing if it could expose another customer's data, disrupt the service or change a live account without permission.

We assess and coordinate

We review the report and coordinate the fix and any notifications that are required.

Shared responsibility

Your part

Protect your devices, keep roles tight, review connected apps and remove members who leave.

Our part

Keep company data isolated, enforce permissions on the server, encrypt data and protect the secrets of your connections.

Connected providers

Providers you connect, such as Google, Microsoft or GitHub, process data for their own functions under their own terms.

Questions and answers

Can admins see or reset a member's password?

No. Owners and admins cannot see, reset or change another member's password.

What happens when someone leaves the company?

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.

Is the reporting channel a bug bounty?

No. It does not give permission for intrusive testing and does not promise a reward.

Where can I read about personal data?

In the privacy policy, the data processing addendum and the subprocessors register.

Work in a place that protects your company

Start free and invite your team with the roles that fit them.