ResurvePrávne centrum

Na tejto stránke

1. What are cookies and similar technologies?2. First-party and third-party technologies2.1 First-party cookies2.2 Third-party cookies and technologies3. Session and persistent cookies4. Categories of cookies and similar technologies we may use4.1 Strictly necessary / essential4.2 Functional / preference technologies4.3 Analytics, product measurement, and performance4.4 Affiliate, referral, and attribution technologies4.5 Marketing and advertising technologies4.6 Security and fraud technologies4.7 Embedded content and third-party functionality5. How cookies may differ across Resurve surfaces6. Business storefronts and Business-added technologies6.1 Resurve-controlled technologies6.2 Business-controlled technologies6.3 Resurve may restrict Business tracking7. Payment and checkout technologies8. Consent and lawful use of non-essential technologies8.1 Consent must be a real choice where required8.2 Withdrawal of consent8.3 Consent may be device- or browser-specific9. Cookie preference manager and live inventory10. Examples of technology purposes11. Analytics providers12. Affiliate and referral attribution13. Do Not Track, Global Privacy Control, and similar signals14. Browser and device controls15. Mobile applications and SDKs16. Location technologies17. Children18. International processing19. Retention20. Changes to providers or technologies21. Changes to this Cookie Policy22. Relationship with the Privacy Policy and Business obligations23. Contact
← Všetky právne dokumenty

Cookie Policy

Posledná aktualizácia 23 August 2026 · Verzia 2

Cookie Policy

Last updated: 23 August 2026

Company: RESURVE LTD, a company incorporated in Mauritius (Company No. 236684; Business Registration Number (BRN) C236684), with registered office at Lot 2, Robert Rey Street, Roches Brunes, Beau Bassin, Mauritius (“Resurve”, “we”, “us”, or “our”).

Contact: legal@resurve.net

This Cookie Policy explains how Resurve uses cookies and similar technologies in connection with:

  • resurve.net;

  • Business storefronts at {handle}.resurve.net;

  • dashboard.resurve.net;

  • affiliate.resurve.net;

  • related Resurve subdomains;

  • embedded booking and checkout experiences;

  • Resurve mobile, tablet, point-of-sale, and web applications where relevant; and

  • other Resurve websites, applications, or Services that link to this Cookie Policy.

This Cookie Policy should be read together with our Privacy Policy, Terms of Service, and Acceptable Use Policy.

Capitalised terms not defined in this Cookie Policy have the meanings given in the Terms of Service or Privacy Policy.

Everyday-language summaries beginning with “Which means” are provided for convenience only. They do not replace, limit, or modify the legal wording of this Cookie Policy.


1. What are cookies and similar technologies?

Which means: Cookies are small pieces of information stored on your device. We also cover technologies that work in similar ways, even if they are not technically cookies.

A cookie is a small text file or data item that a website or service stores on or reads from a browser or device.

Cookies may help a website or application:

  • recognise a browser or device;
  • keep a user signed in;
  • remember settings;
  • maintain a booking or checkout session;
  • secure an Account;
  • prevent fraud;
  • understand how a feature is used;
  • measure referrals or campaigns; or
  • provide other functionality.

For purposes of this Cookie Policy, references to “cookies” or “similar technologies” may also include, where used:

  • local storage;
  • session storage;
  • software development kits (“SDKs”);
  • pixels;
  • web beacons;
  • tags;
  • device identifiers;
  • app identifiers;
  • scripts;
  • link decoration;
  • referral identifiers;
  • browser or device storage;
  • mobile advertising identifiers;
  • server-assisted measurement tied to a browser or device identifier; and
  • other technologies that store information on, access information from, or recognise a browser or device.

Not every technology described in this Policy is necessarily active on every Resurve surface, in every country, or at every time.


2. First-party and third-party technologies

Which means: Some cookies come from Resurve. Others may come from a payment provider, analytics provider, map provider, or another service integrated into Resurve.

2.1 First-party cookies

A first-party cookie is generally set by the website or domain you are visiting.

