Cookie Policy

Consent is required for cookies that are not necessary to provide the service you asked for — typically advertising, cross-site tracking and analytics. We do not use any of those. Every cookie below either keeps you signed in, protects a form, remembers a setting you chose, or limits vote abuse on a public board.

If we ever add analytics or anything else non-essential, we will ask for your consent first and update this page.

In development the session cookie is named authjs.session-token without the __Secure- prefix, because that prefix requires HTTPS.

• Paddle— our payment provider and Merchant of Record. When you check out or open the billing portal, Paddle processes the payment and may set cookies for payment processing and fraud prevention. Those are governed by Paddle’s privacy notice, not ours.
• Cloudflare — our domains are served through Cloudflare, which may set a bot-management cookie (for example __cf_bm) to distinguish humans from automated traffic. It is used for security, not tracking or advertising.
• Ad Swap — our public marketing pages show one small advertisement for another independent site, loaded in an isolated frame from ad-swap.web.app. It is a reciprocal exchange between small sites, not an ad network: it receives no information from us and does not track you across sites, though as a separate site it may set cookies on its own domain, which we cannot read. It never appears on a feedback board — only on our own marketing pages.

We embed no social widgets, advertising pixels or session-recording scripts, so no cookies are set by those.

Alongside cookies we store a small amount of data in your browser’s localStorage — for example whether you have already voted on a post, so the button shows the right state immediately. It stays on your device, is not sent to us as a cookie, and clearing site data removes it.

• You can delete or block cookies in your browser settings, or clear site data for our domain.
• Blocking the session cookie will sign you out and prevent you from signing in — it is the mechanism that keeps you authenticated.
• Blocking the language cookie means pages fall back to English.
• Blocking the visitor cookie means your submissions will not share one identity and vote limits will apply per visit rather than per browser.

How we handle the personal data behind these cookies — including your rights and how long we keep session and log records — is set out in the Privacy Policy. Questions about this page can go to privacy@feedboardapp.com.