RiftbotCookie Notice
This notice explains the cookies, browser storage, and similar technologies Riftbot uses, including which are necessary and which require your choice.
Effective August 20, 2026 · Last updated September 14, 2026
1. What these technologies are
Cookies are small text records a website asks your browser to store and return. Local storage keeps information in your browser without sending it automatically with every request. Riftbot also uses optional analytics scripts that send limited usage events when you allow analytics.
2. Your choice
Necessary technologies support sign-in, chat identity, watchlists, security, and your saved privacy choice. They operate when the related feature is used. Optional PostHog and Vercel Analytics remain off unless you select “Allow analytics.” Riftbot does not use advertising cookies, cross-site behavioral advertising, or session replay.
3. Technologies Riftbot uses
| Technology | Category and purpose | Typical duration |
|---|---|---|
riftbot-visitor | Necessary: signed pseudonymous chat identity, security, and request limits | Up to 1 year |
riftbot-watchlist | Necessary: mirrors starred card identifiers for server-side filtering | Up to 1 year |
__convexAuthJWT and __convexAuthRefreshToken, with a __Host- prefix on the live site | Necessary when signed in: authenticates and refreshes your Riftbot session | Up to 7 days |
__convexAuthOAuthVerifier (secure-prefixed on the live site) and temporary Convex Auth OAuth cookies | Necessary during Google sign-in: protects and completes the redirect flow | Removed after sign-in or expired; the verifier cookie lasts up to 7 days |
Local storage: __convexAuth* keys, namespaced to the Convex deployment | Necessary: keeps sign-in state synchronized between pages and browser tabs | Until sign-out or cleared; synchronization metadata remains until cleared |
Local storage: riftbot-watchlist | Necessary: keeps starred card identifiers in this browser | Until you clear it or remove the items |
Local storage: riftbot-onboarding | Necessary: records the completed introduction version | Until you clear it |
Local storage: riftbot-watchlist-imported:* | Necessary after sign-in: prevents repeated anonymous-watchlist imports | Until you clear it |
Local storage: riftbot-analytics-consent | Necessary: remembers whether you allowed or declined optional analytics | Until you change it or clear browser storage |
| PostHog first-party local storage | Optional: pseudonymous product analytics, page use, navigation, and interactions | Only after consent; until withdrawn, cleared, or no longer needed |
| Vercel Analytics script | Optional: cookieless page-view and web-usage measurement | Runs only while analytics consent is enabled |
4. Managing stored information
You can change your analytics choice at any time using “Analytics choices” in Riftbot’s legal navigation. Declining stops future optional analytics on this browser and resets the active PostHog identity. You may also delete cookies and local storage through browser settings. Doing so may sign you out, clear a local watchlist, restart onboarding, create a new chat visitor identifier, or cause this notice to ask for your choice again.
Browser settings can block all cookies, but blocking necessary cookies may prevent sign-in, chat continuity, watchlist filtering, or security controls from working correctly.
5. Related information and changes
The Privacy Policy explains the personal information associated with these technologies, the providers that receive it, retention, and your rights. This notice may change when Riftbot’s features or providers change. The “Last updated” date identifies the current version.