Security & Privacy

Bright uses managed authentication and protected sessions. The community application stores the identity information needed to operate membership, not a second copy of an account password.

Protected pages require an authenticated member. Sensitive actions reload current account status, role, and scope from the database. Rank, Level, and profile titles do not grant software authority.

Direct-message reads require conversation participation. General Chat is intentionally shared with active members. Bidirectional blocks separate people across profiles, discovery, following, direct messages, posts, comments, and reactions.

Photo and GIF uploads are purpose-bound, size-limited, structurally inspected on the server, and finalized against the authenticated owner. Bright also uses restrictive response headers, rate limits, narrow server validation, and audited privileged actions.

Bright maintains protected data storage, backup and recovery evidence, and controls around production access. Precise GPS and exact addresses are not part of the current member profile model.

Cybersecurity is ongoing work. Bright reviews access controls, records privileged actions, tests recovery paths, and continues improving protections as the community grows. Deletion requests deactivate access and enter an audited, operator-reviewed removal path; final deletion timelines remain subject to owner and legal review.

Use the contact on this page for a suspected security issue, privacy request, or safety concern. Do not include passwords, session cookies, or private credentials in the report.