How we keep your data yours

Aoient keeps every company's data separate from the first line of code. This page lists exactly what protects it today, and what isn't built yet.

  • Principle 1

    Checked on the server

    The browser is never trusted to say who you are or which company you belong to.

  • Principle 2

    Denied by default

    If a permission isn't explicitly granted, the answer is no.

  • Principle 3

    Honest about gaps

    What isn't built yet is listed at the bottom of this page.

What's in place today

Each control below is implemented and covered by automated tests.

  1. 01

    Tenant isolationIn place

    Every page, action, API call and live update proves on the server that you're an active member of the organization. Automated tests try to read and change other companies' data and must fail.

  2. 02

    No existence leaksIn place

    Another company's records and records that don't exist return the same "not found" answer, so nobody can probe for them.

  3. 03

    Locked-down databaseIn place

    Row-level security is on for every table with no browser policies, so the public key can't read or write anything directly.

  4. 04

    Roles without escalationIn place

    Permissions are checked on the server. You can't grant permissions you don't hold, act on more senior members, or change your own role. Linking an account to an employee record needs the right to see private details.

  5. 05

    Verified sign-inIn place

    Accounts are handled by Supabase Auth with email verification or Google. Sign-up and sign-in forms are protected by a Cloudflare Turnstile bot check, and redirects after sign-in can never leave the site.

  6. 06

    Staff loginsIn place

    Temporary passwords set by an admin are never stored or logged by Aoient. People choose their own at first sign-in, and signing in with Google retires the temporary one.

  7. 07

    Safe invitationsIn place

    Invitation links carry a random 256-bit token stored only as a hash, expire after 7 days, work once, and only for the invited email address.

  8. 08

    Verified paymentsIn place

    Plans change only when Paddle's signed webhook or Paddle's API confirms them on our server. A browser redirect never unlocks anything.

  9. 09

    Audit logIn place

    Organization, member, role, people, leave and billing changes are recorded in the same database transaction as the change itself.

  10. 10

    Rate limits and input checksIn place

    Sensitive actions are rate-limited, every input is validated on the server, all database queries are parameterised, and CSV exports are protected against formula injection.

  11. 11

    Secure headers, no secrets in the browserIn place

    Clickjacking and sniffing protections are on, and secret keys are only ever read on the server.

Not built yet

We don't claim these until they exist.

  • Two-factor authentication (MFA)
  • Content Security Policy header
  • Automated backups and monitoring dashboards
  • A searchable audit log page in the app (the data is already recorded)

How we handle personal data is described in the Privacy Policy.

Bring your team in safely.

14-day free trial. No card needed to start.