Cookie Policy
Effective September 17, 2026 · Last updated September 17, 2026
1. What cookies are
Cookies are small text files placed on your device by websites you visit. They allow a website to recognize your device and store information about your visit — for example, your sign-in state or display preferences. Local storage and similar technologies (sessionStorage, IndexedDB) work similarly and are covered by this policy.
2. How meetsage.io uses them
We keep our use of cookies intentionally minimal. The marketing site (meetsage.io) sets only what's needed to make the site work and, if you choose to allow optional cookies, to measure referral activity:
Strictly necessary — the /admin and /delete-account pages use Supabase's auth cookies and local storage to keep you signed in for the length of your session. These are required for the page to function and cannot be disabled.
Referral attribution — when you allow optional cookies, FirstPromoter may set a first-party cookie and an invited partner clicking a referral link (e.g. /r/CODE) may cause us to store the code in localStorage so we can attribute the eventual sign-up to the right partner. The FirstPromoter script is not loaded before you make an optional-cookie choice. Referral codes are cleared once attribution is sent or after 30 days, whichever comes first. You can reject optional cookies without losing access to the marketing site.
We do not use analytics or advertising cookies on the website at this time. If we add other optional technologies in the future, we will update this policy and request consent before loading them.
3. Third parties that may set cookies
If you sign in to /admin, Supabase Auth (our authentication provider) sets cookies on this domain to manage your session. If you allow optional cookies, FirstPromoter may set a first-party cookie to record a referral click. The FirstPromoter script is not loaded until you allow optional cookies. No third-party advertising cookies are set.
4. Inside the mobile app
The Sage iOS and Android apps don't use browser cookies — they use on-device storage (AsyncStorage / Keychain / Keystore) to remember you between launches. The app does not include any third-party advertising SDKs. AppsFlyer, when enabled, is used only to attribute installs from referral links and measure coarse product events in a non-tracking configuration; it does not track you across other apps when that configuration is maintained.
5. iOS install handoff
When you tap an App Store badge from a private invite or referral page, the page may write a short sage-invite:<token> or sage-referral:<code> value to the clipboard. The Sage app checks only for those exact formats on its first launch and clears a matching value after reading it. This is a user-triggered install handoff, not a general clipboard reader; unrelated clipboard contents are ignored and are not sent to Sage or AppsFlyer.
6. How to control cookies
You can clear or block cookies through your browser settings, reject optional cookies in the Sage consent bar, or reopen the choices from the "Cookie settings" link in the site footer. Blocking required storage will sign you out of /admin; rejecting optional cookies may prevent referral attribution from working correctly. Browser-level "Do Not Track" signals are honored where applicable.
7. Changes to this policy
We may update this Cookie Policy from time to time. Material changes will be highlighted on this page and, where appropriate, communicated via email or in-app notice. Your continued use of the Service after changes become effective constitutes your acceptance.
8. Contact
Questions about cookies or other tracking technologies? Please contact:
Otto Research Labs LLC
support@ottoresearch.io
Salt Lake City, Utah, United States