Keep the right information with the right people.

Separate roles for administrators, students and parents

Ariona uses authenticated accounts and role-specific access. Students work with their own application information, parents access information for linked children, and administrators manage agency operations.

Access is enforced through application authorisation and database policies. The exact scope should be tested using representative accounts before onboarding a cohort.

Controlled access to documents

Student files are handled through storage permissions and signed links. Signed links expire, but anyone who receives a valid link may be able to use it until expiry; documents and links should still be shared carefully.

Public marketing pages do not include student records. Do not send passports, transcripts, passwords or other sensitive student information through the public contact form.

Agency data stays with its deployment

The current multi-agency setup uses separate Supabase projects for agency deployments. Shared software updates do not mean copying student records, enquiries or event data between agencies.

Hosting location, backup arrangements, retention, exports and deletion responsibilities should be confirmed for your implementation and included in the relevant agreement.

Questions to cover before onboarding

Ask for a review of the deployment and contractual arrangements against your agency’s requirements. This page describes product mechanisms; it is not a security certification or a blanket statement of regulatory compliance.

• Who is responsible for student data and access approvals?
• Where is the deployment hosted and how are backups handled?
• What are the agreed retention, export and deletion procedures?
• Which staff need administrator access?
• How will the team handle access changes and incidents?