For example, a cookie set by Resurve while you are using dashboard.resurve.net may be used to maintain the Business-user session, remember a security state, or store a privacy preference.

2.2 Third-party cookies and technologies

Third-party technologies may be provided by another organisation whose service appears in, supports, or is integrated with Resurve.

Depending on the feature, these organisations may include:

  • payment service providers and acquiring partners;
  • fraud-prevention providers;
  • authentication providers;
  • analytics and product-measurement providers;
  • mapping providers;
  • communications providers;
  • customer-support providers;
  • embedded media providers;
  • advertising or campaign-measurement providers, where enabled;
  • social-login providers; and
  • other integrated services.

A third party may process information under its own privacy policy where it acts as an independent controller or equivalent party.

Where Resurve uses a third party as a processor or service provider, the relationship is also governed by the applicable contractual and data-protection arrangements.


3. Session and persistent cookies

Which means: Some cookies disappear when the browser session ends. Others remain until their expiry date or until you delete them.

Cookies can generally be:

  1. Session cookies — designed to expire when the relevant browser or application session ends; or
  2. Persistent cookies — designed to remain for a defined period or until they are deleted.

The duration of a cookie depends on:

  • its purpose;
  • the Resurve surface;
  • the provider setting it;
  • whether the user is signed in;
  • the configuration in use at that time; and
  • applicable privacy or consent requirements.

Where Resurve provides a live cookie-preference manager or cookie inventory, that interface may provide more specific information about active technologies, providers, purposes, and durations.

Because Resurve’s infrastructure and providers may change, a cookie’s exact technical name or lifespan may also change without changing the underlying purpose described in this Policy.


4. Categories of cookies and similar technologies we may use

Which means: We separate cookies by why they are used. Essential technologies keep Resurve working; other categories may require your consent depending on the law that applies.

4.1 Strictly necessary / essential

These technologies are used where reasonably necessary to provide, secure, or maintain a website or Service requested by the user.

They may be used for:

  • authentication;
  • maintaining a logged-in session;
  • account security;
  • multi-factor-authentication state;
  • CSRF and similar security protection;
  • load balancing;
  • traffic routing;
  • fraud prevention;
  • abuse prevention;
  • remembering privacy choices;
  • preserving a booking or checkout session;
  • storing items or selections necessary to complete an initiated transaction;
  • payment security;
  • maintaining secure integration state;
  • preventing duplicate submissions;
  • service availability;
  • session recovery;
  • preventing malicious or irregular traffic; and
  • other functionality that is technically required to deliver a Service expressly requested by the user.

Where applicable law exempts such technologies from consent because they are strictly necessary, Resurve may use them without consent.

Strictly necessary technologies cannot always be disabled through a Resurve preference centre because doing so may prevent the relevant Service from functioning.

Users can still block them through browser or device settings, but doing so may cause:

  • sign-in failure;
  • repeated authentication;
  • checkout failure;
  • booking-flow interruption;
  • loss of saved settings;
  • failure of fraud controls;
  • reduced security; or
  • other functional problems.

4.2 Functional / preference technologies

These technologies may remember choices or provide enhanced functionality, such as:

  • language;
  • locale;
  • region;
  • time zone;
  • light or dark appearance;
  • interface preferences;
  • accessibility preferences;
  • remembered display choices; or
  • other optional settings.

Depending on applicable law and the particular technology, these may be treated as necessary for a requested preference or may require consent or another permitted choice mechanism.

4.3 Analytics, product measurement, and performance

These technologies may help Resurve understand:

  • which pages or screens are used;
  • how users move through booking or onboarding flows;
  • where errors occur;
  • how long pages take to load;
  • whether a feature is used;
  • whether a user completes or abandons a funnel;
  • general usage patterns;
  • campaign or referral performance;
  • reliability;
  • crash and diagnostic information; and
  • how the Services can be improved.

Where enabled, Resurve may use product analytics or measurement providers, including providers such as PostHog, or other providers performing similar functions.

Analytics may involve a first-party identifier, device or browser identifier, session identifier, event information, IP-derived information, or similar technical data.

