LCS Community Terms

Public network

Unless a feature is explicitly identified as private, assume content submitted to LCS is public and may be read, linked, quoted, or indexed by other visitors.

Private connection features

Friend requests, accepted friend relationships, LFG match requests, block lists, and private authentication mappings are access-controlled. Do not attempt to access another user's private records or bypass Firestore controls.

Direct messages are not confidential

Direct messages are participant-access-controlled under the current service rules, but you must treat every direct message the same as a public post or public message. Do not disclose private or sensitive information in DMs. A message can be stored, reviewed, copied, shared, or become publicly accessible. The persistent safety notice in the messaging window applies to every direct message.

Status and moderation

LCS uses Status authorization rather than separate role systems. Founder, Moderator, and Timeout can apply globally or, where applicable, to a specific discussion or project. Moderator authority is limited to its assigned scope. Timeout is a read-only state: the affected user may continue browsing but cannot add covered contributions while it is active.

Moderation records and deletion

Removing public content does not necessarily erase it from LCS storage. LCS retains previously public soft-deleted content and append-only history records so author deletions/restorations, moderation decisions, and Status changes can be reviewed later by authorized moderation. Do not submit content you expect to become confidential merely by deleting it afterward.

Do not publish sensitive information

Do not place passwords, authentication tokens, private keys, API secrets, financial information, precise private addresses, phone numbers, private email addresses, or other sensitive information into public posts or LFG listings.

LFG safety

LFG exists for playing together, creating together, and sharing information. Use the built-in request system instead of publishing private contact details. Users remain responsible for deciding whether and how to interact outside LCS.

Identity

Your public display name may be an alias and does not need to match a provider or legal name. Do not impersonate another person or organization deceptively.

Reasoning labels

Reasoning labels describe how a user is presenting a statement. They are organizational aids, not guarantees that a statement is true.

Abuse

Do not use LCS to harass users, automate unsolicited connection requests, exploit the service, distribute malware, expose private information, evade Status restrictions, or interfere with other users' access.