BUILDDA, INC.
Privacy Policy
This policy explains how Buildda uses personal information in its internal operator app and the systems used to manage residential construction work. The app is for Buildda's team; it is not a homeowner account or a public social network.
Effective July 29, 2026
What we collect
We collect information that a homeowner, prospect, representative, team member, or service provider gives us, information created while we work on a project, and some information from public property records.
- Contact and property information: names, property and mailing addresses, phone numbers, email addresses, lead source, and publicly available property-owner information.
- Communications: the content, participants, dates, delivery status, and attachments of SMS, iMessage, WhatsApp, and email conversations. The business mailbox at info@buildda.com is copied into the CRM, including messages that are not yet matched to a project.
- Project records: project scope, appointments, notes, photographs, videos, audio, documents, estimates, contracts, change orders, signatures, and signing status.
- Photo and file details: file name, type, size, and dimensions. An original photo can also contain metadata added by the camera, including the capture date, device details, and GPS location. Buildda keeps the original file as part of the project record.
- Payment and transaction information: invoice and payment amounts, balances, payment descriptions, and Buildda bank transaction details used to match a payment or expense to a project. The app does not ask homeowners to connect their bank accounts.
- App and security information: team member name, role, phone number, login and session records, app actions, and rate-limit records. Login codes are stored only as a hash, and client IP addresses used for rate limiting are also stored only in hashed form.
- Email engagement: for Google review-request emails, delivery, open, link-click, bounce, and spam-complaint events. Open measurements are not always reliable because mail apps can block or pre-load tracking pixels.
Why we use it
Buildda uses this information to:
- respond to inquiries and keep a complete conversation history;
- prepare, schedule, estimate, document, and carry out construction work;
- send messages, estimates, contracts, change orders, and project updates;
- track signatures, payments, costs, appointments, and follow-up work;
- give authorized team members the project information they need;
- protect the app, control access, investigate errors, and keep audit records;
- analyze job messages and files and prepare internal summaries or draft replies for a team member to review; and
- preserve records that may be needed to support warranty, licensing, accounting, insurance, or legal matters.
Who handles the information
In the app and code covered by this policy review, Buildda uses the following service providers or has the conditional provider path described below. The information each provider receives depends on the feature and configuration being used.
Supabase
stores Buildda's CRM records and private project files.
Vercel
hosts the app, public pages, API routes, and server functions.
provides the Buildda business mailbox and calendar. Email content, attachments, addresses, and appointment details pass through Google.
Apple, Twilio, and Meta
carry iMessage, SMS, and WhatsApp communications. Phone numbers, message content, delivery information, and media pass through the provider used for that conversation.
Resend
sends Buildda emails and returns delivery, open, click, bounce, and spam-complaint events for tracked review requests.
Slack
provides Buildda's internal team workspace, where project details, messages, files, and alerts can be shown to the team.
DocuSign
creates, sends, signs, and returns contracts, change orders, signatures, envelope status, and executed documents.
Plaid
connects Buildda's own bank accounts and provides transaction data used to reconcile project payments and expenses.
Voyage AI
turns selected internal notes and search text into a searchable index.
Melissa
receives a property address and returns public property-owner information used to check canvassing leads.
AI processing
Some features use artificial-intelligence services to draft, summarize, or check messages and documents. To provide them, we send the relevant content, such as message text or an attachment, to third-party AI service providers, including model providers and the routing services that connect us to them. These providers act on our behalf, may use the content only to provide the service to us, and are selected for commitments not to train on it or keep it longer than needed.
Separate canvassing intake service
When a roster-matched team member sends a WhatsApp canvassing report, this app forwards the raw canvassing report and the roster-matched team member name to a separate Buildda intake service. The data therefore leaves this app and this code repository.
That separate service's storage, subprocessors, retention, and deletion behavior has not been verified in this repository. This policy does not claim that service deletes data on any fixed schedule. Buildda must complete that review before this policy can describe the service's later handling of the report.
How long we keep it
Buildda keeps CRM records for operating the business and for warranty, licensing, accounting, insurance, and legal purposes. The CRM reviewed in this repository does not currently run an automated retention purge.
It also does not currently provide a legal-hold control that can place and release holds. The separate canvassing intake service's retention and deletion behavior has not been verified.
Because those mechanisms are not implemented and verified, this policy does not promise deletion after a fixed period. In particular, it does not promise the previously proposed ten-year, three-year, or one-year retention schedule.
Contact Buildda about your information
For questions about information associated with you, email info@buildda.com and include your name, the property or project involved, and how to reach you so Buildda can identify the relevant records.
That mailbox is a general contact route. The CRM reviewed in this repository does not currently provide a dedicated privacy-request workflow or an automated way to access, correct, or delete a record. This policy therefore does not promise a particular response or deletion outcome from sending an email.