Cookies and consent

What it is

Syndik8 keeps its cookie footprint as small as possible. The web app sets the cookies it needs to keep you signed in and remember a small set of UI preferences, and it shows a one-time consent banner at the bottom of the screen the first time a visitor lands on the site. The banner records the visitor’s choice and disappears.

Who can use it

The banner is shown to every web visitor before they have made a choice — signed in or not, prospect or paying member. iOS and Android apps do not show the banner; cookies are a web concept and the mobile apps do not host a webview that would trigger one.

Where to find it

Web only — the banner overlays the bottom of the viewport on https://app.syndik8.app until accepted or declined.
Documentation site — https://docs.syndik8.app runs the same banner pattern. The marketing site at https://syndik8.app does the same.
The banner is rendered by the CookieConsentBanner widget in the app and is hidden on non-web platforms via the isWebPlatformProvider gate.

Fields / options

The banner has two buttons.

Button	Effect
Accept	Records `accepted` in the local store and dismisses the banner.
Decline	Records `declined` in the local store and dismisses the banner.

The choice persists in SharedPreferences under the cookie_consent key, so it survives reloads and app restarts. There is no nag — once you have answered, the banner does not return.

Behaviour rules

Functional cookies only at launch. Syndik8’s web platforms set cookies that are strictly necessary for the product to work — Supabase Auth’s session cookie keeps you signed in across reloads, and a small number of UI-preference flags (e.g. theme, last-selected syndicate) live in the same store. These are functional cookies and are exempt from consent under UK PECR and EU GDPR.
No analytics or tracking cookies. The marketing and documentation sites use Cloudflare Web Analytics, which is cookieless. No Google Analytics, no Facebook Pixel, no third-party trackers.
Decline behaviour at launch is informational. Because every cookie set today is functional, declining does not change what cookies are set — the banner records the user’s preference for the future. When non-essential cookies are introduced (for example, an opt-in product-analytics cookie), the recorded choice will gate them.
Banner only renders on web. On iOS and Android the consent flow is part of the native onboarding (Terms of Service acceptance) — there is no in-app cookie banner.
Choice is stored per browser, per device. Clearing site data or signing in from a fresh browser shows the banner again.