Security, without the theatre.

BizPilot is a multi-tenant cloud platform. Every customer workspace is logically isolated by tenant, and all access is authenticated and permission-checked on the server for every request.

Customers own their Customer Content. We process it only to provide the Platform, and our handling is documented in our Privacy Policies and Data Processing Addendums.

All traffic between your browser, our APIs and our infrastructure is encrypted in transit using TLS (HTTPS).

Access requires authenticated sessions with securely hashed passwords, login rate-limiting and account lockout protections against brute force.

Role-based access control with granular per-user permissions and least privilege — staff only see what their role permits. Sensitive actions (refunds, payroll approvals, balance adjustments) require elevated permissions and a stated reason.

BizPilot runs on managed cloud infrastructure (Kubernetes) with isolated services and environment-based secrets. Payment card details are handled by Stripe and are not stored on BizPilot servers.

Platform data is stored in a managed database service with backup and recovery capabilities appropriate to the service.

Value movements and sensitive records are written to append-only audit ledgers — gift card balances, timesheet edits and manager approvals all carry who, when, amount and reason. Manual edits never silently overwrite history.

Changes are developed, reviewed and tested before release, with automated regression testing across critical flows.

We maintain procedures to identify, investigate, contain and respond to suspected security incidents, including notification where required by applicable law (e.g. the Australian Notifiable Data Breaches scheme).

Third-party providers are limited to those needed to run the Platform, are listed publicly in our Subprocessor List and are engaged under their own security and privacy commitments.

Our AU and UK Privacy Policies describe exactly what we collect and why. Marketing consent is never bundled into contractual acceptance, and gift card balances are always maintained server-side.

If you believe you've found a security vulnerability, please report it to complaints@bizpilot.com.au. We appreciate coordinated disclosure and will respond promptly.

Every BizPilot account supports authenticator-app 2FA with one-time recovery codes (Team & Access → Two-factor authentication). We strongly recommend it for owners, admins, payroll and accountant users.

Every team member should have their own account with the minimum permissions they need. Shared logins destroy your audit trail and make offboarding dangerous.

When someone leaves, archive their account immediately. Their access ends instantly across every device and their records are preserved.

Use a password manager and a unique password for BizPilot. We hash every password with bcrypt — we can never see it, and neither should anyone else.

Repeated failed sign-ins are rate-limited and locked automatically. If something looks wrong, change your password — this is logged in your audit trail.

BizPilot holds payroll and HR data. Use device passcodes, auto-lock, and never leave a signed-in till or office computer unattended.

Integration credentials (Stripe, accounting, SMS) belong on servers and in secret managers — never in frontend code, spreadsheets or chat messages.

Rotate integration credentials on a schedule and immediately when a team member with access leaves.

BizPilot verifies the authenticity of inbound payment and telephony webhooks. If you build against BizPilot data, verify signatures on anything you receive too.

If you suspect any credential is exposed: rotate it immediately, then contact complaints@bizpilot.com.au so we can review access logs with you.