Privacy Policy

1. Who we are

C Building (the “Platform”, at cbuilding.ai) is a product of, and is operated by, Goldi Apple LLC, a Wyoming limited liability company at 30 N Gould St #42214, Sheridan, WY 82801, USA. Goldi Apple LLC is the controller of the personal data described in this policy, which explains how we collect, use, protect and share it. For the data of visitors to websites built with C Building (for example their form submissions), the website’s owner decides what is collected and is responsible for it; we process it on the owner’s behalf. By using the Platform’s services, you agree to this policy.

2. Information we collect

• Account information: your e-mail address, your password (stored only as a one-way hash), company name, contact person’s name and similar details.
• Third-party sign-in information: your public name, e-mail address and profile picture, obtained when you sign in with Google. We do not obtain your Google password.
• Website content: the text, images, settings and other website content you create.
• Payment information: plan and top-up orders, and the brand and last four digits of the card saved for renewals. Payments are processed by Stripe; the Platform never stores full card numbers.
• Usage records: activity logs, IP addresses, and browser and device information.
• Lead data: visitor messages and inquiries collected through the websites you create.
• AI conversations: the messages, images and files you send to our AI assistants, and what the AI produces while it works on your websites or account.
• Reports and appeals: when you report a website or appeal a takedown: your name if you give it, e-mail address, IP address and what you write, and for a copyright or trademark notice your postal address, telephone number and signature. We use it to review the report, answer you and keep the records the law asks for (legal obligation and legitimate interests). A copyright or trademark notice may be sent to the owner of the website concerned, as copyright law expects.
• Analytics: which pages and features you use, collected with PostHog only as described in section 9.

3. Why we use information, and our legal bases

Where the law requires a legal basis (for example Article 6 of the EU or UK GDPR), we rely on the following:

• Contract: to create and run your account; build, store, preview and publish your websites; provide the AI features you use; take payments and renew your plan; register domains; send service e-mails; and answer support requests.
• Consent: for the processing of your content by the AI and e-mail providers named in the consent you give at sign-up (section 4), and for analytics where the law requires consent (section 9). You can withdraw consent at any time; this does not affect processing that took place before.
• Legitimate interests: to keep the service secure, prevent abuse and fraud, investigate errors, and improve the service and the quality of our AI. You can object to this processing (section 11).
• Legal obligation: to keep accounting and tax records and to respond to lawful requests from authorities.

4. How AI processes your content

• Our AI features send your messages, website content and the images and files you attach to AI providers in the United States: Anthropic (the website AI and the account assistant), OpenAI (titles, plans, suggestions, and image generation and editing) and TypeSafe (checking what your messages ask). Every account agrees to this with a separate checkbox, never ticked in advance, before using the product. These providers may keep or use the content under their own terms.
• Goldi Apple LLC does not train or fine-tune any AI model on your data.
• Please do not enter sensitive personal data, or other people’s personal data, into AI chats unless the task needs it.

5. Service providers and disclosure

We do not sell your personal information or use it for cross-site advertising. We share it only with the service providers below, which process it for us to the extent necessary; with people you choose to work with or connect (such as members you invite to a project); and where the law requires it or it is needed to protect the safety of users and the public.

• Google Cloud (Taiwan; code backups in Japan): hosts our servers, main database, published websites and backups.
• E2B (United States): runs each website’s editing environment (sandbox), where your website’s code and the AI’s working files are kept.
• Anthropic (United States): AI models for the website AI and the account assistant, web search, and reading web pages for research.
• OpenAI (United States): AI models for conversation titles, website plans, suggestions, and image generation and editing.
• TypeSafe AI, Inc. (United States): classifies what your messages to the website AI ask, and scores form submissions on your websites for spam.
• EngageLab (Singapore): sends our e-mails, such as verification codes, billing notices and new-form-submission notices.
• Stripe (United States): processes card payments, keeps your card for renewals and prevents fraud. Your card number goes directly to Stripe.
• Cloudflare (worldwide network): delivers and protects cbuilding.ai and published websites, and stores media library files (Asia-Pacific region).
• Google (United States): Sign in with Google, if you choose it, and our company e-mail (Google Workspace), where messages to [email protected] arrive.
• Name.com (United States): registers domains you buy through us; the registrant details you enter go to Name.com and the domain registry, as ICANN rules require.
• Amazon Web Services (worldwide): DNS hosting (Route 53) for domains whose DNS we host.
• Tavily (United States): backup web search for the AI; it receives search queries.
• PostHog (United States): product analytics, only as described in section 9.

6. International transfers

