Cookie Policy.

Operator and contact

PANIC ROOM is operated solely by Marko Panić as an individual, based in Belgrade, Serbia. PANIC ROOM is not currently a registered company or legal entity.

For privacy requests, account closure, legal questions or moderation appeals, use the privacy and legal email contact on the Contact page.

Authentication cookies

Supabase session cookie names follow sb-<project-reference>-auth-token and may have numbered chunk suffixes. They hold session information so the server can recognize accounts and refresh sessions.

Temporary authentication-flow cookies may use the same prefix with code-verifier or flow-related suffixes. They support verification and recovery rather than advertising.

Configured cookies use HttpOnly, SameSite=Lax and the site-wide path. Secure is enabled for an HTTPS application origin. The installed adapter’s default maximum age is 400 days; cookies may be refreshed or cleared earlier. Session validity is controlled separately by the authentication service.

Local and session storage

The active application does not persist accounts or bag contents in localStorage, sessionStorage or IndexedDB. Account state and the preview bag use browser memory. Reloading resets the bag. Application code does not store passwords or payment credentials in browser storage.

Third-party video and social links

YouTube thumbnails load with the catalog and send image requests to YouTube servers. The embedded player loads only after you choose to play.

Playback uses youtube-nocookie.com, YouTube’s privacy-enhanced embed domain. YouTube may still process viewing/technical information or use browser storage after activation. Behavior can depend on your browser and YouTube settings. Not all third-party video storage is classified as technically necessary.

External YouTube or Instagram links visit separate websites that may use their own cookies and storage.

Analytics and advertising

No PANIC ROOM analytics, advertising pixel, marketing-cookie system or consent-preference cookie is integrated into the application. Third-party video behavior is separate from this statement.

Browser controls

You can clear or block cookies using browser settings. Blocking account cookies can prevent login or interrupt your session. Signing out ends access to the current account session.

You can browse sets without activating an embedded player or open the recording on YouTube instead. Thumbnail requests still occur when images load.

Changes to storage

The current application uses account cookies for authentication and loads third-party video only when you choose playback. No site-wide cookie-consent banner is currently implemented. Choosing playback is a technical activation action, not a claim that all legal consent requirements have been satisfied.

Any future analytics, marketing or additional storage requires a policy and consent review before activation. This policy will be updated when the implementation changes.