Privacy policy
This policy covers Build to Launch's websites, apps, the Build to Launch MCP (the connector that lets your AI app use our library) and the emails we send. Our newsletter runs on Substack, and Substack's own privacy policy covers what Substack collects.
The short version
What we get: your email address, what you buy, what you type into our forms and the community, and how you use the member tools. With your OK, we also get analytics about which pages people read.
What we never get: your card number (Stripe handles payment), your conversations with your AI, and the files on your computer or phone.
We do not sell or share personal information. We use no ad pixels. You can ask for a copy of your data or ask us to delete it at [email protected].
Who we are
Build to Launch is run by Jenny Ouyang, doing business as Build to Launch, in California, United States. When this page says "we", it means Jenny Ouyang, who is responsible for your personal data.
Contact for privacy, deletion and refund requests: [email protected].
What we collect
| When you | We keep | Why |
|---|---|---|
| Sign in or create an account | Your email address and the display name you choose | To sign you in and show your name on your posts |
| Buy something | Your email, what you bought, the price and the payment reference. Stripe keeps your card details, and we never see them. | To give you access, send receipts and handle refunds |
| Get a free download | Your email, the download you asked for, the page you came from, your IP address and your browser details | To send the download and to stop abuse of the form |
| Fill in a form (session intake, sprint questions, an AMA question) | Your answers | To prepare your session or your sprint |
| Post in the community | Your posts, replies and introductions, with your display name | To show them to other members. Posts on the feedback board are public. |
| Use a course or the program | Which lessons you finished, and any notes you add when you finish one | To show your progress |
| Get our emails | Whether an email was delivered, opened or clicked, which link, and your browser details when you click a link | To know if email arrives and which emails help |
| Use the drafts editor in our tools | Your drafts, the images you upload and your email address. Uploaded images are at public links, and anyone with a draft's share link can read and change that draft. | To save and share your drafts |
| Say yes to analytics | Pages viewed, how you arrived (for example a link in an email or a social post), and a visit ID | To see which pages and articles work |
If you subscribe to the newsletter on Substack, we keep a copy of your email, name and plan. We use it so you do not get the same article twice, and to check paid membership.
The Build to Launch MCP and AI tools
We are not in your conversation. When you connect the Build to Launch MCP to Claude, ChatGPT or another AI app, we see only the requests your AI app sends to us, for example "find a guide about Substack growth". We do not see your chat, and we do not keep a log of your searches.
What we keep:
- A connection key, so your AI app stays connected. It ends after 90 days, or one year for a key you make in Settings.
- The personal skills you save, until you delete them.
- Feedback you send through the MCP. It goes on the public feedback board.
- Your lesson progress and the note you add when you finish a lesson.
- For the AI draft check and the AI answer tool: the date, the length of the text and how much was used. We do not store your draft. Your own question is stored only as a one-way code that cannot be turned back into the text.
- Pages you host for Canva. Each one is at a public link for one hour and is deleted after 24 hours.
To disconnect, remove the Build to Launch connector in your AI app. Then open Settings in the community and make a new key, which ends the old one. To have this data deleted, email [email protected].
Why we can use your data
If you are in the EU, the UK or the European Economic Area, the law (GDPR) asks us to name the reason for each use:
- Contract: your account, your purchases, delivery of what you bought, sign-in emails and receipts.
- Consent: analytics cookies, the newsletter and other marketing emails. You can take consent back at any time. That does not affect what we did before.
- Legitimate interests: keeping the service safe (limits on forms), knowing if our email arrives, and fixing errors. We weigh these against your rights, and you can object.
- Legal obligation: tax and payment records.
Who else gets your data
These companies process data for us, only to run Build to Launch:
| Service | What it gets | For |
|---|---|---|
| Supabase | The data in “What we collect” | Database and sign-in |
| Vercel | Page requests, IP address, server logs | Website hosting |
| Cloudflare | Requests to our sites, the MCP and our podcast files | Network and hosting |
| Stripe | Your email, what you buy, payment details | Payments |
| Resend | Your email address and the emails we send you, with delivery, open and click events | Sending email |
| Google Analytics | Pages viewed, IP address, device type. Only after you click Accept. | Analytics |
| TypeSafe | The draft you send to the AI draft check, and the question you send to the AI answer tool. Not your email. | AI draft checks and answers |
| Anthropic | The research question you type into our prompt tool | Writing the prompts |
| Oracle Cloud | A draft you export to PDF | Making the PDF |
| Gumroad | A Gumroad license key, if you use one to open our tools | Checking the license |
| Google Drive | Nothing about you. Our download files are stored there. | Storing download files |
| Canva | The page you host for Canva, from a link that works for one hour | Importing your page into Canva |
| Cal.com | What you type when you book a call | Booking |
| n8n | New Substack subscriber emails and membership status | Keeping our member list up to date |
| Substack | Your email, if you confirmed that you want the newsletter | The newsletter |
| Google Fonts | Your IP address, on the MCP connect pages | Fonts |
We do not sell or share personal information, and we do not use it for ads. In California law terms, we do not "sell" or "share" personal information. We give data to the authorities only if the law requires it.
International transfers
We are in the United States, and most of the services above store data in the United States. If you are in the EU, the UK or Switzerland, your data goes to the US. Where a service offers them, we rely on the EU-US Data Privacy Framework and its UK and Swiss extensions, or on the standard contractual clauses that the European Commission approved.
How long we keep it
| Data | How long |
|---|---|
| IP address and browser details from forms | 90 days |
| Email delivery, open and click events | 12 months, except bounce and complaint records, which we keep so we never email that address again |
| Your account and everything tied to it, after you close it | Deleted within 30 days |
| Purchase and payment records | As long as tax law requires |
| Download links | 1 year, then they stop working |
| “Stay signed in” sessions | 30 days from your last visit |
| Community posts, skills and progress | Until you delete them or close your account |
| Analytics (Google Analytics) | Up to 14 months |
Some emails are part of what you asked for: sign-in links, receipts, the download you requested and replies to your posts. Marketing emails (new articles, tips and series) have an unsubscribe link.
Your rights
You can ask us to:
- give you a copy of your data, in a format you can take elsewhere
- correct data that is wrong
- delete your data and close your account
- stop or limit a use of your data, or object to a use based on legitimate interests
- take back a consent you gave
Email [email protected] from the address on your account. We reply within 30 days. We may ask you to confirm the request from that address, so no one else can make it for you.
EU and UK: you can also complain to your data protection authority. California: you have the right to know, delete and correct your personal information, and to opt out of its sale or sharing (we do neither). We will not treat you differently for using any of these rights.
Security
Only Jenny and the services above can reach our data. Connections use HTTPS. No system is perfectly safe. If a breach puts your data at risk, we tell you and, where the law requires, the authorities.
Age
Build to Launch is for people 18 or older. We do not knowingly collect data from anyone younger. If you think a child gave us data, email [email protected] and we delete it.
Changes to this page
When this page changes, the date at the top changes and a line goes here. For a change that affects you, we also email you before it takes effect.
| Date | What changed |
|---|---|
| 2026-10-19 | First version of the privacy policy, the cookie notice and the terms, with the refund rules. |