Legal
Cookie Policy
Last updated: June 2026 · Version 2026-06-18.1
This policy lists the cookies and similar storage Oppye uses. We keep it short because Oppye uses very few: at launch we use only what is strictly necessary to sign you in and keep the app working — no analytics, no advertising, no tracking.
What we use today
Supabase authentication / session cookie (strictly necessary) — keeps you signed in across page loads; without it you could not use your account. Set on our domain; expires with your session or when you sign out.
Security tokens (strictly necessary) — protect against cross-site request forgery and keep requests authenticated.
Sidebar layout preference (functional, first-party) — a small value stored in your browser's localStorage to remember whether you prefer the compact sidebar. It never leaves your device and is not used to track you.
Stripe cookies (third-party, payment) — when you upgrade, Stripe Checkout opens on Stripe's own domain and sets cookies for payment and fraud prevention under Stripe's privacy policy. These are necessary to take a payment.
What we do NOT use
No Google Analytics or other third-party analytics, no advertising or re-targeting pixels, no social-media trackers, and no marketing cookies. Because everything we use is strictly necessary or a first-party functional preference, we do not show a consent pop-up that blocks the site.
If this changes
If we ever introduce non-essential cookies (for example privacy-friendly, cookieless analytics, or any marketing technology), we will ask for your consent first through a cookie banner where rejecting is as easy as accepting, we will load those scripts only after you consent, and we will update this policy with the full list before doing so.
Managing cookies
You can delete or block cookies in your browser settings at any time. Blocking the strictly-necessary cookies above will stop you from signing in or completing a payment, so the app will not work properly without them.
Contact
Questions about cookies? Email privacy@oppye.com. See also our Privacy Policy for how we handle personal data more broadly.
