Privacy Policy

Who we are and how to contact us

RinTrade is operated by Sakkarin Grinara, the controller responsible for the website measurement and correspondence described in this policy. For a privacy question or request, email contact@rintrade.com.

This policy covers RinTrade's website, affiliate redirects, analytics and direct correspondence. Brokers operate their own websites under their own privacy notices. Please do not send broker passwords, payment details or unnecessary identity documents to RinTrade.

What we collect and why

The information depends on how you use RinTrade:

Visiting the site

Page paths, campaign or referral information, approximate country, and interaction information help us understand how readers find and use our content. Google Analytics may also receive page titles, device and browser information, and the IP address sent by your browser.

Following a broker link

We record the broker link, time, page and button location, limited acquisition context and traffic classification to operate redirects, count clicks, detect measurement failures and assess content performance. Eligible redirects may also use first-party visitor and session identifiers according to your region, choice and browser privacy signals.

Contacting us

Your email address, sender name if supplied, message and any attachments are processed to respond to enquiries, investigate corrections or accessibility issues, handle privacy requests and legal notices, or discuss business matters. Share only what is needed for your request.

Your measurement choices

In the European Economic Area (EEA), United Kingdom and Switzerland, Google Analytics cookie storage and affiliate visitor/session identifiers stay off until you opt in. Elsewhere, including when your country cannot be determined, they are enabled by default unless you opt out.

Use Privacy & cookie settings here or in the footer to change your choice at any time. A Global Privacy Control (GPC) or Do Not Track (DNT) signal overrides both a regional default and a saved opt-in.

• Allowing measurement saves your choice for 365 days. Eligible broker redirects may create a visitor cookie lasting a rolling 90 days and a session cookie lasting 30 minutes after activity. Affiliate event records store keyed hashes of those identifiers, not the cookie values.
• Turning measurement off saves an opt-out for 365 days, removes the affiliate consent and identifier cookies, updates Google's consent settings, and deletes accessible Google Analytics cookies. It does not erase records already collected; you can contact us about your data rights.
• Turning measurement off does not stop identifier-free landing and redirect records, or limited campaign/referral context stored in the current browser tab and used for up to 30 minutes after the last page view. Turning it off deletes the cross-tab copy of that context. This context contains no RinTrade visitor or session ID. Google tags may still send limited cookieless consent and measurement pings when analytics storage is denied.

Website analytics and linked click reporting

We use Google Tag Manager to deliver Google Analytics 4 for website reporting. Before passing a page location to the tag, RinTrade removes URL fragments and non-campaign query parameters; an external referrer is limited to its origin. Advertising storage, advertising user data, advertising personalization, Google Signals and ad-personalization signals are disabled in this implementation.

When measurement is permitted, analytics events may include exposure to broker-link buttons and affiliate clicks, with page, content and button metadata. Where permitted Google Analytics data is available, we may match an affiliate click with page views from the same analytics session to understand which pages lead to broker-link clicks. A random activation ID links the click records; it is not an additional persistent visitor identifier. Random impression IDs identify a button exposure within a page view.

Google Analytics daily exports and selected affiliate click records are also processed in Google BigQuery for reporting in Singapore. The affiliate export excludes RinTrade visitor and session hashes, raw IP addresses, raw User-Agent strings, cookie values and broker destination URLs. The linked analysis may still use pseudonymous Google Analytics user and session identifiers; removing RinTrade's hashes from an export does not make all reporting anonymous.

SourceHow Google uses information from sites that use its services

Service providers and international processing

Cloudflare provides the infrastructure for the website. We use Cloudflare Workers to operate affiliate redirects and privacy preferences, and Cloudflare D1 to store affiliate measurement records. Measurement events may pass through Cloudflare Queues before storage. Cloudflare handles requests to deliver and protect these services; the exclusions for our affiliate event table below do not mean that no infrastructure provider processes network request information.

Google provides Google Analytics, Tag Manager and BigQuery for the reporting described above. Our published contact address uses Google's Gmail service, which processes messages and attachments for email delivery and storage. RinTrade uses correspondence to handle the matter you raise; the website's cookie settings do not delete email messages.

These providers may process information outside your country, including the Singapore reporting datasets. Their service terms and privacy information describe their international processing and safeguards. You can contact us for information about the arrangements relevant to your data.

After you follow a broker link, the broker handles data sent by your browser under its own privacy notice. We do not give brokers access to our affiliate event table or private reporting dashboard. RinTrade's campaign attribution parameters are not added to the broker's approved destination URL.

