Storage needed for the service

Lockers and its authentication provider use cookies and similar browser storage to maintain sessions and support sign-in, including moving a session between the platform and a community. Browser storage also supports preferences, installation and notification prompts, and the email address used in the account setup flow. Clearing it can sign you out or reset those preferences.

Some service-worker and browser caches keep application resources available between page loads. Storage duration varies by its purpose, session lifetime, browser, and your choices. Do not use a shared device without signing out when you finish.

External services

Stripe checkout and embedded videos or external sites may use their own cookies, local storage, and request data. Opening or playing third-party content can disclose your IP address and browser information to that provider. Joining a live room, playing a stored video, inserting a GIF, or signing in with Google can send your IP address and browser information to Daily, Mux, GIPHY, or Google. Those services can use their own cookies and storage, and they have their own privacy and cookie notices.

On lockers.social, Google's tag loads for Google Analytics and Google Ads attribution. It measures public page visits, creator signups and Locker creation, with campaign and ad-click identifiers where available. For a new creator signup, we link the Google browser identifier to your account for up to 63 days so our server can report your first confirmed paid Pro subscription. We send no name, email, Lockers account identifier or payment details to Google. Free trials and renewals are excluded. Google receives browser and request information. Personalized advertising and Google signals stay off. The tag does not run on private community pages or the operator console.

This measurement uses Google's _ga and related measurement cookies, configured for up to 90 days, plus browser storage for conversion deduplication. A short-lived signup reference in session storage helps confirm a completed creator signup; that reference is not sent to Google. An opaque token stored in that browser is kept with the paid-subscription measurement record.

When configured, Meta Pixel loads on the same public pages. Meta can set _fbp and _fbc cookies and receive public page URLs, browser information, ad-click identifiers and completed signup and Locker creation events. Meta can associate events with your account and use them for advertising measurement and delivery. Automatic event collection and advanced matching are disabled. No pixel events are sent from private community pages or the operator console. Meta's cookie policy describes its cookies at facebook.com/privacy/policies/cookies.

Conversion deduplication stays in browser storage, and a temporary signup reference stays in session storage; neither identifier is sent to Meta. Locker setup names and slugs stay in this tab's session storage for up to one day so they do not appear in tracking URLs.

Your controls

The public site does not show a cookie prompt or a cookie button. Your browser settings can block or clear these measurement cookies. That stops future cookies from this site. It does not erase events already received by Google or Meta. Google's privacy information is at policies.google.com/privacy, and Meta's is at facebook.com/privacy/policy.

You can review, block, or clear cookies and site data in your browser settings, and change notification permission there. Blocking storage required for authentication or security can prevent parts of Lockers from working. Contact support@lockers.social with questions about storage used by the service.