The cookies and similar technologies Qembara uses, and the choices you have.
This Cookie Policy explains how the Qembara legal entity identified above ("Qembara", "we", "us" or "our") uses cookies and similar technologies when you browse or use the Qembara marketplace, including its websites, applications, communications, booking flows and support services (the "Platform"). It applies whether or not you have an account or are signed in.
This Policy should be read with the Qembara Privacy Policy, which explains the wider collection, use, sharing, retention, transfer and protection of personal data. A Host or another third party may use technology on a service or page that it independently operates; its own notice and choices may also apply. Qembara does not authorise Hosts to add tracking technology to Qembara-controlled pages.
With the required choice or consent, Qembara may remember language, currency, region, display, recent-search or other settings. If a preference can be delivered without identifying or tracking a user beyond what is needed, Qembara will use the less intrusive method.
With the required choice or consent, Qembara may measure visits, feature use, page and app performance, errors, referral sources and progress through search and booking flows. Qembara will not use analytics data to make a materially significant account, verification, transaction or Booking decision unless the Privacy Policy and the relevant interface separately explain that processing.
Qembara may use advertising or targeting technologies only after the required affirmative consent or other legally valid choice. They may help attribute visits or Bookings to a campaign, control advertising frequency, create or exclude audiences, or show more relevant promotions. Qembara will not use health, accessibility, allergy, identity-document, payment-card, Participant or private message content to create advertising audiences.
Email controls are separate from browser-cookie choices. Qembara may retain delivery and security records needed to send and protect a message. Open tracking, click tracking, campaign attribution, personalisation and profiling will be separately classified and enabled only where the required choice has been recorded. The message or preference interface will describe the controls the selected provider can actually support, including whether open or click measurement can be disabled separately from unsubscribing. Rejecting browser cookies does not, by itself, disable email pixels, tagged links or provider-side measurement.
Mobile applications may use SDKs, APIs or device identifiers for core functions, security, crash reporting, analytics or advertising. Before publication of this section as an operating description, Qembara will verify each SDK's pre-choice behaviour and delayed-initialisation capability on each supported operating system. Optional SDKs will remain inactive until the required choice is recorded. Operating-system permission does not substitute for Qembara's category choice, and refusing advertising tracking is not permission to initialise optional analytics or profiling SDKs.
First-party cookies are set by Qembara-controlled domains. Third-party technologies are provided or set by another organisation, such as a security, payment, maps, support, analytics or advertising provider. A third party may receive information directly from a browser or device and may independently determine some processing under its own privacy notice.
Before deployment, Qembara will approve the purpose, category, data fields, domain, provider role, recipient locations, safeguards, retention and user control for each technology. Roles are assigned per processing activity, not once for the provider as a whole: the same provider may act on Qembara's instructions for one purpose and independently or jointly for another. The register will identify each activity and role separately. Qembara will contractually restrict providers acting on its instructions. Independent or joint processing will be disclosed with the provider's notice, respective responsibilities and available choice route before activation.
On a first visit, Qembara will provide a clear choice before any technology requiring consent is activated. Rejecting all non-essential technologies will be as prominent and straightforward as accepting them. Category choices will not use pre-ticked boxes, inactivity or continued browsing as affirmative consent where affirmative consent is required.
Choose in the banner: accept all, reject all non-essential technologies, or open category settings.
Change your mind: reopen the Cookie Preference Centre from a persistent footer or settings link and withdraw as easily as you consented.
Use browser or device controls: block or delete cookies, reset advertising identifiers, or limit app tracking. These controls may not communicate every legal choice to Qembara and may affect requested functionality.
Manage marketing separately: unsubscribing from marketing messages does not by itself change browser cookie choices, and rejecting cookies does not necessarily unsubscribe you from marketing messages.
When you withdraw a choice, Qembara will immediately prevent the affected optional technologies from being activated again within the stated scope of that choice. Qembara will delete or disable existing Qembara-controlled identifiers where technically feasible. It may send a supported opt-out or withdrawal instruction to a provider, but cannot promise deletion of identifiers or records independently controlled by that provider. Provider-side records already created remain subject to the provider's notice, the Privacy Policy and applicable retention requirements. The preference centre will state whether withdrawal applies to the current browser or app installation, a signed-in account, other devices, server-side consent state and supported provider instructions. Strictly necessary technologies remain active, but Qembara will not deny core service merely because optional technologies are rejected.
If a choice is stored only on a device, it may need to be repeated after cookies are cleared, a new browser or device is used, an application is reinstalled, or private-browsing mode ends. Where technically supported, signed-in choices may be synchronised across Qembara surfaces after clear notice. Qembara will honour browser or device privacy signals where applicable law requires it and will describe any broader voluntary recognition in the preference centre.
Qembara will record the banner and policy version, categories chosen, date and time, relevant domain or application, consent identifier and withdrawal event. The record will be retained only for the period needed to demonstrate and respect the choice, resolve disputes and meet legal obligations. Qembara will request a fresh choice when purposes or providers materially change, the recorded choice expires, or applicable law requires renewal.
Each cookie or similar technology will have the shortest practical duration for its purpose and the exact maximum will appear in the live register. A non-essential client-side identifier will not remain active for more than 13 months unless a shorter period applies; renewal requires a fresh valid choice where required. Session technologies expire at session end or shortly afterward. Qembara will not silently extend a technology's lifetime or repurpose an identifier beyond the disclosed period. Consent records, server-side derived events and individually justified essential security or fraud identifiers follow separate, purpose-specific periods stated in the Privacy Policy or register.
Server-side event data derived from a cookie may be retained separately under the Privacy Policy. Deleting a browser cookie does not automatically delete records already stored on Qembara's systems; users may use the Privacy Centre to exercise applicable rights. Qembara will delete, anonymise or securely isolate data when it is no longer needed, subject to documented security, fraud, legal-hold and statutory retention requirements.
A person must be at least 21 to create a Qembara account or make a Booking, but Qembara may not know the age of a person viewing public pages before login. Qembara therefore does not claim that every anonymous visitor has been age-verified. It will not design advertising or targeting activities to profile a person it knows is a child and will apply documented audience exclusions and provider restrictions where available. Participant information, including information about minors, will not be connected with cookie-derived advertising audiences merely because a Booking Guest supplied it for an Experience. If Qembara learns that optional tracking was applied contrary to these controls, it will investigate, stop the relevant use and take appropriate deletion or remediation steps.
Qembara will maintain an owner for the consent platform and register; block unapproved tags; restrict deployment access; test the banner before release; scan production surfaces periodically; reconcile scan results with the register; monitor consent-mode failures; and keep an auditable approval history. Strictly necessary classification requires documented necessity and cannot be used to bypass a user's choice.
When Qembara materially changes a purpose, category, provider or sharing practice, it will update the register and Policy before activation and obtain a fresh choice where required. Earlier versions will be archived and the revised date shown. Minor wording or formatting changes may be made without interrupting service where they do not alter the substance of processing or choice.
Qembara Experiences Pte Ltd operates the Qembara Platform and provides marketplace, booking, payment-facilitation and support services. Except where a listing expressly identifies Qembara as the supplier, Qembara is not the host and is not a party to the experience contract.