Privacy Policy

This Privacy Policy explains how Buildrok LLC ("Buildrok", "we", "us", or "our") collects, uses, shares, and protects information when you use our website located at buildrok.com and our website-building service (together, the "Service"). Buildrok is based in Austin, Texas, United States.

By using the Service, you agree to the collection and use of information in accordance with this Policy. If you do not agree, please do not use the Service.

What changed in this version

Updated October 14, 2026:

• Rewrote section 5 (Cookies and tracking technologies) and the browser-storage parts of section 1.2 to describe every cookie and storage key the Service sets, alongside a rewritten Cookie Policy that lists each one by name. Section 5 now says what we actually do with Global Privacy Control and Do Not Track signals: we treat either as an opt-out of analytics.
• Corrected the length of a Support Session to 30 minutes (sections 1.2 and 3.4).

Updated October 9, 2026:

• Expanded the Texas residents part of section 6: how to make a request, how long we take to respond and when that can be extended, and how to appeal a decision we make on your request, including how to reach the Texas Attorney General if we deny your appeal.

Updated October 8, 2026:

• Added the optional AI receptionist: what is recorded when it answers a call, that our voice provider Retell handles those calls, how long call records are kept, and how a caller can have one deleted (sections 1.1, 3.1, 3.5 and 4).
• Added the text messages we send for your business, missed-call text-back and review requests by text: what we keep about them and how an opt-out is kept (section 1.1). Twilio's entry in section 3.1 now names every kind of text it sends for us.

Updated September 22, 2026:

• Added the optional Instagram integration: what we read from a connected account, that we store an access token encrypted, why we keep our own copy of the images, and how to disconnect (section 1.1).

1. Information we collect

1.1 Information you provide directly

• Account information: your name and email address when you create an account or sign in (including via Google OAuth).
• Site and draft content: business name, descriptions, phone numbers, addresses, images, and other content you enter to build, edit, preview, or publish a website.
• Domain information: domain names you search for, purchase, or connect, plus the technical details we need to configure DNS and connect your domain to your hosted site.
• Support communications: messages, names, and email addresses you submit via our contact form or by emailing support@buildrok.com. When you ask for help, we may also record internal notes about the conversation and the steps we took to investigate or resolve the issue (including audit-log entries from any Support Session we open on your account, see Section 3.4).
• Leads from visitors to your published site: when a visitor to your published Buildrok site submits a quote request, booking, or contact form, we record the visitor's name, email address, phone number, message content, the form type used, the form's source page, and any custom field values, and we make this data available to you through your Lead Inbox. For this data, you are the data controller and Buildrok acts as a processor handling the data on your behalf so you can follow up with potential customers. You are responsible for ensuring that your own privacy notice to your visitors accurately describes how you collect and use these submissions. Visitors can request permanent deletion of their form submissions at any time through our self-service data deletion page.
• Calls answered by your AI receptionist (optional add-on): when your AI receptionist answers a call forwarded from your business phone, the call is recorded and transcribed. Every call opens with the words "Calls are recorded so we get your details right.", and that notice cannot be turned off. We keep the caller's phone number, a transcript, a short summary, a link to the recording, and the details the caller gives (such as their name, a callback number, an address, what they need and whether it is urgent), and we email them to you and save them in your Lead Inbox. The receptionist does not pretend to be a person, and if a caller asks, it says it is an AI assistant. Our voice provider, Retell, handles the call itself and stores the audio recording (section 3.1). For this data, as for leads from your site, you are the controller and Buildrok is your processor, so your own privacy notice should tell callers that their calls are recorded and how you use what they tell you. The data deletion page works by email address and cannot find a call; section 4 explains how a call is deleted.
• Texts sent for your business (optional): if you turn on missed-call text-back or review requests by text, we send the message through our SMS provider, Twilio (section 3.1), and keep the recipient's phone number, the message we sent, any reply (a text-back reply becomes a lead in your Lead Inbox; a reply to a review request records their answer), and whether they have opted out. We keep an opt-out so that number is not texted again from your Buildrok number. As with calls, you are the controller of this data and Buildrok is your processor.
• Your AI receptionist's setup: the business details you give it to answer callers with, such as your hours, the services you offer, the area you cover, answers to questions your callers often ask, what counts as urgent for you, anything it must never say, and the number it should put a caller through to if they ask for you.
• Google Business Profile (optional integration): if you connect a Google Business Profile to your site, Buildrok uses Google OAuth to read business-profile data (such as listing details, reviews, posts, and photos) and to sync that data into your Buildrok site. We store an OAuth access token and refresh token associated with your account so the sync can run on a schedule. You can revoke access at any time from your Google account settings or by disconnecting the integration in your Buildrok dashboard.
• Instagram (optional integration): if you connect an Instagram professional account to your site, Buildrok uses Instagram Business Login to read your recent posts (image, caption, permalink and post type) and your username, and shows a selection of those posts on your website. We store an access token associated with your account, encrypted at rest, so the feed can refresh. We copy the images themselves into our own storage, because the image links Instagram provides expire. We never post on your behalf, never read your direct messages, and never access your followers or comments. You can revoke access at any time in your Instagram settings, or by disconnecting the integration in your Buildrok dashboard.
• Payment information: payment processing is handled entirely by Stripe, Inc. We do not receive or store your full card number, CVV, or bank account details. We may receive limited metadata such as payment status, transaction identifiers, the last four digits of the card, and card brand.

