Legal

Privacy Policy

Blueprint Builds mobile app · Last updated 23 September 2026

Blueprint Builds is a private, invitation-only construction delivery app used by authorised project teams and their clients. It is not available for public sign-up. This policy describes what the app collects and how that information is used.

Information we collect

• Work email address and password, used only to sign you in (processed by our database provider, Supabase, acting on our behalf). Sign-in tokens are stored in your device's secure keychain.
• Project evidence notes you type while using the app, linked to your account and the relevant project.
• Confirmed project-history relationships created for authorised build-team use. A Thread can store source references, relationship type, the acting account, timestamps and verification state so Replay can reconstruct confirmed history from its source records. Internal Thread/Replay is not exposed through Client View Preview.
• Photos and voice recordings you choose to attach to an evidence note. These are stored in private, access-controlled storage, linked to your account and project, and are only viewable by authorised members of your workspace. The camera, microphone and photo library are accessed only when you actively choose to capture or attach something.
• Optional site location when you turn on location tagging for field evidence. Location tagging is off by default. If enabled, the app requests when-in-use location permission and takes one location reading when the evidence is saved. The coordinates are stored with that project evidence record. If permission is declined, location services are unavailable, or a reading cannot be obtained promptly, the evidence still saves without a location.
• A device push-notification token, stored only if you allow notifications, used solely to tell you about project decisions that involve you. You can withdraw this at any time in your device's notification settings.
• A minimal authenticated release receipt when a signed-in native app first reports a release. Your user and active workspace are derived server-side; the receipt stores the platform, app version, runtime version, exact update identifier (or embedded state) and first-seen time. It does not store project IDs, project activity, screen history, notes, media, location, advertising identifiers, device serials, launch counts or a last-seen history.
• Standard security, performance and technical logs (e.g. request time, route, duration, error status) generated by our hosting and database providers. These do not include your note content or password.

What we do not collect

• We do not continuously track your location or collect it in the background. We do not collect contacts or payment information through the app, and we do not access your camera, microphone or photos in the background.
• We do not use advertising or analytics tracking, and we do not sell or share your information with third parties for their own marketing.

How information is used

• To authenticate you and show you the correct projects and role-based views.
• To verify that a signed-in account reached a specific native release and troubleshoot rollout problems without building a behavioural analytics history.
• To keep an accurate, auditable record of site evidence for the project it was recorded against.
• When you enable location tagging, to record where a specific item of field evidence was captured or saved as part of that project record, and to compare that same foreground reading against authorised project site pins so Site Sense can warn if the wrong project is selected before the record is sealed.
• When the optional workspace weather service is configured, a coarsened version of that foreground location and the evidence capture time may be sent server-side to the configured commercial weather provider to attach nearest-hour weather context. This is project-record enrichment, not background tracking or advertising, and provider failure never prevents the evidence record from being saved.

Retention and deletion

• Project records, including evidence, attached photos, voice recordings, any location or server-attested weather context attached to evidence, decisions and confirmed Thread relationships, are retained for the life of the project and the applicable project or workspace record-keeping period.
• Release receipts are retained for 180 days and automatically purged after that period. They are also tied to the relevant user and workspace lifecycle.
• You can initiate permanent account deletion inside Blueprint Builds from Account / More → Support & legal. The authenticated request is recorded immediately and completed within 30 days. We remove your login and personal account data we are not required to retain and confirm completion to your registered email. Project construction records may be retained independently where required. See also Support — delete your account.

This website

The public marketing and legal pages are static. The optional Builder Workspace and Plan Desk use the same private Blueprint Builds backend as the app. A normal web sign-in keeps its access token in session storage for the current tab. When a drawing is opened from the native app, Blueprint instead exchanges a one-use, 90-second handoff code for a short-lived session scoped to that exact project and plan; the app access and refresh tokens are never placed in the handoff URL. The site sets no advertising or analytics cookies and loads no third-party trackers or external fonts. Private plan media is delivered through short-lived signed links after access is verified.

Contact