Challenge Terms and Conditions

1. Consent you provide

By accepting these terms, you agree to the following:

• You authorize the challenge's scoped Hugging Face OAuth application to create and access one private artifact repository and to transfer submitted artifacts into isolated evaluation quarantine.
• The organizers may privately process your contact email and institution for challenge administration.
• You must provide your current university, company, research lab, nonprofit, government, or comparable formal affiliation. Independent or unaffiliated entries are not eligible.
• If no participant profile is on record, this submission fixes your team name and institution to your Hugging Face account. Later submissions from that account must use the same values.
• If you select “Remember this email in this browser,” the email is stored only in that browser for form prefilling and remains editable.
• Your team name and scores may be published.

2. Repository authorization explained

The scoped OAuth application creates and accesses one reusable private model repository in your personal namespace. You publish your devkit-built artifact to that repository before submitting it for evaluation.

You also authorize the challenge to transfer the submitted artifact into isolated evaluation quarantine. The OAuth permission is limited to repositories created by this application. Your OAuth access token is used transiently for the transfer and is not returned by challenge APIs or stored in challenge intake, results, or leaderboard data.

3. Private information used for administration

The organizers may privately process the contact email and institution entered in the submission form for challenge administration. The authenticated Hugging Face account is used privately to associate your repository, submissions, limits, and personal status history with you.

Contact email, institution, private repository details, and the private account identifier are not published on the leaderboard. The challenge records the accepted terms version and acceptance time as private consent evidence.

A remembered email is a browser convenience rather than a server-side profile lock. You can edit it for every submission or turn off the remember option. Team name and institution remain locked independently of future terms-version updates.

4. Evaluation and public results

Queuing a submission asks the private challenge controller to validate, execute, and score the submitted artifact in the isolated evaluation system. Detailed submission status is not published on the leaderboard; the frontend returns it only to the authenticated participant account.

You agree that the team display name entered in the form and the scores produced for a selected result may be published on the public leaderboard. Your Hugging Face username, contact email, and institution are not used as the public team identity.

5. Acceptance and versioning

Checking the acceptance box and queuing a submission records your acceptance of this version. If these terms change, the version will change and the submission service will require you to review and accept the updated terms before submitting again.

If you do not agree to these terms, do not check the box or queue a submission.