Setting up the environment, hold tight.
Last updated 28 September 2026.
Carnival Control is built for schools, and a lot of what it stores is information about students - including children. This page explains what's collected, why, and where it's kept.
A school using Carnival Control is the one collecting and entering its students' details - we process that data on the school's behalf so the software can run the carnival. If you're a parent or student with a question about data held about you, the quickest path is usually your school directly; we're also happy to help at carnivalcontrolgo@gmail.com.
We don't collect health, medical or any other sensitive information, and we don't use this data for advertising or sell it to anyone.
We use one cookie to keep you signed in - it's necessary for the site to work and carries no advertising or tracking of any kind. There is no analytics or ad-tracking cookie on this site.
The database lives with Supabase, hosted in Sydney, Australia. The application itself currently runs on Render; we choose infrastructure with data location in mind and this may change as the product grows - this page will be kept up to date if it does.
Nobody, beyond what's needed to run the service: our hosting and database providers (who store it, but don't use it for anything of their own), and - once connected - a payment processor for billing, which never sees student data, only the account holder's billing details.
For as long as the school's account is active, so past carnivals, records and results stay available. If a school closes its account, contact us and we'll delete its data rather than leave it sitting unused.
A school can ask us for a copy of its data, or to have it deleted, at any time - email carnivalcontrolgo@gmail.com. We're a small team, so this is currently handled by us directly rather than a self-service button; we aim to respond within a few business days.
Questions about this policy, or about data we hold: carnivalcontrolgo@gmail.com.