The boring-but-critical basics
Privacy, payments, terms, and accessibility basics for solo builders, explained in plain English, so you can launch without nasty surprises.
Get started: Start: what you need before you launch
In plain English
Before real users arrive, a few boring things matter: how you handle personal data, how you take payments, the policies you show, and basic accessibility. This hub covers the essentials without pretending to be a law firm.
Educational, not legal advice — This hub is general education. Laws vary by place and change over time. Verify anything that matters for your situation with a qualified professional.
Who this is for
- Builders about to launch to real users
- People taking payments or collecting personal data
- Anyone who wants to avoid a preventable legal or trust problem
When to use this hub
- Before you launch publicly
- Before you collect emails, personal data, or payments
- When you are writing your privacy policy and terms
The boring-but-critical basics
Shipping responsibly is mostly about a handful of basics done honestly: collect only the data you need, use compliant providers for payments, show clear policies, and make your app usable for more people.
None of this is legal advice. Where the rules matter for your situation, verify with a qualified professional.
Guides in this hub
- Ship Responsibly: What You Need Before You Launch — the checklist
- Privacy and Consent Basics
- Terms and Policies: The Minimum
- Accessibility Basics for AI-Built Apps
- Payments Compliance in Plain English (PCI)
- Developer, Lawyer, or Neither? A Triage Guide
Where to go next
Secure what you shipped
Responsible shipping and security go hand in hand.
Own your stack
Owning your data is part of handling it responsibly.
Launch with fewer surprises
Work through the pre-launch basics, and verify anything legal with a professional.
Read the pre-launch guide · Read the reading map
Ship Responsibly FAQ
Do I legally need a privacy policy and terms?
Often yes, especially if you collect any personal data or take payments, but specifics vary by place and situation. Treat our guidance as educational and verify with a professional.
Is it safe to take payments as a solo builder?
Yes, if you use a compliant payment provider and do not store card data yourself. The PCI-basics guide explains the plain-English version.
What is the minimum for personal data?
Collect only what you need, tell users what you collect, secure it, and let them ask for deletion. "Privacy and Consent Basics" covers the essentials.
Do I really need accessibility?
It is the right thing to do, it widens your audience, and in some contexts it is required. A few basics, like good contrast and labels, go a long way.
Who do I call when I am unsure — a developer or a lawyer?
It depends on the question. The triage guide maps common worries to the right kind of help.
Kodbe is an independent publication about maintaining and owning software you built with AI or no-code tools. It is not affiliated with, endorsed by, or connected to Kodbe Inc (the Albany, GA educational nonprofit), Kodobe, Kodable, or Kodu.