Cookie Policy.
Which cookies sawa.tours sets, what each one is for, and how to control or delete them.
Effective date: August 8, 2026 · Last updated: August 8, 2026
This Cookie Policy explains how Online Era, trading as Sawa Tours (“Sawa”, “we”, “us” or “our”), uses cookies and similar technologies on sawa.tours, its related booking pages and dashboards, and the Sawa embedded departures widget. It should be read alongside our Privacy Policy and Terms and Conditions.
1. What cookies and similar technologies are
Cookies are small text files stored on a browser or device. They can remember a session, a preference or an identifier. Websites also use related technologies such as local storage and session storage, which keep data in the browser in the same way but are not sent with every request. This Policy calls all of them “cookies” for simplicity, and the table below says which kind each one actually is.
First-party cookies are set by Sawa. Third-party cookies are set by another provider whose service appears on the Platform. Session cookies expire when the browser closes; persistent cookies remain until their stated expiry or until you delete them.
2. Cookie categories
Strictly necessary
Required for security, booking, login, fraud prevention or remembering your choices. The requested service cannot work reliably without them.
Functional — off until you turn it on
Remember optional choices, such as the partner link you arrived through, and provide enhanced features.
Analytics — off until you turn it on
Help us understand visits, traffic sources, errors and feature use, so that we can improve the Platform.
Advertising
Sawa does not use advertising or cross-site tracking cookies, and we do not sell data derived from cookies to anyone. If that ever changes, this Policy and the table below will be updated before the change takes effect.
3. What we currently use
| Name | Set by | Kind | Category | Purpose | Lasts |
|---|---|---|---|---|---|
sawa_consent | Sawa | Local storage | Strictly necessary | Remembers the choices you make on the cookie banner, and when you made them, so you are not asked again on every page. | 12 months |
sb-…-auth-token | Sawa (Supabase) | Local storage | Strictly necessary | Keeps operators and staff signed in to their dashboard. Set only when you sign in; the public site never sets it. | Until you sign out |
sawa_ref | Sawa | Local storage | Functional | Remembers the partner code you arrived through, so the partner is credited if you go on to book. Holds a short code, nothing personal. | 30 days |
sawa_ref_hit_… | Sawa | Session storage | Functional | Counts one click-through per partner per visit, so a single visit is not counted repeatedly. | Until the tab is closed |
_ga | Cookie | Analytics | Distinguishes one browser from another for Google Analytics reporting. | 2 years | |
_ga_VG2G0Q5JFM | Cookie | Analytics | Keeps Google Analytics session state for our measurement property. | 2 years |
Sawa does not currently take payments on the Platform, so no payment-provider cookies are set. If a payment provider is added, its cookies will be listed here first.
4. Your choices
On your first visit we show a cookie banner offering three equally available options: Accept all, Reject optional, or Manage choices to decide category by category. Nothing in the functional or analytics categories is set before you choose. Closing or ignoring the banner is not consent, no optional category is pre-ticked, and refusing does not prevent you browsing or booking.
You can change your mind at any time through Cookie settings in the Company column of the footer. Withdrawing a consent does not undo what was lawful beforehand, but it stops any further use and deletes the cookies and stored values in that category. We ask again after 12 months, and sooner if the purposes materially change.
We use Google Analytics 4, provided by Google LLC, to understand how people find and use the site. We have not enabled Google’s advertising features, Google Signals or User-ID, and we do not use analytics data to identify you personally. Google Analytics is not loaded at all until you accept the analytics category; if you later withdraw, we delete its cookies and set Google’s own opt-out flag for the rest of the session.
Google Analytics reaches the site through Google Tag Manager, also provided by Google LLC, which is the container we use to load and configure it. Tag Manager sets no cookies of its own and, like Google Analytics, is not loaded at all until you accept the analytics category. Should we ever load anything else through it, that purpose and its cookies will be added to the table above before the change takes effect.
Google’s handling of any data it does receive is governed by Google’s privacy policy. If you would rather opt out of Google Analytics everywhere, not only here, Google offers an opt-out browser add-on.
Blocking the strictly necessary sign-in storage only affects the operator and staff dashboards; the public site works without any sign-in.
5. Referral attribution
When you follow a link from a partner, Sawa can store a short referral code in your browser for 30 days so that the correct partner is credited if you reserve or book. The code does not contain your name or contact details, though it can become linked to a booking once you submit one.
This is a functional purpose rather than a necessary one, so the code is only stored if you accept the functional category — it is commercially useful to us, which is not the same as being needed to give you what you asked for. You can clear it by withdrawing that consent in Cookie settings, or by clearing your browser’s site data for sawa.tours.
6. The embedded Sawa widget
Sawa departures may appear inside a partner operator’s website. Loading the widget sends Sawa ordinary network information, such as your IP address, browser details, the referring domain and the widget configuration. The referral store described above is not set by the widget itself — only by a real visit to sawa.tours.
The partner website controls its own cookies and should identify Sawa in its own privacy and cookie notices. Once you submit information to Sawa through the widget, our Privacy Policy applies to Sawa’s handling of it.
7. Third-party content
Some pages load fonts from Google Fonts and tour photography from our storage provider. Serving those files involves your IP address, as any web request does, but neither sets cookies for us. Where a page later includes payment forms, video, maps, chat or similar embedded services, those providers may set their own cookies, and they will be added to the table above.
8. Browser controls
Most browsers let you inspect, block or delete cookies and site data. Blocking every cookie can affect secure sign-in, booking and saved preferences on any website. Instructions are available from:
9. Changes to this Policy
We update this Policy and the table above whenever a technology, purpose, provider or retention period changes. If we add a cookie or change what one is used for, we will update this page and its effective date before the change takes effect.
10. Contact
Questions about cookies or your data are welcome at hello@sawa.tours or on WhatsApp.