Privacy Notice.

01 / SCOPE

What this notice covers

This notice covers information provided directly to the FinReason Cup organizer team through organizer-operated participant services. It also describes the public result fields the organizers may publish. External services, including CyberChair, Hugging Face, GitHub, and the conference website, may apply their own privacy notices and terms.

02 / INFORMATION

Information processed

• Development submission records, including Team Name, submitted prediction archive, validation record, aggregate scores, receipt information, and event times. Team Name is the only participant-provided identity or contact field for development.
• Test submission records, including Team Name, Contact Email, submitted prediction archive, validation and receipt records, and event times. Contact Email is collected only for submission identification, submission-related support, matching final results to the related challenge paper, and selecting the latest accepted test submission and handling repeat uploads through a non-public pseudonymous identifier.
• Support messages and the information needed to investigate a correction, appeal, integrity issue, or service incident.
• Legacy interest-form and access-registration records collected or created before 3 September 2026, if any. These records are no longer used to control Task 1 submission access.

Please do not provide sensitive personal information that is not required for challenge participation.

03 / PURPOSE

Why information is used

The organizer team uses submission records for validation, development scoring, development quota enforcement and repeat-upload handling, leaderboard and result administration, integrity review, and aggregate participation reporting. Contact Email is used only for submission identification, submission-related support, matching final results to the related challenge paper, and selecting the latest accepted test submission and handling repeat uploads through a non-public pseudonymous identifier.

Legacy interest-form and access-registration records are used only for transition support, record consistency, and handling related participant requests. They are not used to require approval or a code for Task 1 participation.

The organizers do not sell participant information or use it for targeted advertising.

04 / PUBLIC SITE

GitHub Pages boundary

The public GitHub Pages website does not collect or store Contact Email, submission files, gold answers, or private evaluation data. Team Name and competition files are entered only in the separate verified participant services linked from the Task 1 hub. Contact Email is entered only on the verified test submission page.

The public site may receive ordinary technical requests handled by GitHub Pages. Refer to GitHub's own privacy documentation for its platform processing.

05 / VISIBILITY

What may be public

The public development leaderboard may display Team Name, rank, aggregate final-answer and reasoning-step scores, and acceptance time. Raw submissions, Contact Email, private identifiers, hidden evaluation data, and receipts are never published through that leaderboard. Test submissions do not produce an online score, rank, diagnostic, score-derived signal, or leaderboard entry.

Final team names, rankings, award results, papers, citations, and aggregate competition statistics may remain public as part of the challenge record. Contact Email is never published or included in a public result or challenge record.

06 / SECURITY

Submission handling

Task 1 participant services are designed to separate public resources from organizer-private submissions and evaluation data. Accepted submission archives are encrypted before storage in the organizer-private submission boundary. Access is limited to the organizer functions needed to operate, evaluate, support, and audit the challenge.

No online service can guarantee absolute security. Participants should not include credentials, personal data, or unrelated files in a competition submission.

07 / RETENTION

How long records are kept

Readable Contact Email is kept only while needed for submission identification, support, result matching, and test-submission administration, then deleted or minimized when those purposes end. A non-public pseudonymous identifier derived from the email may be retained separately for submission-version selection and repeat-upload handling.

Encrypted submission archives and non-public operational event records may remain in restricted organizer-private repository history for challenge administration, integrity review, audit, dispute resolution, security, and applicable institutional or legal requirements. They are not published, and retained fields and access are minimized when the records are no longer operationally needed. Because repository history may preserve prior encrypted records, the organizers do not promise deletion of every historical copy within a fixed period.

Legacy interest-form and access-registration records are kept only while needed to operate the current competition and handle related follow-up, then deleted or minimized, subject to the integrity, dispute-resolution, security, institutional, and legal purposes stated above.

08 / EXTERNAL SERVICES

Where information may be processed

The challenge uses external services for specific functions, including CyberChair for challenge papers, GitHub Pages for the public website, and Hugging Face for verified participant services. Information submitted to an external service may also be processed under that service's terms, privacy notice, account settings, and infrastructure practices.

Before 3 September 2026, the organizers also used a Google Forms interest form. That form is no longer a participation or submission route, but Google may continue to process prior responses under its own privacy notice and account settings.