Community information

Community owners decide the purposes of their community and which member information to collect through its content and activities. Lockers processes that information to provide the configured service. Account security, platform administration, billing, and Lockers' own legal obligations can involve separate responsibilities described in the Privacy notice.

Administrative notes, tags, follow-up dates, saved views, and imported contacts created by community staff in Audience are part of that community's processing of member and contact information. Session chat, attendance, and a recording turned on for a session are part of that community's processing of participant information. Connection intervals used to calculate attendee-hours are also processed to operate and bill the platform.

Owners are responsible for appropriate notices, permissions, member requests, and their authorized staff. They should limit the personal information they collect and use available access and export controls carefully. Do not use the service for regulated or sensitive processing that requires protections we have not agreed to provide.

Contract requirements

Some uses require a separate written data processing agreement, including uses where applicable law requires specific controller and processor terms. Contact support@lockers.social before starting such processing. This information page does not by itself constitute a signed data processing agreement, an international-transfer agreement, or a representation that a particular compliance requirement is satisfied.

A required agreement should address the processing instructions and purpose, categories of data and people, confidentiality, security, subprocessors, assistance with rights and incidents, deletion or return, audits, and any required transfer protections. Confirm those arrangements with Lockers before relying on the service for that use.

Providers and requests

The Privacy notice identifies the main service providers and optional integrations. Contact support for provider information relevant to a proposed agreement, a security concern, or a data request. Community owners should tell us the relevant community and scope without sending unnecessary member information.