Privacy & Cookies Policy
Lapland Explorers uses essential website functionality, booking links, consent-managed analytics, and customer support tools to run this website.
Analytics and cookies
We use Google Tag Manager and Google Analytics 4 to understand site traffic and booking interest. Optional tools are off until you choose them. Analytics, advertising and live chat have separate choices. With necessary cookies only, we do not load Google Tag Manager, Google Analytics, Google Ads, Meta Pixel, Hotjar or Tawk.to. Google Tag Manager loads only when both analytics and advertising are enabled; selecting just one loads only that Google measurement destination.
Hotjar session recordings and heatmaps
With Analytics enabled, we use Hotjar to understand navigation, clicks, scrolling and interactions through heatmaps and session recordings. Capture can continue as you use pages with the integration enabled. Hotjar applies its masking and suppression controls to recordings; a recording is not a video from your camera. We do not intentionally collect passwords or payment-card details through recordings. Bookings and payments are handled by Bókun and its payment provider. See Hotjar’s privacy policy for how it handles this data.
Booking and customer support
Booking buttons may open Bokun, our booking provider. WhatsApp links open WhatsApp directly when clicked. If enabled, Tawk.to live chat loads only after you enable Live chat. It receives the page and relevant tour or booking context to help answer your questions. Turning Live chat off stops this forwarding and disconnects the widget.
Booking attribution
If you accept analytics and advertising cookies, we keep the first and latest marketing touch for up to 90 days. This can include the source, medium, campaign, search keyword, ad identifier, landing page, referring website and an eligible Google click ID. When you start our custom Bokun checkout, approved attribution may be passed to Bokun and recorded in our internal booking-attribution ledger. The ledger stores a SHA-256 digest instead of the raw Google click ID. An operational attribution ID, consent status and checkout details may be recorded without marketing-source evidence so we can diagnose checkout and attribution reliability.
Advertising measurement
With Advertising enabled, Google Ads may measure ad-related activity. If you enable both analytics and advertising, Google and Meta (Facebook and Instagram) may also measure visits and bookings that come from our ads. When a booking from such a visit is confirmed, our server may send Google and Meta a purchase event with the booking value, an internal attribution ID and a one-way SHA-256 hash of the email address and phone number you entered at checkout, so they can match the booking to an ad you saw or clicked. Your email address and phone number are never sent in readable form. Nothing is sent if you choose necessary cookies only.
Retention and your choices
Browser attribution and internal attribution-ledger records are retained for up to 90 days. Choosing necessary cookies only prevents marketing attribution from being collected or forwarded and clears stored browser attribution. You can reopen Your privacy choices from the footer at any time. Withdrawing permission stops new site forwarding, revokes Meta consent where applicable, disconnects live chat when disabled, and reloads the page to unload integrations such as Hotjar. The saved choices prevent disabled tools loading again. Previously transmitted data is not automatically erased by withdrawal. For access, correction or deletion requests, email info@laplandexplorers.com.
If you accept analytics and advertising cookies, we may send Meta an existing browser identifier (_fbp) and click identifier (_fbc, including one derived from an actual fbclid on arrival) in their original form to match a confirmed booking to an ad. They stay separate from general booking attribution and expire within 90 days of their original creation in the browser. The server can use them only within 24 hours of checkout creation and removes them at the next scheduled cleanup. Withdrawing consent clears this matching context.