Terms of Service

Your account

You sign in through Google or GitHub. One account per person. You're responsible for keeping your account secure—though since we use OAuth, there's no password on our end to worry about. If you notice anything strange on your account, let me know immediately.

You must be at least 13 years old to use projectlighthouse. If you're under 18, you should have a parent or guardian who's aware you're using the platform.

What you get

projectlighthouse offers interactive books, hands-on labs, and coding projects. Some content is free. Some requires a paid subscription. What's included in each tier is shown on the subscriptions page.

I'm always adding and updating content. That means things might change—chapters get rewritten, labs get improved, new books get added. The platform is a living thing, not a static product. Your subscription gives you access to whatever is available during your subscription period.

Payments and subscriptions

Paid subscriptions are billed through Stripe. When you subscribe, you're authorizing a recurring charge at the interval you chose—monthly or yearly. Prices are displayed before you confirm.

You can cancel anytime from your account settings. When you cancel, your access continues until the end of your current billing period. No partial refunds for unused time, but no surprise charges either. Clean and simple.

If I ever need to change pricing, existing subscribers will be notified in advance. I won't silently bump your bill.

Content and intellectual property

All the books, lessons, lab instructions, and other educational content on projectlighthouse are my work (or credited where contributed by others). You're welcome to learn from it, take notes, and apply what you've learned to your own projects—that's the whole point.

What you shouldn't do is copy, redistribute, or resell the content. Don't scrape the site to republish lessons elsewhere. Don't share your paid account credentials so others can access subscriber content for free. If you want to reference something you learned here in a blog post or talk, go for it—just don't reproduce the material wholesale.

The code you write in labs and projects is yours. I'm not claiming any ownership over your work. Build something great with it.

Labs and infrastructure

Some labs provision real virtual machines for you to work in. These are sandboxed environments meant for learning. A few ground rules:

• Use lab environments only for the exercises they're designed for. Don't use them for cryptocurrency mining, hosting services, or anything unrelated to learning.
• Don't attempt to break out of the sandbox or access other users' environments.
• Lab sessions have time limits and resource caps. This keeps costs manageable so I can keep offering them.

If you find a security vulnerability in the lab infrastructure, I'd genuinely appreciate you telling me about it rather than exploiting it. That's the kind of engineering ethic this platform is trying to foster.

Acceptable use

This should go without saying, but for the record: don't use projectlighthouse for anything illegal, harmful, or disruptive. Don't harass other users. Don't attempt to compromise the platform's security. Don't automate access in ways that degrade the service for others.

If someone is clearly acting in bad faith, I reserve the right to suspend or terminate their account. I don't want to do that, and in practice I almost never have to. But the option exists.

Availability

I do my best to keep the platform running and available. But I'm building this with a small team, and things break sometimes. Servers go down. Deploys have bugs. If you've built any system of your own, you know how this goes.

I can't guarantee 100% uptime, and I'm not liable for any losses caused by the platform being temporarily unavailable. What I can promise is that I care about reliability and I'll fix things as quickly as I can.

Disclaimer

The educational content on projectlighthouse is provided "as is." I work hard to make it accurate and useful, but I can't guarantee every code example will work perfectly in your specific environment, or that following a tutorial will produce a particular outcome. Programming is like that—context matters.

projectlighthouse is not a substitute for professional advice in areas like security, compliance, or production system design. The content teaches concepts and skills. How you apply them is your responsibility.

Limitation of liability

To the maximum extent permitted by law, projectlighthouse and its creator are not liable for any indirect, incidental, or consequential damages arising from your use of the platform. Our total liability for any claim is limited to the amount you've paid us in the 12 months preceding the claim.

I know that paragraph sounds more like a lawyer wrote it. It kind of has to. But the spirit is simple: this is an educational platform, not critical infrastructure. Use what you learn wisely.

Changes to these terms

I may update these terms as the platform evolves. If something material changes, I'll give you notice—either through email or a visible notice on the site. Continuing to use the platform after changes means you accept the updated terms.

Governing law

These terms are governed by the laws of England and Wales. Any disputes will be resolved under the jurisdiction of the courts of England and Wales. Hopefully it never comes to that—I'd rather just talk things through.