Privacy Policy
This policy explains what personal data conquer.so collects and why. The data controller is Poldertech B.V., De Entree 232, 1101 EE Amsterdam (KvK 96140372). Contact: legal@conquer.so.
1. Founders: people with a conquer.so account
- Account data: email, name, and the sign-in method you use (magic link or Google). Used to run your account. Legal basis: contract.
- Project data: your prompts, chat messages, uploaded media, and the generated code and versions. Used to build and host your sites. Legal basis: contract.
- Usage and billing: builds and edits, their cost, your plan, and your Stripe customer and subscription IDs. Card details are handled by Stripe and never reach conquer.so. Legal basis: contract and legal obligations (tax records).
- Connected Stripe account: only the account ID, so checkout on your site pays into your account.
- Trying a template without an account: if you start from a template without signing up, conquer.so creates a temporary anonymous session in your browser (a sign-in cookie), keeps the answers you gave and the site built from them, and uses a human check (Cloudflare Turnstile) and a daily counter tied to a hashed form of your IP address to prevent abuse; the address itself is not stored. If you do not save the site with an email address or Google within 7 days, it and the session are deleted. If you do, it becomes part of your account like any other project. Legal basis: contract (providing what you asked for) and legitimate interest (preventing abuse).
2. Visitors to sites built with conquer.so
For sites built with conquer.so, the founder who owns the site is the controller of their visitors' data, and conquer.so processes it on their behalf.
- Analytics without cookies: page views, referrer, country and city (the network provider’s coarse location for the connection; the IP address itself is not stored) and a visitor hash that changes every day, so a visitor can't be followed across days or sites. No cookies, nothing stored on the visitor's device.
- Signups and forms: whatever the visitor enters (for example an email address), stored for the site's owner.
- Payments: handled by Stripe on the owner's own Stripe account.
- Member accounts: on sites that let visitors sign in, their email address, sign-in records, a sign-in cookie (only for staying signed in, up to 30 days), what they add on the site and, for paid memberships, whether their membership is active. Sign-in codes are emailed through Resend. Each such site has its own privacy notice for members at
/_conquer/privacy. Members can delete their account on the site, or ask the site's owner.
If you are a visitor or member of a site built with conquer.so, contact that site's owner about your data; we'll help them answer.
3. Who processes data for us
- Supabase: database, sign-in and file storage (EU, Ireland).
- Vercel: hosting of the conquer.so app (functions in Frankfurt, EU).
- Cloudflare: hosting of generated sites; site files in EU-jurisdiction storage. Also runs the server functions of sites that have them; Workers run on Cloudflare's network worldwide rather than only in the EU.
- Anthropic: the AI models that write sites and answer the Idea chat. Prompts and project files are sent to generate output.
- Anthropic also handles the text that members send to AI actions in sites that have them, to produce the answer; conquer.so keeps the cost and size of each call, not the text.
- The services a founder connects: when a member connects their account at another service, or a founder's function calls one, data is sent to that service as part of what the site does. Those services are the founder's processors or independent controllers, not conquer.so's.
- E2B: isolated sandboxes that build your site's code.
- Stripe: subscriptions and payments, including paid memberships on founders' own Stripe accounts.
- Resend: sign-in emails for conquer.so and for members of founders' sites, and notification emails (EU, Ireland).
- Google: only if you choose Google sign-in.
- GitHub: only if you import a site from GitHub. conquer.so reads the repositories you give it access to and never writes to them.
- Your browser's speech service: only if you use the microphone button. Dictation runs on your browser's built-in speech recognition; Chrome and Edge send the audio to Google or Microsoft to turn it into text. conquer.so receives only the text.
Where data leaves the EU, we rely on the European Commission's Standard Contractual Clauses or the EU-US Data Privacy Framework. We don't sell personal data or use it for advertising.
4. How long we keep it
Account and project data are kept while your account exists and deleted when you delete it (backups roll off within 7 days). Billing records are kept as long as tax law requires (7 years in the Netherlands). A site made without an account and not saved is deleted after 7 days.
For sites with server functions: a record of each run (which function, when, whether it worked, how long and an error message, never what was sent to it) is kept for 14 days; finished timed jobs for 30 days; files members upload until the member or the founder deletes them or the project or account is deleted; secrets and connected accounts until the founder or the member removes them or the project, member or account is deleted.
5. Your rights
Under the GDPR you can access, correct, export or delete your data, object to or restrict processing, and complain to your data protection authority. Most of this you can do yourself in Account settings; for the rest, email legal@conquer.so. Visitors to a site built with conquer.so should contact that site's owner first.
6. Cookies on conquer.so
The conquer.so app (app.conquer.so) uses only cookies needed to keep you signed in. No tracking or advertising cookies.
On our marketing site (www.conquer.so) we count visits without cookies and without storing anything on your device. If you press Accept all in the cookie banner, we also load analytics and advertising tools: Google Analytics and Google Ads (Google), the Meta pixel, the LinkedIn Insight Tag, the TikTok pixel and the Reddit pixel. They set their own cookies and tell those companies about your visit, so we can measure which of our ads work and how people use the site. If you press Reject all, or ignore the banner, none of them is loaded. Your choice is kept in your browser (local storage, key cq-consent) and you can change it any time with “Cookie settings” in the footer; withdrawing removes the cookies we can reach and reloads the page. Legal basis: your consent (Art. 6(1)(a) GDPR).