Skip to content

Security & privacy

Your people’s data, handled with care.

Company data stored in the EU, private by default, every change on the record, and an honest list of what we have not done yet.

Activity: every change with who made it, when, and through which app

Stored in the EU. Your sign-in.

Company data is stored in the EU. Sign in with a password, Google or Microsoft; each company chooses which methods are on.

  • Password
  • Google
  • Microsoft
Sign-in methods: password, Google and Microsoft, each switched on or off

Private by default.

Every field has a visibility level. Pay is seen only by the person and by owners, admins and HR. Private details never go to an AI assistant other than one the person connected themself.

  • Public
  • Job
  • Private
  • Pay
Members and roles: who can do what

GDPR tools and Activity.

Export everything held about a person in one file, erase a former employee’s personal data, download all company data. Leaving is easy: export to Personio, Factorial, Sesame, HiBob, BambooHR or any spreadsheet in a few clicks. Activity records what changed, when, and whether it came from the app, the API or an AI assistant.

  • Export
  • Move to another tool
  • Erase
  • Activity
Connected apps: the AI apps connected to the company, and how to connect one

In place today

How we protect your data

Each of these is true in production today. The same list is Annex II of our data processing agreement.

Hosting and data residency

  • Google Cloud, in Belgium

    Bizisy runs on Google Cloud in the europe-west1 region (Belgium, EU): the application servers on Cloud Run, the database on Firestore and files on Cloud Storage.

  • Company data stays in the EU

    Company data is stored in the EU. Some providers (sign-in, content delivery, email delivery) may process data outside the European Economic Area, covered by Standard Contractual Clauses or the EU-U.S. Data Privacy Framework; the subprocessor list says which.

Encryption

  • Encrypted in transit

    Every connection uses HTTPS, with TLS 1.2 or later at our edge (Cloudflare). The session cookie is HttpOnly, sent only over HTTPS and only to your organization’s own address.

  • Encrypted at rest

    Google Cloud encrypts all stored data at rest with Google-managed keys. Session tokens, API keys, invite secrets and the tokens of connected AI apps are stored only as hashes; the secrets of connected tools and webhook signing secrets are stored encrypted. Passwords are held by Google Identity Platform, never by Bizisy.

Backups and restore

  • Point-in-time recovery for 7 days

    The database keeps point-in-time recovery data for 7 days and has delete protection on. Bizisy’s operators can restore it to any minute in those 7 days; there is no self-service restore and no other backup, so deleted data is gone for good after 7 days.

  • Your own copy, any time

    Owners and admins can download all company data at any time (in Settings, under Data & privacy), and keep their own copies.

Access control

  • Roles and field-level visibility

    Access follows roles (owner, admin, HR, member, viewer, or custom roles) and every field has a visibility level (public, job, private, pay). API keys and AI apps never receive other people’s private or pay details.

  • Least privilege inside Bizisy

    Each service runs with its own service account and only the permissions it needs. Secrets live in Google Secret Manager. The administration service never holds the secrets of the customer API.

  • Rate limits

    Sign-up, invite and password-reset requests, public lookups and API keys are rate limited.

  • Partner access only with the owner’s consent

    An accountant or other partner firm sees a company’s data only after one of its owners approves, on a page that lists exactly what the firm would see and do. The firm works with the role of its type (the Accountant role is read-only), never gets API keys or AI apps in the company, and everything its people do is in Activity under their own name, “via” the firm. An owner can change or revoke the access at any time, which ends the firm’s sessions in the company at once.

  • A separate sign-in for partners

    People of partner firms sign in to partners.bizisy.com with partner accounts in a sign-in tenant of their own, apart from every company’s. The partner console accepts only its own session cookie, sent to partners.bizisy.com alone, never an API key or token. A company is opened from the console with a one-time link valid for 60 seconds.

Access by Bizisy staff

  • Named operators only

    Only named Bizisy operators can open the administration page: an allow-list in the code, a Google sign-in less than 5 minutes old, and sessions that end after 8 hours.

  • No browsing of HR records

    The administration page shows each company’s counts, plan, billing and owners’ contact details, never its people’s HR records. Every request to it is recorded, with who made it, for a year.

Audit logs

  • Activity, in your hands

    Activity records every change: who made it, when, and whether it came from the app, the API or an AI assistant. Owners, admins and HR see it in the app, and assistants can look it up.

Incidents

  • A public status page

    status.bizisy.com shows the health of the app, the API, email and integration sync, checked every 5 minutes, with 90 days of history and every incident’s updates.

  • Breach notification within 48 hours

    If we confirm a personal data breach affecting your organization’s data, we tell its owners and admins without undue delay and within 48 hours: what happened, which data, what we did and what you should do.

Said plainly

What we have not done yet

Bizisy is in early access. Rather than imply more, here is what is not in place today.

  • No certifications yet

    Bizisy is not ISO 27001 or SOC 2 certified. Google Cloud and Cloudflare hold their own certifications, which do not make Bizisy certified.

  • No independent penetration test yet

    Bizisy has not had an independent penetration test. Changes that touch access, money or personal data get a security review before they ship.

  • No scheduled restore tests yet

    Restores are possible for 7 days, but we do not yet test them on a schedule.

  • No customer-managed keys

    Encryption keys are managed by Google; using your own keys is not offered.

Vulnerability disclosure

Found a security problem? Tell us.

Write to security@bizisy.com with what you found and how to reproduce it. We acknowledge every report within 2 business days and keep you informed until it is fixed.

Also in /.well-known/security.txt, as RFC 9116 describes.

In scope
bizisy.com and its subdomains: the app, the API, MCP, the developer site, the partner console and this website.
Out of scope
Denial of service, social engineering, spam, physical attacks, and the services of other companies we use.
Good faith
We will not take legal action against research that respects people’s data, stops at proof of the problem and gives us time to fix it before sharing it.

Ask your AI

“Who changed that?”

Activity answers it in the app, and your assistant can look it up for you too.

What your assistant can do
  1. You: Who changed Lukas Weber’s job this week?
  2. Assistant: Ana Ferreira, through Claude, 5 minutes ago: a job change from 1 November. It was previewed first. (platform_activity_list · done) Activity: Changed a person’s job. Through Claude, as Ana Ferreira.
Illustration

Keep exploring

Your people’s data, in good hands.

Free up to 9 people, then €1.50 per active person per month, excl. VAT · Every module included · Company data stored in the EU

New: time off, with public holidays per country, in every plan.