Bright Community
Security & PrivacyJoin Bright
Back to Bright
Status
Owner-review draft
Version
privacy-2026-08-25-owner-review-1
Published
August 25, 2026
Contact
admin@brightentertainmentllc.com

Your information

Privacy Policy

This policy explains the information Bright currently uses to operate a private creative community.

Review statusThis owner-review draft is grounded in the implemented application and current providers. Final retention periods, request timelines, age policy, and jurisdiction-specific rights require qualified legal review.

1. Information Bright collects

Bright stores account email, membership status, profile identity, Instagram handle, optional profile details, posts, comments, follows, blocks, messages, media records, progression, reports, restrictions, and security or moderation audit evidence.

Bright currently accepts a member-entered location label. It does not request an exact address, GPS coordinates, phone number, date of birth, or legal name during normal signup.

2. Why Bright uses it

Information is used to authenticate members, review access, display profiles and community content, deliver conversations, operate progression, prevent abuse, respond to reports, maintain reliability, and improve Bright.

3. Who can see it

Profile information, posts, comments, General Chat, and visible progression are available within the active member community according to account and block rules.

Direct messages are limited to their participants and narrowly authorized operational access required for safety, moderation, legal obligations, or incident response. Bright does not use private-message volume as meaningful progression.

4. Service providers

Bright currently relies on Neon for managed authentication and Postgres data, Vercel for application hosting and media storage, and Cloudflare for domain and network services. Those providers process technical or account data needed to provide their services.

Bright does not currently sell member personal information.

5. Security and operational data

Bright uses managed sessions, server-side authorization, bounded media validation, security headers, audit records, backups, and restricted production access. No internet service can guarantee absolute security.

Operational logging is designed to avoid passwords, cookies, private message bodies, and unnecessary personal content.

6. Retention, correction, and deletion

Members can edit supported profile fields, remove supported content, review blocks, manage active sessions, and request account deletion from Account & Privacy.

A deletion request immediately deactivates community access and closes signed-in sessions. It does not represent instant erasure: operator-reviewed removal and final retention timelines still require legal approval. Bright may retain limited moderation, security, backup, or legal evidence where there is a legitimate obligation to do so.

7. Changes

Bright will version material policy changes. Continued use may require acknowledging a newer version when the change affects the community agreement.

Bright Community BetaActively evolving with the people inside it.
TermsPrivacyCommunity RulesSecurity & Privacy