GameBeacon Privacy Policy

Version: Draft 1.0 · Status: For private review — not final legal advice

This draft contains operational details that must be verified or completed before public registration or live collection of user data.

1. Scope and Controller

This policy describes personal information processed when people use the GameBeacon mobile app and related services. The legal entity or individual operating GameBeacon and the privacy contact must be identified before live publication.

2. Information You Provide

Depending on features used, GameBeacon may process email address, username, password-related authentication records handled by our authentication provider, date of birth supplied at signup, profile biography, profile photo, selected games and formats, experience levels, session or tournament details, reports, and other content you submit. We should verify the exact fields against the production database before publication.

3. Location and Discovery

GameBeacon is designed to support approximate location-based discovery. Precise device location may be accessed with permission to calculate proximity; the intended product rule is not to display exact GPS coordinates to other players. We must verify actual collection, storage, rounding, and retention behavior before representing those controls as implemented. Home addresses must not be publicly displayed; private sharing with confirmed participants is a planned feature.

4. How Information Is Used

Information is used to create and secure accounts, enable profiles and game discovery, organize sessions, moderate content and reports, communicate service notices, troubleshoot errors, and protect the platform. We do not plan to sell personal or precise location data.

5. Service Providers

GameBeacon currently uses Supabase for authentication and database functionality and uses hosting or email-confirmation services as configured by the developer. Providers may process information to operate these services. The complete provider list, hosting regions, and contractual roles require confirmation before live publication.

6. Visibility and Sharing

Your username, selected profile information, and participation details may be visible to other users according to app settings. Other users may see approximate proximity or discovery information, not an intentionally published precise GPS location. Reports and moderation materials are intended for authorized reviewers. Users can separately disclose information to one another during offline interactions.

7. Photos and Moderation

Profile photos may undergo review. The intended design maintains one active approved photo while a replacement awaits approval, preserves moderation decision metadata, and schedules deletion of certain inactive or rejected image files after approximately 24 hours. These are product requirements; the policy must be reconciled with deployed storage rules and cleanup jobs before publication.

8. Retention and Deletion

Retention depends on the information type and operational needs. Authentication, profiles, moderation records, backups, and logs may have different retention periods. Specific periods, deletion request procedures, and whether all cleanup jobs are operational must be confirmed and disclosed before live publication.

9. Security

We use or plan to use access controls and other safeguards appropriate to the service, but no online system can guarantee absolute security. Security claims must be checked against the deployed configuration and pre-beta audit.

10. Age Restriction

GameBeacon is intended only for adults aged 18 or older. We require date-of-birth information during registration to enforce eligibility. We should confirm where birth dates are retained, who can access them, and whether they are removed or minimized after age verification.

11. Your Choices and Rights

You may be able to edit profile details, control location permissions through your device, and request access, correction, or deletion of personal data. Rights vary by jurisdiction. We need to publish a functioning privacy contact and confirm how requests are fulfilled before live use.

12. Changes and Contact — TO COMPLETE BEFORE LIVE PUBLICATION

Material changes will be communicated as appropriate, and renewed acknowledgment may be required. Before publication, provide the legal operator, contact email, effective date, actual retention schedule, provider list, and any jurisdiction-specific notices required by law.