Privacy policy

01Who we are

homebuild To confirm legal entity name, state of organization and mailing address provides homebuild.ai and the home board software that builders use with their customers.

This policy covers:

• Visitors to homebuild.ai, our own website.
• Builders and their teams who use homebuild’s team workspace.
• Families and the people they invite on a board a builder runs on homebuild. For them, the builder’s privacy notice comes first (see Boards run for builders).

02On homebuild.ai

What we collect

• What you send us: if you ask to talk with us, your name, work email, company, phone number (optional) and message. To confirm form fields at launch
• Visit counts: pages viewed and where visitors came from, counted without cookies and without storing your IP address. To confirm analytics tool at launch; a cookieless tool such as Plausible or Cloudflare Web Analytics keeps this true
• Security details: your IP address and browser details, which our hosting provider uses to deliver the site and block abuse, and which may appear in short-lived logs.

How we use it

• To answer you and, if you’re a builder, to talk with you about homebuild.
• To keep the site running, secure and free of spam.
• To see which pages are useful, in counts not tied to you.

Emails from us

• If you ask us to, we may email you about homebuild. Every marketing email says who it’s from, includes our mailing address, and has an unsubscribe link. We honor unsubscribes within 10 business days, usually much sooner. To confirm the tool homebuild uses for its own sales email
• We don’t buy email lists.

Cookies

• homebuild.ai sets no advertising or tracking cookies. To confirm at launch
• If a form uses Cloudflare’s bot check (Turnstile), Cloudflare may set a cookie that the check needs.

Our product pictures

• Screenshots and examples on homebuild.ai use a made-up sample builder and made-up families. We never show a real builder’s name, logo or photos, or a real family’s information, without permission.

03Builders and their teams

What we collect

• Account details: name, work email, role and notification settings for each team member.
• Security details: sign-ins, invites, role changes, deletions and similar events in a security log, with a hashed (scrambled) IP address.
• What you write: messages to families, internal notes, stage changes, corrections to AI briefs, and your settings.
• Business details: your company’s contact, billing and contract information. To confirm how builders are billed; if a payment processor is used, it handles card details and we never see full card numbers

How we use it

• To provide the team workspace, send the notifications you choose, and support you.
• To keep accounts secure and investigate problems.
• To bill you and manage our contract. To confirm
• To improve homebuild, using counts not tied to any person.

Who sees it

• Your team admins can see and manage your team’s accounts.
• Families never see your team’s internal notes, the AI brief, readiness scores, activity levels, or team members’ last-visit times. Whether team members’ names appear to families is the builder’s choice.
• Your internal notes are sent to our AI provider as part of the brief (see How we use AI).

04Boards run for builders

When a builder uses homebuild, the builder decides how a family’s information is used. homebuild is the builder’s service provider (sometimes called a “processor”). To confirm data processing agreement signed with each builder

What that means

• We use board information only to run the board, keep the service secure, and measure and improve it, as our contract with the builder allows. Never sold or used for ads.
• Each builder’s information is kept separate. Boards with two builders are separate accounts, and neither builder can see the other’s board.
• We follow the builder’s instructions, including requests to delete a board or a person. To confirm deletion tools or a tested runbook exist
• The builder’s privacy notice, at /privacy on the builder’s board site, explains what’s collected, who sees it and your choices.

What “secure” and “improve” cover

• Security across all builders: bot checks, rate limits, and a hashed version of IP addresses and emails to spot abuse.
• Service-wide counts: for example, how many people finish Start Your Build, never tied to a person.
• AI quality: how often AI photo suggestions and briefs are corrected, to make them better for the builder. To confirm counts only, or also the photos and corrections themselves; the spec treats corrections as the evaluation set (SPEC 7.11)

Your requests

• Send requests about a board to the builder, or to us. If you write to us, we’ll pass your request to the builder and help them answer it.

05How we use AI

• On boards, AI:
  • suggests rooms and captions for photos;
  • writes short room summaries for families;
  • writes a private brief for the builder’s team, including its own read on a family’s readiness and budget.