Where applicable law requires consent for analytics technologies, Resurve will apply the consent mechanism required for the relevant use. In jurisdictions where a lawful exemption or alternative mechanism applies to limited first-party or statistical measurement, Resurve may rely on that mechanism where its conditions are met.

4.4 Affiliate, referral, and attribution technologies

Resurve may use cookies or similar technologies to understand whether a visitor or Business arrived through:

  • an affiliate link;
  • a referral link;
  • a Business link;
  • a marketplace surface;
  • an advertising campaign;
  • an email;
  • a promotional campaign; or
  • another permitted source.

These technologies may be used to:

  • preserve attribution;
  • measure a referral;
  • prevent affiliate fraud;
  • calculate or validate commissions;
  • distinguish Resurve-originated demand from Business-originated demand;
  • avoid duplicate attribution;
  • analyse campaign performance; or
  • maintain source information through a booking or signup flow.

Affiliate and referral cookies are not automatically treated as strictly necessary merely because they support a commercial program.

Where applicable law requires consent before using a non-essential attribution technology, Resurve will apply the required consent mechanism.

4.5 Marketing and advertising technologies

Where Resurve uses advertising or remarketing technologies, they may be used to:

  • measure advertising effectiveness;
  • understand whether an advertisement resulted in a visit or signup;
  • build or measure campaign audiences;
  • limit repeated advertisements;
  • attribute conversions;
  • deliver more relevant advertising; or
  • measure interactions with Resurve marketing.

These technologies may be operated by Resurve or by third-party advertising or measurement providers.

Resurve does not assume that marketing or advertising cookies are strictly necessary.

Where prior consent is required by applicable law, Resurve will not intentionally rely on a user’s mere continued browsing as a substitute for the affirmative consent required by that law.

Where Resurve does not use a particular advertising provider, this Policy should not be interpreted as stating that the provider is in use merely because the category is described here.

4.6 Security and fraud technologies

Security technologies may be used to:

  • detect suspicious sign-ins;
  • identify malicious traffic;
  • detect automated abuse;
  • reduce account takeover;
  • prevent fake bookings;
  • prevent payment abuse;
  • detect unusual device or network behaviour;
  • protect checkout;
  • protect APIs;
  • enforce rate limits;
  • maintain platform integrity; or
  • investigate a security incident.

Some security technologies may process device, browser, network, session, or risk information.

Where a technology is strictly necessary to secure a Service requested by a user, it may fall within the essential category.

4.7 Embedded content and third-party functionality

A page may include functionality supplied by a third party, such as:

  • payment checkout;
  • maps;
  • video;
  • social sign-in;
  • support tools;
  • chat;
  • embedded documents; or
  • other interactive services.

Such third parties may set or access cookies or similar technologies when the functionality is loaded or used.

Where the technology is not necessary and applicable law requires prior consent, Resurve may delay or block the relevant third-party functionality until the required choice has been made.


5. How cookies may differ across Resurve surfaces

Which means: Your Customer session, Business dashboard session, Affiliate session, and internal Resurve session are different contexts. Signing into one does not necessarily sign you into all of them.

Resurve operates multiple audiences and technical surfaces.

SurfaceTypical purposes
resurve.netResurve website, marketplace discovery, public content, Customer features, account or campaign attribution where enabled
{handle}.resurve.netBusiness storefront, booking flow, Customer session, checkout continuity, Business-originated attribution
dashboard.resurve.netBusiness operator authentication, security, account preferences, product analytics where permitted
affiliate.resurve.netAffiliate authentication, security, referral and commission functionality, permitted analytics
ops.resurve.netResurve staff authentication, security, internal functionality, audit and operational controls
embedded booking or checkoutBooking continuity, fraud prevention, payment-provider functionality, session state

Resurve may use separate cookie names, storage keys, authentication domains, and technical configurations for different audiences.

Cross-host authentication should not be assumed. A user may be required to authenticate separately to different Resurve applications.

The fact that two Resurve surfaces share a parent domain does not mean every cookie is available to or used by every surface.