If you buy Done for you

Our Done For You service means you send us material for us to build your website with, and that material often contains personal data belonging to people other than you. Specifically:

• Photographs. Images of your work, your premises, your staff and sometimes your customers' homes. Photographs of identifiable people are personal data, and photographs taken on a phone frequently carry location metadata. We strip location metadata from images on upload.
• Your logo and brand material.
• Business contact details: the trading address, phone number and email you want shown on your site. For a sole trader these are often personal details as well as business ones.
• Staff names and biographies, where your template has a team section.
• Reviews and testimonials you supply, including the reviewer's name.
• Your ICANN registrant contact. If we register a domain for you, ICANN requires a real name, organization, postal address, email and phone number, and we pass those to our registrar. We keep a copy so we can complete the registration when you approve your site, which may be several days after you order. See section 3.1.

Before you send us photographs of people, please make sure you have their permission. Section 6.6 of our Terms of Service covers this.

1.2 Information collected automatically

• Server and access logs: standard server logs may include IP addresses, browser type, operating system, referring URLs, request timestamps, and HTTP status codes. These are used for security, debugging, and abuse prevention.
• Custom page-view analytics (for published customer sites): when a visitor views a website published through Buildrok, we record a page view. We hash the visitor's IP address and user agent using a daily-rotating SHA-256 hash, the raw IP address is not stored. We record the page path, referring domain (hostname only), and device type (mobile, tablet, or desktop). This lightweight system does not use persistent cookies or fingerprinting and is designed to be privacy-respecting.
• Product analytics on our marketing pages: on our own marketing pages at buildrok.com (not on the websites you publish), we use two analytics tools, PostHog and Vercel Web Analytics, to understand which pages are viewed and how visitors move through our signup flow so we can improve the product. PostHog keeps an identifier in your browser's localStorage rather than a cookie; we switch off its session recording, automatic click capture and heatmaps, and it does not keep your IP address. Vercel Web Analytics stores nothing on your device. Neither tool sets an advertising or tracking cookie or is used for cross-site tracking, and neither loads when your browser sends a Global Privacy Control or Do Not Track signal. See our Cookie Policy for the exact storage keys.
• Product usage events (first-party, on our own pages only): on our own pages, including your dashboard and the site editor, we record a small set of named steps such as "a draft was created", "a site was published" and "a custom domain went live", so we can see where the process loses people and fix it. Each record holds the step name, the time, an internal draft or site reference, which of our deployments produced it, a few technical labels about the step itself (for example which template or which editing surface), and, where you are signed in, your account reference. It never contains the content of your site, and it never contains anything a visitor submitted through a form on a site you publish. Nothing is stored on or read from your device for this, no third party receives it, and the websites you publish never send it.
• Browser storage: we store your authentication token (JWT) and email address in your browser's localStorage to keep you signed in, and we use localStorage and sessionStorage to remember choices you make in our interface, such as light or dark mode, the editor's layout and tips you have dismissed. This data stays on your device. Our Cookie Policy lists every key.
• Sign-in and account cookies: our authentication provider, Neon Auth, sets session cookies on its own domain when you sign up or sign in, by email and password or with Google. Our own servers set two strictly necessary cookies on buildrok.com: brk_sess, a signed, HTTP-only cookie naming the signed-in account so we can draw your pages, and brk_anon, which ties a draft started before you have an account to the browser that started it. Short-lived cookies also protect the connection while you link an Instagram account or a Google Business Profile.
• Support-session cookie (brk_imp): when authorized Buildrok personnel start a Support Session (see Section 3.4), our servers set a short-lived (30-minute), HTTP-only, HMAC-signed cookie named brk_imp on the support staff member's browser. This cookie is used solely to identify the active support session on the server side. The cookie is never set on your browser.

