Spaces:
Runtime error
Runtime error
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8" /> | |
| <meta name="viewport" content="width=device-width, initial-scale=1.0" /> | |
| <title>Terms and Conditions · AV Causal Scenario Retrieval Challenge</title> | |
| <link rel="stylesheet" href="/style.css" /> | |
| </head> | |
| <body> | |
| <nav class="top" aria-label="Primary navigation"> | |
| <div class="inner"> | |
| <a class="brand" href="/">AV Causal Scenario<span class="dot">.</span> Retrieval Challenge</a> | |
| <ul> | |
| <li><a href="/#overview">Overview</a></li> | |
| <li><a href="/#challenge">Challenge</a></li> | |
| <li><a class="nav-primary" href="/participate">Leaderboard & Submit</a></li> | |
| <li><a href="/#timeline">Timeline</a></li> | |
| <li><a href="/#communications">Communications</a></li> | |
| <li><a href="/#organizers">Organizers</a></li> | |
| <li><a href="/terms">Terms</a></li> | |
| </ul> | |
| </div> | |
| </nav> | |
| <main class="terms-main"> | |
| <article class="terms-document"> | |
| <header class="terms-header"> | |
| <div class="eyebrow">AV Causal Scenario Retrieval Challenge</div> | |
| <h1>Challenge Terms and Conditions</h1> | |
| <p class="terms-version">Version <code id="terms-document-version">2026-06-30-v4</code></p> | |
| <p class="terms-intro"> | |
| These terms explain the consent requested when you queue a challenge | |
| submission. They cover affiliation eligibility, scoped repository | |
| access, private administrative data, evaluation handling, and public | |
| leaderboard information. | |
| </p> | |
| </header> | |
| <section> | |
| <h2>1. Consent you provide</h2> | |
| <p>By accepting these terms, you agree to the following:</p> | |
| <ul class="terms-list"> | |
| <li> | |
| 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. | |
| </li> | |
| <li> | |
| The organizers may privately process your contact email and | |
| institution for challenge administration. | |
| </li> | |
| <li> | |
| You must provide your current university, company, research lab, | |
| nonprofit, government, or comparable formal affiliation. Independent | |
| or unaffiliated entries are not eligible. | |
| </li> | |
| <li> | |
| 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. | |
| </li> | |
| <li> | |
| If you select “Remember this email in this browser,” the email is | |
| stored only in that browser for form prefilling and remains editable. | |
| </li> | |
| <li>Your team name and scores may be published.</li> | |
| </ul> | |
| </section> | |
| <section> | |
| <h2>2. Repository authorization explained</h2> | |
| <p> | |
| 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. | |
| </p> | |
| <p> | |
| 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. | |
| </p> | |
| </section> | |
| <section> | |
| <h2>3. Private information used for administration</h2> | |
| <p> | |
| 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. | |
| </p> | |
| <p> | |
| 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. | |
| </p> | |
| <p> | |
| 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. | |
| </p> | |
| </section> | |
| <section> | |
| <h2>4. Evaluation and public results</h2> | |
| <p> | |
| 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. | |
| </p> | |
| <p> | |
| 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. | |
| </p> | |
| </section> | |
| <section> | |
| <h2>5. Acceptance and versioning</h2> | |
| <p> | |
| 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. | |
| </p> | |
| <p> | |
| If you do not agree to these terms, do not check the box or queue a | |
| submission. | |
| </p> | |
| </section> | |
| <div class="terms-actions"> | |
| <a class="button" href="/participate#submit">Return to the submission form</a> | |
| </div> | |
| </article> | |
| </main> | |
| <footer> | |
| © 2026 NVIDIA · Spatial Intelligence Lab | |
| </footer> | |
| </body> | |
| </html> | |