Cookie Policy

Cookies are small text files that a website or online service may store on your device. They can recognise a browser or session, remember settings, keep you signed in, protect accounts, measure use and support advertising or conversion measurement.

For simplicity, this policy also uses the term cookies for similar technologies, including local storage, software-development kits, pixels, tags, web beacons, device or browser identifiers, APIs, consent signals, server-side measurement and technologies that derive device or browser fingerprints.

Cookies may be set directly by RIFM as first-party cookies or by another provider as third-party cookies. They may last only for the current session or remain on the device for a stated period.

This policy covers RebelsFunding websites and online services where the CookieYes banner or a link to this policy is displayed. A separate provider may use its own cookies when you leave our website or use an embedded or external service.

RIFM uses CookieYes as a consent-management platform to display cookie information, record your choices and communicate consent signals to supported tools.

Strictly necessary cookies and technologies may operate without consent where they are required to provide a service requested by you, authenticate a user, remember essential security state, maintain a shopping or order process, prevent fraud or meet another permitted purpose.

Functional, analytical, personalisation, advertising and other non-essential technologies are activated only after the consent required by applicable electronic-communications and data-protection law.

You may accept all optional categories, reject them or select individual categories. Refusing optional cookies does not prevent you from accessing the public website, although some personalisation, embedded content, measurement or advertising functions may be limited.

CookieYes may store a consent identifier, your selected categories, the time of the choice, domain information and technical data needed to prove and apply your preferences.

CookieYes: consent banner, preference management, consent records and communication of consent choices to supported technologies.

Google services: services such as Google Analytics, Google Ads, Google Tag Manager, Google Consent Mode and related measurement, conversion, advertising and security technologies where configured.

Stape and server-side measurement providers: server-side tag management, routing, conversion measurement and first-party or server-assisted transmission of events to configured analytics and advertising providers.

Affilbox and affiliate technologies: referral and affiliate identifiers, attribution of orders, commission calculation, campaign analysis and prevention of affiliate misuse.

Security and infrastructure providers: Cloudflare and other hosting, CDN, bot-management, fraud-prevention, performance and cybersecurity providers may use essential identifiers or logs to protect the website and services.

Advertising, social-media and communication providers: social networks, advertising platforms, pixels, chat, community and embedded-content providers may receive events or set their own technologies when the relevant feature or consent category is enabled.

Other providers: RIFM may add, remove or replace analytics, advertising, testing, conversion, affiliate, support, video, communication and security tools. The CookieYes list and the provider's own privacy information give the current operational detail.

Identifiers: cookie ID, consent ID, advertising ID, affiliate ID, session ID, account or order reference, device or browser identifier and pseudonymous user identifier.

Device and network data: IP address, approximate region, browser, operating system, device type, language, time zone, screen and technical characteristics, network and referral information.

Website and event data: pages viewed, buttons or links used, time and duration, navigation path, errors, campaign source, referral page, search terms, form or checkout events and interactions with embedded content.

Conversion and transaction-related data: whether an order, registration or other conversion occurred, the relevant campaign or affiliate source, order value or category, currency and a limited order or transaction identifier. Payment-card data are not placed in analytics cookies by RIFM.

Consent data: selected cookie categories, time and version of the choice, domain, consent status and technical information needed to respect and evidence the choice.

Security and fingerprint signals: combinations of device, browser, network, session and interaction characteristics may be used to recognise a device or connected activity and detect duplicate profiles, account sharing, promotion abuse, payment fraud, chargebacks, bots or other misuse.

Strictly necessary technologies are used to provide a service requested by you, maintain authentication, remember security and consent state, process an order, protect accounts and systems and prevent fraud. Their use is based on the necessity of the requested service, performance of the contractual relationship and RIFM's legitimate interests, together with the applicable exception from cookie-consent requirements.

Functional, analytical, advertising, remarketing and other non-essential technologies are used on the basis of consent where required. Consent is requested through CookieYes before the relevant category is enabled.

Server-side measurement, first-party endpoints or Google Consent Mode do not remove the need to respect your consent choices. RIFM configures these systems so that optional measurement and advertising use the applicable consent signal.

Withdrawal of consent does not affect the lawfulness of processing carried out before withdrawal. Essential security, consent and account technologies may continue where they are necessary and legally permitted.

Some third-party providers act as processors for RIFM, while others determine their own purposes and act as independent controllers. Their own privacy and cookie terms may therefore apply in addition to this policy.

Data collected through cookies and similar technologies may be processed in the European Economic Area and in other countries where providers or their subprocessors operate.

Where a transfer outside the European Economic Area takes place, the relevant provider or RIFM uses an applicable mechanism such as an adequacy decision, Standard Contractual Clauses, another recognised safeguard or a permitted exception.

The use of an advertising or social-media technology may allow the relevant provider to combine website activity with data it already holds about you, subject to your consent choices and that provider's own terms.

Session cookies normally expire when the browser session ends. Persistent cookies remain for the period set in the cookie or until you delete them, withdraw consent or the provider removes them.

The current name, provider, purpose, category and lifespan of detected cookies are shown in the CookieYes interface. The list may change after a scan, technology update, campaign change or replacement of a provider.

CookieYes consent records may be retained for the period reasonably necessary to demonstrate the consent choice, apply preferences and comply with legal obligations. A limited record of withdrawal or objection may be retained to ensure that the choice continues to be respected.

Security identifiers, fingerprints and related logs are not necessarily governed by the lifespan of a browser cookie. They are retained only for as long as reasonably necessary for account protection, fraud investigation, rule enforcement, chargebacks, disputes and legal claims. Records linked to a material investigation or dispute may be retained for up to 10 years.

Third-party providers apply their own retention periods to data held in their systems. RIFM cannot directly delete data controlled independently by another provider, but you may exercise your rights with that provider where applicable.

You may reopen the CookieYes settings at any time and change or withdraw your consent for optional categories.

You may also use your browser or device settings to block or delete cookies. Browser controls differ and may not manage every local-storage, pixel, server-side or device-identification technology.

If you block strictly necessary cookies, parts of the website, login, checkout, security, language selection or account functions may not work correctly.

Deleting cookies can remove your saved preferences and may cause the consent banner to appear again. A preference recorded on one browser or device may not automatically apply to another browser or device.

You may also manage advertising choices through the controls offered by the relevant advertising or social-media provider. These settings are separate from the RebelsFunding CookieYes preference.

Where cookie or similar-technology data relate to an identifiable person, the rights described in the Data Protection and Privacy Policy may apply, including access, correction, erasure, restriction, portability, objection and withdrawal of consent, subject to applicable conditions and exceptions.

You may submit a privacy request through the contact details at the end of this policy. RIFM may need reasonable information, such as the relevant account, browser, consent or order identifier, to locate the data and verify the request.

RIFM may update this policy when cookies, providers, website functionality, consent tools, advertising systems or applicable law change. The current published version applies from the effective date stated above.

The CookieYes list may be updated more frequently than this explanatory policy because it reflects the technologies detected or configured on the website. RIFM aims to review categories and descriptions regularly, but a newly added or changed tool may require a short period before the list is updated.