Skip to content

Cookies Policy

Clear consent, clear controls.

This page explains which cookies and similar technologies ReasyPort uses, which ones are necessary to run the platform, how analytics consent is stored, and how you can reject or change that choice at any time.

Cookie policy version 2026-04-21. Effective from 21 April 2026.

Privacy Policy

How ReasyPort Uses Storage

Essential first, analytics only by consent.

Under GDPR and European cookie rules, storage that is strictly necessary to provide a requested service may run without consent.

Optional analytics should not run until the user has made a valid choice. ReasyPort keeps analytics off until that consent is actively given, and internal service logs are treated separately from optional cookie-based analytics.

The site offers symmetric controls on desktop and mobile: Accept analytics and Essential only are both available directly from the banner, and the footer, this page, and Profile > Privacy can reopen your choice at any time.

Strictly necessary

Security, session integrity, and requested account or platform operations.

Functional storage

Theme, language, saved favorites, watchlists, and similar settings the user chooses to keep locally.

Optional analytics

Google Analytics 4, loaded only if the user actively accepts analytics.

Detailed Register

Cookies and similar technologies currently used by ReasyPort

Strictly necessary

Authentication and session cookies

Examples
Auth.js session cookies and short-lived admin access cookies
Purpose
Keep authenticated areas available, protect account sessions, and preserve requested sign-in flows.
Legal basis
Necessary for the requested service and security-related legitimate interests.
Duration
Session or limited duration, depending on the cookie

Strictly necessary

Privacy preference cookies

Examples
rp_privacy_subject and rp_privacy_consent
Purpose
Remember the privacy subject identifier and the latest analytics choice so optional analytics stays off until the user opts in.
Legal basis
Necessary to honour the user’s privacy preference and document the current choice.
Duration
Up to 12 months for the subject cookie and up to 180 days for the consent state cookie

Functional storage

Local preferences

Examples
report-theme, report-lang, report-avatar, report-username, report-country
Purpose
Remember interface, display, and local profile preferences the user actively selected on this device.
Legal basis
Necessary to provide the setting or function requested by the user.
Duration
Until changed or cleared by the user

Functional storage

Local product state

Examples
Saved watchlists, local report state, and cached company branding where available
Purpose
Keep optional product conveniences locally on the device without sending them to Google Analytics.
Legal basis
Necessary to provide the selected feature or user action.
Duration
Until changed, refreshed, or cleared by the user

Optional analytics

Google Analytics 4 (Google LLC)

Examples
_ga, _ga_<container-id>, _gid, _gat
Purpose
Measure aggregated traffic and broad usage trends only after the user actively accepts analytics. IP addresses are anonymised and Google Signals / ad personalisation are disabled.
Legal basis
Consent
Duration
_ga and _ga_<container-id>: up to 2 years · _gid: 24 hours · _gat: 1 minute. Set only after consent is granted; removed when analytics is refused or withdrawn.

Consent Records

How consent records are stored

First-party consent state

ReasyPort stores the latest analytics choice in first-party storage and in a first-party cookie so the site can consistently keep optional analytics disabled until you opt in again.

Server-side proof of consent

When you update analytics preferences, ReasyPort stores a consent record with the consent source, the policy version, the accepted categories, a pseudonymous subject id, and minimized audit hashes where needed.

Consent records are kept for up to 730 days to document the latest choice history for a limited audit period. The current implementation does not use raw IP addresses in the consent log; it stores minimized hashes when necessary for audit integrity.

Download logs follow a separate retention window of up to 90 days and never contain raw network identifiers — only hashed identifiers are stored. This operational logging is not the same as optional analytics cookies.

Your Choices

Your choices remain available at any time.

Manage consent

You can review and update analytics consent at any time from the footer, from this page, or from Profile > Privacy. The privacy controls remain available even if you are not signed in.

Third-party analytics

When analytics is enabled, Google Analytics 4 may place cookies and process usage data according to Google’s own settings and roles. If you need a support contact about cookie choices, you can write to support@reasyport.com.