Privacy policy
Version 0.21-draft · Last updated
1. Who we are
This policy explains how Buildly handles personal information collected through thebuildly.com. Contact us at [email protected] with any privacy question. Our registered business details will be added here once finalised.
2. What we collect
Project briefs
When you submit a project brief we collect:
- Your name, email address, business name, country, and preferred language.
- Project details: product type, target platforms, description, intended users, required features, existing product link or technology, integrations, hosting region preference, and timeline.
- Your selected plan and billing interval.
- Whether you agreed to receive marketing emails, and the privacy policy version you acknowledged.
Discovery calls
When you book a call we store the time you chose, your time zone, and any topics you add.
Contact messages
When you use the contact form we collect your name, email address, topic, and message.
Payments and the customer portal
Payments are processed by PayPal. We do not receive or store your card or bank details. We keep records of your invoices and payments (amounts, dates, and PayPal transaction references) and of your customer portal account (name, email address, and preferred language).
People on your project
You can add other people to a project in the portal (for example a colleague or a partner), and so can our team when you ask. We store each person’s name, email address, and language, and email them an invitation. They sign in with their own email address, see the project (its stages, comments, shared content, requests, and previews), and receive its emails; people you give the client’s rights also see and pay its invoices. We record who approved, accepted, or paid what. You can change their role or remove them at any time; their own account stays until they ask us to delete it.
Technical information
We process IP addresses briefly to protect forms from abuse (rate limiting). We do not store them with your brief.
3. How we use it
- To review your brief, prepare a scope, and arrange and hold discovery calls.
- To send operational emails such as confirmations, booking details, and updates about your request.
- To send marketing emails, only if you opted in. You can withdraw consent at any time.
- To protect our services from spam and abuse.
Operational emails are separate from marketing consent: declining marketing does not stop messages you need about your request.
4. Analytics and advertising measurement
We measure how the website is used, such as page views, which plan or form step is chosen, and which buttons and links are clicked, with Google Analytics and PostHog (PostHog’s servers in the European Union; it never records what you type, and we don’t record screen sessions). We also use the Reddit Pixel and the Meta Pixel to measure our advertising on Reddit, Facebook, and Instagram: they tell Reddit and Meta which pages were visited and when a brief, a call booking, or a message was sent, so we can see which ads bring visitors. When you send a brief, book a call, or send a message, our server also reports it to Reddit directly, with your IP address, your browser type, and the Reddit Pixel’s identifier, so it counts even when the pixel is blocked; Reddit counts it once. We never send project descriptions, files, names, email addresses, phone numbers, credentials, or payment details to any of them.
All four use cookies. If you visit from the European Economic Area, the United Kingdom, or Switzerland, none of them is used, and our server sends nothing to Reddit, until you accept in the banner. Elsewhere they are on when you visit, unless you decline in the banner. If you decline, Google Analytics uses no cookies and receives only basic, cookieless signals, PostHog and the Reddit and Meta pixels receive nothing further, and we delete their cookies and stored identifiers on this site. You can change your choice at any time with “Cookie settings” at the bottom of every page. We do not use Google’s advertising features. Reddit and Meta process what they receive under their own privacy policies.
5. Buildly in Claude, ChatGPT, and other AI apps
You can connect an AI app you use (for example Claude or ChatGPT) to Buildly at thebuildly.com/mcp, so it can build and edit your websites and start projects for you. Details are on the Buildly for AI apps page.
What we store
- Your account (name, email address, preferred language) and each connection you approve: the app’s name, when you approved it, and its access tokens, which we store only in a scrambled (hashed) form. You can remove a connection at any time under Account in the portal; its tokens stop working at once.
- Your sites: the files you or your AI app create (pages, styles, scripts, photos), the content you edit in the portal, blog posts and other entries (drafts included), and each published version.
- Messages that visitors send through your site’s forms, kept for you for one year.
- Feedback that you, or people you share your preview with, leave on the preview.
What the AI app sends us
Only what it sends to Buildly’s tools: for example the text of a page to write, a change to make, or a question about your sites. We don’t receive your conversations with the app. The app’s provider (such as Anthropic or OpenAI) processes your conversations under its own privacy policy and terms.
Building with Buildly’s AI
You can also build and edit a site with Buildly’s own AI: in the portal (a site’s “Build with AI” tab), or by asking for a free first version on our request form. Then we send what it needs to Anthropic, which runs the AI (Claude) for us: your messages or your request (your business name and what you wrote about it), and the site’s files and previews as it works. Anthropic processes them on our behalf under its commercial terms, which don’t allow it to train its models on them. We keep the conversation with the site so it can carry on where it left off, and how much AI use it took, for your monthly allowance.
To keep sites within our acceptable use, the text and photos of self-built sites and apps are also checked automatically when they’re added and before they go live, by the same AI (Anthropic, under the same terms). Something that clearly breaks our rules may be refused or held for a person at Buildly to review. We keep the result of each check, and a small copy of a refused or flagged photo, for that review.
Who sees your sites
- A published site is public at its address (yourname.buildly.page and any domain you connect). Don’t put anything in a site you don’t want published.
- The preview of your latest changes is private: it opens only from signed links, from your portal or your AI app, or that you share. Search engines are told not to index it.
- To show you and your AI app what a page looks like, our servers open your preview and take pictures of it. The pictures are sent back to you and not kept.
Images
When your AI app searches for stock photos, the search words are sent to Pexels, and the photo you choose is saved into your site. Don’t include personal information in photo searches.
Your visitors
For your site’s visitors, you decide what your site collects and you are responsible for telling them; Buildly stores form messages on your behalf and doesn’t use them for anything else. When a message arrives we email you that it came, without its text.
Shops
When your site is a shop, we store each order for you: what was bought, the totals, and the buyer’s name, phone, address, and email if they gave one. We use them only to run your shop: to show you the order, to email the buyer their confirmation and you the new order, and to keep the stock right. Card payments happen on your own PayPal, Stripe, or PayTabs account’s page: we never see or store card details, and the money goes to your account, not through us. Your payment keys are saved encrypted and never shown back. You are the seller, responsible to your buyers for their orders and for telling them how you use their details.
Bookings
When your site takes bookings, we store each booking for you: the service, the time, and the answers to your booking form (such as a name, phone, email, or address). We use them only to run your bookings: to show them to you and in your calendar feed, to email the customer their confirmation, a reminder the day before, and their cancel link, and, when you set it up, to send the booking to another service you connected. Payment before a booking happens on your own PayPal, Stripe, or PayTabs page, or by CliQ to you: we never see card details. You decide what your form asks for, and you are responsible to your customers for their bookings and their details.
Members
When your site lets its customers sign in, we keep an account for each of them for you: their email, and the name, phone, address, and city they add, with when they joined and last signed in. They sign in with a code we email them; we keep only a scrambled copy of each code (for 10 minutes) and of each sign-in (for 30 days after it was last used). We use the account only to sign them in, to fill in your shop’s checkout and your booking form, and to show them their own orders and bookings. You can see, export, and remove your members in the portal, and each member can delete their own account from your site at any time; their orders and bookings stay with you.
Deleting
You can delete files, posts, form messages, and feedback in the portal at any time, and a whole site in its Settings, with its published versions, content, form messages, feedback, and AI chat. To delete your account, email us. Copies in our backups, which can’t be changed or deleted early, expire within 30 days.
6. Sharing
We use service providers to host the website and database, to send email, and to run AI features (Anthropic). They process data on our behalf. Payments are processed by PayPal, which handles your payment details under its own privacy policy. We do not sell your personal information. The list of providers will be published here once finalised.
7. Security
- Data is transmitted over HTTPS and access is limited to people who need it.
- We never ask for passwords in forms, comments, or email. Access is shared through a secure method.
- Links to manage your booking contain a secret; keep them private.
8. Retention and your rights
We keep briefs and messages for as long as needed to respond and to maintain a record of accepted terms. Retention periods and the process for access, correction, and deletion requests are being finalised. In the meantime, email us and we will handle your request.
9. Changes
We version this policy. The version you acknowledged is recorded with your submission, and material changes will be shown here with a new version and date.