Security & Privacy

Your data is yours. Here is how it is protected.

Build It Pros is built for multi-tenant use — your estimates, customers, and settings are isolated from every other operator on the platform at the database level. Below is a plain-language breakdown of the technical controls in place.

Platform Security Controls

Complete Data Isolation

Every estimate, request, and customer record is tagged to your company at the database level. Server-side access controls prevent any other operator from reading or modifying your data — it is architecturally impossible, not just a policy.

API Keys Encrypted at Rest

Third-party API keys (AI provider, mapping) are encrypted in the database using symmetric encryption. The encryption key is stored separately from the encrypted data — and can be moved entirely out of the database by defining it in the server configuration for maximum protection.

Unguessable Estimate URLs

Customer-facing estimate links use 64-character cryptographically random tokens — not sequential IDs. No customer can guess another customer’s estimate URL by incrementing a number, and there is no way to enumerate estimates on the platform.

Secure Registration Tokens

Customer registration invite links use 48-character tokens with a 7-day expiry. Each token can only be used once — once a customer registers, the token is permanently invalidated. Expired and superseded tokens are rejected automatically.

Photo Upload Protection

Customer-submitted photos are validated for actual file content — a malicious file renamed as a JPEG is rejected before it reaches the server. Uploads are rate-limited to 10 per IP per hour to prevent abuse. File size is capped at 10 MB per photo.

Private Estimate Numbers

Estimate numbers are sequential per your account only — they reveal nothing about how many estimates other operators have created, and no relationship to internal system IDs is exposed to customers or third parties.

Google Maps & Customer Addresses

Address geocoding and routing use the Google Maps API — but the integration is built to minimise what Google ever sees about your customers.

  • Geocoding is admin-triggered only. Addresses are only sent to Google when an admin opens the estimate builder and clicks Geocode — never automatically on customer form submission.
  • All calls are server-side. Your Google Maps API key is never sent to a browser. Geocoding and routing requests go from the server to Google — your customer’s IP address is never transmitted to Google.
  • Customer pages are map-free. The customer-facing estimate view and registration pages load no Google Maps resources whatsoever.
  • Street addresses are optional at the initial request stage, reducing the personal information collected before a business relationship exists.

AI Prompt Security

AI scoping uses your customer’s project description to generate a draft estimate. The platform takes precautions to prevent that content from being misused.

  • Admin-only. AI scoping is never accessible from a customer-facing page. It is an internal admin tool only, preventing public abuse of the AI feature.
  • Input isolation. Customer-supplied content is wrapped in delimiters in the AI prompt and explicitly flagged as untrusted data — the model is instructed to treat it as content to process, not as instructions to follow. This prevents prompt injection from influencing estimate generation.
  • No training use. API calls go directly to Anthropic’s API. Anthropic does not use API request content to train its models by default.

What Data Is Stored & Where

A plain summary of customer data, where it lives, and who it is ever transmitted to.

Data point Where stored Transmitted to Risk level
Customer name, email, phone Your database only Nobody Low
Customer city & state Your database only Google (admin geocoding only) Low
Customer street address Your database only Google (admin geocoding only) Low–Med
Job site lat/lng Your database only Google (map display, admin only) Low
Project description Your database only Anthropic API (AI scoping, admin-triggered) Low
Customer IP address Not stored by the platform Nobody Low

Questions about security or data handling?

If you have specific questions about how the platform handles your data, how encryption is configured, or how to request data deletion, reach out — we are happy to walk through the technical details.