Cookie Policy
Choose whether RinTrade may use analytics cookies and affiliate identifiers. Essential preference cookies remember that choice, while limited cookieless counts and temporary per-tab attribution may still operate.
- Your choice: One measurement control. Turn analytics cookies and eligible affiliate identifiers on or off at any time.
- Preference cookies: Remember the setting. A consent or opt-out cookie records your selection for 365 days.
- Source attribution: Session plus up to 30 days. Browser storage keeps limited campaign or referral context without a visitor ID: per tab for up to 30 minutes after the last page view, and across tabs for up to 30 days only while measurement is on.
Temporary session storage
Scroll horizontally to see all columns
| Stored item | Purpose | Duration |
|---|---|---|
rt_aff_attr_v5 | sessionStorage record of the first touch and the latest non-direct campaign or referral context in this browser tab. It contains no visitor or session ID. | Up to 30 minutes after the last page view, or until the tab closes |
rt_aff_attr_persist_v1 | localStorage copy of the same context so it works in other tabs, plus the latest non-direct source. Written only while measurement is on. It contains no visitor or session ID. | Session context up to 30 minutes after the last page view; latest non-direct source up to 30 days. Deleted when measurement is turned off |
Regional defaults and consent
Outside the EEA, United Kingdom, and Switzerland, analytics storage and eligible first-party affiliate identifiers are enabled by default until you opt out. This default also applies when RinTrade cannot determine a country. In the EEA, United Kingdom, and Switzerland, they remain off until you make an affirmative choice.
Enabling measurement stores rt_aff_consent. An eligible browser redirect to an active affiliate destination may then create rt_aff_vid and rt_aff_sid. HEAD checks, suspected automation or prefetch, inactive-broker fallbacks, admin requests, GPC or DNT traffic, and opted-out requests do not create or use those IDs.
Google Analytics cookies and cookieless signals
RinTrade delivers Google Analytics 4 through Google Tag Manager. When analytics_storage is granted, Google Analytics may set _ga and _ga_<container-id>. Google documents a default expiry of two years for both. Google Tag Manager is the delivery system and does not require a separate RinTrade cookie.
When analytics_storage is denied, Google tags may still send limited cookieless consent and measurement pings. Advertising storage, advertising user data, advertising personalization, Google Signals, and ad-personalization signals remain denied in this implementation.
Permitted analytics may include CTA exposure and affiliate-click events. Google processes these events, and GA4 Daily Export may store raw events in a Singapore BigQuery dataset. Daily export tables are configured to expire after 730 days; delayed exports or expiry setup can keep individual records longer. Temporary activation and impression IDs are event keys, not cookies or persistent identities.
Acquisition attribution in browser storage
The rt_aff_attr_v5 sessionStorage item may keep a valid campaign's source, medium, campaign name, stable campaign ID (utm_id), and content. For an external referral, it keeps only the browser-supplied hostname, never its path, query, fragment, or credentials.
This per-tab record keeps the first touch and latest non-direct touch for up to 30 minutes after the last page view; each page view in the tab extends it. A direct return does not overwrite a recent non-direct touch, and sending a landing event does not clear the record. It expires automatically and is removed when the tab closes.
While measurement is on, the same context is also written to the rt_aff_attr_persist_v1 localStorage item so a page opened in another tab keeps its source. That item also keeps the latest non-direct source for up to 30 days, so a later direct visit can still be credited to it. In the EEA, United Kingdom, and Switzerland it is written only after an affirmative choice. It is deleted when measurement is turned off.
RinTrade does not add a visitor or session ID to this record. It is used only with a later same-origin /go/ request, is not forwarded to the broker, and is separate from the optional identifier cookies. Campaign URLs must not contain personal data or per-user identifiers.
Technical safeguards, providers, and retention
The four rt_aff_* cookies are first-party and use Secure, HttpOnly, SameSite=Lax, and Path=/. Page JavaScript cannot read their values. Visitor and session IDs are random, and affiliate event records store only HMAC-SHA-256 keyed hashes of them. Google Analytics cookies are first-party but are created and read by the Google tag when settings allow it.
When the affiliate service is active, Cloudflare provides the Worker, Queue, and D1 infrastructure. Landing and click events may pass through Cloudflare Queues before D1 storage, with a direct D1 fallback. Messages exclude raw IP addresses, User-Agent strings, full referrers, and broker destination URLs.
Change or withdraw your choice
Open Privacy & cookie settings at any time. Turning measurement off stores rt_aff_optout, deletes rt_aff_consent, rt_aff_vid, rt_aff_sid and accessible Google Analytics cookies, and updates Google Consent Mode. Turning it on stores a fresh consent choice, clears the opt-out, and does not revive old affiliate IDs.
Turning measurement off does not stop every form of measurement. RinTrade may still record identifier-free aggregate landing or redirect events, and limited Google cookieless pings may still be sent. Turning it off deletes rt_aff_attr_persist_v1 but does not clear rt_aff_attr_v5 from sessionStorage; that per-tab source context remains until it expires or the tab closes.
Sec-GPC: 1 and DNT: 1 override regional defaults and a stored opt-in. Requests covered by these signals do not use affiliate visitor or session identifiers.