Skip to Main Content

Client debug ships on Free, Pro, and Max. See Features

Legal / Cookies

Cookie Policy

Last Updated April 30, 2026

This Cookie Policy explains how FeedBlox uses cookies and comparable technologies when you visit our marketing site, sign in to the dashboard, or load the embeddable feedback widget on a customer site. It supplements our Privacy Policy.

What Cookies Are

Cookies are small text files stored on your device by your browser. We also use comparable browser storage (such as localStorage and sessionStorage) for preferences and short-lived state. Where this policy refers to "cookies," it includes those technologies.

What We Use, and Why

  • Strictly necessary: sign-in and security. A first-party session cookie (better-auth.session_token, prefixed __Secure- on HTTPS) identifies your authenticated dashboard session. It is HTTP-only, uses SameSite=Lax, and is marked Secure on HTTPS. Without it, the dashboard cannot work. It is cleared when your session ends or when you sign out.
  • Functional: interface preferences. The dashboard may use localStorage to remember the last selected workspace site and similar UI state.
  • First-party product analytics (optional). When OpenPanel is enabled for a deployment, the marketing site and dashboard load a first-party script from our domain and may store a first-party analytics identifier. We do not use advertising cookies.
  • Advertising. FeedBlox does not use third-party advertising cookies on our marketing site or dashboard, and the embeddable widget does not set advertising cookies.

The Widget on Customer Sites

Our widget loads from app.feedblox.net when a customer embeds it on their site. The widget itself does not set advertising or cross-site tracking cookies. It may write a short-lived first-party preference (for example, to remember that a visitor has dismissed the widget) using browser storage. Customers are responsible for ensuring their own cookie notices and consent flows cover the widget where required.

Third-Party Sign-In

If you sign in via a federated provider (for example, GitHub or Google), that provider may set its own cookies on its domain when its pages load. Those providers' cookie practices are governed by their own policies.

Your Choices

Most browsers let you block or delete cookies, refuse third-party cookies, or be alerted when a cookie is set. Blocking strictly necessary cookies will prevent you from signing in. We respect Global Privacy Control (GPC) signals where required by law as a request to opt out of sale or sharing of personal information; because we do not sell or share personal information, no further action is required for that purpose.

Changes

We may update this Cookie Policy when our practices change. The Last Updated date at the top reflects the latest revision. For material changes that affect how cookies are used to process personal information, account owners will be notified consistent with our Privacy Policy.