Політика щодо файлів cookie
How Each4Other™ uses browser storage for core operation, security, preferences, and consent-controlled features.
Last updated: September 1, 2026
1. Necessary browser storage
Each4Other™ uses necessary cookies and similar browser storage to maintain secure sessions, remember language and accessibility preferences, protect forms, record cookie choices, support checkout, and prevent fraud or abuse. The Platform may not work correctly when these technologies are blocked.
2. First-party security device identifier
We set a first-party, random security identifier in a Secure, HttpOnly, SameSite=Lax cookie. It helps detect repeated account or campaign activity from the same browser. The identifier does not contain your name, email address, telephone number, IP address, or payment information, and it is stored by our systems only as a keyed hash.
This control does not use canvas rendering, installed-font enumeration, audio fingerprinting, or other invasive browser-fingerprinting techniques. A shared or reset browser is treated as one signal and is not by itself proof of abuse.
3. Optional technologies
Analytics, embedded services, advertising, or other non-essential technologies are enabled only when they are actually configured and when the applicable consent choice permits them. Available choices can be changed through the cookie-consent interface.
4. Duration and retention
The first-party security identifier may remain in the browser for up to 180 days and can be replaced if it is deleted or invalid. Server-side correlation signals are subject to separate retention limits and are deleted or anonymized when no longer needed, while security decisions and administrator audit records may be retained longer for safety, disputes, and legal obligations.
5. Your controls
You can clear or block browser storage through your browser. Blocking necessary storage may sign you out, reset the security identifier, or prevent protected Platform functions from working. Optional choices can also be changed through the Platform's consent controls.
For more information, see our Privacy Policy or contact us through the Platform support channels.