Back to Building Code Assist

Privacy Policy

Last updated: October 3, 2026

Building Code Assist is an online service operated from Vancouver, British Columbia, Canada. This Policy explains how information is handled when you use the service. Our privacy contact is the Building Code Assist Privacy Officer at admin@buildingcodeassist.ca.

Information we handle

  • Account and authentication information: account identifiers and contact details managed through Clerk.
  • Questions and service content: questions, generated answers, conversation history, feedback, project names and settings, drawing filenames, uploaded drawings while they are being processed, and drawing-derived analysis and reports.
  • Billing information: plan, subscription status, usage, and transaction references. Stripe processes payment details; we do not receive or store full payment card numbers.
  • Operational information: technical events and diagnostic logs used to operate and secure the service. We also send aggregate service metrics to Grafana; these metrics do not include question text or drawing contents.

We use this information to authenticate users, provide answers and drawing reviews, save user-requested work, manage subscriptions and usage limits, respond to support requests, and maintain service security and reliability. We do not sell personal information or use it for advertising or unrelated marketing.

Questions, drawings, and AI providers

When you ask a question, its text may be sent to OpenAI to create a search embedding and to Anthropic to generate an answer. When you use drawing analysis, the drawing or drawing-derived text is sent to Anthropic for processing. If an optional reranking service is enabled, relevant search text may also be sent to Voyage AI or Cohere.

We use these services to provide Building Code Assist. We do not use your submissions to train our own AI models. These providers may process or retain submitted information under their own service terms and security or abuse-monitoring practices, which may differ from our retention periods. We do not claim that special zero-retention settings apply to these integrations.

Temporary drawing files are removed from our processing environment after analysis. When we upload a PDF to Anthropic for analysis, our system attempts to delete the provider-side file after processing. If deletion fails, the system records a warning and the provider may retain the file under its own rules. Please do not upload confidential or personal information unless you have authority to share it with us and the service providers needed to process it.

Service providers and processing locations

We use Clerk for authentication, Stripe for payments, Vercel for the frontend, Railway for the backend and database hosting, Anthropic and OpenAI for AI features, and, if enabled, Voyage AI or Cohere for search reranking. These providers process information to deliver their services to us. They may process information outside Canada, including in the United States or other countries where they or their subprocessors operate. Their own terms and privacy practices also apply to their handling of information.

Retention and deletion

Operational application logs are retained for up to 14 days in our systems. Question-and-answer records, subscription and usage records in our database are retained indefinitely while associated with an active account. Conversations and drawing analyses remain available until you delete them or request account deletion. Deleting a conversation does not remove its separate question-and-answer log entry. Payment details and invoices are handled by Stripe under its own retention practices.

Self-service account deletion is not yet available. To request deletion, email admin@buildingcodeassist.ca. We will delete account-associated information from our application systems, including account content and database records. Independent providers may retain records under their own policies, and we may retain information where required by law. Deletion of an individual conversation or analysis is available in the app where that feature is provided.

Cookies and local storage

Clerk uses essential authentication cookies to sign users in and maintain sessions. These are not advertising or analytics cookies. The app stores your theme preference in your browser’s local storage. We do not currently use Google Analytics, advertising cookies, or a separate web analytics tracker.

Security and your choices

We use access controls and service providers to protect information. No online service can guarantee absolute security. You may ask us to access, correct, or delete personal information by emailing our Privacy Officer. You may also contact us with a privacy concern or complaint at the same address.

Policy changes

We may update this Policy as the service changes. We will post the revised version with an updated date and provide notice of material changes through the service or by email where appropriate.