What happens to what you type
The short version: we keep your request and the files we write for it, we remove personal details before anything is published, and a build plan is plain text files that cannot reach your accounts.
What it receives and keeps
- It receives what you type into the form: your idea, the project type, language, experience and team size, plus your email address once you sign in.
- It never asks for passwords, API keys or access to your code, your repository or any account.
- We store your request and the files written for it, linked to your account, so you can open, download and refresh them from your lab.
- We keep them until you delete them with your account. Sign-in links expire after 15 minutes and work once.
What is published, and what is removed first
Free and Pro build plans go to the public archive so other people can learn from them. Builder and Studio can keep a run private, and a private run is never published.
Before a public copy is saved, two passes remove personal details:
- A fixed set of rules replaces email addresses, phone numbers, links to private sites, and anything that looks like an API key, token, password or private key with a placeholder.
- A second pass finds names of people and companies and replaces them too.
Only the cleaned copy is ever shown in the archive. Your email address is never published. Anyone can report an archive entry, and reported entries are reviewed by hand.
Who else handles your data
- Cloudflare
- Hosting, the database, file storage, bot protection (Turnstile) and cookie-free analytics.
- Stripe
- Payments, invoices and receipts. We never see or store card numbers.
- Anthropic
- The Claude API writes your build plan. Your generator input is sent to it for that run.
- GitHub
- Only when you open a pull request with your build plan, through our GitHub App on the repositories you pick.
- GoHighLevel
- Sends our emails (sign-in links, receipts, the weekly email) from the levelpartner.ai account.
What a build plan can and cannot do
A build plan is a folder of plain text files: CLAUDE.md, a spec, a phased plan with the prompts to paste, a review checklist, settings and skills. Nothing in it runs by itself, and nothing in it connects to your accounts.
- Claude Code reads the files when you start it in that folder. You see every step it proposes before it runs.
- The settings file in the plan says what Claude may do without asking, for example run the tests, and what it must always ask about first. You can read and change it before you start.
- The plan never contains your secrets. It uses placeholders such as YOUR_API_KEY, and you decide where the real values go.
How to delete it
Open your lab and delete your account. That removes your email address, your private runs, your health checks, your seats and the original files of your public runs. Cleaned public archive entries stay, no longer linked to you. With an active membership, cancel it first; the lab shows you how.
Want a copy of your data first, or something removed from the archive? Email us and we answer within two working days.
Questions or a security report
Email support@levelpartner.ai. Found a security problem? Tell us there first and give us a reasonable time to fix it before you share it. See also theprivacy policy.