6. Business storefronts and Business-added technologies

Which means: A Business using Resurve cannot add trackers and then automatically make Resurve responsible for the Business’s tracking.

A Business storefront may process cookies or similar technologies placed or controlled by:

  1. Resurve;
  2. a provider integrated by Resurve;
  3. a payment or checkout provider;
  4. a Business through a feature or integration that Resurve permits; or
  5. another authorised service used in connection with the storefront.

6.1 Resurve-controlled technologies

Where Resurve determines the purpose and essential means of a tracking technology, Resurve is responsible for its own obligations under applicable privacy law.

6.2 Business-controlled technologies

Where a Business chooses to enable, configure, insert, or direct a third-party tracking technology for the Business’s own purposes, the Business may act as controller or equivalent responsible party for that processing.

The Business is responsible for determining whether it must:

  • disclose the technology;
  • obtain consent;
  • provide an opt-out;
  • enter into a data-processing agreement;
  • configure the technology in a privacy-preserving manner;
  • honour privacy signals;
  • restrict international transfers;
  • provide Customer rights; or
  • otherwise comply with applicable law.

A Business must not use a Resurve storefront to circumvent cookie, direct-marketing, advertising, surveillance, or privacy laws.

6.3 Resurve may restrict Business tracking

Resurve may technically restrict, block, remove, delay, or disable Business-added pixels, scripts, SDKs, trackers, or integrations where we reasonably believe they:

  • violate applicable law;
  • violate the Terms or AUP;
  • create a security risk;
  • collect excessive Customer information;
  • interfere with checkout;
  • degrade performance;
  • circumvent consent controls;
  • create misleading Customer experiences;
  • undermine locked-storefront trust; or
  • expose Resurve or another person to unreasonable legal or reputational risk.

The availability of an integration or custom-tracking feature does not constitute legal approval of the Business’s use of it.


7. Payment and checkout technologies

Which means: Payment providers may need their own cookies for security, fraud prevention, authentication, and checkout.

Where a Customer uses an embedded, redirected, hosted, tokenised, or otherwise integrated payment flow, the payment provider, acquiring bank, wallet provider, fraud provider, authentication provider, or related service may use cookies or similar technologies.

These technologies may support:

  • payment-session continuity;
  • fraud detection;
  • payment authentication;
  • 3-D Secure;
  • device-risk analysis;
  • transaction security;
  • payment method display;
  • regulatory compliance; or
  • other payment functions.

Some payment technologies may be essential to complete a payment requested by the user.

Payment providers may act as independent controllers for certain processing and may have their own cookie and privacy policies.

Resurve does not control an independent payment provider’s cookies merely because its checkout is embedded in or reached through Resurve.

Blocking payment-provider technologies may prevent a payment from being completed.


8. Consent and lawful use of non-essential technologies

Which means: Where the law requires opt-in consent, non-essential tracking should not be treated as accepted merely because someone opened the website.

Cookie and tracking laws differ by jurisdiction.

Where applicable law requires prior consent for a non-essential cookie or similar technology, Resurve uses or seeks to use an appropriate consent mechanism before the relevant technology is activated.

Where applicable law allows a technology to be used without consent because it is:

  • strictly necessary;
  • requested by the user;
  • used for a permitted security purpose;
  • used under a lawful limited analytics or statistical exemption; or
  • otherwise exempt,

Resurve may use that technology in accordance with the conditions of the exemption.

8.1 Consent must be a real choice where required

Where consent is the required basis, Resurve’s consent process is intended to allow the user to make a meaningful choice.

Where applicable law requires it:

  • non-essential technologies should not be pre-selected as accepted;
  • refusing non-essential technologies should be possible;
  • withdrawing consent should be reasonably accessible;
  • consent should be specific enough for the relevant purposes; and
  • withdrawing consent should not be made materially harder than granting it.

8.2 Withdrawal of consent

Where you previously consented to a non-essential category, you may withdraw that consent through the cookie-preference controls made available on the relevant Resurve surface, where such controls are provided.