Goldi Apple LLC is a US company and our providers are in several countries, so your data is processed outside the country where you live: mainly in Taiwan (our servers and main database), the United States (website workspaces, AI, payments, domains and sign-in), Singapore (e-mail delivery) and Japan (code backups), and on Cloudflare’s worldwide network. Where your law requires a safeguard for these transfers, we rely on the EU–US Data Privacy Framework for US providers certified under it (Google, Cloudflare, Stripe, Name.com and Amazon Web Services); on the Standard Contractual Clauses included in the data processing terms of Google Cloud, Cloudflare, Stripe and Amazon Web Services; and, for Anthropic, OpenAI, TypeSafe and EngageLab, on the explicit consent you give at sign-up. For E2B, Tavily and PostHog we have not signed Standard Contractual Clauses or a data processing agreement: we rely on their standard terms, and we send them only what their service needs. You can ask for a copy of these safeguards at [email protected].

7. How long we keep data

We keep personal data only as long as we need it, then delete it:

• Account and profile: while your account is open. When you delete your account, it is closed at once and its data is deleted, normally within minutes.
• Websites you delete: kept in the recycle bin for 30 days so you can restore them, then deleted for good; copies in our off-site code backups expire after 45 days.
• AI conversations: until you delete the conversation or your account. Files you attach in chat are kept for 14 days; records we keep to monitor and fix the AI are deleted after about 90 days.
• Form submissions and media you delete: erased from our database within a day; deleted media first stays in the trash for 30 days.
• Billing and payment records: 7 years, for tax and accounting. After you delete your account they are kept without your personal details.
• Logs: error and application logs 90 days; AI turn logs, AI-tool call logs and staff action logs 180 days; notifications, DNS change logs and abuse reports 365 days; web server logs about 14 days.
• Database backups: encrypted, and kept for 30 days.
• We may keep data longer where the law requires it or to establish or defend legal claims.

8. Data security

We take reasonable technical and organisational measures, including HTTPS encryption in transit, passwords stored only as one-way hashes, encryption of sensitive tokens and domain registrant details, a separate isolated sandbox for each website’s editing environment, access control, system updates and daily encrypted database backups. No system is completely secure; if a security incident affects your personal data, we will notify you and the authorities as the law requires.

9. Cookies and analytics

• Necessary cookies: keep you signed in, remember your language and protect the sign-in and payment steps (Stripe’s payment form may set its own cookies to prevent fraud). They are always on; if you block them, you cannot sign in.
• Analytics: we use PostHog to understand which pages and features are used, so we can improve the product. Where the law requires your consent, PostHog loads only after you agree in our cookie banner, and you can withdraw your consent at any time.
• We do not use advertising cookies. Cookies on websites built with C Building are controlled by their owners.

10. Visitor statistics on websites published with the Platform

To show you how many people visit the websites you publish with the Platform and how they use them, we keep statistics on visits to those websites. We do this on your behalf, as your service provider. It is on by default, and you can turn it off for each website on its Integrations page.

• What we record: for each page view, the page address (query parameters are dropped, except utm_source, utm_medium and utm_campaign), the domain of the website the visitor came from, the visitor’s country, the type of device (computer, phone or tablet), the browser’s name, and how long the page was shown on the visitor’s screen. Visits by known bots and from data-center networks are not counted.
• Form submissions: when a visitor successfully sends a form on the website, the statistics record one inquiry, with the form’s name, the page it was sent from and the time, and add it to the totals by source, campaign and page, so that you can see which sources and campaigns bring inquiries. The source and campaign are taken from the visitor’s first page view that day, found through the daily one-way result described below. The inquiry record does not contain what the visitor wrote in the form or their contact details; those are kept separately as lead data (section 2). The two are not connected, but because both note the same website, form, page and time, during the 30 days the inquiry record is kept (see Retention) it could be matched to that form submission, and through it to that visitor’s page views that day. We do not make that match (see Use). After 30 days only daily totals remain, and they cannot be matched to anyone.
• Country: provided by our network provider or, when it does not provide one, looked up from the visitor’s IP address in an IP geolocation database kept on our own servers. The IP address is used only at the moment of the visit, to find the country and to recognize data-center networks, and is not stored.
• No cookies, no stored IP addresses: the counting uses no cookies and stores nothing on the visitor’s device. To count each visitor once per day, we combine the visitor’s IP address and browser identifier with a random value that changes every day and keep only the one-way result. The IP address itself is not stored. The daily random value is deleted after 48 hours; after that, the result can no longer be linked to an IP address. To match the time on a page to the right page view, the page creates a random number for each view; on the visitor’s device it is kept only in memory while the page is open. The number is stored on our servers with the record of that view (and of an inquiry sent from that page), and is deleted with them after 30 days.
• Retention: individual records (page views and inquiries) are deleted after 30 days. After that we keep only daily totals that contain no individual records (for example, page views, visitors, average time on page and inquiries per page, source, campaign, country, device or browser), until the website is permanently deleted.
• Use: only to show the statistics to the website’s owner and the people they share the website with, according to their permissions, in the Platform and through the Platform’s AI assistants when asked. We do not use them for advertising, we do not sell them, and we do not combine them with other information to identify visitors.
• Your website’s own privacy notice: if your website has its own privacy notice, we recommend that it mentions these statistics, for example: “This website counts visits, time on page and form submissions without cookies to understand how it is used; IP addresses are not stored.”

