Remsee Cookie Policy

Version: v1.0
Effective date: 29 June 2026
Company: Numtrend Co., Ltd.

1. Purpose

This Cookie Policy explains how Remsee uses cookies, SDKs, pixels, local storage, device identifiers, and similar technologies on websites, mobile applications, emails, and related services.

2. Relationship to Privacy Policy

This policy supplements the Privacy Policy. Terms defined in the Privacy Policy and Terms of Service have the same meaning here.

3. Technologies We Use

  1. Cookies: small files stored in a browser.
  2. Local storage: browser or app storage used for preferences and sessions.
  3. SDKs: mobile or web software development kits used for analytics, crash reporting, attribution, security, or app functionality.
  4. Pixels and tags: tracking technologies used to measure visits, conversions, and campaign performance.
  5. Device identifiers: identifiers used for app analytics, fraud prevention, diagnostics, and preference management.

4. Cookie Categories

  1. Strictly necessary technologies: authentication, security, fraud prevention, load balancing, consent management, and core app operation.
  2. Functional technologies: language, region, saved preferences, accessibility settings, and product personalization.
  3. Analytics technologies: usage metrics, performance, crash reporting, feature adoption, and product improvement.
  4. Advertising and attribution technologies: campaign measurement, affiliate attribution, conversion tracking, and where enabled, personalized advertising.
  5. Affiliate booking technologies: partner click identifiers, booking referral attribution, commission tracking, and travel partner reporting.

5. Legal Bases

  1. Strictly necessary technologies may be used to provide the Service and protect security.
  2. Where required by law, analytics, advertising, attribution, and non-essential technologies will be based on consent or other permitted legal basis.
  3. You may withdraw consent where applicable.

6. Third-Party Technologies

We may use third-party technologies from providers such as:

  1. Analytics and diagnostics providers.
  2. Authentication providers.
  3. Payment and subscription providers.
  4. Affiliate networks and Travel Partners.
  5. Advertising and attribution providers.
  6. Cloud and security providers.

The technologies currently in use are listed below. This table is reviewed and updated as providers and features change. Durations are approximate and may vary by platform and provider configuration.

| Name / pattern | Provider | Category | Purpose | Duration | | --- | --- | --- | --- | --- | | sb-access-token, sb-refresh-token | Supabase (auth) | Strictly necessary | Maintains your authenticated session and keeps you signed in. | Session / up to 60 days | | remsee_consent | Remsee | Strictly necessary | Stores your cookie and tracking consent choices. | 12 months | | __cf_bm, load-balancer cookies | Cloudflare / hosting | Strictly necessary | Bot management, security, and load balancing. | Session / up to 30 minutes | | remsee_lang, remsee_region, app local storage | Remsee | Functional | Remembers language, region, and saved preferences. | Up to 12 months | | Firebase Analytics identifiers (app instance ID) | Google (Firebase) | Analytics | Usage metrics, feature adoption, and crash diagnostics. | Up to 14 months | | PostHog identifiers (ph_*) | PostHog | Analytics | Product analytics, funnels, and feature-usage measurement. | Up to 12 months | | RevenueCat / app-store purchase identifiers | RevenueCat, Apple, Google | Strictly necessary / functional | Subscription and in-app purchase state, receipt validation. | Duration of subscription + legal retention | | Affiliate click identifiers (e.g. aid, label, partner click IDs) | Booking.com, Agoda | Advertising and attribution | Records hotel/travel referral clicks so Remsee can receive commission. | Up to 30 days | | Advertising / attribution identifiers (IDFA, GAID) | Apple, Google | Advertising and attribution | Campaign measurement and, where consented, personalized advertising. | Until reset by you / device-controlled |

Where required by Applicable Law, analytics, advertising, attribution, and affiliate technologies are loaded only after you provide consent through the Remsee consent banner or preference center. Strictly necessary technologies are always active so the Service can function.

7. Managing Preferences

  1. You may manage cookie preferences through Remsee's cookie banner or preference center where available.
  2. You may use browser settings to block or delete cookies.
  3. You may use mobile device settings to limit ad tracking or reset advertising identifiers.
  4. Blocking certain technologies may affect Service functionality.

8. Do Not Track and Global Privacy Controls

  1. Remsee will evaluate browser-based privacy signals, including Global Privacy Control, where required by Applicable Law.
  2. Technical implementation and jurisdictional scope require counsel and engineering review.

9. Affiliate Tracking Notice

  1. When you click hotel, accommodation, or travel offers, affiliate technologies may record the referral so Remsee can receive commission.
  2. Travel Partners may place their own cookies or tracking technologies subject to their policies.

10. Updates

We may update this Cookie Policy to reflect new technologies, partners, legal requirements, or Service changes.

11. Contact

Privacy: privacy@numtrend.com
Address: 1575/5 Phahonyothin Rd., Samsan Nai, Bangkok, Thailand

12. Governing Law

This Cookie Policy is subject to the laws of the Kingdom of Thailand, with the courts of Bangkok having jurisdiction, unless mandatory privacy or consumer protection law provides otherwise.

13. Change History

| Version | Date | Owner | Summary | | --- | --- | --- | --- | | v1.0 | 29 June 2026 | NUMTREND Co., Ltd. | Initial Cookie Policy draft. | | v1.0 | 29 June 2026 | NUMTREND Co., Ltd. | Reviewed and approved by NUMTREND — ready for use. |