Privacy Policy

Version 1.1 | Effective date: June 1, 2024

Last updated: 16 August 2026

At Buildkey Pty Ltd (“Buildkey”, “Company”, “us” or “we”), we respect and protect the privacy of visitors to our website, www.buildkey.net, and the other websites under the buildkey.net domain (collectively, the “Sites”), and the users of our web and mobile applications (the “Apps”) and related services (together with the Sites and the Apps, the “Service”).

This Privacy Policy (“Policy”) explains how we collect, use, disclose and protect visitors’ and users’ (“Users”) personal data and information as part of the Service.

Any discussion of your use of the Service in this Policy is meant to include your visits and other interactions with the Sites and Services, whether or not you are a user of the Service. Capitalized terms that are not defined in this Policy have the meaning given them in our Terms of Service.

By using the Service, you do hereby warrant and represent that

• you have read, understood, and agreed to all terms and conditions stated herein, and
• you are giving Buildkey the permission to use and store such information consistent with this Privacy Policy.

1. Information We Collect

We collect:

• Account data: your first and last name, email address, password (stored as a salted hash), workspace name, company name and chosen plan when you sign up, along with your billing email and billing country. Payment card details are collected directly by our payment provider, Stripe, and are never stored on Buildkey's servers.
• Profile data: optional details you add to your profile, such as a mobile number, postal address, city, state, postcode, country and a profile picture.
• Content you provide: your projects and their site addresses, notes, areas, uploaded files, comments, QR posters and company logos.
• Information about other people: project contact details (name, job title, phone number and email address) that you or your team record against a project, email addresses of people you invite to your workspace, and names that visitors choose to attach to comments on public project pages. If you give us personal information about someone else, you must be entitled to share it with us.
• Contact form: your name, email address and message when you use the contact form on our website, which is processed for us by Formspark.
• Usage data: an activity log of actions taken in your workspace (such as creating, editing or deleting projects, areas, files and comments) and aggregate QR code scan counts, which contain no personal identifiers.
• Cookies and similar technologies: see section 4 below.

2. How We Use Your Data

We use your information to:

• Provide and personalise Buildkey's services.
• Process subscription payments and invoices through Stripe.
• Send service emails, such as verification codes, password resets and workspace invitations, through our email provider, Postmark.
• Send our product newsletter through Beehiiv. Creating an account subscribes you to the newsletter; you can leave it at any time from your profile settings or via the unsubscribe link in any newsletter email.
• Improve features and troubleshoot issues.
• Comply with legal obligations.

3. Data Sharing & Disclosure

We do not sell your data. We share it with the service providers we rely on to run Buildkey, under their respective confidentiality and data protection terms:

• Stripe: payment and subscription processing.
• Amazon Web Services: application hosting and file storage, in the Sydney (Australia) region.
• MongoDB Atlas: our database.
• Postmark: transactional email.
• Beehiiv: our newsletter.
• Vercel: website hosting.
• Formspark: contact form processing.
• Meta: advertising measurement on our marketing site (see section 4).

We may also disclose information if required by law or to protect our rights, and in a merger or acquisition (with notice to you).

Separately, if you or your workspace set a project to public, anyone with the link can view that project, including its files, comments and any project contact details recorded on it, and can post comments on it without an account. Only share publicly what you are comfortable making public.

4. Cookies & Tracking

We use a session cookie to keep you signed in to the App, and your browser's local storage to remember preferences such as your theme and selected workspace. These are necessary for the Service to function.

Our marketing site at buildkey.net uses the Meta Pixel, which helps us measure the effectiveness of our advertising. Meta may set cookies and collect information about your visit as described in Meta's own privacy policy; you can limit this through your browser settings, Meta's ad preferences or common ad-blocking tools. Pages with embedded videos load them from YouTube in privacy-enhanced mode.

5. Data Security

We protect your data with encryption in transit, hashed passwords and access controls. However, no system is 100% secure, so please use a strong password.

6. Your Rights

You may:

• Access and correct your account and profile data in your account settings.
• Opt out of marketing emails in your profile settings or via the unsubscribe link in any newsletter email.
• Request deletion of your account and personal data, or a copy of the data we hold about you, by emailing support@buildkey.net. We will action verified requests within a reasonable time, subject to records we are required to keep by law (such as billing records).

Contact us at support@buildkey.net for any privacy request or question. If you are not satisfied with our response, you may complain to your local privacy regulator, such as the Office of the Australian Information Commissioner.

7. International Transfers

The Service is hosted in Australia. Some of the service providers listed above process data in other countries, including the United States and the European Union; where they do, we rely on safeguards such as GDPR Standard Contractual Clauses and the providers' own data protection commitments.

8. Changes to This Policy

We will notify you of material changes via email or in-app alerts. Continued use of the Service after changes take effect constitutes acceptance.