11. Your rights

Depending on where you live, you have the right to access your personal data and get a copy of it, to correct it, to delete it, to receive it in a portable format, to restrict or object to its processing (including processing based on our legitimate interests), and to withdraw your consent at any time.

• Do it yourself: in Account settings, “Download your data” gives you a zip of your account details, websites, AI conversations, form submissions, articles and billing records, and “Delete account” closes and deletes your account. You can correct your profile on the Account page.
• Ask us: for anything else, e-mail [email protected] from your account’s e-mail address. We may ask you to confirm your identity. We do not charge a fee, and we reply within the time your law sets, or within 30 days where it sets none.
• Complain: you also have the right to complain to the data protection authority of the country where you live or work.

12. Children’s privacy

The Platform is intended for business users and is not directed at children under the age of 16. If we discover that we have inadvertently collected information from a minor, we will delete it as soon as possible.

13. Changes to this policy

We may update this policy from time to time and will update the date on this page. If we make material changes, we will notify you by e-mail or through the Platform.

14. Information from Google services and Microsoft Bing (Connect Google, Connect Bing)

On a website’s Integrations page you can choose “Connect Google” to let the Platform set up Google Search Console, Google Analytics and Google Tag Manager for that website. This section explains what we do with the information we receive from Google when you do.

• What we access: your Google account’s e-mail address; Google Site Verification, to verify that you own your website; Google Search Console, to add your website and submit its sitemap; Google Analytics, to list your accounts and properties and, when you ask, create a property and a web data stream; and Google Tag Manager, to list your accounts and containers and, when you ask, create a container; and, only if you allow it, your Google Analytics report data for your website’s property (visitor counts, pages viewed, traffic sources and countries), read-only. When you ask the Platform’s AI assistant about your website’s Google search performance, we also read your website’s Google Search Console data (searches, clicks, impressions, average positions and sitemap status), read-only. We only access what you approve on Google’s consent screen.
• How we use it: only to carry out the setup you ask for on the Integrations page and to show its status there: for example, writing the Google Analytics measurement ID or Tag Manager container ID into your website’s tracking settings and adding Google’s verification tag to your published website. If you allow report access, we read your Google Analytics report data read-only, only to show it to you in your C Building dashboard and, when you ask, in your conversations with the Platform’s AI assistants; the report itself is kept briefly in server memory (about an hour), never stored in our database except as part of an AI conversation described below, and never combined with other customers’ data. We do not use it for advertising, we do not sell it, and we do not use it to develop, improve or train AI or machine-learning models. When you ask the Platform’s AI assistant about your own website’s visitors or search performance, it may read this data for that website to answer you in that conversation: the data is then sent to our AI provider Anthropic only to produce the answer, it is not used by us or by Anthropic to train AI models, and it is never shown to other customers. The answer, and the report figures used for it, stay in that conversation’s history, which you can delete, and are not used for anything else.
• Sharing: we do not share information received from Google with anyone, except as needed to provide this feature, to comply with the law, or with your explicit consent. Our staff do not read it unless you ask us to for support, or as needed for security or to comply with the law.
• Storage and protection: we keep the authorization Google gives us (a refresh token) encrypted with AES-256 in our database, linked to the website and the account that connected it. It is never sent to your browser, your website or the AI assistants. Short-lived access tokens are kept only in server memory.
• Retention and deletion: you can disconnect at any time with “Disconnect” on the Integrations page, or in your Google Account’s security settings. When you disconnect, or delete the website or your account, we revoke the authorization at Google and delete the stored token. What was set up (for example a property or container created in your Google account) stays in your Google account and is managed there.
• Limited Use: C Building’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.
• Microsoft Bing (Connect Bing): on a website’s Integrations page you can also choose “Connect Bing” to let the Platform add your website to your Bing Webmaster Tools account, verify it (by adding Bing’s verification tag to your published website) and submit its sitemap. When you ask the Platform’s AI assistant about your website on Bing, it reads that website’s Bing Webmaster Tools data (searches, clicks, impressions, pages in Bing’s index and crawl issues), read-only, to answer you in that conversation; it is sent to Anthropic only to produce the answer and is not used to train AI models. We keep Bing’s authorization encrypted like Google’s, keep the data itself only briefly in server memory (about an hour), and delete the authorization when you disconnect or delete the website or your account; you can also remove C Building in Bing Webmaster Tools. Every time you publish, we also tell search engines that take part in IndexNow (such as Bing, Yandex and Naver) the public addresses of the pages that changed; no personal data is sent.

15. Contact us