Privacy Policy

Last updated: November 7, 2026

This Privacy Policy explains how Guidewake (“Guidewake,” “we,” “us,” or “our”), a service operated by Ocean Labs Media LLC, collects, uses, and shares information when you interact with a fishing charter business through our booking and customer-service assistant, including by text message (SMS), our website chat, phone, or email.

Information we collect

We collect information you provide directly, including:

  • Contact details such as your name, mobile phone number, and email address.
  • The content of messages you send us and inquiry details such as requested trip dates, group size, and questions about availability or rates.
  • Information you submit through a charter business’s website chat widget, including a phone number you provide so we can reply about your inquiry.

If a charter operator signs in to the Guidewake back office with a Google Account, we also receive their name, email address, and basic Google profile information. See Google user data below.

We also automatically collect limited technical and usage data (such as message delivery status) needed to operate the messaging service.

When you open a captain’s booking chat, we also record how you arrived — for example the search engine, social site, QR code or link that brought you to his website. On his website this is kept in your browser for up to 30 days so it reflects your first visit, not your last click. It is shown to that captain so he can tell which of his marketing works. We do not use it for advertising and do not share it with ad networks.

How we use your information

  • To respond to your questions and help book or manage your trip.
  • To send you conversational replies and booking-related follow-up text messages about the inquiry you started.
  • To operate, maintain, secure, and improve the service.
  • To comply with legal obligations.

Text messaging (SMS)

When you text a charter business’s number or submit your phone number through its website chat, you consent to receive text messages from that business through Guidewake about your inquiry and booking. Message frequency varies. Message and data rates may apply. You can reply STOP at any time to opt out, or HELP for help.

No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent are not shared with any third parties.

Calls, recording & AI processing

Calls to or from a Guidewake business line may be recorded and transcribed on bothsides of the call — the caller’s and the charter business’s. Both parties hear a spoken notice before the conversation continues. We record to answer and route calls, build the booking record, resolve payment or trip disputes, and improve the assistant for that business.

Your messages, chats, and call transcripts are processed by automated systems, including third-party AI model providers acting as our service providers, to draft replies and capture booking details. They are not sold, and they are not used for marketing by anyone other than the charter business you contacted.

If you would rather not be recorded, you can reach the charter business by text or email instead of by phone. To request deletion of a specific recording or transcript, contact us using the details below.

Google user data

Charter businesses (“captains”) who use the Guidewake back office may sign in with a Google Account. When a captain does, we receive only their name, email address, and basic Google profile information, and we use it for one purpose: to create and authenticate their Guidewake account. We do not read their Gmail, their contacts, or their Google Drive, and we do not request permission to.

