Legal

Terms of service

Last updated October 10, 2026

1. The agreement

These terms are an agreement between you and [Legal entity name] ("QuackCode", "we", "us"). They cover the quackcode.dev website and waitlist, the QuackCode web app at app.quackcode.dev, and the emails we send (together, "QuackCode"). By using QuackCode you agree to these terms and to our privacy policy. If you don't agree, please don't use QuackCode.

2. Who can use QuackCode and your account

• You must be at least 13. If you're under 18 (or the age of majority where you live), you need a parent or guardian's permission, and they must agree to these terms for you. In the EU or UK, if you're under 16, you need a parent's consent where local law requires it.
• You can sign in with an email and password, an email sign-in link, GitHub or Google.
• An account is for one person. Keep your sign-in secure, and tell us at support@quackcode.dev if you think someone else is using it.
• Information you give us, such as your email and username, should be accurate. Usernames must not be offensive, impersonate anyone, or include contact details.

3. What QuackCode is, and isn't

• A practice and learning tool. QuackCode helps you practice real-world coding with AI: filling gaps in real-looking codebases, writing specs for the Duck, reviewing AI-written pull requests, daily drills and capstone projects. We don't promise or guarantee any job, interview, offer, grade or certification, and nothing in QuackCode should be read that way.
• Practice code, not production code. Project codebases are realistic practice material, not production software. Don't deploy starter code or anything the Duck writes to production without your own careful review and testing.
• Checks are automated. In the current beta, checks are automated checks on your code. They may not catch every bug, and results may not reflect how the code behaves when it runs. A passing check doesn't mean code is correct, secure or ready to ship.
• Always improving. Mistakes can happen in projects, tests and hints. If something looks wrong, tell us at support@quackcode.dev. Features, tracks, projects and launch dates may change.

4. Free trial and subscriptions

• Free trial. Every new account gets a 7-day free trial of QuackCode Pro, with no payment details needed. The trial is offered once per person. When it ends, you need a Pro subscription to keep working on projects. Your progress stays saved.
• QuackCode Pro. Pro is billed monthly or yearly. The price, billing period and what's included are shown before you buy.
• Billing. You subscribe on our website, and Stripe processes the payment. Your subscription renews automatically for the same period, at the then-current price, until you cancel.
• Cancelling. Cancel any time in Settings, Manage billing, which opens Stripe's customer portal. Cancelling takes effect at the end of the period you've paid for, and you keep Pro until then.
• Refunds. We don't give refunds for partial periods, except where the law requires it or where we say otherwise at checkout. Nothing here limits a right to cancel or a refund that the law gives you.
• Price changes. If the price of your subscription changes, we'll tell you before the new price applies. If you don't agree, you can cancel before it takes effect.
• Public beta. During the public beta, some or all paid features may be free, and the free trial may not apply. We'll give you notice before we start charging.
• Team, Campus and Hire plans. Plans for teams, schools, bootcamps and employers may come with a separate written agreement. Where that agreement and these terms differ, the agreement takes precedence.

5. Your code and content

You keep ownership of the original code, specs and text you write in QuackCode.

To run QuackCode, you give us a worldwide, royalty-free license to host, store, run, check, display back to you and to the people you choose to share it with, and otherwise process that content to provide the service, and to use de-identified samples of it to improve projects, hints and checks. We never use it to train third-party AI models.

Sharing replays. From a scorecard, you can create a replay of a project you finished, with your scores, a timeline of what you did and snapshots of your code. Replays are private unless you make them public. When you make one public, anyone with its link can view it, and it shows on your public profile if you have one turned on. You can make a replay private again or delete it at any time. Replays also go to the instructor of a class you join, for assigned projects, and to the employer whose assessment you take (see sections 10 and 11).

Feedback and suggestions you send us can be used freely, without any obligation to you. You're responsible for what you write and send, and we may remove anything that breaks these terms.

6. Our content

QuackCode's projects, starter code, tests, hints, drills, Duck prompts, design and software belong to QuackCode and are protected by law. We give you a personal, non-exclusive, non-transferable, revocable license to use them for your own learning, in line with these terms.

You may keep code you completed and reuse it in your own portfolio. You may not republish our projects, tests, reference solutions, answer keys or hints in bulk; scrape or download our content in bulk; use it to train or test AI models; or use it to build a competing product. You also may not copy, change, reverse engineer or get around any security of QuackCode, except where the law expressly allows it.

7. Acceptable use

• Don't run malicious code, malware or crypto mining, launch network attacks, or try to escape or overload the code sandboxes.
• Don't attack QuackCode's systems or other users, or try to reach data that isn't yours.
• Don't try to extract hidden tests, reference solutions or the Duck's instructions (for example through prompt injection) in order to publish them.
• Don't use bots or automation, share your account, or make repeated accounts to get more free trials.
• Don't post or share answer keys.
• Academic and hiring integrity. Don't use QuackCode to cheat on a school assignment, exam or employer assessment where outside help isn't allowed. In a sponsored or Hire assessment, do your own work.
• Follow the law.

Found a security issue? Please tell us at support@quackcode.dev rather than testing further or sharing it publicly, and give us a fair chance to fix it.

8. The Duck and AI features

The Duck is QuackCode's AI assistant. In Hint mode it gives hints, not answers. In Build mode it builds from your spec. Its replies are generated automatically and may be wrong, insecure or incomplete, so review and test anything it writes. You're responsible for the code you choose to use, in QuackCode or anywhere else.

Daily usage limits apply, and we may change or stop AI features. Don't put personal information, passwords, API keys or other secrets in your code or messages. See the privacy policy for how Duck requests are handled.

9. Community features