Withdrawal affects future use governed by that consent. It does not retroactively make earlier lawful processing unlawful.

Information already lawfully received by an independent third party before withdrawal may remain subject to that third party’s lawful retention obligations.

8.3 Consent may be device- or browser-specific

Cookie preferences may be stored in a cookie or local-storage entry.

As a result:

  • deleting cookies may delete the saved preference;
  • using another browser may require another choice;
  • using another device may require another choice;
  • private browsing may not retain a previous preference; and
  • different Resurve surfaces may not always share the same consent state.

Where Resurve supports account-level synchronisation of privacy preferences, some choices may be associated with the Account instead.


9. Cookie preference manager and live inventory

Which means: The exact technology actually running is more useful than a stale legal document. Where available, the live preference manager should show the current non-essential categories and technologies.

Where Resurve provides a cookie banner, preference manager, or similar privacy interface, users may be able to:

  • accept non-essential technologies;
  • reject non-essential technologies;
  • choose categories;
  • change prior choices; or
  • review information about active technologies.

Where technically available, the live interface or associated cookie inventory may identify:

  • cookie or technology name;
  • provider;
  • purpose;
  • category;
  • whether it is first-party or third-party; and
  • duration or expiry.

The live inventory may change as Resurve adds, removes, replaces, or reconfigures providers.

If a conflict arises between a generic example in this Cookie Policy and a more specific current technology description in Resurve’s live preference manager, the current description should be treated as the more specific technical disclosure for that technology.

This does not allow Resurve to use a technology unlawfully or remove any non-waivable privacy right.


10. Examples of technology purposes

Which means: These are examples of the kinds of things Resurve may need cookies for. They are not a claim that every named technical implementation is active today.

The following illustrates the types of purposes that may appear in a Resurve cookie inventory:

CategoryExample purposeTypical effect if blocked
EssentialAuthentication/sessionUser may be signed out or unable to sign in
EssentialCSRF/security protectionRequests or forms may fail
EssentialBooking/checkout continuityBooking or payment flow may not complete
EssentialConsent-state storageCookie choices may need to be requested again
SecurityFraud/abuse preventionResurve may be unable to safely provide a feature
FunctionalLanguage/localeDefault language or locale may be shown
FunctionalUI preferencesInterface preferences may not persist
AnalyticsProduct usage measurementResurve receives less information about feature performance
PerformanceError or reliability measurementDiagnosis of failures may be reduced
AttributionAffiliate/referral sourceReferral or commission attribution may be unavailable
MarketingCampaign measurement or remarketingAdvertising may be less measurable or less relevant
Third-party serviceMap, payment, media, support functionalityEmbedded feature may not load or may work differently

The exact legal treatment of a technology depends on how it is configured and the law applicable to the user.


11. Analytics providers

Which means: Analytics helps us improve Resurve, but we should not quietly turn analytics into unrestricted advertising tracking.

Where enabled, Resurve may use analytics providers such as PostHog or other providers to understand use of the Services.

Depending on configuration, analytics events may include information such as:

  • page or screen viewed;
  • feature used;
  • event time;
  • session identifier;
  • device or browser type;
  • operating system;
  • approximate region derived from network information;
  • referral source;
  • error or performance information; and
  • account or pseudonymous identifiers where appropriate.

Resurve may configure analytics differently on:

  • public marketing pages;
  • Customer storefronts;
  • Business dashboards;
  • Affiliate tools;
  • internal tools; and
  • authenticated applications.

A provider being used for product analytics does not automatically mean Resurve authorises that provider to use Business Customer Data for unrelated advertising.

Where Resurve acts as processor for identifiable Business Customer Data, use of that data remains subject to the applicable Business agreement and DPA.


12. Affiliate and referral attribution

Which means: If someone reaches Resurve through an affiliate, we may need to remember that source long enough to decide whether a legitimate commission is due.

Resurve may store a referral identifier, campaign identifier, click identifier, or similar information when a person follows an authorised affiliate or referral link.