• Cloudflare privacy policy
• Google privacy policy

How long we keep data

Different records have different retention periods. A copy exported for reporting has its own retention period; deletion from Cloudflare D1 does not also delete that copy.

Raw affiliate events in Cloudflare D1

Landing events, click events and limited tracking-failure audit rows are scheduled for deletion after 90 days. Raw landing and click events are deleted only after their daily summary has been completed successfully, so a processing failure can delay deletion.

Daily affiliate summaries

Daily landing and click aggregates are retained for up to 24 months and do not contain visitor or session identifiers.

Affiliate click exports in BigQuery

Selected click-level records copied from D1 are configured to expire after 730 days. This is separate from the 90-day D1 retention period. These exports exclude RinTrade visitor and session hashes and the other fields listed under linked click reporting.

Google Analytics exports in BigQuery

Daily GA4 export tables are configured to expire after 730 days. Individual records may remain longer when a daily export is created later or expiry is applied after table creation. This is separate from Google Analytics' own reporting controls. Search Console reports follow Google's reporting and retention controls.

Browser cookies and temporary context

Preference cookies last 365 days; the affiliate visitor cookie lasts a rolling 90 days and the session cookie 30 minutes after activity. Google Analytics cookies use Google's default two-year expiry when allowed. Acquisition context is used for up to 30 minutes after the last page view in the current tab; while measurement is on, a cross-tab copy keeps the latest non-direct source for up to 30 days.

Legal bases and your rights

Where applicable law requires a lawful basis, we rely on legitimate interests in operating and securing the site, handling enquiries and measuring requested redirects for minimal identifier-free events and default measurement where local law permits it. Consent is used in consent-required regions for Google Analytics cookie storage and affiliate identifiers. Legal obligations may require us to handle or retain a privacy request or legal notice.

You can withdraw consent or opt out through Privacy & cookie settings at any time. Depending on the law that applies, you may have rights to access, correct or delete personal data, restrict processing, receive a portable copy where applicable, or complain to your local data protection supervisory authority. These rights have legal limits and exceptions.

You may also object to processing based on legitimate interests. Email contact@rintrade.com to exercise your rights or raise an objection. Explain your request without sending unnecessary sensitive information. We may ask for proportionate verification where needed, and handle privacy requests within the time limits of applicable law.

Data excluded from affiliate records

Our affiliate event table does not persist the following. These exclusions apply to that table, not to information independently processed by Google, Cloudflare, a broker or our contact mailbox:

• Raw IP addresses or raw User-Agent strings.
• Raw visitor or session cookie identifiers.
• Full external referrer URLs, referrer query strings or affiliate destination URLs.
• Broker account, sign-up, deposit or other conversion data in this version of the system.

Technical details of affiliate measurement

A /go/ request creates a redirect event before sending you to the broker. Landing events record a new campaign, external referral or direct arrival. The browser may retain the first touch and latest non-direct touch in per-tab session storage for up to 30 minutes after the last page view; a direct return does not replace a recent non-direct touch. While measurement is on, a local storage copy shares that context across tabs and keeps the latest non-direct source for up to 30 days. Limited context is attached only to a later same-origin /go/ request.

Eligible redirects can create rt_aff_vid and rt_aff_sid. Identifiers are not used for HEAD checks, suspected automation or prefetch requests, inactive-broker review fallbacks, admin requests, GPC or DNT traffic, or explicit opt-outs. The choice cookies are rt_aff_consent and rt_aff_optout. Campaign values must not contain personal data or per-user identifiers.

• Landing records: random event ID, UTC timestamp, landing pathname, acquisition type, normalized channel, validated source, medium, campaign name, stable campaign ID (utm_id) and content, or an external referrer hostname.
• Redirect records: random event ID and UTC timestamp, broker slug, affiliate link ID and revision, redirect reason, button placement, landing and click pathnames, first/latest acquisition context and touch age.
• Measurement metadata: page locale, target country, country code supplied by Cloudflare where available, traffic classification and classifier version, tracking mode, content ID/type/locale/revision, button variant, ranking position, and random activation or impression IDs where applicable.
• Referrer fields contain only a RinTrade pathname or an external hostname. When identifier measurement is allowed, affiliate records may contain HMAC-SHA-256 visitor and session hashes and the hash-key version.
• Limited failure audits contain a random event ID, UTC timestamp, operation, error class and broker slug to detect missing measurement records; they do not contain the failed request payload.