See RTOSure in action.
-
30 minutes. Tailored to your framework. No hard sell.
+
30-45 minutes. Tailored to your framework. No hard sell.
Book a Demo
diff --git a/security.html b/security.html
index b1431c1..4e1cee9 100644
--- a/security.html
+++ b/security.html
@@ -221,7 +221,7 @@
Where is our data stored?
RTOSure data is hosted on Australian servers. [Specific hosting provider and region to be confirmed — e.g. AWS Sydney, Azure Australia East.] We do not store or process your compliance data offshore.
How is data encrypted?
All data in transit is encrypted using TLS 1.2 or higher. Data at rest is encrypted using AES-256. This includes all compliance documents, student records, trainer credentials, and governance files stored in your evidence register.
Who can access our data?
Access is controlled at the college level. Your nominated administrator manages user roles and permissions. RTOSure staff do not access your data without your explicit permission, except for the purposes of support and system maintenance (logged).
-
What happens to our data if we cancel?
On cancellation, you can export all your evidence, registers, and compliance records in standard formats before your account closes. Data is retained for [30 days / 90 days — to be confirmed] after cancellation, then permanently deleted.
+
What happens to our data if we cancel?
On cancellation, you can export all your evidence, registers, and compliance records in standard formats before your account closes. Data is retained for 90 days after cancellation, then permanently deleted.
Is RTOSure compliant with the Australian Privacy Act?
RTOSure is designed to support your obligations under the Privacy Act 1988 and the Australian Privacy Principles. Our Privacy Policy details how we collect, store, and handle personal information. [Link to privacy policy once published.]
Security detail is v1 — to be reviewed by technical team and legal counsel before launch.