Cookie policy

Last updated October 13, 2026

This page covers two separate things: the cookies we set on our own website and dashboard, and the storage the Rupt SDK and challenge pages use when they run for a customer.

Cookies on rupt.dev and the dashboard

Strictly necessary. Authentication and session cookies that keep you signed in to the dashboard, the cookie that remembers your selected project and theme, and the cookie that records your cookie preferences. These cannot be turned off without breaking the site.

Analytics. Google Analytics (_ga, _gid) and PostHog, used to understand how the site and dashboard are used and to diagnose bugs. PostHog may record sessions on these properties.

Advertising. Google Ads conversion tracking (_gcl_aw and related), used to measure which campaigns lead to signups. We do not use it for personalised advertising.

You can accept or decline analytics and advertising through the cookie banner and change your mind at any time from the same control. In the European Economic Area, the United Kingdom and Switzerland, analytics and advertising storage are denied until you choose otherwise. We do not currently respond to Do Not Track signals.

Storage the Rupt SDK uses on customer sites

When Rupt runs on a customer's site, it uses two pieces of storage. Neither is used for advertising, and neither is readable by any site other than the one it was set on.

A session cookie named rupt_sid, set on the Rupt API domain. It is HttpOnly, Secure, SameSite=None and Partitioned, so the browser keeps a separate copy per top-level site and it cannot recognise anyone across different sites. It expires after one hour of inactivity.

A local record of the last challenge shown to the person, named rpt_last_challenge, so that a completed challenge is not repeated. It is kept in browser local storage where available and otherwise in a first-party cookie that expires after one year. It holds a challenge identifier, not an identifier for the person.

Because this storage is set in the context of our customer's site, describing it in their own cookie notice and deciding whether to seek consent for it belongs to them. We treat it as strictly necessary for fraud prevention and account security.

Challenge pages

The challenge pages that end users see carry no analytics, advertising tags or session recording. They keep one local storage flag so that the evaluation on that page runs once.

Questions

Write to support@rupt.dev.