Skip to content
← Back to home

Cookie policy

This policy explains which cookies and similar technologies are used on ClickOnB.io. The rules depend on where you are: public creator bio pages follow different rules from our own marketing, information and account pages.

1. What are cookies?

Cookies are small text files that websites store on your device. They enable certain features, save your settings or, in the case of marketing cookies, measure your behaviour across pages. In this policy, cookies also include similar technologies such as local storage and pixels.

2. On public profile pages (clickonb.io/yourname)

Our own visitor statistics do not use an analytics cookie. A hashed visitor identifier is generated on the server from the IP address, browser identifier and UTC date to group views and clicks within a day. We also process a browser hash that does not change daily, the device type, referring domain and limited campaign values (source, medium and campaign). These data are pseudonymised, not anonymous. The legal basis is our legitimate interest in measuring reach (Article 6(1)(f) GDPR).

Eligible creators may additionally configure Google Analytics 4 and/or Meta Pixel for their profile. These providers load only after you give separate consent for that profile and its current provider configuration. You can change your decision there through “Creator privacy”. ClickOnB.io’s general browser diagnostics settings are separate. We do not load these creator integrations for embedded or age-restricted profiles. Embedded profiles do not use a separate page-view counter; content clicks may use the shared click counter.

If you activate an embedded OpenStreetMap map, your browser loads content from OpenStreetMap. Map permission is stored separately under map_consent_…locally, without automatic expiry. Links and other content from a creator may lead to external providers. Known campaign and tracking parameters may also be passed to permitted link destinations. This forwarding is separate from our reduced internal statistics.

3. On our own pages

The general choice covers only optional browser diagnostics with Sentry. On our marketing and information pages, it appears when there is no valid current decision. No large banner opens automatically in the workspace, login, payment, support, onboarding or administration areas. You can open the dialog at any time under Account → Privacy in this browser. Public profile pages show only the profile-specific creator choice where needed.

After your current permission, Sentry receives technical error types and code positions, not form contents, user profiles, page addresses or screen recordings. Sentry receives your IP address when your browser connects. The browser SDK does not start on public creator pages or embedded profiles. Server-side error diagnostics are independent of this choice. The native app has its own optional diagnostics setting.

Necessary login, security and saving your decision remain available. Language and appearance are separate local settings. The browser diagnostics choice does not permit any global Google Analytics, Google Ads, Google Tag Manager or Meta integration. Earlier statistics, marketing or preference permissions do not activate this new diagnostics decision.

3.2 Storage for login and settings

We use the following cookies or local storage entries for login, language selection and recording your choice:

NamePurposeProviderRetention period
Authentication session tokenKeeps you signed inClickOnB.io (Supabase)Until you sign out or it expires; tokens may be renewed during use
NEXT_LOCALESaves your language preferenceClickOnB.io1 year
clickonbio.appearanceSaves your appearance preference (local storage)ClickOnB.ioUntil changed or deleted; no automatic expiry
clickonbio_cookie_consent_v1Saves your browser diagnostics decision (local storage)ClickOnB.ioUntil you change it, the consent version changes or you clear browser storage; a refusal is also saved

When you submit a contact form, we remember the submission confirmation for the current browser session. A dismissed PWA installation prompt is also saved locally so it does not reappear on every visit. The PWA stores static application files, fonts and a general offline page in the browser. Account data, API responses and your uploaded media are not included in this PWA cache.

3.3 Storage for optional creator providers

  • cob-creator-<Profile-ID>: a signed cookie that JavaScript cannot read links your browser to the decision for the relevant profile. It applies only to the creator tracking API path and expires after 180 days. A refusal is also saved. The associated server decision also expires after 180 days.
  • cob-creator-pending:… and cob-creator-withdraw:…: local markers block measurements while a choice is being changed and share a withdrawal with other tabs. The pending marker is removed after a successful save. The withdrawal marker has no automatic expiry.
  • Google Analytics 4: after profile-specific statistics permission, Google may use cookies in the separate measurement document. Our integration separates these using a prefix derived from the profile identifier and configuration revision (cob_…_r…), the measurement host and a profile-specific path. We do not set a fixed cookie lifetime in this integration.
  • Meta Pixel: loads only after profile-specific marketing permission. Which provider cookies are set and how long they last depends on the provider integration. We do not promise a fixed lifetime here.

The server decision contains the profile, configuration revision, purposes and timestamps. It is separate from the record of the general browser diagnostics choice, which may also contain IP and browser hashes and, when you are signed in, an account ID. For details about providers and processing, see our privacy policy.

4. Changing your choice

You can allow or withdraw optional browser diagnostics through “Browser diagnostics settings” in the footer of our own information pages or under Account → Privacy in this browser. Withdrawal stops new diagnostic transmissions from the browser.

You can change the separate Google or Meta choice through “Creator privacy” on the relevant profile page. Withdrawal stops the measurement document immediately, even if saving fails. Data already transmitted is not retrieved. You can also delete existing cookies and local storage entries in your browser settings.

5. Third-party cookies during payment

Mollie may set its own cookies during checkout. These are covered by Mollie’s privacy policy. This processing takes place as part of payment processing and is necessary to perform the contract under Article 6(1)(b) GDPR.

6. Further information

For detailed information about data processing, the services used, retention periods and your rights, see our privacy policy.

If you have questions, contact us at: info@clickonb.io


Last updated: 8 October 2026