Privacy policy

Bedrock is operated by 1238723 B.C. Ltd. ("Bedrock", "we", "us"), a company based in British Columbia, Canada. This policy covers getbedrock.ca, the Bedrock console, the Bedrock deck viewer, and decks embedded on other websites.

We play two different roles, and which one applies changes who you should talk to:

• We are responsible (a "controller" under the GDPR) for account information, demo requests, correspondence and error reports.
• We act on a customer's behalf (a "processor" or "service provider") for the content a customer uploads and for the engagement analytics collected when people view that customer's decks. The customer, usually a mining company, decides what is published and to whom, and is responsible for that information. We use it only to provide Bedrock to them.

We have designated a Privacy Officer who is accountable for our compliance with this policy and with applicable privacy law. Contact details are in section 12.

If you have a Bedrock account

• Your email address. We sign you in by emailing a one-time link. There are no passwords.
• Your organization and role (owner, admin, member or client), and when you joined.
• Invitations: the invitee's email address, the role offered, who sent it, and when it expires or was accepted.
• Sign-in records kept by our authentication provider: when you signed in and the session tokens that keep you signed in.
• Authorship: which account created a project, dataset, deck or share link.

Content customers upload

Project details (name, commodity, location, stage), logos, slide text, camera positions and map annotations, and geological data files: drill collars, surveys and assays, geochemistry, geophysics grids, topography, surfaces and claim boundaries. We store the original files you upload so they can be audited, along with the display files derived from them.

Block models are the exception. The console reads a block model inside your browser and uploads only the derived display files. The source file never reaches us.

This content is mostly technical rather than personal. It can include personal information, such as a geologist's name in a data file, and we protect it the same way either way.

Error reports

If a deck fails to load, the viewer sends a short report so we can fix it: the error message and where it happened, your browser's user-agent string, screen size and pixel density, whether 3D graphics are available, whether you were online, approximate device memory, the page address without its query string, and the viewer build. No IP address or identifier is stored with it, and it is sent only when something breaks.

Demo requests and correspondence

The demo form on our home page composes an email in your own mail program. Nothing is sent to us unless you send that email. If you do, we receive what you wrote (typically your name, email, company and project description) and keep it in our email inbox.

Collected by our hosting providers

Like any website, the servers that deliver Bedrock see your IP address, browser user-agent, the address requested and the time. Our hosting and database providers process this in their own logs for security and to keep the service running, for a limited period set by them. We do not combine these logs with deck analytics or use them to identify viewers.

When you open a deck through a share link or on a company's website, the viewer reports how the deck was used to the company that published it. It is built to describe the visit, not the person.

Where we issue a share link to one organisation — for example a link sent with an introduction — visits through that link are attributed to that organisation, so the sender can see whether the deck was opened and how much of it was read. What is recorded is still only what the table below lists: no name, no email, no IP address.

Email we send. A message we send you carries a small image hosted on our servers. When your mail program displays it we learn that the message was displayed, when, and which mail client or proxy fetched it. We do not learn your IP address or your location. Many mail systems fetch that image automatically — on delivery, or for every message regardless of whether it is read — so we treat the signal as weak and it is not used to make any decision about you. Turning off remote images in your mail program, or sending Global Privacy Control or Do Not Track, means nothing is recorded.

When a deck asks who you are

A company can choose to put a short form in front of its deck. When it does, you are asked for your name and email address, and the deck says so before you open it. You can decline: every gated deck carries a continue without link, and the deck opens either way.

What you enter goes to the company that published the deck, not to us — we hold it on their behalf so they can see who asked to look and follow up. They can export it and delete it. We keep it for 24 months, and we do not use it for our own marketing or pass it to anyone else. If you want your details removed, ask the company that sent you the deck, or email us and we will pass it on.

Opting out. If your browser sends Global Privacy Control or Do Not Track, the viewer sends no analytics, and our servers discard any that arrive. The deck works exactly the same.

Map services. To draw terrain and imagery, and to load the software that renders it, your browser requests files directly from Esri, OpenStreetMap and the jsDelivr content network. As with any web request, they receive your IP address. We send them no information about you or the deck.

Where the GDPR or UK GDPR applies, the legal basis for each use is shown.

