Last updated 2026-10-18. Plain English version of what we do with your data.
When you create a Buildliy account we collect your email, display name, and OAuth provider ID. When you build a project we store your prompts, generated code, the resulting project files, and any files you upload in chat. We log basic usage metrics (build counts, response times, error rates) to keep the service running and to detect abuse, and we use IP addresses for rate limits and abuse checks. Payments are handled by Stripe, so we never receive your full card number. If you take affiliate payouts in cash we store your PayPal email. Keys you add for your apps are stored encrypted. The data your app's own users enter is stored in your app's database on your behalf.
Your data is used to operate the product, bill you accurately, and improve Buildliy — for example, by looking into a build that went wrong — never to train AI models (see below). Prompts and generated code are processed by the AI provider we use to run builds (currently Anthropic) and by the other service providers listed below, such as image generation, web search, and monitoring, under their respective data-processing terms — we do not sell your data to anyone for any reason.
Buildliy never uses your prompts, uploaded files, generated code or your app's data to train AI models. The AI that builds your app (Anthropic's Claude) receives your prompts, files and code, and under Anthropic's business terms it doesn't train on them. The AI inside apps you build runs only on providers that don't keep or train on what your app's visitors send it. A few services get only short text the AI writes for them, never your prompt or code: Tavily, which runs web searches, receives the search words, and its privacy policy says it may use search words to improve its search, including training its own models; fal.ai and the companies whose models it runs (such as OpenAI, Google and ByteDance) receive the descriptions used to make images, videos and music, plus any photo you ask the AI to edit, and handle them under their own terms.
These companies process data for us to run Buildliy. Each one gets only what it needs for the job listed.
Your projects are visible only to you, any teammates you invite to your team, and Buildliy admins when needed for support, billing or safety. The live preview of your app, and any app you publish, can be opened by anyone who has its link. You can delete any project at any time from your dashboard; deletion is permanent: within 24 hours it removes the project and its chat history from our primary store, deletes its app database, and takes its published app offline. Files uploaded to it or generated for it (such as images and screenshots) stay in our file storage until you ask us to delete them.
We use first-party cookies to keep you signed in, to secure sign-in and account-connection steps, and — if you arrive through an affiliate link — to remember who referred you for 60 days. UI preferences are saved in your browser's local storage. If you pick a language or a currency on buildliy.com, a first-party cookie remembers it for a year. To show prices in your own currency as an estimate, we look up your approximate country from your IP address when a page loads; it isn't stored. We run our own product analytics, stored in our own database: page views with the page address, referring page, browser type, country and, if you're signed in, your account, to understand which features get used and where people get stuck. We also advertise Buildliy with Google Ads. To learn which of our ads lead to sign-ups, buildliy.com loads Google's ad measurement tag (the Google Ads conversion tag). For visitors outside the EEA, the UK and Switzerland it sets Google advertising cookies. Visitors in the EEA, the UK and Switzerland get no advertising cookies: we don't show a cookie consent banner yet, so we don't set them. When you create an account, and again when you start building your first app, your browser sends Google a scrambled copy of your email address (SHA-256 hashed — Google calls this enhanced conversions) so Google can match the sign-up to an ad you saw or clicked. If your browser sends the Global Privacy Control (GPC) signal, we treat it as an opt-out wherever you are: no advertising cookies and no copy of your email, though Google still learns that a sign-up happened. When you arrive from one of our ads, we keep the ad's click ID and campaign tags in a first-party cookie for up to 90 days and save them with your account when you sign up, to learn which ads lead to paying customers (we skip this when your browser sends GPC). The same Google advertising cookies let us show Buildliy's ads on YouTube to people who visited buildliy.com in the last 30 days but haven't started building yet (never in the EEA, the UK or Switzerland, and never when your browser sends GPC). To opt out, turn on GPC in your browser (some browsers and extensions send it), or block advertising and third-party cookies in your browser settings. To stop Google showing you personalized ads, visit adssettings.google.com. Google gets nothing you build, and we don't use Google Analytics. Voice input uses your browser's built-in speech recognition; the audio is handled by your browser and never reaches our servers.
You can request a copy of all the data we hold about you, ask us to delete your account, or ask us to delete the analytics data linked to your account — email privacy@buildliy.com. For users in the EU and California, we honor GDPR and CCPA rights including data portability and right to erasure.
Buildliy is not directed to children under 16. We do not knowingly collect data from anyone under that age; if you believe a child has signed up, contact us and we will delete the account.
We may update this policy as the product evolves. Material changes will be announced in-app and via email at least 14 days before they take effect.