2. How we use information

• Provide, operate, and maintain the Service (drafts, editing, previewing, publishing, domain management, and the Lead Inbox)
• Process payments, manage subscriptions, and prevent fraud
• Respond to support requests and communicate with you about your account, including providing supervised in-account help via time-limited, audit-logged Support Sessions (see Section 3.4)
• Receive form submissions from visitors to your published site and surface them to you through your Lead Inbox so you can follow up with potential customers
• Send transactional and lifecycle emails (e.g., support replies, password resets, and abandoned-draft reminders that include a one-click unsubscribe link). We do not send promotional marketing emails without your separate consent
• Sync data with third-party integrations you have connected (such as Google Business Profile)
• Improve the reliability, performance, and user experience of the Service
• Detect and prevent abuse, fraud, and unauthorized access, including investigating reports of policy or content violations on published sites
• Comply with legal obligations

3. How we share information

We do not sell your personal information. We share information only as necessary to provide the Service or as required by law.

3.1 Service providers (sub-processors)

We use the following third parties to run the Service. Each processes personal data on our behalf, under contract, and only for the purpose listed.

The last column matters if you are one of our customers: it says whether that provider also handles data belonging to your website's visitors (and, for the AI receptionist, the people who call you). For that data we act as your processor rather than as the controller, which is explained in section 3.5.

We do not sell personal data and we do not share it with advertisers. We update this list when a provider changes; the "last updated" date at the top of this page tells you when it was last reviewed.

3.5 Controller and processor: which one we are

This distinction decides who is answerable for what, so it is worth two paragraphs.

For your own account data we are the controller. That is your name, your email, your billing details, the content of your website, and how you use the Service. We decide why and how it is processed, and this policy governs it.

For data submitted by visitors to your published website we are your processor, and you are the controller. When somebody fills in your quote form, requests a booking, or places an order, that person is your prospective customer, not ours. We store and forward their details so that you receive them, and we act on your instructions. You decide why you collected them, how long you keep them and what you do with them, and it is your responsibility to tell those visitors what you are doing, in your own privacy notice.

The same applies to people your AI receptionist answers. They are calling your business, not ours. We record the call and pass on what they told you, on your behalf, and your privacy notice is where they should learn that their calls are recorded.

The providers that touch visitor data on our behalf are Vercel, Neon, Resend, Cloudflare, Retell and Twilio. If you need to name your sub-processors in your own privacy notice, those are the ones to name alongside Buildrok.

Section 11 of our Terms of Service sets out the data processing terms that apply between us for that visitor data, including our commitments and yours. If you need a separate signed data processing agreement, email support@buildrok.com and we will provide one.

3.2 Legal disclosures

We may disclose information if required to do so by law, court order, or governmental authority, or if we believe disclosure is necessary to protect the rights, property, or safety of Buildrok, our users, or others.

3.3 Business transfers

If Buildrok is involved in a merger, acquisition, or sale of assets, your information may be transferred as part of that transaction. We will notify you via a notice on the Service or by email before your information becomes subject to a different privacy policy.

3.4 Customer support access (support sessions)

Authorized Buildrok personnel may sign in to your account on your behalf to investigate a support request, a billing or abuse report, or a suspected security incident. We treat this as an internal data access rather than a third-party disclosure. Every such access is governed by the safeguards described in our Terms of Service (Section 8), including:

• Role-restricted access: only staff who hold the admin role in our internal role table can initiate a Support Session.
• A mandatory written reason (4 to 500 characters) captured at the time of access.
• Recording of the staff member's identity and email, the target user, the reason, the IP address, and the user agent in an append-only audit log.
• An automatic 30-minute expiry, after which a new session (and a new audit record) is required.
• A persistent banner shown on every page during the session, identifying the staff member acting on your behalf.
• Sensitive self-service operations are blocked during a Support Session and cannot be performed on your behalf: subscription cancellation, profile changes, personal-data export requests, domain checkout, and domain purchase.

