Privacy Policy
Last updated: November 2026
Seascape Booking Systems (“Seascape”) (“we”, “our”, “us”) is committed to protecting your privacy. This Privacy Policy explains how we collect, use, and safeguard your information when you use our platform.
Information We Collect
We collect information you provide directly, such as your name, email address, phone number, and business details when you create an account. We also collect usage data to improve our services.
How We Use Your Information
We use your information to provide and maintain our services, communicate with you, and improve the platform experience.
Analytics on seascape.bz
On Seascape’s own website, seascape.bz, we use Google Analytics to see how people find and use our pages, so we can make them clearer. It runs only if you choose Accept on the cookie banner. Until you do, or if you choose Decline, Google Analytics does not load and sets no cookies.
If you accept, Google Analytics records the pages you open, the site or link that brought you here, the menus and buttons you use on our pages, your browser, device and screen size, and your approximate location (country and city), which Google works out from your IP address. It sets two cookies, one named _ga and one whose name starts with _ga_, which last up to two years. We don’t send Google your name, your email address or anything you type into a form, and we don’t use Analytics for advertising. Google handles what it collects under its own privacy policy.
It never runs inside the Seascape dashboard, or on the pages a shop’s customers use: booking, payment, waiver and check-in pages, and the links a shop sends. If your browser sends a Global Privacy Control signal, we treat it as a Decline and don’t ask.
To change your mind at any time, choose Cookie settings at the bottom of any page on seascape.bz. Choosing Decline stops Google Analytics and deletes its cookies. Your browser keeps your choice for about 13 months, and then we ask again. A shop’s own website has its own banner, described under “Cookies and consent on shop websites” below.
Text messages (SMS) and WhatsApp
If you sign up for Seascape SMS Alerts, we keep your mobile number, when you agreed, where you agreed (at sign-up, in Settings, or from an invite your shop emailed you), the wording you agreed to, and whether you chose WhatsApp or SMS. We use them only to send the alerts you asked for and to keep a record of your consent. WhatsApp messages are delivered through WhatsApp (Meta) and our messaging provider, Twilio, which see your number and the message in order to deliver it. You can stop at any time by replying STOP, in Settings, or from your manage link. See our SMS Terms.
We do not sell or share your SMS opt-in data or personal information with third parties for marketing purposes.
Google and Meta connections for shop websites
This section explains how we handle data when a dive shop connects its own Google account or its own Meta (Facebook and Instagram) account to Seascape. The accounts stay the shop’s. If a shop has not connected one, none of this applies and we send nothing to Google or Meta for that shop.
What we access in a shop’s Google account
A staff member with permission signs in with Google and approves access on Google’s own screen. We ask for these permissions, and use each one only for the job listed:
- Google Analytics (edit) — to list the shop’s Analytics accounts and properties; to create a property and a web data stream for the shop’s website if the shop asks us to; to record that the shop accepted Google’s data-collection terms, which the shop ticks itself; and to create the key our server uses to send the shop’s bookings to that property.
- Search Console — to add the shop’s website to its Search Console, submit the website’s sitemap, and show the shop whether the site is verified.
- Site Verification (new sites only) — to prove to Google that the shop owns its website, using a tag we place on that website. This permission cannot see sites the shop verified before.
- The signed-in Google account’s email address — to show the shop which account is connected.
We do not read the shop’s Analytics reports or Search Console results, and we do not ask for its email, files, contacts or calendar.
How we use Google user data
We use what we receive from Google only to set up and run the connection the shop asked for, and to show the shop its status in the Seascape dashboard. We do not sell it, use it for advertising, use it to build profiles of anyone, or use it to train AI models. Nothing we receive from a shop’s Google account is passed to Meta or to anyone else. Our staff look at it only when the shop asks us for help, to investigate a security problem, or when the law requires it.
Seascape’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
What we access in a shop’s Meta account
The shop signs in with Facebook and picks, on Meta’s own screen, the business, ad account, Page and pixel Seascape may use. We use that access to find or create the shop’s pixel and to send it the shop’s website visits and bookings. We do not post to the shop’s Page, create or change its ads, or read its messages.
What we send to Google and Meta for a shop
When a booking with a connected shop is paid, our server sends a purchase to the shop’s own Google Analytics property, and to its own Meta pixel if Meta is connected. A refund sends a refund to Google. Each event carries the booking reference, the amount and currency, and the activities booked. If the customer accepted cookies on the shop’s website, it also carries the identifiers Google and Meta set there, plus any ad-click identifier from the link the customer arrived on, so the shop can see which visit or ad led to the booking.
Customer contact details sent to Meta. Only if the shop turns this on, and only if the customer accepted advertising cookies on the shop’s website, we also send Meta the customer’s email address, phone number and name, which Meta uses to match the booking to an ad. Our server scrambles each one with SHA-256 hashing before it leaves us, so Meta receives the hashed values. We also send the browser’s IP address and type, recorded when the booking was made, because Meta requires them for website events. Mobile numbers given for Seascape text alerts are never included.
That is the only sharing. Events go to the shop’s own Google and Meta accounts, at the shop’s request, and to no one else. Seascape does not sell personal information. Once an event arrives, Google and Meta handle it under their own terms and the shop’s agreements with them.
Cookies and consent on shop websites
On a shop’s website, the shop’s Google Analytics tag and Meta pixel load only after a visitor chooses to accept them on the cookie banner. Before that, or after a decline, neither loads and neither sets a cookie. If the visitor’s browser sends a Global Privacy Control signal, we treat it as a no to advertising. The banner keeps the visitor’s choice in one cookie on the shop’s website, and the visitor can change it at any time. The choice travels with the booking: without advertising consent, we send nothing to Meta for that booking, and we tell Google not to use it for advertising.
These tags are never placed on booking, payment, waiver or check-in pages.
Storage, security and how long we keep it
- The access tokens Google and Meta give us are encrypted with AES-256 before we store them, with a key kept outside the database. They are never sent to a browser. All traffic to and from Google, Meta and Seascape is encrypted in transit.
- Tokens and the ids of the shop’s property, website and pixel are kept while the connection is on, and deleted when the shop disconnects.
- The website identifiers stored with a booking are deleted 90 days after the booking is made.
- Our log of each event sent, and Google’s or Meta’s reply, is deleted after 90 days.
- We keep a record of who connected or disconnected an account, and who accepted Google’s data-collection terms, and when, for as long as the shop has a Seascape account.
Disconnecting and deleting
A shop can disconnect Google or Meta from its website settings in the Seascape dashboard. We then stop sending, take the tags off its website, cancel our access with Google or Meta, and delete the stored tokens. Access can also be removed from the other side: in the Google account at myaccount.google.com/connections, or in Meta’s Business settings under Integrations › Connected apps. The next time we try to use removed access, we stop and delete the token.
The Analytics property, Search Console site and pixel belong to the shop, even when Seascape created them. We never delete them, and they stay in the shop’s accounts after it disconnects.
To have us delete everything we hold from a shop’s Google or Meta connection, email info@seascape.bz from the shop’s account email. We delete it within 30 days and reply to confirm.
Deleting data Seascape received from Meta
You can ask us to delete the data we received through Facebook or Meta in either of two ways:
- Remove Seascape in Meta’s Business settings, under Integrations › Connected apps. We delete the token and the ids of the shop’s business, ad account, Page and pixel that we stored.
- Email info@seascape.bz with “Meta data deletion” in the subject and the name of your shop. We delete the data within 30 days and reply with a confirmation.
We are also building Meta’s automatic deletion request. Once it is live, removing Seascape from your Facebook or Meta settings will notify us directly and give you a confirmation code and a page to check the status of your request.
If you booked with a shop and want your details removed from what the shop sent to Meta, ask the shop, which controls its Meta account, or email us and we will pass your request on and stop sending your details.
Contact
If you have questions about this policy, please contact us at info@seascape.bz.