Privacy
We collect only what the workflow needs.
Address searches and Property Briefs
GTA address searches can query public address services operated by the City of Toronto, Region of Peel, Region of Durham and Town of Oakville. For current GTA cities where exact civic-address validation is not yet connected, BuildRules can use the municipality written in the search to route you to that city’s published guidance and labels that result accordingly. Toronto Property Briefs use the selected City address identifier and project type to retrieve available public mapped property information.
When you continue from a Property Brief to the free preparation report, the address and project answers can be kept temporarily in this tab’s session storage for up to 30 minutes, then removed after the handoff. They are not added to analytics or the report link. BuildRules processes this information for the request; it does not save your search or Property Brief in a report database or create an account. Hosting and municipal service providers may keep operational request logs under their own policies. A property link and its address identifier can also remain in your browser history.
Ask BuildRules AI
Questions entered into Ask BuildRules are sent to Cloudflare AI Search to match them with relevant published BuildRules guidance. BuildRules does not save the question text in its content database or include it in custom analytics events. Cloudflare may retain operational request logs under its own policies.
Please leave street addresses, contact details and other personal information out of AI guide questions. Use the separate address-check workflow when you need property-specific guidance.
Sharing a property link
A Property Brief URL identifies a public property and project. Anyone with that URL can open the current brief without signing in, and they can pass it to someone else. Share it only when you are comfortable making the property and planned project visible to the recipient.
Property Brief pages ask search engines not to index them and are excluded from the sitemap. These instructions do not restrict access or make a link private. A shared link is not a saved report: it retrieves current information when opened, so the findings, source dates and unresolved checks can change.
Requests for professional help
When you submit a request for professional help, BuildRules may collect the contact information you provide, the jurisdiction, project type and page that generated the request. This information is used to respond to your request, operate the service and, when matching is requested, connect the request with a relevant service provider.
BuildRules Directory
Company submissions can include public profile information such as the company name, description, website, public contact details, logo, service areas and project specialties. Information intended for the public profile can become publicly accessible after moderation. The submitter’s private contact name and contact email are stored separately for moderation and directory operations.
Company managers can sign in with a password and, when enabled, supported third-party identity providers such as Google or Microsoft. Before an existing profile becomes company-managed, BuildRules can send a time-limited confirmation link to an email address whose domain matches the company website. BuildRules stores the account-to-company relationship, ownership claim state, confirmation status, profile change requests and moderation states needed to operate the workspace. Authentication credentials are handled by the authentication provider; BuildRules does not store readable passwords. Owner-submitted profile changes can be held for staff review before replacing the public version.
When a visitor sends a project request from a company profile, they can separately choose to attach their property address and a reference to the current Property Brief. This attachment stays in the selected company’s private request record and is not included in directory analytics or the notification email summary. The linked brief remains accessible to anyone with its URL and retrieves current guidance rather than a saved assessment. BuildRules stores the contact and project information entered in the form and makes that request available to the selected company so it can respond. Companies can record an operational lead status such as contacted, qualified or closed.
When you ask BuildRules to match a project with professionals, BuildRules stores the project, location, timing, budget range and contact details you submit. The project can be shown to companies whose published service areas and specialties match the request. Your contact details are disclosed to a matched company when that company chooses to respond to an eligible opportunity.
Company owners can create one-time customer review invitations. BuildRules stores the invited email privately to validate the review link. Published reviews can show the reviewer name, rating, review text, project type and city, but not the reviewer email. Reviews are moderated before publication.
Directory correction reports can include an optional reporter email and the details supplied about an inaccurate, outdated, abusive or impersonating listing. Reports are available to authorized staff, not displayed publicly.
Free Project Brief and newsletter preferences
When you request a free Project Brief, BuildRules stores the email address, municipality, project type, property address, project scope and generated report securely in Supabase to fulfill your request. The brief appears in your browser and a requested copy is sent through Resend when delivery is available. Report requests are visible only to authorized BuildRules staff; they are not automatically shared with contractors.
An optional, unchecked newsletter box offers BuildRules project-planning tips and permit updates. Declining does not affect your free report. We record the text version and timestamp of express consent only if you opt in. If you opt in, we email a confirmation link. Only after that link is confirmed will we synchronize your address to the dedicated Resend newsletter topic. We do not add unverified or non-consenting report recipients to marketing audiences. The confirmation email includes a link to withdraw consent. Unsubscribing revokes earlier confirmation links and updates the dedicated topic without changing contractor newsletter preferences. Marketing messages must also include Resend’s unsubscribe option. We keep delivery receipts and use temporary keyed hashes of network identifiers to limit abuse.
You may ask for access, correction, deletion or marketing-consent withdrawal by emailing support@buildrules.ca. A report request is not permission to send promotional emails.
Directory payments and prior paid briefs
Paid directory memberships are processed by Stripe, which handles payment details. BuildRules may retain subscription identifiers and statuses. Project Brief purchases made before the move to free reports retain their original payment records, intake, private order links and refund or delivery rights. We do not receive full card numbers.
What we do not need
Do not submit permit drawings, government identification, financial information or other sensitive personal information through the lead form.
Website analytics
BuildRules uses Google Analytics to understand visits and actions such as starting a property check, opening another guide, selecting a project, preparing a checklist, estimating a fee and sharing a link.
Our custom events use fixed project identifiers, action names and completion counts; they exclude names, emails, property addresses, official address identifiers, coordinates, search text and quantities entered into our tools.
Advertising and third-party technologies
BuildRules plans to use Google AdSense to support its public editorial guides. When advertising is enabled, Google and participating advertising partners may place or read browser cookies and use web beacons, IP addresses, device or browser identifiers, and information about visits to serve, measure and help prevent abuse of ads. Depending on your settings and consent choices, these technologies may be used for personalized advertising.
Learn how Google uses information from partner websites at Google's partner-site privacy information. You can manage Google advertising personalization at My Ad Center, and manage cookie permissions through your browser. Where consent is required, advertising technology must respect the consent choices presented to you.
Advertising is separate from permit research and does not determine the regulatory guidance shown on BuildRules.
Contact and mailing address
BuildRules can be contacted about privacy matters at support@buildrules.ca. Postal correspondence may be sent to BuildRules, Anik Beauchemin, 2967 Dundas St. W. #379D, Toronto, ON M6P 1Z2, Canada. This is a mailing address, not a walk-in office.
Retention and requests
BuildRules keeps lead, directory, billing and moderation records only as long as reasonably needed to operate the service, maintain account and transaction history, address abuse or disputes, and meet applicable legal obligations. Privacy or account-support requests can be sent to support@buildrules.ca.