Support Session audit records (admin identity, target user, reason, IP, user agent, start and end times) are retained for at least twelve (12) months for security, compliance, and incident-response purposes. You may request a copy of the audit-log entries relating to your own account, or ask us to refrain from initiating future Support Sessions on your account, by emailing support@buildrok.com.

4. Data retention

If you take a refund under our guarantee, your website is taken offline immediately and your content and your leads are kept for 30 days so that you can export anything you need. After 30 days they are deleted and cannot be recovered. Your domain is unaffected: you own it, you keep it, and its registration data stays with the registrar.

Done For You material you sent us (photographs, logo, copy) follows the same retention as the rest of your site content. If you never complete an order, the material you uploaded is deleted with the draft it belongs to.

Domain registrant contact details are kept for as long as we manage the domain for you, and afterwards only where a registrar or ICANN requires us to. The registrar keeps its own copy under ICANN's rules, and we cannot delete that on your behalf.

Records of refunds and payments are kept for seven years, because tax and accounting law requires it. That is a legal obligation and is not something we can delete on request.

We retain your account and site data for as long as your account is active or as needed to provide the Service. Draft sites expire and are permanently deleted after a period of inactivity: drafts created without an account expire after roughly 24 hours, and drafts attached to an account expire after 14 days of inactivity. When you delete a published site it is held for a 30-day recovery period and then permanently deleted along with its associated data. Product usage events (Section 1.2) are retained for 24 months and then deleted; once the draft or site they refer to has been deleted, the reference they hold no longer identifies anything. Transaction records, billing history, and related logs may be retained for a period consistent with accounting and legal requirements (typically up to seven years). You may request deletion of your account and personal data at any time (see Section 6).

Lead Inbox data: visitor submissions captured by your published site are retained for the life of your site so you can refer back to them. You can archive a lead, which hides it from your Lead Inbox without deleting it; we delete a lead on request. When you delete a site or your account, the leads associated with that site are deleted on the same schedule as the rest of your site data. A visitor can also delete their own submissions, including attached files, at any time through our data deletion page; appointment records linked to a deleted submission are anonymized so the calendar slot remains accurate without identifying the visitor.

AI receptionist calls: the transcript, summary and recording link for each call are kept for as long as your receptionist is set up with us, so you can refer back to them. Archiving a lead does not delete it or the call it came from. When you ask us to remove your receptionist or to close your account, we delete its call records, and a receptionist attached to a website also loses them when that site is deleted, on the schedule above. Retell keeps its own copy of each call's recording and transcript under its retention terms. We will delete any single call on request, from our records and from Retell's: a caller can ask you, or email support@buildrok.com with the number they called from and roughly when, since the data deletion page works by email address and cannot find a call.

Support Session audit log: records of every Support Session opened on any account (admin identity, target user, written reason, IP address, user agent, and start and end timestamps) are retained for twelve (12) months after the session ends for security, compliance, and incident-response purposes, then automatically deleted, unless we are legally required to retain specific records longer.

Email suppression lists: if you unsubscribe from lifecycle emails (such as abandoned-draft reminders), we retain a minimal record of your unsubscribe (email address and timestamp) so we do not email you again.

5. Cookies and tracking technologies

We do not use third-party advertising cookies or tracking pixels. Our marketing pages set no cookies. The Service uses the following, and our Cookie Policy lists each one by name with how long it lasts:

