RELAY2 TECHNOLOGIES, INC. / 2026-10-17
Cookies & Link Tracking
Effective date: October 17, 2026
Last updated: October 19, 2026
1. Redirects are separate from accounts
Following a Relay2 short link does not create an account or consent to optional tracking. Relay2 Technologies, Inc. remains responsible for information it processes while delivering and securing the redirect. Contact support@relay2.app for privacy questions. This notice explains the cookies, similar technologies, and logs Relay2 uses on relay2.app and when you open a short link on rly2.link. The Privacy Policy explains how Relay2 handles the information they collect.
2. Basic redirects
Basic redirects work without cookies or other identifiers stored on your device. To deliver a redirect, Relay2 processes the request your browser sends, including your IP address, and records a click with the time and the approximate region, device type, and traffic source. Relay2 does not use advertising pixels, returning-browser recognition, or cross-link profiling on redirects.
Request logs. Relay2 and its hosting and network providers record request logs, including IP addresses, to operate and secure the Service. These logs involve no storage on your device. Relay2 keeps raw redirect logs for 30 days and security logs for 90 days.
3. Essential and optional storage
Relay2 uses cookies and local storage for account sign-in, ownership of links created before sign-in, appearance preferences, and creator media-kit drafts, as listed below. Account storage is separate from short-link visitor measurement. Local storage does not automatically expire like a cookie; its removal conditions are listed in the table. Clearing site storage can sign you out and remove unsaved drafts or access to unclaimed links. Relay2 does not use fingerprinting or other techniques to recognize a device after you decline or delete cookies. Relay2 does not offer returning-visitor or unique-visitor measurement on short links. Optional Google Analytics (GA4) may load on marketing pages only after you accept analytics cookies; it is not used on account workspace pages or on rly2.link redirects. Relay2 does not respond to browser Do Not Track signals because no common standard exists.
4. Affiliate destinations
A link may pass creator affiliate identifiers and campaign parameters to a configured merchant or network. The destination may receive browser information and use its own technologies under its own policies. Your Relay2 settings do not automatically configure a destination's preferences. Relay2 remains responsible for its own processing.
5. Technologies Relay2 uses
The table lists application-defined cookies, browser storage, and server logs. Marketing-page Google Analytics loads only after consent (see the table). Relay2 does not initialize Google Ads or Meta Pixel in this build. Basic redirects do not read or set visitor cookies. Existing legacy relay_vid cookies are ignored; they may remain in a browser until they expire or you clear them. Relay2 updates this notice when technologies change. Contact support@relay2.app with questions.
| Name / technology | Provider | Where used | Purpose | Category | Duration | Your choice |
|---|---|---|---|---|---|---|
| relay_session (cookie) | Relay2 | Account API; never issued by the redirect route | Account authentication | Essential | 30 days; cleared on sign-out | Required for cookie-based sign-in |
| relay_anon (cookie) | Relay2 | Link-creation API; never issued by the redirect route | Connect links you create before sign-in to your account; not a click-visitor identifier | Essential | 30 days; cleared after a successful account claim | Used when creating links before sign-in |
| relay_session_token (local storage) | Relay2 | App/sign-in origin | Account authentication token | Essential | No automatic browser expiry; removed on sign-out or browser storage clearing. Server session validity is separate. | Sign out or clear site storage |
| relay_anon_owner (local storage) | Relay2 | App origin | Recover and claim links created before sign-in | Essential | No automatic expiry; removed after successful claim or site-storage clearing | Claim links or clear site storage |
| relay_theme (local storage) | Relay2 | App and sign-in pages | Remember your selected light/dark appearance | Preference | Until site storage is cleared or preference replaced | Change theme or clear site storage |
| relay-kit-draft:<account ID> (local storage) | Relay2 | Media-kit editor | Save a creator's draft on this browser | Functional | Until successful kit generation removes the draft, or site storage is cleared | Clear site storage to remove saved drafts |
| Legacy sessionStorage keys: relay_session_token, relay_anon_owner | Relay2 | App origin | Migrate older sign-in/link-owner storage to local storage | Essential | Removed when migrated; otherwise the browser's page session | Sign out or clear site storage |
| Request logs (server-side) | Relay2, Amazon Web Services | App/API and redirect infrastructure | Operations and security; no device storage | Operational | 30 days raw redirect logs; 90 days security logs | Not applicable |
| relay_marketing_analytics_consent (local storage) | Relay2 | Marketing pages on relay2.app | Remember Accept/Decline for optional analytics | Preference | Until cleared or replaced | Change choice by clearing site storage or contacting support |
| _ga / _ga_* (cookies) | Google Analytics (GA4) | Marketing pages only, after Accept | Measure marketing traffic for Search Console and Ads | Optional analytics | Up to 24 months (Google default) | Decline analytics cookies or clear site cookies |