relay2Back to app ↗

Cookies & Link Tracking

1. Redirects are separate from accounts

Following a Relay 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.

2. Proposed launch baseline

Basic redirects should work without persistent visitor cookies. Limited operational processing and appropriately minimized counts are separate from optional returning-browser recognition, advertising pixels, or cross-link profiling. This is the approved design direction, not a verified description of all current infrastructure.

3. Essential and optional storage

Authentication, security, and privacy-preference storage must be documented separately from optional analytics. Optional recognition or advertising must have appropriate notice and controls before activation. No fingerprinting should be used to circumvent a person’s choices. Returning-visitor metrics must disclose their measurement limits.

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. Relay choices do not automatically configure a destination’s preferences. Relay remains responsible for its own processing.

5. Inventory required before publication

For every deployed cookie or similar technology, record name, provider, domain, purpose, category, duration, recipients, and activation/withdrawal controls. Include CDN/server logs and conversion callbacks, not only browser cookies. No cookie inventory or working preference manager is represented by this draft.