Privacy policy
Effective July 8, 2026 · Applies to the Home Builder Hub private beta
Home Builder Hub exists to document jobsite conversations, so we take holding your data seriously. This page explains, in plain language, what we collect and what we do with it.
What we collect
- Account basics: your name, email address, and authentication details when you sign in.
- Captured evidence: the calls, voice memos, walkthrough videos, notes, and files you choose to upload so AI-prepared drafts can cite their sources.
- Project records: projects, tasks, change orders, approvals, and the audit trail of who decided what and when.
- Recipient details: email addresses, trade labels, and secure-link activity when you choose to send a homeowner review or trade acknowledgment request.
- Product analytics: how the app is used (screens visited, features used) so we can improve it. We use PostHog for this.
How we use it
- To run the product: storing captured evidence, preparing draft scope and tasks, creating links when you request them, recording responses, and keeping the audit trail.
- AI processing: captured content may be sent to third-party transcription and AI providers to produce the feature you requested. We do not use project content to train our own models; provider handling is governed by the terms and configuration in effect for the beta. Contact us for the current provider list.
- To improve Home Builder Hub: usage and error data help us understand reliability and product behavior. We do not claim that every analytics event is anonymous or de-identified.
- We do not sell project data. We share it only with service providers needed to operate the beta, authorized operators, and recipients you or your team deliberately give access to.
The demo and sample data
- The interactive demo and its scenarios use fictional sample data. Exploring the demo requires no account and does not create a live project or send messages, but our hosting and analytics services may receive standard technical and usage data.
Storage, security, and beta limits
- Data is stored with hosted cloud providers and protected in transit. We use authentication, access gating, and record-scoped recipient links, but the private beta has not completed an independent security certification or enterprise control audit.
- Secure approval and acknowledgment URLs grant access to a specific record. Treat them as private bearer links; a recipient should not forward them.
Who can see a home
- A builder owns each home and everything recorded on it. The builder can invite a homeowner or a trade partner by email; that person signs in with the same email and sees only the homes they were invited to. Homeowners see the changes sent to them for a decision, the confirmed schedule, and a customer-safe history. Trade partners see the work directives that affect them. Neither sees the builder's private review queue, cost notes, or AI tools. The builder can remove anyone at any time; access ends on their next request.
Keeping, exporting, and deleting your data
- Archiving a home keeps its full record readable to the builder and hides it from homeowners and trades. Only an archived home can be deleted. Scheduling a deletion starts a 30-day window during which nothing is removed and the builder can cancel from the home's settings. After 30 days, the home's photos, recordings, transcripts, decisions, messages, schedule, invitations and member list are permanently deleted from our database and file storage. Backups roll off on their own schedule and are not restored to recover deleted homes.
- A builder can export any home they own from its settings. The export is a JSON file containing the home's record, members, changes and their decisions, evidence text and transcripts, schedule and history, with links to any photos or recordings that stay valid for 7 days. Exports are available to the builder who requested them for 7 days, then expire.
- A builder can delete their account from the More screen. This archives and schedules deletion of every home they own, with the same 30-day cancellation window. After the window, those homes are removed as described above, and then the account, its sign-in methods and sessions, and its beta access are removed. A minimal audit record (the account email, when deletion was requested, and when it completed) is retained so we can show the request was honored.
- Homeowner and trade participants do not own the home's record; the builder does. A participant who wants their own account removed can email us and we will verify the request and remove the sign-in identity; decisions they signed remain part of the builder's record.
Your choices
- You can ask to access or correct account data by emailing us; export and deletion of homes and builder accounts are self-service as described above. We will verify identity for anything that requires our help.
Changes to this policy
- We'll post updates here and note the new effective date. We will provide additional notice when required by law or an applicable beta agreement.
Questions?
Email support@homebuilderhub.app or use the contact page.