Cookie Policy

Cookies and local storage are small pieces of data stored in your browser. We use a small number of them to keep you signed in and remember your preferences. We do not run product analytics that identify a device or account; the only usage measurement is cookieless aggregate measurement, described in section 4. This policy is part of, and should be read with, our Privacy Policy.

These are required for the Service to work.

• Authentication (Clerk): session cookies (such as __session and __client_uat) that keep you signed in and secure your session.
• Bot protection (Cloudflare Turnstile): used by Clerk on our sign-in and sign-up pages to tell real visitors from automated ones. It may set its own cookies in your browser as part of that check.

These remember preferences or recent activity on your own device. They are stored in your browser’s local storage and are not sent to an analytics provider or used for cross-site tracking. Clearing local storage resets the corresponding feature on that device.

• theme: your light/dark appearance preference.
• rh:dashboard-sections: which dashboard sections you have collapsed or expanded.
• rh:card-picker-recent-searches: up to three card-search queries you recently used in the call card picker, so you can repeat them on that device. You can clear this list from the picker.

We do not use analytics cookies. We use Vercel Analytics & Speed Insights: aggregate traffic and performance measurement that is cookieless, stores no persistent identifier, and measures page volume and load performance rather than individuals.

After a recognized search-engine visit, we also count signup views, completed signups, and the first successful watch or call save after signup. A session-storage entry,rh:organic-visit:v1, holds the search-engine and landing-page categories, visit start time and completed milestones. It has no unique visitor or account identifier. It expires from use after 30 minutes and is removed when next read after expiry; closing the tab normally clears session storage. Browser session restore may retain it, but does not extend the 30-minute measurement window.

Only category labels and the save type are sent with these events. No account details, card identifiers, search terms or call contents are included. Blocking session storage or enabling Do Not Track disables these additional milestones. They do not connect activity across devices or later visits.

If you used the site while it still ran a product-analytics tool and accepted it then, any leftover ph_* cookies or storage entries in your browser are no longer read by anything and expire on their own; clearing your cookies removes them immediately.

Our sign-in provider (Clerk) sends its own SDK usage telemetry to its servers. That is Clerk measuring its software, not us measuring you: it is not linked to your Rip & Hold activity and we receive nothing from it.

Two things are worth naming here even though they are not analytics. Neither sets a cookie. First, feature activity that is part of the Service itself (publishing a call) is recorded on our servers when the action happens, as part of operating the Service. Second, if something on a page tries to load from a source our security policy blocks, your browser reports it and we record a minimal entry in our server logs; the Privacy Policy describes exactly what that record contains.

We do not use advertising or cross-site tracking cookies, and we do not sell or share your personal information for cross-context behavioral advertising.

You can manage or delete cookies through your browser settings. Because we set no analytics or advertising cookies, there is nothing further to opt out of on the site itself. Blocking strictly necessary cookies may prevent parts of the Service (such as staying signed in) from working.

For more about how we handle personal information, see our Privacy Policy. Questions? Contact us at contact@ripandhold.com.