We use personal information only for these purposes, or for a purpose you consent to. We send business-to-business email to people whose work address is published for that purpose, and we stop on request — tell us and you will not hear from us again. We do not make automated decisions that have legal or similarly significant effects on anyone, and we do not build profiles of individual viewers. Engagement with a deck is attributed to the organisation a share link was issued to. Email we send carries a small image that tells us the message was displayed; because that message was addressed to one person, that single signal is attributable to them. We record the time and the mail client or proxy that fetched it — never your IP address, your location, or anything you do afterwards.

Bedrock sets no cookies, and uses no advertising or third-party analytics scripts. We use your browser's own storage only for things the service needs to work:

Clearing your browser's site data removes all of it.

We use these service providers. Each receives only what its job needs and is bound by contract to protect it and use it only on our instructions.

We may also disclose information:

• Within your organization. Members see the organization's content; owners and admins also see members' and invitees' email addresses.
• To anyone holding a share link. A deck opened through a live link shows what its publisher chose to include.
• When the law requires it, such as a valid court order, or to protect the rights, property or safety of people or of Bedrock.
• In a business transfer, such as a merger or sale, to a successor bound by this policy. We will tell account holders before their information falls under a different policy.

Our database and file storage are in Canada (Supabase, Canada Central region). Some providers in section 7 process information in the United States and elsewhere, where it may be accessible to courts and authorities under local law.

Where information about people in the European Economic Area, the United Kingdom or Switzerland is transferred to a country without an adequacy decision, we rely on the European Commission's Standard Contractual Clauses (and the UK Addendum) in our providers' data processing terms. Canada has an adequacy decision from the European Commission. For Quebec residents, we assess whether information transferred outside Quebec receives adequate protection before transferring it.

We may keep information longer only where the law requires it, or while needed to resolve a dispute, and only for that purpose.

• Organizations are walled off in the database with row-level security, not only in the app. Tests check that one organization cannot read another's data.
• Files are private. A deck receives signed links that expire within an hour, issued only after its share link is checked.
• Share links carry 192 bits of randomness, and can have a passcode and an expiry date. Revoking a link takes effect immediately.
• No passwords to steal or reuse: sign-in is by one-time email link.
• Encrypted in transit (HTTPS) and at rest by our providers.
• Least privilege. The client role can edit slides but cannot delete data or files. Full database access is limited to a few server functions and our operators.

No system is perfectly secure. If a breach of security safeguards creates a real risk of significant harm, we will notify affected people and the relevant regulators, such as the Office of the Privacy Commissioner of Canada and, where the GDPR applies, the supervisory authority within 72 hours, as the law requires. We keep a record of every such breach.

Depending on where you live, you have the right to:

• Access the personal information we hold about you, and learn how it is used and who it has been disclosed to
• Correct it if it is inaccurate or incomplete
• Delete it, or have it de-indexed
• Receive a copy in a portable, structured format
• Object to or restrict how we use it
• Withdraw consent where we rely on it, without affecting past use
• Complain to a privacy regulator

To use any of these rights, email hello@getbedrock.ca. We will confirm the request comes from the right person, usually by replying to the email address on the account, and respond within 30 days. It is free.

• Deleting an account removes your sign-in and memberships. If you are the only owner of an organization that has other members, we will ask you to hand over ownership or close the organization first.
• Deck viewers: we cannot tell who you are, so we usually cannot find your records. Turning on Global Privacy Control stops collection.
• Information in a customer's deck: the company that published it decides about it. Contact them; we will help them respond.

United States residents

We do not sell personal information, "share" it for cross-context behavioural advertising, or process sensitive personal information. We treat Global Privacy Control as a valid opt-out. We will not discriminate against you for using your rights, and you may use an authorized agent to make a request.

Regulators

You can complain to the Office of the Privacy Commissioner of Canada, the Information and Privacy Commissioner for British Columbia, the Commission d'accès à l'information du Québec, the UK Information Commissioner's Office, or your local data protection authority. We would appreciate the chance to fix it first.

Children

Bedrock is a business tool, not directed at anyone under 16, and we do not knowingly collect children's information. If you believe we have, contact us and we will delete it.

When we change this policy, we update the date at the top. We keep past versions. For a material change, such as a new use of personal information or a new kind of provider, we will email account holders before it takes effect.

Company

1238723 B.C. Ltd., operating as Bedrock

Responsible

Privacy Officer

Email

hello@getbedrock.ca

Location

British Columbia, Canada