Privacy Policy

This explains what GuideOps Platform, Inc. collects, why, and who else touches it. It covers GuideOps Platform and the products on it — including MeetPoint, FieldBook, SummitGuard, HeliOps, and the Operator Console. The Terms of Service sit alongside this policy.

What we collect

• Account — your name, email address, and which sign-in method you used. If you sign in with Google we receive your name, email, and profile picture from Google. We never receive your Google password. Google sign-in is separate from the Google Calendar integration below.
• Google Calendar — if you connect the integration: encrypted authorization tokens, and the identifier of the dedicated guide-ops calendar we create in your Google account. We write GuideOps events onto that calendar. We do not read your other calendars.
• Guide profile and availability — the profile a guide keeps on the platform, and when they are available to work.
• Customer and booking — clients, bookings, trip details, messages, gear lists, passes, deposits, and related records an operator keeps in MeetPoint.
• Waivers — SummitGuard signed waivers and medical intake attached to a booking.
• Operational — the observations, reports, photographs, voice recordings, zone boundaries, and notes you create in FieldBook, along with the device timestamps attached to them.
• Location — GPS coordinates attached to observations and, while a day is open, your position shared with your own operation. See below.
• Billing — handled entirely by Stripe. We store a Stripe customer reference and your subscription or commission status. We never see or store your card number.
• Technical — server logs (IP address, timestamp, which endpoint was called) kept to operate and secure the service.

Customer data stays in the operation

Each operator’s customer data stays inside that operator’s operation. Clients, bookings, waivers, medical intake, messages, and related records are visible to that operation’s members. They are not visible to other operators, not public, and not sold. A guide invited onto a trip does not take that client record to any other operation.

Guide profiles and availability

Guide profiles and availability can be seen by more than one operator — only the operators who have each invited that same guide. If operator A and operator B both invite the guide, both may see the profile and availability. An operator who has not invited the guide does not. This is not a public listing.

Sharing a guide’s profile and availability does not share either operator’s customer data. Work done for operator A stays with operator A.

Location data

Location is the most sensitive thing here, so it gets its own section. It is collected in two ways: attached to an observation, so the record says where it was made; and while a day is open, so the people in your own operation can see where their team is. It is tied to your operation and visible to that operation’s members. It is not visible to the public, it is not shared with other operations as your track, and it is never sold or used for advertising. Where another operation sees anything of yours in a snow-safety briefing, it is because your operating zones overlap on the map — the match is spatial, never by a shared identifier, and it is not a customer record.

How we use it

• To run the service: store your work, sync it between your devices, and show it to your team.
• To keep each operator’s customer data inside that operation.
• To show a guide’s profile and availability to operators who have invited that guide.
• To produce the drafts and briefings you asked for.
• To run the Google Calendar integration you connect: create a dedicated guide-ops calendar, and create, update, or delete events on it when scheduled work in GuideOps changes.
• To bill you, and to send transactional email such as invites and account notices.
• To keep the service secure and diagnose faults.

We do not sell personal information, we do not run advertising, and we do not use your content to train AI models.

Who else processes it

• Supabase (United States) — database, file storage, authentication.
• Vercel (United States) — hosting for the web applications.
• Anthropic (United States) — AI processing of FieldBook observation text and briefing content. Operator keys and identifiers are stripped before anything is sent, and Anthropic does not train on it.
• Stripe (United States) — payment processing.
• Resend (United States) — transactional email delivery.
• Google (United States) — Google Calendar, when you connect the integration. Events we create on your guide-ops calendar are stored by Google under your Google account.

If you use the service from outside the United States, your data is transferred to and stored in the United States.

Sharing outside GuideOps

Nothing leaves the platform on its own, except the Google Calendar integration you connect: we create a dedicated guide-ops calendar in your Google account and write GuideOps events onto it. An observation reaches InfoEx or any other external system only when a person in your operation explicitly approves that submission. We will disclose data if the law compels us, and we will tell you unless we are prohibited from doing so.

Retention

We keep your content while your account is active. After an account is closed we delete its content within 90 days, except where we must retain records for tax or legal reasons. Backups roll off within 30 days. Observations you have already submitted to InfoEx live in InfoEx too, under their retention rules, not ours. If you disconnect Google Calendar, we delete the stored authorization tokens; the guide-ops calendar and events already written to Google remain in your Google account until you remove them there.

Your rights

You can ask for a copy of your data, ask us to correct it, or ask us to delete it. Email steve@guide-ops.com and we will respond within 30 days. Depending on where you live you may have further rights under the GDPR, the CCPA, or Canadian privacy law. We honour those requests regardless of where you are.

Security

Data is encrypted in transit and at rest. Access between operations is enforced in the database itself, not only in the application. Customer data is scoped to the operation that collected it. We keep the number of people who can reach production data as small as possible.

Children

The service is for working guides and operators and is not directed at anyone under 18. We do not knowingly collect information from children.

Changes

If we change this policy in a way that materially affects you, we will email you before it takes effect.

Contact

GuideOps Platform, Inc. — steve@guide-ops.com