Know where uploaded work goes

Current data flow

• Supabase provides account authentication and stores profile or application records.
• Original uploaded files are stored in browser IndexedDB on that device for local job recovery.
• Prepared script pages are sent over HTTPS to the Maiths marking service.
• The marking service sends the required page and marking context to Hugging Face's inference routing service, which may route the request to a downstream inference provider.
• Job status, warnings and completed marking results are stored in the Maiths Supabase project.
• Vercel hosts the web application and receives ordinary request and operational data.

Deletion and retention

Deleting a local marking job removes its browser-stored upload files from that browser. That action does not by itself prove deletion of server-side job status, results, provider logs or backups.

A precise production retention schedule and an end-to-end account deletion workflow have not yet been published. Contact Maiths to request access or deletion while those controls are being completed.

Training use

Maiths does not present uploaded student work as public content and does not claim ownership of it. The repository does not implement a Maiths model-training pipeline using uploaded scripts. Processing by Hugging Face and any routed inference provider remains subject to the applicable provider configuration and terms; organisations should verify those terms before sending personal or sensitive work.

Practical safeguards

• Avoid names and unnecessary personal information on uploaded pages.
• Use only work you are authorised to process.
• Do not include medical, safeguarding or other special-category information.
• Use a supported browser and device access controls.
• Report a suspected security issue through the contact form without attaching student work.