Skip to main content
BC Coast Hikerswhere salt meets sky

Privacy Policy

BC Coast Hikers Privacy Policy

Last updated:

BC Coast Hikers (“we,” “us,” “our”) is based in North Vancouver, British Columbia, and operates bccoasthikers.org, including our public website and member area (“platform”).

Information We Collect

Public site visitors: we collect no personal information from browsing our public pages.

Members: when you sign in with Google, we receive the name and email address on your Google account. We do not use that address to contact you. We then collect:

We do not collect medical, health, or fitness information. If that changes, we will update this policy first.

How We Use Your Information

A leader hosting or co-hosting an outing you are on can see your emergency information — your legal name, emergency photo, and emergency contact details. They may need to act without delay and without a phone signal. No other member sees them, and administrators see them only to manage waivers and emergency information.

Where Your Information Is Held

We use service providers to run the platform, and some hold your information outside Canada:

While your information is outside Canada it may be accessible to the courts and to law enforcement there. Our other service providers are configured not to receive personal information.

Information Sharing

We do not sell your personal information. We share it only:

Your Rights

Under the British Columbia Personal Information Protection Act (PIPA) and the Canada Personal Information Protection and Electronic Documents Act (PIPEDA), you have the right to access, correct, or request deletion of your personal information, and to ask how it is used.

Signed waivers are the exception. A waiver is a legal record. We keep signed waivers after a membership ends, and deleting your information does not remove them.

Contact

To exercise your rights, ask a question, or report a privacy concern, please contact us.

Changes to This Policy

BC Coast Hikers and the platform are under active development, and this policy may change. The date at the top always reflects the current version.