Blueprint

Privacy by Design

Private WorkspaceBlueprint

Policy Card

Privacy
Policy

How we handle information with respect and transparency.

Blueprint privacy archive board
Effective March 23, 2026Archive reference

What we collect

What we collect

We collect the information you submit through forms, account creation, checkout, support requests, and capture-related workflows. Depending on the product area, that can include contact details, account information, company information, payment metadata from our payment processor, uploaded files, and technical logs tied to site packages or hosted sessions.

Capture and site data

Capture and site data

Blueprint may process walkthrough media, timestamps, poses, depth, device metadata, and site-level rights or privacy metadata when those records are part of a capture bundle or world-model package. That data is part of the product record and may be used to package, deliver, operate, refresh, or audit a listing or hosted session.

Sharing

Sharing

We do not sell personal data. We may share information with service providers who help us host the product, process payments, deliver analytics, or support customer communication. We may also share information when required by law or when needed to protect rights, privacy, security, or the integrity of the service.

Your choices

Your choices

Depending on your location, you may have rights to access, correct, delete, or restrict certain personal data. You can also opt out of non-essential marketing messages at any time.

Rights, privacy, and retention

Blueprint keeps rights and privacy metadata attached to the product record because those limits matter after capture, not just during intake. We retain information for as long as needed to operate the service, meet legal obligations, enforce product terms, and manage package or hosted-session records.

Contact

Questions or privacy requests?

privacy@tryblueprint.io

Capture privacy annex

Raw walkthrough mediaUsed to package, review, redact, and audit exact-site outputs. Buyer visibility depends on listing rights and privacy state.
Faces, screens, and paperworkExpected to be avoided or redacted where practical before buyer-facing proof is presented.
Location and route metadataUsed to keep proof tied to the exact site, capture window, allowed route, and restricted-zone boundaries.
RetentionKept only as needed for service operation, legal obligations, product records, hosted sessions, audits, and agreed refresh paths.
Buyer sharingShared according to the listing, order form, rights sheet, hosted-review scope, or other written agreement.

Robot teams

Buyer workspaces may include site requests, robot profiles, hosted-session notes, exports, and account activity.

Site operators

Operator records may include authority, access windows, restricted zones, commercialization preferences, and privacy instructions.

Capturers

Capturer records may include application details, city access, device metadata, submitted routes, review status, and payout eligibility state.