Privacy & data handling
How Aurelian handles data during the pilot.
This page explains the current product approach in plain language. It is not a substitute for a formal data processing agreement or legal advice.
School and student trading history
Pilot schools may upload real student trading history that they are authorised to process. Aurelian uses the data to provide behavioural analysis, student views, school analytics and coaching workflows.
Student summaries and white-labeling
Student summaries are generated for the school and can use the school's name and logo. The product is designed so school-facing outputs can be presented as part of the school's coaching experience.
Product analytics
Aurelian's product-learning dataset is intended to use anonymised information rather than directly identifying student information. Do not upload data you are not authorised to process.
Access control
School data is separated using Supabase row-level security and school membership. Platform administration is restricted separately from school workspaces.
Pilot applications
Contact and paid-pilot applications include the information you submit, such as your name, school, email and details about your student population. These are stored so Aurelian can review and respond to the application.
Before onboarding
For a production relationship, the school and Aurelian should agree appropriate contractual terms for processing student information, retention, deletion and responsibilities. A formal DPA should be reviewed before processing sensitive customer datasets at scale.