We collect only what we need.

BuildBlox is a product of Green Metrics Technology Corp., incorporated in British Columbia, Canada. GMT is responsible for the personal information described here — its “controller” under the EU and UK GDPR — and our Privacy Officer is accountable for our compliance with Canada’s Personal Information Protection and Electronic Documents Act (PIPEDA), British Columbia’s and Alberta’s Personal Information Protection Acts (PIPA), and the GDPR where it applies.

If you use BuildBlox through an organisation that has a separate written agreement with us, that agreement may also govern how we handle the information in its projects. Where it does, it takes precedence over this policy for that information.

On the Site

• Demo and partner requests. The forms on our Contact and Partners pages send us your name and email (required), and optionally your role, company, city and notes. Submissions are emailed to our team and stored in the Site’s back office. If a submission can’t reach us, the form opens your own email app instead. The “Request a demo” buttons elsewhere on the Site open your email app directly; we receive only what you choose to send.
• Intake form. Your name and email (required), and optionally your phone number, property address, city, the housing types you’re interested in, and notes. Submissions are emailed to our team and stored in the Site’s back office and in the intake inbox of our internal project tracker.
• Visit statistics. To see which pages are useful and how people find us, the Site records each page you view: the page, the website that linked you to it (its domain only), any campaign tag in the link, whether you’re on a desktop, tablet or phone, your country where our hosting provider supplies it, how long the page stayed open, and which demo, contact, email, phone or outbound links you click. To count visitors without identifying them, we store a one-way code made from your IP address and browser details that changes every day. We never store your IP address or browser details themselves, we don’t link your visits from one day to the next, and nothing is placed on your device. Our own staff pages aren’t counted, and known automated traffic is discarded.
• Technical data. Like any website, our hosting provider records each request — your IP address, the time, the page requested and your browser type — in its logs.

On the Platform

• Your account. Your name and email address, how you sign in, the personas you choose (Builder, Owner, Consultant) and any staff role. If you sign in with a password, only a salted hash of it is stored. If you sign in with Microsoft or Google, we receive your name, email address and an account identifier from them — never your Microsoft or Google password.
• Projects and teams. What you and your teammates enter: project names and details, site addresses, legal land descriptions and map pins, the names, emails and roles of project members, and the email addresses of people invited to a project.
• Your work in the engines. Design options, building models (IFC and Revit), drawings and other documents, cost estimates, pro-formas, readiness scores, gate sign-offs (including who signed and when), comments and reports. Files can contain personal information — a name in a drawing’s title block, for example — and we handle it as part of the file.
• Business roster. Businesses added to the roster and the documents uploaded for them.
• Feedback. When you use the Feedback button: your report, the address of the page you were on (with query strings, fragments and any invitation, reset or share token removed), your browser, the app version, and your name, email and roles.
• Security and technical data. Sign-in events, session cookies, IP addresses, browser type and request logs, used to keep accounts and the service secure.

From other sources

• A teammate who invites you to a project gives us your name and email address.
• Microsoft or Google, if you choose to sign in with them, as described above.
• Public land records — parcels, zoning, bylaws and property assessment data — which describe land rather than people, but may relate to you if you own a property shown in them.

We use personal information only for the purposes below. Where the GDPR applies, each has the legal basis shown. Under Canadian law we rely on your consent, which is implied when you give us information for an obvious purpose (such as submitting a form or joining a project) and express where the purpose is less obvious.

Where we rely on legitimate interests, they are answering the people who contact us, keeping accounts and the service safe from misuse, fixing the problems people report, and understanding in aggregate how the Site is used. Each uses only the information it needs, in ways you would expect, and we’ve weighed it against your interests. You can object at any time (see Your rights).

Giving us information is voluntary, but without an email address we can’t answer an enquiry or create an account, and without project information the engines have nothing to work with.

We don’t use your information for advertising, we don’t build profiles of you, and we make no decision with legal or similarly significant effects about you by automated means alone. Readiness scores, code checks, estimates and AI briefs are tools for the people on your project, who decide what to do with them.

The Pre-Construction Engine can draft discipline briefs and answer questions through its LisaAI assistant. When someone on a project uses these features, the question and that project’s information are sent to Anthropic’s Claude service to produce the response. That can include the project’s owner, site, programme and geometry, model summaries, code and bylaw assessments, its pro-forma and financial assumptions, existing briefs, and the names of the people and firms responsible for each discipline and their sign-offs. Anthropic acts as our service provider and, under its commercial terms, does not use this content to train its models.

These features run only when a person on the project uses them. We do not use your projects, files or prompts to train AI models, ours or anyone else’s. AI output can be wrong: treat it as a draft for a qualified professional to review.

Our own cookies and browser storage are only what the Site and Platform need to work. We use no analytics, advertising or cross-site tracking cookies, and the Site loads nothing from third parties until you ask it to, which is why it doesn’t show a cookie banner. Our visit statistics use no cookies or browser storage at all. Third-party content is described below the table.

Third-party content