Some features show your progress to other learners. Your public name is your username if you set one, otherwise your first name. The privacy policy lists exactly what each feature shows and to whom.

• Weekly leagues. If you earn XP in a week, you're placed in a league group of up to 30 learners at your tier, from Bronze to Diamond. Others in your group see your public name, the Duck you chose and your XP that week. Each week, the top 5 move up a tier and the bottom 5 move down. Don't use bots, extra accounts or other tricks to earn XP; we may correct XP or league placements gained that way.
• Friends. Every account has a friend code. When you connect with someone using a code, each of you sees the other's public name, Duck, current streak, XP this week, total XP and whether they practiced today. Either of you can remove the other at any time, which stops this for both of you.
• Usernames and public profiles. Your public profile is off unless you turn it on in Settings, and it needs a username. When it's on, anyone with the link can see it. Usernames, and anything you make public, must not be offensive, impersonate anyone or include contact details. We may reset a username that breaks these rules, and remove anything else that breaks these terms.
• Be kind. Don't harass, bully, threaten or spam other learners, including through friend codes, usernames or replays.

10. Campus

Campus lets instructors run classes in QuackCode. Anyone can create a class and share its join code. Students who join with the code can see the class name, the instructor's public name and the assignments. The instructor can see each student's name, email address, streak, last active date and total XP, and for assigned projects, their best score and score breakdown, flags (for example accepting AI code without running checks), number of attempts and the replay of that submission.

• For students. By joining a class, you agree to share this information with its instructor. You can leave a class at any time.
• For instructors. Only invite students who may use QuackCode under section 2, including having a parent or guardian's permission where needed. Follow your school's or organization's rules, including any about student data and AI tools. Use student information only for teaching your class, and not for anything else. You can remove students from your class at any time.
• Scores are a starting point. Scores and flags are produced automatically and may be wrong, so review a student's work before relying on them.
• Pilot feature. Classes are a pilot feature and are free during the beta. What they include, how they work and whether they stay free may change.

11. Hire

Hire lets employers assess candidates with QuackCode projects. An employer creates an assessment based on a QuackCode project and invites candidates by email; we send the invite on the employer's behalf. A candidate opens the link, signs in and takes a timed round. The employer sees the candidate's name and email as the employer entered them, status, start and submit times, scores and the replay of the assessment. A candidate's assessment work is shared only with that employer.

• For candidates. Hire is only for people who are 18 or older, or of legal working age where they live. By taking an assessment, you agree to share your results and the replay of it with the employer who invited you. Do your own work (see section 7). If you later delete your account, the employer keeps the scores and status you already submitted, but the replay is deleted.
• For employers. You're responsible for your own hiring decisions and for complying with employment law and any other laws that apply to how you hire. Only invite people you're considering, using their correct email address.
• No discrimination. Don't use Hire to discriminate against anyone, including on the basis of a characteristic protected by law.
• Human review. QuackCode scores are one signal, not a hiring decision. Employers must not use QuackCode as the sole basis for any decision with legal or similarly significant effects on a candidate, such as rejecting them, without human review.
• No guarantee of scores. Scores are produced automatically, and in the beta, checks and flags are pattern-based, so they can miss problems or flag work that is fine. We don't guarantee that scores are fair, accurate or complete, or that they predict how anyone will perform in a job.

12. Ending your use

You can stop using QuackCode at any time and delete your account in Settings, Account (see Delete your account). We may suspend or end your access if you seriously or repeatedly break these terms, if the law requires it, or if we stop offering QuackCode; where reasonable, we'll tell you first. If we stop offering QuackCode while you have a paid subscription, we'll stop renewals and tell you how to request a pro rata refund for the unused part of your current paid period.

Sections 5, 6, 11, 13, 14 and 15 continue after your use ends.

13. Disclaimers and liability

To the extent the law allows, QuackCode is provided "as is" and "as available", without warranties of any kind, express or implied, including warranties of merchantability, fitness for a particular purpose, accuracy and non-infringement. We don't warrant that QuackCode, its checks or the Duck will be uninterrupted, error-free or correct, or that QuackCode will help you reach any particular result.

To the extent the law allows, QuackCode won't be liable for any indirect, incidental, special, consequential or punitive damages, or for lost profits, data, opportunities, jobs or grades, arising from your use of QuackCode or from code you choose to use or deploy. Our total liability for any claim relating to QuackCode is limited to the greater of the amount you paid us in the 12 months before the claim and US$50.

You agree to cover QuackCode's reasonable losses and costs from claims caused by your breach of these terms or your misuse of QuackCode.

Some places don't allow these exclusions or limits, so some may not apply to you. Nothing in these terms limits rights you have under consumer law that can't be limited by contract.

14. Disputes and governing law

If you have a problem with QuackCode, please email support@quackcode.dev first; most things can be fixed quickly. If we can't resolve it within 60 days, either of us may bring a claim. These terms are governed by the laws of the State of Georgia, United States, without regard to conflict of law rules, and claims will be brought in the state or federal courts located in Georgia, unless the consumer law where you live gives you the right to bring claims in your local courts.

15. Changes and general terms

We may update these terms as QuackCode grows. If a change is material, we'll tell you by email or in the app before it takes effect; continuing to use QuackCode after that means you accept the new terms. If you don't, you can stop using QuackCode and cancel your subscription.

These terms, the privacy policy and any separate written agreement for your plan are the whole agreement between you and QuackCode about QuackCode. If any part is found unenforceable, the rest stays in effect. If we don't enforce a term right away, we don't give up the right to later. You may not transfer these terms; we may transfer them as part of a merger or sale of QuackCode. We aren't responsible for delays caused by events outside our reasonable control.

Questions about these terms: hello@quackcode.dev. Help with the app or your subscription: support@quackcode.dev.