This information may be used to:

  • identify the referral source;
  • connect a later signup to the referral;
  • validate eligibility;
  • calculate a commission;
  • detect duplicate attribution;
  • prevent self-referrals or fraud;
  • resolve attribution disputes; or
  • report aggregate referral performance.

The duration of attribution may depend on the applicable Affiliate Program Terms and technical configuration.

A cookie or attribution identifier does not guarantee that a commission is payable. Commission eligibility is governed by the applicable Affiliate Program Terms.

Where consent is required for the relevant attribution technology, the referral process remains subject to that consent requirement.


13. Do Not Track, Global Privacy Control, and similar signals

Which means: Browser privacy signals are not all legally equivalent. We honour signals where the law requires us to.

Some browsers, extensions, or devices send privacy signals such as:

  • “Do Not Track” (“DNT”); or
  • Global Privacy Control (“GPC”).

There is no universally applicable legal or technical standard requiring identical treatment of every DNT signal.

Where applicable law requires Resurve to recognise a legally valid opt-out preference signal, including a qualifying GPC signal, Resurve will handle it as required by that law for the processing to which the requirement applies.

A browser privacy signal may not disable technologies that are strictly necessary to provide or secure the Service.


14. Browser and device controls

Which means: You can also manage cookies through your browser or device, but blocking everything can break Resurve.

Most browsers allow users to:

  • view stored cookies;
  • delete cookies;
  • block first-party cookies;
  • block third-party cookies;
  • limit cross-site tracking;
  • clear site data;
  • restrict local storage; or
  • configure privacy protections.

Mobile operating systems may also provide settings for:

  • advertising identifiers;
  • app tracking;
  • location;
  • notifications;
  • device permissions; and
  • other tracking-related controls.

Browser and device controls operate independently of Resurve and may change over time.

If you delete or block cookies:

  • saved privacy preferences may disappear;
  • you may be asked for consent again;
  • authentication may fail;
  • checkout may fail;
  • Resurve may not remember language or other settings;
  • attribution may be lost; or
  • embedded third-party functionality may not work.

Resurve is not responsible for functionality prevented by a user’s browser, extension, privacy tool, network filter, or device setting, except to the extent required by applicable law.


15. Mobile applications and SDKs

Which means: Apps do not always use browser cookies, but they can use SDKs, app identifiers, or device storage for similar purposes.

Where Resurve offers a mobile, tablet, POS, or other installed application, similar technologies may include:

  • SDKs;
  • application storage;
  • app-instance identifiers;
  • device identifiers;
  • crash-reporting tools;
  • notification tokens;
  • authentication tokens;
  • analytics identifiers; and
  • security signals.

These technologies may be used for the same broad purposes described in this Cookie Policy.

Device-level settings may provide additional controls for:

  • notifications;
  • location;
  • advertising identifiers;
  • tracking;
  • camera;
  • photos;
  • Bluetooth; or
  • other permissions.

A permission requested by an application should be interpreted according to the feature requesting it and the related Privacy Policy disclosures, not as blanket permission for unrelated processing.


16. Location technologies

Which means: Approximate location can come from an IP address; precise device location generally requires a separate device permission.

Resurve may infer an approximate location from:

  • IP address;
  • language;
  • time zone; or
  • similar network or device information.

Where a Resurve feature requests precise device location, the user may be asked to grant a device or browser permission.

Precise location permission is separate from ordinary cookie consent.

A Business that uses a separate vehicle tracker, telematics device, camera, or other monitoring technology is responsible for its own obligations as described in the Privacy Policy and Acceptable Use Policy.


17. Children

Which means: Resurve is not designed as a child-directed tracking service.

Resurve Business and Affiliate Services are not directed to children.

Where Resurve knows that a surface is likely to be accessed by a child and applicable law imposes special rules on cookies, targeted advertising, consent, or profiling involving children, Resurve will apply those rules where required.

Businesses must not use Business-added tracking technologies on Resurve storefronts to unlawfully profile, target, or monitor children.


18. International processing