• Strictly necessary cookies: brk_sess and brk_anon on buildrok.com (see section 1.2), the session cookies our authentication provider, Neon Auth, sets on its own domain when you sign in, and short-lived cookies that protect the connection while you link an Instagram account or a Google Business Profile.
• localStorage (authentication): your JWT and email are stored locally to maintain your session.
• localStorage and sessionStorage (preferences and interface state): choices you make in our interface, such as light or dark mode, the editor's layout, the site you last opened, tips you have dismissed and the editor's undo history.
• localStorage and sessionStorage (analytics): on our marketing pages only, PostHog keeps an identifier in localStorage and details of the current visit in sessionStorage. This is not strictly necessary, and privacy laws in some places, including the European Union and the United Kingdom, treat it the same way as a cookie. It is not used for cross-site tracking or advertising, clearing your browser storage removes it, and it is never written when your browser sends a GPC or DNT signal (see below). Vercel Web Analytics on those pages stores nothing on your device.
• sessionStorage (error monitoring): on your dashboard and in the editor, Sentry keeps the state of its error replay for the current tab. Replays mask all text and form input and block all images and video.
• Support-session and build cookies (brk_imp, brk_build): HTTP-only, HMAC-signed cookies set only on Buildrok staff browsers, for 30 minutes during a Support Session (see Section 3.4) and for 8 hours while staff build a Done-For-You order's site. Never set on customer browsers.

Do Not Track and Global Privacy Control signals. Some browsers can send a "Do Not Track" (DNT) signal or a Global Privacy Control (GPC) opt-out preference signal. We treat either one as an opt-out of analytics: when your browser sends it, our pages load neither PostHog nor Vercel Web Analytics, and we drop the product usage events described in section 1.2 that your browser would otherwise send. Three of those events are recorded by our servers when the step happens, whatever your browser sends, because they are part of providing the Service: a draft being created, a site being published and a custom domain going live. We do not sell or "share" your personal information for cross-context behavioral advertising, so there is no sale or sharing for a GPC signal to stop; where GPC is legally treated as a request to opt out of sale or sharing, we honor it by default.

For more detail, see our Cookie Policy.

6. Your rights and choices

Depending on where you live, you may have certain rights regarding your personal information. These may include the right to access, correct, delete, or obtain a copy of your personal data. To exercise any of these rights, please contact us using the information in Section 10 below.

• You can edit or delete your drafts and published sites from the dashboard.
• You can delete your account from your account settings (Danger Zone tab). Deleting your account will remove your profile and disable access to the Service. Some transaction records may be retained for legal and accounting purposes.
• You can request an export of the data we hold for your account from your account settings; the export includes your profile, sites, domain purchases, Lead Inbox, bookings, support access log, and your product usage events in a machine-readable format.
• If you are a visitor who submitted a form on a website hosted by Buildrok, you can permanently delete your submissions through our data deletion page without contacting anyone.
• You can contact us to request access to, correction of, or deletion of your personal information.

Users in the European Economic Area and the United Kingdom

Where the GDPR or UK GDPR applies, we process personal data on the following legal bases:

• Performance of a contract (Article 6(1)(b)): providing the Service you signed up for, including building, hosting, and publishing your site, processing payments, and delivering leads to your Lead Inbox.
• Legitimate interests (Article 6(1)(f)): securing the Service, preventing fraud, spam, and abuse, debugging and error monitoring, measuring how the product is used so we can improve it, and improving reliability and performance.
• Consent (Article 6(1)(a)): optional integrations you choose to connect (such as Google Business Profile) and any communications that require an opt-in. You can withdraw consent at any time.
• Legal obligation (Article 6(1)(c)): retaining transaction and billing records for tax and accounting purposes.

You have the rights to access, rectify, erase, restrict, and port your personal data, and to object to processing based on legitimate interests. To exercise these rights, contact us using the details in Section 10, use the data export option in your account settings, or, for form submissions made on a Buildrok-hosted website, use the self-service data deletion page. You also have the right to lodge a complaint with your local data-protection supervisory authority.

International data transfers

Buildrok is based in the United States, and the service providers (sub-processors) listed in Section 3.1 process data in the United States and other countries. If you access the Service from the European Economic Area, the United Kingdom, or another region with data-transfer restrictions, your personal data may be transferred to and processed in the United States, where data-protection laws may differ from those in your jurisdiction. Where we transfer personal data out of the EEA or the UK, we rely on appropriate safeguards under applicable law, such as the European Commission's Standard Contractual Clauses (and the UK International Data Transfer Addendum), and, where a sub-processor is certified, the EU-U.S. Data Privacy Framework and its UK extension. You may contact us using the details in Section 10 for more information about the safeguards we use.

California residents

This section applies if you are a California resident.

