Cookie Policy

1. What are cookies?

Cookies are small text files stored on your device when you visit a website. Local storage and similar browser technologies work in a comparable way. They help websites remember your session, preferences, and—where you agree—analytics or marketing settings.

2. How Inflyze uses cookies

Inflyze uses cookies and similar technologies to operate the platform — authentication, security, language preference, and core UX. On first visit we show a one-time notice at the bottom of the screen; tap “Got it” to acknowledge. This policy explains what is stored and why.

3. Strictly necessary cookies

These cookies are required for the platform to function. They cannot be disabled in our banner because the service would not work without them.

• authjs.session-token / __Secure-authjs.session-token — Keeps you signed in on the web (NextAuth session). Duration: up to 30 days.
• OAuth state cookies (e.g. ig_oauth_state, kick_oauth_state, twitch_oauth_state) — Short-lived CSRF protection during social account linking. Duration: session / minutes.
• Kick PKCE verifier cookie — Required for Kick OAuth security during connection. Duration: session.
• sidebar_state — Remembers sidebar open/closed preference. Duration: 7 days.

4. Functional cookies

These cookies remember choices you make so the platform works smoothly across visits.

• NEXT_LOCALE — Stores your selected language. Duration: 1 year.
• Onboarding step cookies — May store onboarding progress where applicable.

5. Analytics cookies

If we enable product analytics (e.g. Google Analytics), those cookies help us understand aggregated usage and reliability. They are used only to improve the platform.

• Product analytics (if enabled) — Page views, feature usage, error rates in aggregated form.
• Performance monitoring — Helps us detect outages and slow endpoints.

6. Marketing cookies

If we run advertising or remarketing campaigns, related cookies may measure campaign performance. Details appear here when such tools are active.

• Advertising attribution cookies (if ad booking features are used).
• Remarketing pixels (only if explicitly enabled and consented).

7. Third-party cookies

Some cookies are set by services we integrate with:

• Google — OAuth sign-in (when you choose “Continue with Google”).
• Apple — Sign in with Apple on supported clients.
• Stripe — Payment checkout session (when you top up wallet or pay).
• Pusher — Realtime connection for collaboration messages (when feature is active).

8. Mobile applications

The Inflyze mobile app uses secure device storage (e.g. expo-secure-store) for access and refresh tokens rather than browser cookies. Push notification tokens and language preferences are stored according to your device OS settings and in-app choices.

9. Managing cookies

Because cookies are essential to how Inflyze works, we show a one-time acknowledgment notice instead of granular opt-out controls. You can still control or delete cookies through your browser settings; blocking strictly necessary cookies may prevent login or normal use of the platform.

10. Updates

We may update this Cookie Policy when we add features or change providers. The effective date at the top of this page will change accordingly.