• Maps on the Site. The live Lot Locator maps (from Felt) don’t load until you press the button on them. Once loaded, Felt receives your IP address and may set its own cookies. Each map loads only for the one you press, and nothing is remembered. The product demo film is hosted by us, not a third party.
• Maps on the Platform. Your browser fetches map images directly from mapping providers (Esri ArcGIS, CARTO, OpenStreetMap and OpenTopoMap), so they receive your IP address and the area of the map on screen. Addresses you search for in MapBlox may be sent to OpenStreetMap’s Nominatim service to find them. The Pre-Construction Engine’s site stage has a Felt map that doesn’t load until you press the button on it; once loaded, Felt receives your IP address and may set its own cookies.
• Site look-ups on the Platform. To find parcel, zoning and site information, our servers send a project’s address or coordinates to public geodata services: the Government of British Columbia’s Geocoder and OpenMaps, the Overpass API for OpenStreetMap data, and municipal open-data services such as the City of Abbotsford’s. They receive the location, not who you are.

We never sell or rent personal information, and we never share it for anyone’s advertising. We share it only as follows.

Service providers

These companies process information on our behalf, under contracts that limit them to providing their service to us and require them to protect it.

Others

• Your project team. Members of a project see its content and each other’s names, emails and roles.
• Data exports. People we authorise to use the Project Tracker’s data API can export the project data it holds, for example into a spreadsheet.
• BuildBlox staff. Authorised GMT staff can open every project in order to operate, support and secure the Platform, and only for those purposes. Named GMT staff, each with their own sign-in, can see the enquiries and visit statistics held in the Site’s back office.
• Advisers. Our lawyers, accountants and auditors, under a duty of confidentiality.
• When the law requires it. To comply with a law, court order or lawful request, or to protect the safety or rights of people or of GMT.
• Business changes. If GMT or BuildBlox is merged, acquired or sold, to the new owner, who must keep honouring this policy. We’ll tell you before that happens.

GMT is based in Canada. The Site and Platform are hosted in the United States, and most of the service providers above are there too, so your information is stored and processed in the United States. While it is there it is subject to US law and may be accessed by US courts and authorities. Some map and site look-ups also go to services in Canada, the United Kingdom and the European Union (see the table above).

The European Commission recognises Canada as providing adequate protection for personal information handled by businesses. For information we transfer from Canada to the United States or elsewhere, we rely on the EU–US Data Privacy Framework where the provider is certified, or on the European Commission’s standard contractual clauses (with the UK addendum for UK information).

Deleted information can remain in backups until they’re overwritten on their normal cycle.

• All traffic to the Site and Platform is encrypted in transit (HTTPS).
• Access to projects is limited to their members, and staff access is limited to operating the service.
• Passwords are stored only as salted hashes, and service credentials stay on our servers.
• The Site’s back office is open only to named GMT staff, with per-person sign-in and limits on repeated failed attempts.
• Feedback reports have query strings and invitation, reset and share tokens removed before they leave the Platform.

No system is perfectly secure. If a breach of security creates a real risk of significant harm to you, we will notify you and the regulators as PIPEDA, PIPA and the GDPR require.

Depending on where you live, you have some or all of these rights over your personal information:

• Access — ask what we hold about you and get a copy.
• Correction — ask us to fix anything inaccurate or incomplete.
• Deletion — ask us to delete it, including closing your account.
• Portability — get information you gave us in a machine-readable format.
• Restriction and objection — ask us to limit or stop a use, including one based on our legitimate interests.
• Withdraw consent — where we rely on consent, withdraw it at any time. This doesn’t affect what we did before.
• Complain — to the Office of the Privacy Commissioner of Canada, the Information and Privacy Commissioner for British Columbia, the Information and Privacy Commissioner of Alberta, or, in the EU or UK, your local data protection authority. We’d appreciate the chance to put things right first.

To use any of these rights, email buildblox@greenmetrics.ca. We may need to confirm your identity first. We respond within 30 days and don’t charge for requests unless they are manifestly unfounded or excessive. For information in a project run by an organisation under its own agreement with us, we may refer your request to that organisation.

Choices you can make any time

• Sign in with an email and password instead of Microsoft or Google.
• Leave the maps on the Site unloaded.
• Not use the AI-assisted features.
• Leave a project, or ask us to close your account.

We don’t add you to a newsletter or mailing list, and we don’t send commercial electronic messages without your consent, consistent with Canada’s Anti-Spam Legislation (CASL). Invitations, sign-in and password emails and project reminders are service messages that the Platform needs to work. If we ever send you marketing with your consent, every message will include a way to unsubscribe.

BuildBlox is for businesses and adults working in housing delivery. The Site isn’t directed at anyone under 16, and you must be 18 or older to use the Platform. We don’t knowingly collect information from children; if you believe we have, contact us and we’ll delete it.

We’ll update the date at the top when this policy changes. If we make a material change, we’ll say so on the Site and tell Platform users by email or in the Platform before it takes effect. We won’t use information collected under an earlier version of this policy in a way that version didn’t disclose without your consent.

For privacy requests or questions, contact our Privacy Officer at buildblox@greenmetrics.ca, or write to: Privacy Officer, Green Metrics Technology Corp., 2028 W 11th Ave, Vancouver, BC V6J 2C9, Canada.

See also our Terms of Service.