• Provider: Anthropic, through its business service. Under its commercial terms, Anthropic may not train its models on this information. It deletes it within 30 days, or keeps it up to 2 years if a safety review flags it. To confirm recheck at launch
• What it never receives: email addresses, phone numbers or IP addresses, unless someone types them into a note or message.
• AI can be wrong. AI-written captions and summaries are labeled as AI on screen. To confirm labels built AI doesn’t decide anything about anyone. Builders’ teams review everything and make their own calls.

06Service providers

These companies help us run homebuild. Each is bound by a contract to protect the information and use it only for us, except as noted.

Cloudflare’s bot check (Turnstile) also uses IP addresses and browser details to improve its own bot detection, as its own business, under its Turnstile privacy addendum.

Tools a builder turns on

A builder can send new inquiries to its own tools: its customer database (CRM), Orbit (a lead inbox run by 3engines), a text alert to its team To confirm text provider, or Plausible Analytics. Those tools work for the builder, and the builder’s privacy notice lists the ones it uses.

We’ll update this list, and tell builders at least To confirm for example, 15 days ahead, before adding a provider that handles board information.

07When we share information

• With service providers, as listed above.
• With a builder, for boards that builder runs.
• When the law requires it (for example, a valid subpoena), to protect someone’s safety or rights, or to investigate fraud or abuse.
• If homebuild merges or is sold, information may move to the new owner, who must keep protecting it as this policy describes. To confirm lawyer review

We don’t sell personal information, and we don’t share it for targeted ads.

08Do Not Track and Global Privacy Control

• We don’t track visitors across other websites. Our sites work the same whether or not your browser sends “Do Not Track.”
• We treat a Global Privacy Control (GPC) signal as a request to opt out of any sale or sharing. There’s nothing to switch off today. If that ever changes, we’ll honor GPC automatically. To confirm lawyer confirms Cloudflare’s own use of bot-check data isn’t a “sale” or “sharing”

09How long we keep it

Board information follows the builder’s privacy notice while the builder is a customer.

10Your choices and rights

You can ask us to:

• See the information we have about you and get a copy.
• Correct anything that’s wrong.
• Delete your information.
• Opt out of any sale, sharing or targeted ads (we don’t do any of these).
• Unsubscribe from marketing email, using the link in any of them.
• Review our answer: if we turn down a request, reply and someone else will review it. If you’re still not satisfied, you can contact your state attorney general.

How it works

• We offer these rights to everyone in the US, whether or not your state’s law requires it.
• We’ll confirm it’s you, usually by email.
• We’ll answer within 45 days. To confirm
• Someone can act for you with your written permission. To confirm lawyer review
• We won’t treat you differently for asking.

For information on a builder’s board, the builder decides, and we help them.

11Keeping information safe

• Encrypted in transit (HTTPS) and when stored.
• No passwords to steal. Sign-in uses one-time links and short codes that expire.
• Each builder’s information is kept separate, and every request is checked against who may see what.
• Photos are served only to people with access, with location data removed before storage.
• Bot checks, rate limits and caps on AI and email use guard against abuse.
• Logs leave out messages, notes, email addresses and sign-in links.
• Access by homebuild staff is limited to what’s needed to run and support the service. To confirm who has access, when, and how it’s logged
• If a breach affects personal information the law protects, we’ll tell the affected builders immediately, and notify you and the authorities as the law requires (in New York, within 30 days of discovery).

No system is perfectly secure. If you think something is wrong, tell us right away.

12Children

homebuild is for adults 18 and over. We don’t knowingly collect information from children. If we learn we have, we’ll delete it. To confirm lawyer review, including the New York Child Data Protection Act

13Where information is stored

homebuild is for people and businesses in the US. To confirm “Information is stored in the United States,” only after checking the storage location settings. Our providers may handle it in other countries, under contracts that protect it.

14Changes to this policy

When we change this policy, we’ll update the date at the top. If a change would use information you’ve already given us in a new way, we’ll tell you before it takes effect (by email if we have your address) and ask for your OK where the law requires. We’ll give builders notice as their contract says.

15Contact us

• Email: To confirm homebuild privacy email
• Mail: To confirm homebuild mailing address