Skip to content

Data Retention & Disposal Policy

This policy defines the requirements for retaining, archiving, and securely disposing of data held by XBert Pty Ltd. It ensures compliance with Australian privacy legislation and contractual obligations to customers while minimising risk from holding data longer than necessary.

This policy applies to all data processed, stored, or transmitted by XBert systems, including:

  • Customer accounting data (synced from Xero, QuickBooks, MYOB, FreeAgent, XPM)
  • Employee and payroll data (synced from Xero Payroll, Employment Hero)
  • User account and identity data (managed via Auth0)
  • Application logs and telemetry
  • Internal business records and communications
  • Backup and disaster recovery copies
  • AI processing data (ephemeral data sent to AI providers)
TermData ClassificationDefinition
Customer DataConfidentialAccounting and financial data belonging to customer organisations, synced via OAuth 2.0 integrations
User DataInternalPersonal information associated with individual user accounts (name, email, role)
Operational DataInternalLogs, metrics, telemetry, and audit trails generated by XBert systems
Ephemeral DataConfidential (in transit)Data transmitted to third-party AI services for processing that is not persisted by the provider

Data classifications align with the three-tier scheme defined in the Architecture & Design document (Confidential, Internal, Public).

Data CategoryRetention PeriodStorage LocationNotes
Active customer dataDuration of subscriptionAzure SQL (Australia Southeast)Synced from accounting platform
Disconnected client data90 days post-disconnectionAzure SQL (Australia Southeast)Grace period for reconnection
Deleted account dataPurged within 30 days of account deletionAll data storesIncludes all backups within retention window
Data CategoryRetention PeriodStorage LocationNotes
Active user profilesDuration of accountAuth0 + Azure SQLManaged via Auth0 identity provider
Deactivated user profiles90 days post-deactivationAuth0 + Azure SQLThen permanently deleted
Authentication logs90 daysAuth0Per Auth0 retention policy
Data CategoryRetention PeriodStorage LocationNotes
Application logs90 days (hot) + 12 months (cold)Azure Log Analytics + Blob StorageRolling retention
Audit trails12 months (hot) + 7 years (cold)Azure Log Analytics + Blob StorageRegulatory compliance
Security event logs12 months (hot) + 7 years (cold)Microsoft Defender for CloudIncident investigation
Performance telemetry90 daysApplication InsightsAggregated metrics retained longer
Data CategoryRetention PeriodStorage LocationNotes
Database backups (PITR)28 daysAzure SQL (geo-replicated within Australia)Point-in-time recovery
Long-term backups12 monthsAzure Blob Storage (Australia)Monthly snapshots
Azure DevOps artifacts28 days (PITR)Azure DevOpsPipeline metadata and release artifacts
Data CategoryRetention PeriodStorage LocationNotes
AI request/response dataEphemeral (not persisted by provider)OpenAI API, Anthropic Claude APIPer DPA - not stored by AI providers
AI memory (Mem0)Duration of subscriptionAzure Container Apps (Australia)Deleted with account
AI audit logs90 daysAzure Log AnalyticsFor quality and compliance review

When data reaches the end of its retention period, the following procedures apply:

  1. Database records: Soft-deleted immediately, hard-deleted via scheduled purge job within 30 days
  2. Blob storage: Objects deleted and storage reclaimed; Azure handles secure erasure of underlying media
  3. Log data: Automatically expired by Azure Log Analytics retention policies
  4. Backups: Automatically expired per Azure backup retention configuration

When a customer deletes their account or disconnects a client:

  1. Customer initiates deletion via XBert product interface (self-service)
  2. All associated data is marked for deletion
  3. Active database records are purged within 30 days
  4. Backup copies are purged as backup retention windows expire (maximum 28 days for PITR, 12 months for long-term)
  5. Confirmation of deletion is logged in the audit trail
Media TypeDisposal Method
Azure SQL DatabaseLogical deletion with Azure-managed secure erasure of underlying storage
Azure Blob StorageObject deletion with Azure-managed secure erasure
Auth0 user recordsAPI-driven deletion per Auth0 data deletion procedures
Local development dataSecure wipe using platform-appropriate tools
Physical media (if any)Not applicable - XBert operates entirely in cloud

For data held by third-party service providers:

ProviderData HeldDisposal Mechanism
Auth0User identity and authentication dataAuth0 Management API deletion + Auth0 retention policies
ChargebeeSubscription and billing dataChargebee API deletion; PCI-DSS compliant disposal
StripePayment processing dataStripe data deletion API; PCI-DSS Level 1 compliant
OpenAIEphemeral processing dataNot persisted per DPA; zero-retention API usage
AnthropicEphemeral processing dataNot persisted per DPA; zero-retention API usage

Any deviation from the retention schedule requires:

  1. Written approval from the CTO
  2. Documented business or legal justification
  3. A defined expiry date for the exception
  4. Entry in the exceptions register

Legal holds or regulatory investigations may require data to be retained beyond the standard retention period. The CTO will coordinate with legal counsel as required.

RoleResponsibility
CTOPolicy owner; approves exceptions; ensures compliance
Development ManagerImplements and maintains automated retention/disposal mechanisms
Database AdministratorsExecute and verify data purge operations
All StaffComply with policy; report data handling concerns

This policy supports compliance with:

  • Privacy Act 1988 (Cth) - Australian Privacy Principles (APPs)
  • APP 11 - Security of personal information (including disposal)
  • GDPR (where applicable to EU/UK customers)
  • Contractual obligations to customers regarding data ownership and deletion
  • Automated alerts for any data retained beyond its scheduled retention period
  • Quarterly review of disposal job execution logs
  • Annual policy review aligned with security assessment cycle
  • Review triggered by significant changes to infrastructure, legislation, or customer contracts
VersionDateChanges
1.0April 2026Initial creation