Google Calendar (optional). A captain may choose to connect Google Calendar from their Guidewake settings. If they do, we request narrow permissions, each for one job. The first is required to connect; the captain can decline any of the others and the rest keeps working:

  • View their availability (free/busy) on their calendars. From the calendars the captain chooses (or only their main calendar, if they do not let us see their calendar list), we receive only the times they are busy for the next 60 days — never event titles, descriptions, locations, or attendees. We use those busy times for one purpose: so the captain’s booking assistant does not tell a customer that a busy time looks open. The busy times are included in the instructions our AI assistant uses when it answers that captain’s customers, are processed by our AI service provider only to produce that answer, and are kept for no longer than needed to refresh them. We also show those busy times — the time and the calendar’s name, never what the event is — to the captain, and only the captain, on their own Guidewake bookings calendar for the next 30 days, so they can see their whole schedule in one place. These are the same busy times the assistant uses, refreshed from Google about every ten minutes.
  • See the availability of events on the calendars they choose. Google marks all-day events “free” by default, so they would never count as busy. With this permission we read, for each event on the chosen calendars, only its start and end, its free/busy setting, whether it was cancelled, and whether the captain declined it — never its title, description, location, or other attendees — and count every all-day event the captain has not declined as busy for those whole days, for the assistant and for the captain’s own schedule view. Only those busy times are kept, as described above. The captain can turn this off in their settings (“All-day events block my calendar”).
  • See the list of their calendars (read-only).We read each calendar’s ID, name, and the captain’s access level so the captain can choose which calendars count as busy. By default their main calendar, the calendars they own, and subscribed calendars named like a booking calendar (for example FishingBooker) count; Google’s holiday and birthday calendars and other subscribed calendars do not, and the captain can change the choice at any time in their settings. We store those calendar IDs, names, and access levels, and which ones the captain chose.
  • View the events on the calendars they choose (read-only). We request this permission only once Google has approved it for Guidewake; until then it is not asked for. If the captain grants it, their own Guidewake bookings calendar — visible only when the captain is signed in — also shows the title of each event on the chosen calendars for the next 30 days, marked “Busy.” Events the captain declined, and events marked “free,” are left out. These titles are read from Google when the captain opens that page and held in memory for at most five minutes. They are never stored or logged, and never shown to customers, to other captains, or to our AI assistant.
  • Make one secondary calendar, and manage the events on it. We create a single calendar named “Guidewake trips” in the captain’s Google account and keep one all-day event on it for each trip booked through Guidewake. Google limits this permission to calendars Guidewake itself created: it does not let us create, change, or delete anything on the captain’s own calendars or any other calendar. Each event holds the trip date and trip type; the customer’s name and phone number; the number of anglers and target species; the trip price; the deposit and balance amounts, whether each has been paid and how the balance was settled (for example card or cash), and any refund; the meeting spot the captain chose for that trip (or, if none was chosen, a note naming the captain’s default spot); and a link to that booking in the captain’s Guidewake dashboard. The event also carries the Guidewake booking’s ID in its private extended properties (a hidden field Google Calendar does not display), so we can match the event to the booking. We update the event when the booking changes and remove it if the trip is cancelled. On our side we store the calendar’s ID and, for each booking, its event’s ID, a fingerprint of what we last wrote, and its sync status (when it last synced and any error) — never the event contents themselves.

A captain can disconnect at any time in their settings, which revokes our access and deletes the stored connection. After that we write nothing more. The “Guidewake trips” calendar and its events stay in the captain’s Google account; trips already on it won’t update anymore, and the captain can delete it in Google Calendar if they are not reconnecting. We keep the calendar and event IDs and sync status described above after a disconnect, so that reconnecting the same Google account updates the existing events instead of creating duplicates; they are deleted with the captain’s booking records or account.

Customers booking a fishing trip are never asked to connect a Google Account.

Sign-in credentials issued by Google are held by our authentication provider on managed infrastructure in the United States and are never exposed to a captain’s customers or to another captain. A captain can revoke Guidewake’s access at any time at myaccount.google.com/permissions, and can ask us to delete their account and associated data using the contact details below.

Guidewake’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data for advertising, we do not sell it, we do not share it with third parties for their own purposes, and we do not use it to train generative artificial-intelligence or machine-learning models. If we add a Google integration that accesses anything beyond what is described above, we will update this policy to describe it before that integration is available.

How we share information

We share information only as needed to provide the service:

  • With the fishing charter business you contacted, so it can respond to and fulfill your inquiry. If that business has connected Google Calendar to Guidewake, the details of your booked trip (your name, phone number, party size, trip, payment status, and meeting spot) are also placed on a calendar in the business’s own Google account.
  • With service providers that operate the platform on our behalf (for example, messaging and cloud-hosting providers), under obligations of confidentiality and only for that purpose.
  • When required by law or to protect rights, safety, and security.

We do not sell your personal information, and we do not share text messaging consent or phone numbers with third parties or affiliates for their own marketing.

Data retention

We keep information for as long as needed to provide the service and for legitimate business or legal purposes, then delete or de-identify it.

Your choices

  • Opt out of text messages at any time by replying STOP.
  • Request access to, correction of, or deletion of your information by contacting us using the details below.

Children’s privacy

The service is intended for adults and is not directed to children under 16. We do not knowingly collect information from children.

Security

We use reasonable administrative, technical, and physical safeguards to protect your information. No method of transmission or storage is completely secure.

Changes to this policy

We may update this Privacy Policy from time to time. Changes take effect when we post the updated policy on this page.

Contact us

Questions about this policy or your information? Contact us at support@guidewake.com or call (407) 993-1209.