1. The short version
Cookies are small files a website saves in your browser. Flendy uses a handful, all set by flendy.co itself, to keep you signed in, remember your choices and credit the right creator or ad when you arrive from a link.
We don’t use advertising cookies, analytics cookies or tracking pixels, and no third party sets cookies on flendy.co. Essential cookies are there because the service can’t work without them. Referral cookies are only set when you arrive through an affiliate or recruitment link, only record which link it was, and are never used to follow you around the web. If we ever add optional cookies, we’ll ask first and update this page.
2. The cookies we set
| Cookie | What it does | Type | Lasts |
|---|---|---|---|
sb-…-auth-token | Keeps you signed in (our sign-in provider, Supabase, on our domain). May be split into numbered parts. | Essential | Up to 400 days, renewed while you use Flendy; removed when you sign out |
fl_brand | Remembers which brand you were working on, if your team has more than one. | Essential | 1 year |
fl_connect_state | Protects the step where you connect TikTok, Instagram or YouTube (stops forged requests). | Essential, security | 10 minutes |
fl_rl_… | Remembers that you unlocked a shared report with its code, so you're not asked again. | Essential | 30 days |
fl_spot | Keeps a spotter's private link signed in on their phone. | Essential | 180 days |
fl_aff | Records the creator's referral code when you arrive from an affiliate link, so a later order is credited to them. | Referral | The campaign's referral window, 30 days unless the campaign says otherwise |
fl_rc | Records which recruitment campaign link brought a creator to sign up (campaign tags and the ad click id), so we know which ad worked. | Referral | 30 days |
Every cookie is first-party, sent only over HTTPS, and limited to same-site requests (SameSite=Lax). Our own fl_ cookies can’t be read by page scripts (HttpOnly); the sign-in cookie can, because our pages use it to keep your session fresh.
Our sample version of Flendy, used for demonstrations with made-up people and never with real accounts, uses one more essential cookie, fl_uid(which sample person you’re viewing as, 1 year), in place of the sign-in cookie. flendy.co accounts never get it.
3. Things stored on your device that aren't cookies
- In your browser: small notes in local storage, such as that you dismissed the notifications prompt, the name you typed on an approval link, a campaign draft in progress, or how you arranged a table. They never leave your device.
- In the Flendy app: your sign-in, encrypted with a key kept in your phone’s secure storage, and a cache of screens and filters so the app opens quickly. Deleting the app removes them.
4. Other sites you pass through
When you pay by card, connect a social account or sign in with Google or Apple, you briefly go to Paystack, TikTok, Instagram (Meta), Google or Apple. Those pages set their own cookies under their own policies. Recruitment ads run on Facebook and Instagram; we don’t put a Meta pixel on flendy.co. When a creator signs up from one of those ads, our server tells Meta about the sign-up (see the privacy policy).
5. Your choices
- You can delete or block cookies in your browser settings. If you block essential cookies, you won’t be able to sign in.
- Blocking or clearing
fl_afforfl_rchas no effect on what you can do; the creator or ad just won’t be credited. - Signing out removes the sign-in cookie.
6. Contact
Questions about cookies: privacy@flendy.co. More about how we use data is in the privacy policy.