How 24G handles the data a season requires.

What we collect

From a registering team we collect team name, captain email, school or independent status, country, age band, member names, month and year of birth, coordinator contacts for anyone under 18, optional portfolio URLs, fee-waiver notes, and payment references processed by our payment provider. During the season we collect submissions, credits lists, mentor-channel messages, and scores. At Finals we may collect travel details for invited teams and consent for team photographs used on the Finalists page.

From a verifier we collect the ID that was typed and basic server logs (time, coarse location of the request, browser). We do not ask a verifier for their name. From a general enquiry we collect whatever you put in the email or contact form.

Why we collect it

To run the competition: eligibility, banding, one-team-per-school, fee waivers, briefing, scoring, critique, Finals logistics, prize payment, and certificates. To keep a public verifier honest. To answer you. To keep a limited archive of the season so that a certificate issued in 2024 still resolves in 2026. We do not sell mailing lists. We do not use student submissions to train a public generative model.

Legal bases (UK / EU readers)

Contract and pre-contract steps for registered teams. Legitimate interests in running a fair worldwide student competition and in preventing certificate fraud. Consent for optional portfolio links, marketing emails you can refuse, and under-18 photography. Legal obligation where tax, accounting or safeguarding law requires a record. If you are in a jurisdiction with additional rules, write to us before registering.

Under 18

We do not knowingly complete a Band A registration without a coordinator adult and a guardian consent mark. We do not publish home addresses. We do not require medical disclosure in a mental-health brief; those briefs are service-design exercises. Safeguarding concerns are routed to the coordinator, not to a public page.

Who else sees it

Jurors see anonymised files at first pass, then names for Finals. Mentors see the teams they are assigned. Platform partners (Bluebeam, Figma for Education) see the accounts we provision, under their own terms. Payment providers see payment data. We do not pass your work to D&AD, ADC, Cannes Lions, The One Show, YCN or Adobe. A verified certificate record is public by design: holder, team, school, award, category, season, date.

How long

Registration and scoring records: for the season plus six years, so that a certificate can still be explained. Public verifier records for issued certificates: until revoked or until we shut the programme, because a certificate without a check is theatre. Server logs: a short rolling window unless needed for security. You may ask for a copy, a correction, or — where the law allows — erasure. Certificate IDs that have been issued cannot be silently deleted without breaking the public record; we may suppress a name in the public view if there is a serious welfare reason, and keep a sealed internal note.

Cookies and this static site

The marketing pages are static HTML. We do not drop an advertising pixel from this domain as part of the design system. The portal, if hosted later under the same domain, may use a session cookie strictly to keep you signed in. You can refuse non-essential cookies if a later banner appears; this page will be updated if that happens.

Security and international transfer

Files sit on systems we control or on named processors. Teams upload from many countries; that is the point of a worldwide season. We do not pretend a student in one jurisdiction can only be judged by servers in the same one. If that is unacceptable, do not enter.

Your requests

Write to hello@24g.org with “privacy” in the subject. Certificate questions go to verify@24g.org. You may also have the right to complain to a data protection authority in your country. This notice was last updated for the 2026 public season.