Cookies Policy
Short version: this site uses no third-party cookies. The mobile apps store a login token in OS-protected secure storage.
What is a cookie?
A cookie is a small file your browser stores when you visit a website. Cookies can be first-party (set by us) or third-party (set by advertisers, analytics providers, etc.).
Cookies on skillflirt.com
The marketing site you're reading right now sets no cookies of any kind. No analytics, no advertising, no remarketing pixels.
Cookies on skilldash.skillflirt.com
The admin dashboard stores a single session token in
browser localStorage (not a cookie) when an
administrator signs in. It's named skillflirt_admin_token
and is cleared when they sign out or when the 12-hour session
expires.
"Cookies" inside the mobile apps
The Android and iOS apps don't use cookies. They store the following in OS-protected secure storage (Keychain on iOS, Keystore on Android):
- Your session token (so you stay logged in)
- Your onboarding-complete flag
- Your last-seen feature-flag values (for offline UX)
Clearing the app's data from your device's Settings deletes all of the above.
Analytics
In-app usage events are sent to PostHog (EU region). PostHog is configured without cookies — it identifies sessions via a randomly generated installation ID stored locally on your device. No cross-site tracking is possible. You can disable analytics in Settings → Notifications → Anonymous analytics.
Payment processing
When you reach a Stripe-hosted checkout page (after tapping a
Premium or coin-pack button), Stripe sets its
own cookies on stripe.com for fraud prevention.
Those cookies are governed by
Stripe's cookie
policy, not ours. They're set on the
stripe.com domain, not on skillflirt.com,
and can't be read by our code.
Changes
If we ever add a cookie that does anything beyond keeping you logged in, you'll get an in-app banner with explicit opt-in first. We won't slide things in silently.
Related: Privacy Policy · Privacy & Security