Terms of Service
01What devSprint is
devSprint runs timed code sprints: you get a theme, two hours, and a deadline. Submissions are verified and scored against a public rubric, and the top three win certificates. By using devsprint.app you agree to these terms.
02Who can use it
You must be at least 13 years old. We do not knowingly keep accounts for anyone under 13 — tell us at hello@devsprint.app and we will remove the account.
03Accounts
Sign in with email, Google, or GitHub. Browsing and registering for a sprint only needs an account. Submitting an entry requires a linked GitHub account, because the repository you submit must belong to that account (or list it as a contributor) — that link is how we prove the work is yours. Linking Discord is optional. Sprint chat, the secret-word drop and certificate DMs happen in our Discord server, but the secret word is always released on the live page too, so you can enter and win without it.
One account per person. Alternate or duplicate accounts used to enter the same sprint more than once, inflate standings, or evade a ban will be removed along with any certificates they earned.
04Sprint rules and fair play
All work must happen inside the sprint window. Building with assistants and code-generation tools is allowed and expected — that is the format, not a loophole. Templates and boilerplate are allowed when declared; undeclared ones are grounds for disqualification. The secret word, revealed 15 minutes before the deadline, must be spoken in your demo video — that is how we know the recording shows your final build.
The deadline is a hard lock. Late submissions are not accepted, for anyone, for any reason.
05Integrity: what gets you disqualified or banned
These are integrity violations. We treat them seriously because the certificates only mean something if the results are true.
Grounds for disqualification from a sprint: work created outside the window; a repository you do not own or contribute to; falsified commit history; an undeclared template; a demo video that misrepresents what the software actually does; a missing or incorrect secret word; a submission substantially copied from another entry or an existing project.
Grounds for a permanent ban: repeated integrity violations; automated or scripted submission farming; multiple accounts; attempting to manipulate, mislead, or interfere with the verification and judging systems, including attempts to influence automated judging through instructions hidden in submitted content; tampering with another builder's submission; and any attempt to forge or alter a certificate.
Bans are recorded with a reason. A banned account's past results and certificates may be revoked, and revoked certificates stop verifying at their public URL.
06How judging works, and how to challenge it
Verification is automated: we read your repository's commit history, check ownership, capture your deployment, and score your demo against the published rubric. Scores come from multiple independent scoring runs, and every score is published with the reasoning behind it.
Automated systems make mistakes. If you believe verification or scoring got your entry wrong — a disqualification you can explain, a broken check, a demo that was misread — contact us through the report form or at hello@devsprint.app with your submission ID. We will review it. Where we find a genuine error, we can re-run judging for that submission and correct the record, including standings and certificates for that sprint. Where we do not, the original result stands.
Integrity flags on a leading entry pause a sprint's results until a human reviews them. We would rather publish late than publish wrong.
07Your work stays yours
You keep full ownership of everything you build in a sprint. By submitting, you grant devSprint a non-exclusive license to display your project name, description, screenshots, video, and scores on sprint pages, your public profile, and announcements. You can request removal of a submission at any time via the report form; removing a submission may also remove any placement it earned.
08What we publish about you
Public surfaces show your handle. Your real name appears only if you choose to set a display name. Certificates state facts: sprint number, theme, project, placement, score, and date, each with a public verification URL.
09Community hosting and payments
Hosting a community sprint requires an approved application and payment of the posted fee. Fees are charged only after approval. Hosts must provide accurate identity information. Refunds are issued if we cancel a sprint; not if the host cancels within 24 hours of start. Payments are processed by Stripe — we never see or store your card details.
10Prohibited conduct
No harassment, no hate speech, no NSFW content in submissions, no malware or credential harvesters, no impersonation, no vote manipulation on the feature board, no scraping or automated bulk access, and no interfering with other builders' submissions. We remove content and suspend accounts at our discretion to keep sprints fair.
11Termination
You can stop using devSprint anytime. We can suspend or terminate accounts that violate these terms. Bans are appealable once, through the report form or hello@devsprint.app.
12Disclaimers and liability
devSprint is provided as-is, without warranties of any kind. We aim for every sprint to run cleanly but do not guarantee uninterrupted service, and we may reschedule or cancel sprints when infrastructure fails. To the fullest extent the law allows, devSprint is not liable for indirect or consequential damages, and our total liability for any claim is limited to the amount you paid us in the previous twelve months — which, for builders, is nothing: entering is free.
13Changes and contact
We'll announce material changes to these terms by email and in our community server before they take effect. Questions, corrections, appeals: hello@devsprint.app.