Cookie Policy

This Cookie Policy of QEMBARA EXPERIENCES PRIVATE LIMITED, a company incorporated in Singapore with Company Unique Entity (UEN) Number 202645696M (Qembara, we, us or our), explains how Qembara 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 covers qembara.com and its current and future subdomains, including any Qembara mobile applications for iOS and Android.

This Policy forms part of the Privacy Policy at qembara.com/privacy and should be read with it, in particular sections 8 (Cookies, Analytics and Advertising), 11 (Data Retention) and 13 (Your Privacy Rights). It uses the defined terms in the Guest Terms, Host Terms and Privacy Policy. A Host or another third party may use technology on a service or page that it operates independently, and its own notice and choices may then apply. Qembara does not allow Hosts to add tracking technology to Qembara-controlled pages. This Policy is provided in English. This does not limit any language-related right required by law.

A cookie is a small text file stored by a browser. A session cookie normally expires when the browser session ends; a persistent cookie remains until its stated expiry or deletion. In this Policy, cookies also include comparable technologies where relevant, such as pixels, web beacons, tags, scripts, software development kits (SDKs), local or session storage, device identifiers and email interaction tools.

These technologies may collect or infer information such as IP address, browser or app type, device and advertising identifiers, language, approximate location derived from IP, referring page, pages and content viewed, searches, clicks, booking-funnel events, timestamps, errors, authentication events, consent choices and interactions with messages or advertisements. Qembara treats this information as personal data where it identifies, relates to or can reasonably be linked with a person or device.

Qembara uses the same four categories in this Policy, the cookie banner and the Cookie preferences control. Optional functional, analytics and advertising technologies remain inactive until you have made a choice. A technology serving more than one purpose is classified and controlled according to its most privacy-intrusive purpose unless it is technically separated.

Strictly necessary: runs core functions such as security, fraud prevention, network management, load balancing, login, session continuity, checkout, payment routing and recording your privacy choices. These are always active, but only where genuinely necessary, and are never used for unrelated analytics, personalisation or advertising.

Functional: remembers optional choices such as language, display currency, display settings, recent searches or accessibility preferences, and may enable optional features such as embedded maps of meeting points. Off until you allow them, unless you have expressly requested the function and the law permits it.

Analytics and performance: measures traffic, feature use, errors and booking journeys so Qembara can understand and improve the Platform, using privacy-preserving settings and aggregate reporting where practicable. Off until you allow them.

Advertising and targeting: measures campaigns, limits how often an advertisement is shown, builds or uses audiences, personalises advertising or recognises activity across services or devices. Off until you give affirmative consent, and never treated as strictly necessary.

4.1 Operate, secure and complete transactions. Qembara uses strictly necessary technologies to maintain sessions, authenticate users, prevent account takeover and detect suspicious or fraudulent activity; support searches, availability, Bookings, checkout, payment facilitation, Host Payouts, support and incident handling; route traffic, balance system load, identify errors and protect the Platform; and store your privacy choices so that rejected technologies stay blocked. The payment provider described in the Payment Terms may set its own fraud-prevention and authentication cookies at checkout; these are strictly necessary for secure payment.

4.2 Remember requested preferences. With your choice or consent, Qembara may remember language, display currency, market, display, recent-search or other settings. If a preference can be delivered without identifying or tracking you beyond what is needed, Qembara will use the less intrusive method.

4.3 Measure and improve the Platform. With your 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 significant account, verification, transaction or Booking decision unless the Privacy Policy and the relevant interface explain that processing.

4.4 Advertising, campaign measurement and personalisation. Qembara may use advertising or targeting technologies only after your affirmative consent. At launch, Qembara uses them only to measure the results of its own advertising campaigns, for example on social-media platforms, and does not use retargeting across other websites, lookalike audiences built from Guest data or cross-device tracking. Qembara will not use health, accessibility, allergy, religious-belief, identity-document, payment-card, Participant or private-message information to create advertising audiences.

5.1 Emails and notifications. Email choices are separate from browser-cookie choices. Qembara keeps the delivery and security records needed to send and protect a message. Marketing emails may measure opens and clicks to understand campaign performance; transactional emails, such as Booking Confirmations and payment notices, do not use open or click tracking. You can stop marketing emails as described in section 9 of the Privacy Policy. Rejecting browser cookies does not by itself disable email pixels or tagged links.

5.2 Mobile applications. Mobile applications may use SDKs, APIs or device identifiers for core functions, security, crash reporting, analytics or advertising. Optional SDKs remain inactive until you make a choice. Operating-system permissions, such as Apple’s App Tracking Transparency prompt, do not replace your choice in Qembara’s Cookie preferences, and refusing advertising tracking will not be treated as permission to start optional analytics 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 your browser or device and may decide some processing independently under its own privacy notice.

