Cookie Policy

How Ripple uses cookies and browser storage, and how you can control them.

Our current approach

Ripple does not include advertising pixels, visitor analytics scripts or third-party social video embeds. We use browser storage for authentication and requested workflows, and remember an appearance preference when you choose one. There is no advertising or analytics consent to accept on this version of the site.

Storage inventory

Supabase authentication: sb-…-auth-token (including numbered chunks) and sb-…-auth-token-code-verifier

First-party cookies used to sign you in, refresh your session and complete secure authentication. The installed authentication library sets cookies with a maximum lifetime of 400 days; actual session validity is separately controlled by authentication settings. Signing out clears session cookies. Authentication cookies are necessary for the sign-in service you request.

ripple-social-oauth

A first-party security cookie used only when you connect a social account. It expires after 10 minutes and is cleared on callback.

ripple:pending-website:v1

Session storage carries the website you submitted through sign-in and onboarding. It lasts for the browser tab’s session or until the workflow clears it.

ripple:approved-brand-profile-id, ripple:approved-website-id and ripple:campaign-job:…

Session storage remembers your selected brand and active campaign job so the requested workflow can continue. It lasts for the tab’s session; completed campaign jobs clear their marker.

ripple:email-confirmed

A transient local-storage message used to notify another open tab that email confirmation completed. It is removed immediately after sending; a browser messaging channel provides an additional notification path.

ripple:theme

A local-storage value remembers a light or dark theme you explicitly select, until you remove it or clear site data. It is not an advertising identifier. Use the control below to remove it and follow your device appearance instead.

Payments and external services

Stripe Checkout and the billing portal open only when you choose a payment or billing action. Google, GitHub and social account authorisation also open at your request. Those services have their own storage and privacy notices. Their use is not enabled by accepting Ripple’s terms. Hosting infrastructure may use security controls to handle malicious traffic.

Campaign links

Campaign links redirect to the chosen destination with campaign-level UTM parameters. They do not set visitor identifiers or record conversion events. The former ripple_anon tracking cookie is expired when a campaign link is opened. Ordinary hosting security logs may still record requests, as described in our Privacy Policy.

Your choices

You can clear or block site data in your browser. Blocking essential authentication cookies may prevent sign-in. Selecting a theme again saves that preference. We will review consent requirements before adding optional tracking or embeds, and obtain consent before using technologies that require it. See the Privacy Policy for personal information processing.