Cookies

EyeRise uses cookies and similar technologies so checkout, referrals, and (when enabled) site analytics can work. The desktop app does not use third-party advertising trackers.

• eyerise_ref (HttpOnly, about 30 days) — referral or creator code from a /r/ link so checkout can attribute a subscription
• eyerise_ref_pub (readable, about 30 days) — same referral code for the browser so the site can show or reuse it
• eyerise_vid (HttpOnly) — an anonymous visitor key used with referral attribution
• eyerise_partner_code, eyerise_invite_token, eyerise_attribution_source, eyerise_patient_email (about 90 days, readable) — invite or partner attribution when you arrive from those links
• Session or local storage for a creator dashboard token after you confirm your email

Marketing pages may load Google Analytics 4 when a measurement ID is configured. Those tools typically set cookies such as _ga. Analytics is for understanding how the marketing site is used — not for selling your browsing history.

Stripe Checkout and the Stripe customer portal are hosted by Stripe and may set their own cookies on stripe.com. EyeRise does not store full card numbers.

You can block or delete cookies in your browser. Blocking referral cookies may mean we cannot attribute a creator or friend link. Blocking analytics cookies (or using a browser that rejects them) simply reduces how we measure the marketing site.

The EyeRise desktop app does not embed third-party advertising trackers.

Questions: support@geteyerise.com

See also our Privacy Policy.