BranchWise HR Back to home
Security and privacy

Your people data belongs to your company.

BranchWise is being built to protect employee information, keep each customer environment separate, and never monetize the data entrusted to us.

We do not sell data

We will not sell, rent, or trade customer or employee data. We will not use it for advertising or share it with third parties except to deliver the service or when legally required.

Every company stays separate

Each company is a tenant. Its records will carry a company identifier and be stored in a dedicated collection or tenant-bound partition. Requests must always be scoped to the authenticated company.

Access is intentional

Users will only be able to access data permitted by their company membership and role. Administrative access will be limited, reviewed, and logged.

Launch security plan

Controls we will complete before handling production customer data.

This is our baseline plan. It is designed to keep tenant boundaries enforceable in the application, database, and operations that support it.

  1. 01

    Tenant-bound data model

    Use a company ID on every tenant-owned record, with collection or partition boundaries per company. Never query tenant data without that company scope.

  2. 02

    Authorization on every request

    Derive the tenant from the authenticated session, then enforce membership and role permissions server-side. Client-provided company IDs are never trusted for access decisions.

  3. 03

    Isolation tests in delivery

    Add automated tests that attempt cross-company reads and writes. A release does not pass when one tenant can retrieve, modify, or infer another tenant's records.

  4. 04

    Protect data and credentials

    Encrypt data in transit, protect production secrets in a managed secret store, use least-privilege service accounts, and keep access credentials out of source control.

  5. 05

    Operate with accountability

    Maintain audit logs for sensitive actions, monitor access failures, review dependencies and permissions regularly, and maintain an incident-response and customer-notification process.

A simple rule for every feature

Before a feature ships, we will ask: does it preserve each company's data boundary, and does it give only the right people access to the right information?

Back to BranchWise