Repository navigation
Description
Summary
Every self-hosted release from v2.7.0 up to and including today's v2.9.3 writes a persistent unique ID (rybbit-visitor-id) to each visitor's localStorage on the first page load. This happens on every tracked site, including sites that never use feature flags or identify().
For self-hosted installs, this makes the following statements on rybbit.com untrue:
No consent banner needed
Yes, Rybbit is fully compliant with GDPR, CCPA, and other privacy regulations
You will not need to display a cookie consent banner to your users
Storing an identifier on a user's device requires prior consent under Art. 5(3) of the ePrivacy Directive (in Germany: § 25 TDDDG), unless it is strictly necessary for a service the user explicitly requested. That rule covers localStorage exactly like cookies. An ID that only serves feature flag assignment, written on sites that have no feature flags, is not strictly necessary.
Anyone who runs a released self-hosted version and relies on the "no banner" promise is storing an identifier without consent, and carries the legal risk for it. Agencies and site owners choose Rybbit specifically because of this promise.
The fix exists, but self-hosters do not get it
- 2026-09-24: Tracking script always persists a visitor ID in localStorage, which requires consent under ePrivacy / German TDDDG #1221 reports the problem.
- 2026-09-28: the fix lands on master as 63e8198, titled "fix(docs): clarify visitor ID handling for feature flags and consent requirements". The ID is only persisted when feature flags are enabled for the site.
- 2026-10-24: v2.9.2 is released without the fix (one commit, Node update).
- 2026-11-18: v2.9.3 is released without the fix (one commit, dependency updates).
- Rybbit Cloud serves the fixed script today (
app.rybbit.io/api/script.jsonly calls the persisting function inside the feature flag branch).
So the hosted product is fixed, while two consecutive self-hosted releases shipped with a known consent problem. Neither set of release notes mentions it.
There has been no maintainer reply in #1221 at all. Follow-up questions from 2026-10-13, 2026-10-29 and 2026-11-04, from three different users, are unanswered. I am opening a separate issue because #1221 now reads like a fixed bug, while every released version is still affected.
How to verify
- Run the official v2.9.3 images (
ghcr.io/rybbit-io/rybbit-backend:v2.9.3), no feature flags configured. - Open a tracked site in a fresh browser profile.
- DevTools > Application > Local Storage:
rybbit-visitor-idcontains a UUID.
In the script served by v2.9.3 at /api/script.js, the ID is read or created unconditionally during config setup:
function Je(r){let e=`${r}-visitor-id`;try{let t=localStorage.getItem(e);if(t)return t;let n=ce();return localStorage.setItem(e,n),n}catch{return ce()}}
// ...
let i=r.getAttribute("data-namespace")||"rybbit",s=Je(i)The script served by Rybbit Cloud creates an in-memory ID at that point and only persists it inside if (featureFlagsEnabled).
What is needed
- A patch release (v2.9.4) with 63e8198 cherry-picked onto the release line. The commit touches four files.
- Until that release exists: a clear warning in the release notes and the docs that self-hosted v2.7.0 to v2.9.3 require a consent banner.
- A status note in Tracking script always persists a visitor ID in localStorage, which requires consent under ePrivacy / German TDDDG #1221 so affected users know where this stands.
If a patch release is not planned, please say so. Then self-hosters can decide whether to add a banner, patch the script themselves, or wait for v2.10.
Activity
update rybbit to 2.9.3 and also patch for rybbit-io/rybbit#1368