Privacy Policy
Launchpad by BuilderCult · Last updated October 10, 2026
This policy explains what BuilderCult ("we") collects when you use Launchpad, why, who helps us process it, and the choices you have. Short version: we collect what we need to run the product, we don't sell your data, and we don't use it for ads.
1. What we collect
- Account: your name, email address, a hashed password or, if you sign in with an outside account, the name, email and profile picture it shares; your settings.
- What you make: ideas, briefs, prompts, uploads (footage, images, logos, voice recordings), generated apps and their code, scripts, videos, carousels, posts and schedules.
- Connected accounts: the access we need to the social, store, database and payments accounts you connect (handled as tokens; we don't see those accounts' passwords), and the analytics they return for your posts.
- Billing: your plan, credits, purchases and refunds. Card details go straight to the payment processor; we never see or store them.
- Usage and device: logs of what ran and what it cost, errors, IP address, browser and device type. We use these to run, secure and price the service.
- Support: what you send us when you write in.
We don't knowingly collect data from children under 16. Launchpad is for adults.
2. Why we use it (and the legal basis)
- To provide Launchpad: build your apps, render your videos, publish what you schedule, keep your credits right (performance of our contract with you).
- To keep it safe and working: preventing fraud and abuse, enforcing limits, fixing bugs (legitimate interests).
- To improve it, using aggregated usage data (legitimate interests). We don't train our own AI models on your private projects.
- To meet legal duties: tax, accounting, answering lawful requests (legal obligation).
- To email you about your account, and about product news only if you agree (consent, which you can withdraw).
3. No ad tracking
Launchpad has no advertising trackers, doesn't sell or rent personal data, and doesn't share it for cross-context behavioural advertising. Cookies are used only to keep you logged in and remember settings such as light or dark mode.
4. Who processes data for us
We use service providers (processors) in the categories below to run Launchpad. They may only use your data to provide their service to us, and each receives only what its part of the job needs. A current list of our sub-processors is available on request at adi@buildercult.com.
| Category | What they do and what they receive |
|---|---|
| Cloud hosting and storage | Run our servers and databases and store your account, projects, uploads and renders. |
| Content delivery | Deliver pages and media quickly and protect the service from attacks; they see network data such as IP addresses. |
| AI model providers | Text, image, voice and video generation. They receive the prompts, files and context needed for the task you started. |
| Payment processing | Checkout, subscriptions and refunds for Launchpad, and payments in the apps you build when you turn them on. Card details go to them, not to us. |
| Email delivery | Send account emails: verifying your email address, password reset and set-password links, and a welcome message. They receive your email address, your name and the message. |
| Error monitoring | Help us find and fix crashes and slow pages in our servers and in your browser. They receive technical details (error messages, code locations, the page or route, browser and device type, timings). Before anything is sent we remove cookies, sign-in headers, tokens, email addresses and the values in web addresses. |
| Social media posting and analytics partners | Publish the posts you schedule to the accounts you connect and return their analytics. |
| App build and store submission services | Build your iPhone and Android apps, stream phone previews, and submit apps to the stores with the store accounts you connect. |
| App and market data providers | Supply public data about apps and markets for idea research; they receive search terms, not your personal data. |
| Research and web data providers | Supply public posts, discussions, web results and media for research and content; they receive search terms, not your personal data. |
| Backend providers you choose | Host the database and sign-in of an app you build, in your own account with them, when you connect one. |
We use providers under terms that don't allow them to use your content to train their models, where those terms are available; where a provider's terms differ, we limit what we send.
We may also disclose data if the law requires it, to protect people's safety, or as part of a merger or sale of the business (we would tell you first). We are based in India, and some providers are in the United States or other countries; where data leaves the UK or EEA we rely on standard contractual clauses or an equivalent safeguard.
5. How long we keep it
- Account data and your projects: while your account is open.
- When you delete your account (Account → Delete account): we delete your profile, projects, uploads and renders within 30 days; copies in backups are overwritten within a further 30 days.
- Billing records: as long as tax and accounting law requires (usually up to 7 years).
- Logs: up to 90 days, unless needed longer to investigate abuse.
6. Your rights
Depending on where you live (for example under the GDPR, UK GDPR, India's Digital Personal Data Protection Act or California's CCPA/CPRA) you can ask to access, correct, delete or export your data, object to or restrict some uses, and withdraw consent. Californians can also ask what we collect and share and will not be treated differently for asking; we don't sell or share personal information as those laws define it. Much of this you can do yourself in Account. Otherwise write to adi@buildercult.com; we answer within 30 days and may need to check it's you. You can also complain to your data protection authority.
7. Security
We use encryption in transit, hashed passwords, scoped access tokens and per-user separation of projects. No system is perfect; if a breach affects you we will tell you as the law requires.
8. The apps you build
For the end users of an app you build, you are the controller of their data and we process it for you. You need your own privacy policy for your app (Launchpad can draft one), and you are responsible for the consents your app asks for.
9. Changes and contact
We will post changes here and tell you about material ones before they apply. Controller: BuilderCult, South Delhi, New Delhi, India. Privacy questions: adi@buildercult.com.