Which means: A cookie provider may process data outside Mauritius or outside your home country.

A cookie or similar technology may result in information being processed by a provider located outside the country from which a user accesses Resurve.

International transfers of personal data are addressed in the Privacy Policy.

Where a third-party provider acts independently, its own international-transfer practices may also apply.

A Business enabling its own third-party tracker is separately responsible for international-transfer obligations relating to that Business-controlled processing.


19. Retention

Which means: Cookies should not last forever just because technically they can.

Cookie and similar-technology lifetimes vary according to purpose and configuration.

Resurve considers factors such as:

  • whether the technology is session-based;
  • the reason it is needed;
  • security requirements;
  • whether a shorter duration will achieve the purpose;
  • legal or regulatory requirements;
  • provider defaults;
  • fraud-prevention needs;
  • consent duration;
  • attribution rules; and
  • whether the user has withdrawn consent.

Session cookies generally expire at the end of the relevant session.

Persistent technologies remain until:

  • their configured expiry;
  • they are deleted by the user;
  • the user withdraws consent and the technology is removed or disabled where applicable;
  • Resurve or the provider changes its configuration; or
  • they are otherwise cleared.

Where Resurve provides a live cookie inventory, the current duration of a particular technology may be shown there.

Consent itself may need to be refreshed from time to time under applicable law, regulatory guidance, technical changes, or where the purposes or providers materially change.


20. Changes to providers or technologies

Which means: Our technology stack will evolve. We do not need to rewrite the entire legal framework every time an analytics vendor is replaced, but material privacy changes still matter.

Resurve may:

  • add a technology;
  • remove a technology;
  • replace a provider;
  • change a cookie name;
  • change a technical implementation;
  • change a duration;
  • move from a cookie to another permitted storage technology; or
  • reconfigure an integration.

We may update the live cookie inventory or preference manager as these changes occur.

Where a change introduces a materially different processing purpose or legally requires renewed consent or additional notice, Resurve will provide the required choice or notice.

A purely technical change that does not materially change the stated purpose or privacy impact may not require separate notice beyond updating the relevant technical inventory.


21. Changes to this Cookie Policy

Which means: We may update the Policy when our stack, Services, or the law changes.

We may update this Cookie Policy to reflect:

  • changes to the Services;
  • changes to tracking technologies;
  • changes to providers;
  • changes to consent requirements;
  • security changes;
  • product changes;
  • new Resurve surfaces;
  • changes to applicable law or regulatory guidance; or
  • other legitimate operational changes.

The “Last updated” date at the top identifies the most recent revision.

Where applicable law requires notice or renewed consent for a particular change, Resurve will provide that notice or seek that consent.


22. Relationship with the Privacy Policy and Business obligations

Which means: This Policy explains tracking technologies. The Privacy Policy explains the broader use of personal data. Businesses still have their own obligations for trackers they control.

The Privacy Policy provides additional information concerning:

  • categories of personal data;
  • purposes of processing;
  • legal bases;
  • Business and Resurve controller/processor roles;
  • disclosures;
  • international transfers;
  • retention;
  • security;
  • individual rights; and
  • contact information.

Nothing in this Cookie Policy:

  • makes Resurve responsible for an independent Business’s tracking choices;
  • makes Resurve responsible for an independent third party’s privacy practices;
  • authorises a Business to place a technology unlawfully;
  • guarantees that a third-party feature will function if cookies or tracking are blocked;
  • creates a warranty that every browser or third-party provider will honour a preference exactly as expected;
  • converts a non-essential technology into a necessary one merely because a Business prefers to use it; or
  • limits a non-waivable privacy right.

Businesses using Resurve are responsible for ensuring that Business-controlled cookies, pixels, integrations, or similar technologies comply with applicable law.


23. Contact

Questions about this Cookie Policy or Resurve’s use of cookies and similar technologies may be sent to:

RESURVE LTD
Company No. 236684
Business Registration Number (BRN) C236684
Lot 2, Robert Rey Street
Roches Brunes, Beau Bassin
Mauritius

Email: legal@resurve.net