Trust & Security

How We Protect Your Data

Sentinel connects to your Xero, QuickBooks, or MYOB ledger to catch fraud and anomalies. Here's exactly how we protect that data, and where our compliance program honestly stands today.

Encryption

Data at rest is protected with AES-256-GCM envelope encryption, using a unique encryption key per tenant wrapped by a project-level key in Google Cloud KMS. Every connection uses TLS, with HTTP Strict Transport Security (HSTS) enforced on all API responses.

Hosting

Sentinel runs on Google Cloud, hosted in Australia (Sydney, australia-southeast1), using Google Kubernetes Engine Autopilot and Cloud SQL PostgreSQL with regional high availability.

Tenant Isolation

Every query is scoped to your organisation at the data-access layer — there is no cross-tenant data exposure. Machine-learning scoring runs within your tenant, so nothing crosses tenant boundaries even at the ML layer.

Read-Only Access

Sentinel connects to Xero, QuickBooks, and MYOB using read-only access. We read your transactions, invoices, bills, and payroll records to score them for risk — Sentinel never creates, edits, voids, or deletes anything in your ledger.

Additional Safeguards

  • PII protection — sensitive fields are never queried in the clear; lookups use HMAC-SHA256 tokens instead of raw values.
  • Secrets management — all credentials and signing keys are stored in Google Secret Manager, never in source code or config files.
  • SQL injection protection — parameterised queries throughout the data layer.
  • Security headers enforced on every response — X-Frame-Options: DENY, X-Content-Type-Options: nosniff, HSTS with includeSubDomains.
  • Webhook integrity — inbound Xero and QuickBooks webhooks are verified by signature; outbound webhooks support optional HMAC-SHA256 signing for your own verification.
  • Independent code and dependency scanning — SonarQube static analysis and Snyk vulnerability scanning run on every build, before it ships.
  • Automated testing — over 1,400 automated tests across the stack, including integration tests against real databases, run before every deploy.
  • Raw payload archiving — source-system payloads are archived for audit trail and compliance retention.

Incident Response

If we become aware of a data breach affecting your information, we will notify affected customers as soon as reasonably practicable, consistent with our obligations under the Notifiable Data Breaches (NDB) scheme in the Privacy Act 1988 (Cth). We will investigate promptly, take steps to contain and remediate the issue, and where required, notify the Office of the Australian Information Commissioner (OAIC).

Compliance Roadmap

We are working toward SOC 2 Type II certification. That process is in progress, targeting completion in Q3 2027 — we won't claim the certification before we've earned it. In the meantime, the safeguards on this page — encryption, tenant isolation, secrets management, and independent code and dependency scanning — are already in place today, not promises for later.

Questions

If you have questions about our security practices, or need documentation for your own vendor review, contact us at support@synexium.ai.