• No sale or sharing of personal information. We do not sell your personal information, and we have not sold it in the prior twelve (12) months. We do not "share" personal information for cross-context behavioral advertising, as those terms are defined under the California Consumer Privacy Act (CCPA), as amended by the California Privacy Rights Act (CPRA). We do not use third-party advertising cookies or tracking pixels. Because we do not sell or share personal information, we do not provide a separate "Do Not Sell or Share My Personal Information" page, this disclosure serves that purpose.
• "Shine the Light" (Cal. Civil Code § 1798.83). We do not disclose personal information to third parties for those third parties' own direct marketing purposes. California residents may contact us at support@buildrok.com with any questions about this practice.
• Do Not Track. We disclose how we respond to "Do Not Track" and Global Privacy Control browser signals in Section 5 (Cookies and tracking technologies) above.
• CCPA rights. To the extent the CCPA applies to your interaction with us, you have the right to know and access the personal information we have collected about you, to request that we correct or delete it, and to be free from discrimination for exercising these rights. To exercise these rights, email support@buildrok.com or use the data export and account-deletion tools described above. Visitors who submitted a lead through a published Buildrok site can permanently delete their information at any time through our data deletion page.

Texas residents

The Texas Data Privacy and Security Act (TDPSA), effective July 1, 2024, gives Texas residents the right to confirm whether we process your personal data and to access it, to correct inaccuracies in it, to delete personal data you provided or we obtained about you, to obtain a copy of it in a portable format, and to opt out of the sale of personal data, targeted advertising, and profiling in furtherance of decisions that produce legal or similarly significant effects. We do not sell personal data, and we do not use it for targeted advertising or for that kind of profiling.

• How to make a request. Email support@buildrok.com or use our contact form. You do not need a Buildrok account to make one. If you have an account, you can also export or delete your data yourself from your account settings, and anyone who submitted a form on a Buildrok-hosted website can delete it through our data deletion page. We may ask for information reasonably necessary to confirm who you are before we act on a request.
• When we respond. Within 45 days of receiving your request. If we need longer, we may extend that once by a further 45 days, and if we do we will tell you within the first 45 days, with the reason. We answer requests free of charge, at least twice a year.
• Authorized agents. Someone you authorize, including through a browser setting such as Global Privacy Control, may opt out on your behalf.
• Appealing our decision. If we decline to act on your request, we will tell you why. You can appeal by replying to that decision, or by emailing support@buildrok.com with "Privacy appeal" in the subject line. Within 60 days of receiving your appeal, we will tell you in writing what we did or did not do in response and why. If we deny your appeal, you can submit a complaint to the Texas Attorney General through its online consumer complaint form.

Other U.S. state residents

A number of other U.S. states (including Colorado, Connecticut, Virginia, Oregon, Montana, and others) have comprehensive privacy laws that grant rights similar to those described above, such as the rights to access, correct, delete, and obtain a copy of your personal data, and to opt out of targeted advertising, the sale of personal data, and certain profiling. We extend these rights to residents of any U.S. state that grants them. As noted above, we do not sell personal data or use it for targeted advertising or for profiling that produces legal or similarly significant effects, and where your browser sends a recognized universal opt-out signal such as Global Privacy Control, we honor it. To exercise any of these rights, email support@buildrok.com; we will respond within the timeframe required by your state's law.

7. Children's privacy

The Service is not directed to children under the age of 13, and we do not knowingly collect personal information from children under 13. If you believe we have inadvertently collected information from a child under 13, please contact us immediately so we can take appropriate steps to delete it.

8. Security

We use reasonable administrative, technical, and organizational measures designed to protect your information from unauthorized access, disclosure, alteration, or destruction. However, no method of internet transmission or electronic storage is 100% secure. We cannot guarantee absolute security. In the event of a data breach that is likely to result in a risk to your rights and freedoms, we will notify affected users and relevant authorities as required by applicable law.

9. Changes to this policy

We may update this Privacy Policy from time to time. When we make material changes, we will update the "Last updated" date at the top of this page and, where feasible, provide notice within the Service or by email. Your continued use of the Service after changes are posted constitutes acceptance of the updated Policy.

10. Contact us

If you have questions or concerns about this Privacy Policy or how we handle your information, please contact us:

• Email: support@buildrok.com
• Contact form: buildrok.com/contact
• Mailing address: Buildrok LLC, 5900 Balcones Drive, Suite 100, Austin, TX 78731, United States