Terms of Service

Short version: ReviewLabs is free, built by one person, and provided as-is. The long version is below.

Last updated: July 16, 2026

Using ReviewLabs

By using ReviewLabs you agree to these terms. If you don’t agree, the only ask is that you don’t use the site — there’s no account or payment required to walk away.

It's free, and stays free

There is no paid tier, subscription, or paywall on ReviewLabs, and there never will be. Any future rewards program (see the Rewards page) is a separate, optional program with its own eligibility rules — it doesn’t change the core practice loop being free.

Signing in with GitHub

Sign-in is optional and handled entirely by GitHub — we never see or store your GitHub password. You’re responsible for keeping your own GitHub account secure. If GitHub is down or your OAuth session is revoked, ReviewLabs isn’t responsible for the resulting loss of access.

Fair use

Don’t attempt to scrape, disrupt, rate-limit-bypass, or attack the service, and don’t use scripts or multiple accounts to game challenge attempts or any future leaderboard standings. Accounts found doing this may be suspended.

Challenge content

Challenges, explanations, and heuristics on ReviewLabs are written and reviewed by hand to be accurate, but they’re educational material, not professional security or legal advice. Always verify anything security-sensitive against your own project’s requirements before shipping it.

No warranty

ReviewLabs is provided “as is,” with no uptime guarantee — it’s a student-run, single-maintainer project, not a hosted SaaS product with an SLA. To the extent allowed by law, we aren’t liable for damages arising from using or being unable to use the site.

Changes

Features here are still evolving — expect things to be added, changed, or occasionally removed as the project grows. Material changes to these terms will update the date above.

Governing law

These terms are governed by the laws of India, where ReviewLabs is built and maintained.

Questions

Reach out via the Contact page.