#01Purpose and status
ACADEMYSHIP PTY LTD (ACN 698 283 448, ABN 89 698 283 448) publishes this page to explain the backup and recovery commitments in its Terms of Service and Data Processing Addendum (DPA), how continuity information fits with the service agreement, and what Institutions should plan for themselves.
This is an informational summary. It is not a service-level agreement, a confidential disaster-recovery runbook or a promise of uninterrupted availability. It does not add to or reduce an applicable Order Form, the Terms or the DPA.
#02What continuity and recovery cover
Continuity concerns maintaining or resuming important operations when something disrupts them. Recovery concerns restoring affected services and information. Disruption can involve an application fault, infrastructure failure, security incident, accidental deletion, a supplier outage or loss of access to an external service.
Academyship is responsible for its platform and managed infrastructure under the service agreement. Institutions are responsible for their own educational, payroll, payment, safeguarding and records-management operations, including alternative procedures where the platform or a third-party service is temporarily unavailable.
#03Published backup arrangements
Terms section 22 and DPA Annex II Part A specify daily platform backups in Sydney, Australia (ap-southeast-2), with 30 daily recovery points, 15 weekly recovery points and 7 monthly recovery points, together with recovery procedures and the defined backup-expiry lifecycle.
Recovery points are copies available under the backup lifecycle. They are not a guarantee that every change can be restored independently, that a customer-selected timestamp is available, or that restoration can be completed within a particular time. Backups support platform recovery and are not the Institution's permanent archive.
#04Recovery and verification
Where a platform incident causes loss or corruption of Customer Data, the Terms require Academyship to use its documented recovery procedures and provide reasonable information and assistance to affected Customers. Recovery may involve assessment, containment, selecting suitable recovery data, restoration, integrity checks and controlled return to use.
A backup schedule, a restore test and an independently audited recovery capability are different things. This page does not claim a completed restore exercise, successful independent assessment or tested recovery target unless such evidence is separately provided. Institutions may request relevant recovery information through team@academyship.com.au, subject to appropriate confidentiality and security restrictions.
#05Recovery objectives and service targets
A recovery time objective concerns how quickly a service is intended to resume. A recovery point objective concerns the intended limit on data loss measured in time. This page does not publish a fixed RTO or RPO and does not promise zero downtime or zero data loss.
An uptime commitment, service credit, response target or other service obligation applies only where expressly set out in the agreement applicable to the Institution. A daily backup schedule alone does not establish a guaranteed recovery point objective.
#06Deletion, legal holds and restored data
Deletion from active systems does not erase every backup copy immediately. A copy can remain in a recovery point until it expires under the backup lifecycle. The Data Retention page and DPA section 20 explain deletion, exceptions and legal holds.
If Academyship restores Customer Data from a backup, the DPA requires it to reapply relevant deletions made after that backup was taken so that restoration does not return deleted Customer Data to ordinary use. Where an Institution asks for recovery of records deleted by mistake, that is an authorised recovery request rather than a reason to disregard other deletion instructions or legal restrictions.
#07Supplier and external-service dependencies
Some workflows depend on systems outside Academyship's direct operation, including AWS, Stripe, banks, payment networks, PayTo, payroll reporting providers, the ATO, email and SMS networks and calendar services selected by Users. An outside outage can delay a workflow even where Academyship remains available.
Starting a payment does not prove settlement. Sending a refund request does not prove receipt of the refund. Submitting a payroll report does not prove acceptance. Institutions should check the final status and use their own contingency arrangements for statutory or operational deadlines, as explained in the relevant module documents and Support page.
#08Maintenance and communications
The Terms describe reasonable advance notice of scheduled maintenance expected to materially affect availability and the possibility of emergency maintenance where necessary to protect security, integrity or availability.
The Support page describes communication with affected Institutions through account contacts and, where appropriate, in-product. Keep administrator and operational contact details current. This page does not promise a separate status website, round-the-clock response or a fixed recovery deadline.
#09What Institutions should plan
Institutions should identify critical operations and alternative procedures; maintain current authorised contacts; keep copies of records they are legally required to retain using available exports and appropriate arrangements; know how to handle urgent payroll, payment and reporting deadlines; and confirm any particular availability or recovery requirements in writing before relying on them.
Use the supported export functions and check that the exported records and files you need are complete and readable. The DPA describes standard export coverage and reasonable assistance for otherwise unavailable Customer Data needed to meet a legal obligation. Do not assume a single standard export contains every record, attachment, relationship and historical event.
#10Reporting a disruption
For a service outage or recovery question, contact support@academyship.com.au with the Institution, affected function, approximate time and impact, and non-sensitive references. For suspected unauthorised access, a security incident or exposure of personal information, contact security@academyship.com.au promptly. Do not email passwords, full tax file numbers, full bank or card details or customer database exports.
#11Review and related documents
Academyship reviews this public summary when material changes to backup, recovery, supplier or service commitments require an update. Internal continuity planning and evidence are part of the security programme and are not published through this page.
| Version | Date | Summary of changes |
|---|---|---|
| 1.0 | 11 October 2026 | Initial publication explaining existing backup commitments, recovery limits, deletion safeguards, dependencies and Institution continuity responsibilities. |