Cookie Policy
What we store on your device, and why. The short version: only what's needed to keep you signed in — no ad or tracking cookies.
Last updated: 26 juin 2026
This policy explains how Guillaume SEVRIN uses cookies and similar technologies on https://flowjat.com. We've tried to keep it plain and honest, because that's how we'd want it explained to us.
Flowjat is an early-stage product. As of 26 juin 2026, the only cookies we set are strictly necessary ones used to keep you authenticated. We do not use advertising cookies, cross-site tracking, or third-party analytics cookies on this site or in the app. We do use a cookieless product-analytics tool (PostHog, EU Cloud) to understand usage — it sets no cookie and stores no tracking identifier on your device, which is why it is not listed below; see our Privacy Policy for details.
What is a cookie?
A cookie is a small text file a website stores in your browser. It lets a
site remember things between page loads — for example, that you've
already signed in. "Similar technologies" such as localStorage work the same way: they keep a little data on
your device so the app behaves correctly. Where we mention "cookies"
below, we mean both.
The cookies we use
We rely on strictly necessary cookies only. These are required for the service to function — without them, you simply could not stay signed in. Under the ePrivacy rules, strictly necessary cookies do not require prior consent, but we still list them in full here.
These cookies are set by Supabase Auth, the authentication system that powers
sign-in for Flowjat. They contain the tokens that prove you are
logged in. The exact names may carry a project-specific prefix in your
browser (for example sb-<project>-auth-token).
| Cookie | Type | Purpose | Duration |
|---|---|---|---|
sb-access-token | Strictly necessary | Short-lived authentication token from Supabase Auth that keeps your session active while you use the app. | Session / ~1 hour, then refreshed |
sb-refresh-token | Strictly necessary | Lets Supabase Auth renew your access token so you stay signed in without re-entering your password on every visit. | Persistent, until you sign out |
On the public marketing pages — the ones you can read without an account — no cookies are set at all until you sign in.
What we don't use
We want to be specific about this, because it's the part that matters most for your privacy:
- No advertising cookies. Flowjat helps you manage your own ad campaigns, but we do not place ad-targeting or retargeting pixels on our own site.
- No third-party tracking cookies. We do not embed social trackers or cross-site tracking scripts that follow you around the web.
- No third-party analytics cookies at this stage. If we ever add privacy-respecting analytics, we will update this page and, if consent is required, ask for it first.
Because we currently set strictly necessary cookies only, we do not show a consent banner. If that changes, we'll introduce one and update this policy before any non-essential cookie is set.
Connecting your ad and revenue accounts
When you connect an ad platform (such as Meta, Google Ads, TikTok, Snapchat, or Apple Search Ads) or a revenue tool (such as Stripe, Paddle, or RevenueCat), Flowjat talks to those providers through their official APIs to read your campaign and revenue data. That happens server-side and does not place additional cookies in your browser through Flowjat. Those providers have their own cookie and privacy policies, which apply when you visit their websites directly.
Managing and deleting cookies
You're always in control of cookies through your browser. Note that because our cookies are strictly necessary, deleting them will sign you out of Flowjat and you'll need to log in again.
- Sign out: the simplest way to clear your Flowjat session cookies is to use the sign-out option in the app.
- Delete cookies manually: open your browser settings and clear cookies and site data for flowjat.com.
- Block cookies: most browsers let you block cookies entirely. If you block ours, the app will not be able to keep you signed in and core features will not work.
The major browsers document this here:
Changes to this policy
If we start using new cookies — for example optional analytics — we'll update this page, revise the "Last updated" date above, and, where the law requires consent, ask for it before those cookies are set.
Related documents
This policy sits alongside our broader explanation of how we handle your data:
- The Privacy Policy explains what personal data we collect, why, and the rights you have over it.
- The Subprocessors page lists the third-party services we rely on to run Flowjat.
Questions
If anything here is unclear, or you'd like to know more about how we use cookies, reach us at privacy@flowjat.com.