Before deployment, Qembara approves the purpose, category, data collected, domain, provider role, recipient locations, safeguards, retention and user control for each technology. Roles are assigned per processing activity: the same provider may act on Qembara’s instructions for one purpose and independently for another, and the Cookie Register identifies each activity and role separately. Qembara contractually restricts providers acting on its instructions, and discloses independent or joint processing, with the provider’s notice and choice route, before activation.

On your first visit, Qembara will ask for your choice before any technology requiring consent is activated. Rejecting all optional technologies will be as prominent and easy as accepting them. Qembara will not use pre-ticked boxes, inactivity or continued browsing as consent. You can:

Choose in the banner: accept all, reject all optional technologies, or open the category settings.

Change your mind: reopen Cookie preferences at any time from the link in the website footer 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 pass every choice to Qembara and may affect functions you have requested.

Manage marketing separately: unsubscribing from marketing messages does not change your cookie choices, and rejecting cookies does not unsubscribe you from marketing messages.

When you withdraw a choice, Qembara will immediately stop the affected optional technologies from being activated again, and will delete or disable Qembara-controlled identifiers where technically feasible. Qembara may send a supported opt-out instruction to a provider, but cannot guarantee deletion of records the provider controls independently; those records remain subject to the provider’s notice, the Privacy Policy and applicable retention requirements. Strictly necessary technologies remain active, but Qembara will not deny you core services because you reject optional technologies.

If a choice is stored only on your device, you may need to make it again after clearing cookies, using a new browser or device, reinstalling an app or leaving private browsing. Where technically supported, choices made while signed in may be applied across Qembara websites and apps after clear notice. Qembara will honour browser or device privacy signals, such as Global Privacy Control, where applicable law requires it.

Qembara records the banner and Policy version, the categories chosen, the date and time, the relevant website or app, a consent identifier and any withdrawal. Qembara will ask you to confirm your choice again every 12 months and keeps consent records for 24 months after a choice is withdrawn or expires. Qembara will also ask for a fresh choice when purposes or providers change materially or applicable law requires it.

The Cookie Register forms part of this Policy and is updated before a technology is deployed or materially changed. For each technology it identifies the name and provider (with a link to the provider’s notice); whether it is first- or third-party and the provider’s role; its category; its specific purpose and the main data collected; where it is used; its duration, stated as session or an exact maximum lifetime; whether it is always active or consent-controlled and how to withdraw; and the recipient’s role, principal processing locations and transfer safeguard, where applicable.

Each technology has the shortest practical duration for its purpose, and its exact maximum appears in the Cookie Register. An optional identifier stored on your device will not remain active for more than 13 months, as stated in section 11 of the Privacy Policy, and renewal requires a fresh choice where required. Session technologies expire at the end of the session or shortly afterwards. Qembara will not silently extend a technology’s lifetime or repurpose an identifier.

Server-side data derived from a cookie is kept under the retention periods in section 11 of the Privacy Policy. Deleting a browser cookie does not automatically delete records already stored on Qembara’s systems; you may exercise your rights under section 13 of the Privacy Policy.

You must be at least 18 to create an account and at least 21 to make a Booking, as stated in section 4 of the Guest Terms and section 14 of the Privacy Policy. Qembara may not know the age of a person viewing public pages before sign-in and does not claim that every anonymous visitor has been age-verified. Qembara will not design advertising to profile a person it knows is a child and will apply audience exclusions and provider restrictions where available. Participant information, including information about minors, will never be connected with cookie-derived advertising audiences. 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 maintains an owner for its consent tool and the Cookie Register; blocks unapproved tags; restricts who can deploy them; tests the cookie banner before release; scans production pages regularly and reconciles the results with the Cookie Register; and keeps an auditable approval history. A technology may be classified as strictly necessary only where its necessity is documented; this classification cannot be used to bypass your choice.

When Qembara materially changes a purpose, category, provider or sharing practice, it will update the Cookie Register and this Policy before activation and ask for a fresh choice where required. Qembara will show the new effective date and archive earlier versions. Minor wording or formatting changes that do not alter the substance of processing or your choices may be made without interrupting service.

For questions, requests or complaints about cookies, consent or tracking, contact Qembara’s Data Protection Officer at support@qembara.com. Qembara will respond as described in section 13 of the Privacy Policy. You may also complain to Singapore’s Personal Data Protection Commission at www.pdpc.gov.sg or to the data-protection authority where you live.