Who handles your information

LOCKERS LLC operates Lockers and handles information for account administration, billing, support, security, and running the platform. Each community owner is responsible for its own decisions about collecting and using member information. Contact the community owner about that community's activities, or support@lockers.social for platform requests.

Information we collect

Account information includes your email address, authentication records, profile name, avatar, biography, community memberships, preferences, and policy acceptance records. Content includes posts, comments, messages, uploads, course responses, learning progress, learning notes, event responses, reports, and optional AI conversations that you submit or generate through the service.

Community staff can store private administrative notes, tags, follow-up dates, and saved views about members in Audience. Members do not see those records on their profiles.

Owners and admins can import contacts into Audience. Each contact stores a name, an email address, the importer's note of where the contact came from and how permission was given, and import details: a permission-version marker, which owner or admin imported it, and when. The email status stored on the contact is not subscribed. Importing a contact does not create a membership, subscribe the address to email, or send a message.

Billing records include customer and subscription references, checkout and payment status, receipts, and limited card details such as card brand and last four digits. Stripe processes card information. Lockers does not store your full payment-card number.

We also process operational information such as request and error logs, device and browser information, IP addresses where available to our hosting or security providers, notification and email delivery records, API activity, and administrative audit records. Support correspondence can include information you choose to send us.

Live sessions can include audio, video, and screen sharing in the room, the choice to record a session, session chat that participants send, and attendance such as who joined and when. Connection intervals are kept so attendee-hours can be calculated. If you sign in with Google, we receive the Google account id, email address, whether Google verified that email, and a name when Google provides one. If you insert a GIF, we store the GIF identifier and an optional title. Your browser loads the image from GIPHY.

How information is used

We use information to authenticate accounts, show community content to its permitted audience, deliver messages and notifications, track course progress, process subscriptions, respond to requests, prevent fraud and abuse, investigate errors, and meet legal obligations. Optional features process the information needed to provide them when you use them. Live connection records are used to operate the room and to calculate attendee-hours. A recording, when it is turned on before the session starts, is used to make a replay for people who can enter that event.

Depending on applicable law and the activity, the basis for processing may be performing an agreement, legitimate interests in operating and securing the service, consent, or a legal obligation. Where consent is required, you can withdraw it for future processing without changing the lawfulness of earlier processing.

Who can see or receive information

Your profile and contributions are visible to the audiences allowed by the community and feature. Community staff can access member information, including email addresses, and learning or administrative records relevant to managing the community. Do not assume that course answers, progress, or AI tutor conversations are private from community staff.

Private Audience notes, tags, follow-up dates, and saved views are available to the Locker's current owner and admins. They are not included in the community content export, and existing customer API keys do not receive them. Within Audience, payment amounts and purchase history remain visible only to the owner. Imported contacts are also available to the current owner and admins, and they are not included in the community content export.

Direct messages are shown to their participants. If a participant reports a message, that message and the report are shared with community staff. Authorized Lockers personnel and providers may access information when needed for support, operations, security, or legal requirements. Direct messages are not end-to-end encrypted.

Community staff can read session chat from a live session and can download an attendance file that includes name and email. A stored replay is available to people who can enter that event. Connection records used for attendee-hours are not included in the community content export.

Providers process information for hosting, storage, authentication, billing, email delivery, and other contracted services. The service uses Convex, Vercel, Stripe, and Resend. Live rooms use Daily for audio, video, screen sharing, and join and leave events. Lockers stores session chat. Daily's own chat is not used. Uploaded video and stored session replays use Mux. When you insert a GIF, your browser requests it from GIPHY. Optional Google sign-in uses Google. Optional AI features send relevant prompts, course context, and conversation content to OpenAI when used and configured. Embedded media and external links may send information directly to their providers under those providers' policies.

We may disclose information when legally required, to protect rights or safety, or as part of a business transaction with appropriate protections. Advertising measurement on the public website is described below. Community owners and third-party sites may have separate practices. Providers may process information outside your country; no particular data residency is promised by this notice.

Email, cookies, and choices

On lockers.social, Google Analytics records public page visits, creator signup and Locker creation, browser information, and campaign or ad-click identifiers. Google Analytics and Google Ads use these events to report which ads bring people to Lockers. When you register a creator account, we retain your Google browser identifier for up to 63 days to report your first confirmed paid Pro subscription to Google. Free trials and renewals do not count as new paid accounts. Personalized advertising and Google signals are disabled. We do not send email addresses, names, community content, or account identifiers in these events. Private community pages and the operator console are excluded.

When configured, Meta Pixel on those same public pages receives public page URLs, browser and request information, cookie and ad-click identifiers, and completed creator signup and Locker creation events. Meta can match this information to a Facebook or Instagram account and use it for advertising measurement and delivery under its own policies. Automatic event collection and advanced matching are disabled. We do not supply email addresses, names, community content or account identifiers to the pixel. URLs containing draft names or other unrecognized query parameters are excluded.

The public site does not ask you to accept cookies before this measurement runs. Your browser settings can block or clear cookies and site data. Blocking or clearing them stops future measurement cookies from this site. It does not delete data already sent. The separate App usage preference controls Lockers' own product analytics.

Account security, verification, password reset, and billing messages are necessary service communications. Community settings and email unsubscribe links let you turn off optional community emails where offered. Turning off optional email does not stop necessary account or billing messages. Your browser controls push-notification permission.

Cookies and browser storage keep you signed in, route you to the right community, remember settings, and support features you request. Embedded services and payment providers may use their own cookies. See the Cookie notice for more information.

Retention and deletion

We retain information for as long as needed to provide the service and for legitimate support, security, dispute, accounting, and legal purposes. The appropriate period depends on the type of record and applicable obligations. Content can remain visible until it is removed by someone with permission. Copies in recipients' messages, exports, legal records, or backups may have different retention periods.

Leaving a community does not delete your global account or every contribution. A community deletion request may include a recovery period before scheduled removal; the applicable timing is shown in the product. Completion also depends on processing stored files and connected services. We may retain limited records after deletion where required or justified for legal, billing, or security purposes.

If a member's account is deleted, Audience notes about that member, their tag assignments, and their follow-up date are removed. Workspace tag definitions and shared saved filter definitions can remain. If an admin's account is deleted, notes they authored can remain in the Locker and lose that author's attribution. Deleting a community removes its private Audience records. An imported contact that uses a deleted account's email address is removed. A contact that person imported can remain without that person's attribution. Deleting an account also removes that person's session chat and attendance rows. Billing connection intervals can remain without the account identifier.

Requests and concerns

Contact support@lockers.social to request access, correction, deletion, or an export of your personal information, or to raise a privacy concern. Identify the account email and relevant community. We may need to verify your identity and clarify the request. Rights to object, restrict processing, withdraw consent, or complain to a privacy regulator may apply depending on your location. Requests are handled subject to applicable law and the rights of other people.

Lockers is for adults 18 and older. We do not knowingly allow children to create accounts. If you believe a child has provided personal information, contact support. We use safeguards intended to protect information, but no online service can guarantee complete security.

We will update the version date when this notice changes and provide further notice of material changes where appropriate.