Cookies English only

Cookies and Browser Storage

What Shuuka stores in your browser, why it is there, and how app-level third-party consent works on public profiles.

Updated

13 March 2026

Covers first-party cookies, browser storage used by profile analytics, and consent storage for profile apps.

Site model

First-party session, preference, analytics, and app-consent storage

Advertising cookies

Not used on Shuuka marketing pages

Profile apps

Some apps can connect to third parties and may be gated behind consent before they load

Contact

[email protected]

1. Overview

Cookies are only one part of the story

Shuuka uses both cookies and similar browser storage such as localStorage or sessionStorage. We group them together here because, from your perspective, they all store state in your browser and affect how the service remembers you, secures your session, measures profile activity, or respects app-level privacy choices.

2. Purpose

Why Shuuka uses browser storage

To keep you signed in and protect authenticated requests.
To remember product preferences such as language, theme, or dashboard layout.
To operate first-party public-profile analytics and session continuity on Shuuka profiles.
To remember whether you accepted or declined a consent-gated app on a public profile.

3. Storage list

Storage used by Shuuka

Name	Type	Purpose	Typical lifetime
`shuuka_session`	Cookie	Keeps the Laravel web session active for signed-in use and session continuity.	Session
`XSRF-TOKEN`	Cookie	Helps protect forms and API requests against CSRF attacks.	Session
`bearer_token`	Cookie	Supports authenticated API calls for signed-in dashboard use.	Up to 30 days, unless cleared earlier
`locale`	Cookie	Remembers your selected language.	Up to 1 year
`theme`	Cookie	Remembers your light or dark theme preference.	Up to 1 year
`sidebar_expanded`	Cookie	Remembers dashboard sidebar state.	Up to 1 year
`session_id`	sessionStorage / localStorage	Stores the current profile analytics session identifier on public profiles.	Usually the active browser session
`device_hash`	sessionStorage / localStorage	Stores the current analytics device or session reference returned by the Shuuka API for a public profile.	Usually the active browser session
`shk_did`	sessionStorage / localStorage	Stores a random browser identifier used by first-party Shuuka profile analytics instead of deterministic fingerprinting.	Until browser storage is cleared
`shuuka_app_consents`	localStorage	Stores per-app consent choices for consent-gated profile apps.	Until cleared or changed
`shuuka_consent_global_all`	localStorage	Stores a broader accept-all choice for consent-gated profile apps.	Until cleared or changed
`__stripe_mid`, `__stripe_sid`	Cookie (third-party — Stripe)	Security and fraud-prevention cookies set by Stripe, Inc. during the payment checkout flow. Only active on checkout pages. See Stripe's Privacy Policy.	Up to 1 year / Session

Storage names and lifetimes can change as the product evolves, but the categories above reflect the current Shuuka web and analytics code in this repository.

4. Third parties

Apps can bring their own third-party storage

A profile owner can install apps that connect to providers such as media platforms, map services, booking tools, or other external services. Once a visitor chooses to load that app, the external provider can set or read its own cookies or browser storage under its own rules.

Shuuka expects app developers to declare these flows in the app privacy manifest and, where required, link to the provider's privacy policy and request visitor consent before activation.

5. Control

How you can control storage

Use your browser settings to clear cookies, localStorage, or sessionStorage.
Log out to remove active authenticated session state from the current device.
On public profiles, use the privacy or consent controls shown by Shuuka when an app requires a decision before loading.
Be aware that clearing storage can sign you out, reset language or theme choices, or cause consent-gated apps to ask again.