Trust

Security & Compliance

Last updated: 19 September 2026

Note: This page describes the security measures AspireOS is designed with. It is written to align with the Australian Privacy Principles; it does not by itself constitute a certification. For a formal posture (e.g. an independent security review or ISO 27001), we engage an accredited assessor.

Data residency

Your practice data is stored in a Postgres database hosted in Sydney, Australia, on infrastructure operated by Contabo Australia Pty Ltd. Patient data does not leave Australia in the course of running the service, which supports Australian data-residency expectations for health information.

Encryption

  • In transit — all traffic is served over HTTPS/TLS.
  • At rest — full-disk encryption on the database host is not enabled today. Data at rest is protected by operating-system and network access controls rather than by disk-level encryption. We would rather say so here than imply a control we have not turned on; it is on our roadmap and we will update this page when it changes.
  • Passwords are never stored in readable form (scrypt, salted), and API keys are stored only as hashes.
  • Card data is never stored or handled by AspireOS. Card payments run through your chosen provider — Tyro Health or Stripe — on their own hosted payment pages, under their PCI-DSS compliance.

Multi-tenant isolation

Every practice’s data is separated, and the separation is enforced in the application: each request is resolved to one practice and every read and write is scoped to it, and public capability links (payments, patient portal, booking, telehealth) are gated by unguessable per-practice tokens. We state the mechanism rather than promise an absolute, because that is the honest description of the control: it is application-enforced, not a database-level policy, and it is covered by our own automated tests and reviews.

Access control

  • Role-based access — owner, admin, senior and practitioner roles gate who can see and change what (for example, financials are restricted).
  • Least privilege — platform administration is limited to an explicit allowlist and is separate from practice accounts.
  • Passwords are hashed (scrypt, salted); sessions are HTTP-only cookies.

Audit logging

Sensitive actions — record changes, status changes, exports, administrative actions and impersonation — are written to an audit trail so there is a record of who did what and when.

Backups & availability

The database is backed up automatically on a scheduled basis, and backups are monitored so a run that fails is noticed rather than discovered later. Those are periodic snapshots — we do not currently offer point-in-time recovery to an arbitrary moment. We work to keep the service available and to recover quickly from incidents.

Breach response

We maintain an incident-response process and comply with the Notifiable Data Breaches (NDB) scheme. If an eligible breach likely to cause serious harm occurs, we notify the OAIC and affected individuals as required, and support your practice in meeting its obligations. See the Privacy Policy.

Sub-processors

We use a small set of vetted providers to run the service:

  • Contabo Australia Pty Ltd — application and database hosting, Sydney.
  • Anthropic — the AI model behind AspireAi, for the requests you send it.
  • Stripe and/or Tyro Health — card payment processing (optional, and only the one you connect).
  • Your chosen SMS, email, claiming (Tyro Health / HICAPS) and drive providers — only when you connect them.

Responsible disclosure

Found a security issue? Please report it privately to admin@aspireos.io so we can fix it before disclosure. We appreciate responsible reports.