Privacy Policy
Privacy Policy · Version 1.0 · Version date: 17 November 2026
1. About this Privacy Policy
Project Beacon (“Beacon,” “we,” “us,” or “our”) is a gaming social and connection platform operated from Ontario, Canada. This Privacy Policy explains what personal information Beacon collects, why we collect it, how it is used and disclosed, how long we keep it, and the choices available to members and waitlist applicants.
This Policy applies to Beacon’s website, apps, member features, waitlist, support and safety processes, and related services. Beacon is currently intended for people aged 18 or older.
Because Beacon is an evolving service, features and data practices may change. If we make a material change to this Policy, we will update the effective date and provide notice where required or appropriate.
2. Privacy at a glance
- Beacon does not sell personal information.
- Beacon does not record Clan Voice conversations. Cloudflare provides the live voice infrastructure for the Clan Voice beta (section 3.12).
- Beacon does not use advertising networks, behavioural advertising, marketing pixels, or cross-site tracking. Beacon uses Cloudflare Web Analytics to count visits in aggregate, and records where a new member first came from when they join (for example “reddit.com”). Both are explained in sections 3.10, 3.11 and 12.
- Member profiles are not public on the open web. Profile visibility inside Beacon is controlled by member privacy settings.
- Gamer DNA is optional.
- Favourites are private to the member who creates them, and blocks are not disclosed to the blocked member.
- Beacon’s referral feature shows you only totals. It never shows you who you invited, and never tells a friend who invited them (section 3.13).
- Private messages are not end-to-end encrypted. Beacon’s ordinary admin interface does not provide a tool for casually browsing private conversations; message content may be preserved for review when a member files a report.
- Deleting an account removes most account and profile information, but does not erase messages already sent to another member or safety evidence that Beacon must retain under the rules described below.
- Beacon uses service providers to operate the platform, including Supabase, Cloudflare, Resend, Google (when Google sign-in is used), Apple (when Sign in with Apple is used), and Wikidata/Wikimedia for game-title lookup.
3. Information we collect
3.1 Account and authentication information
To create and secure an account, Beacon collects your email address and authentication information. If you use email and password, your password is handled by our authentication provider and is not stored by Beacon in readable form. If you choose Google sign-in, Beacon receives the email address and authentication identifier needed to link your Google identity to your Beacon account; Beacon does not use Google sign-in to import your Google profile photo, contacts, or other unrelated Google profile information.
If you choose Sign in with Apple in the Beacon iPhone app, Beacon receives the email address Apple provides (which may be a private relay address if you choose to hide your email) and a stable identifier Apple assigns to you for Beacon. Beacon does not ask Apple for your name. When you use Sign in with Apple, Beacon checks before signing you in whether an account with the same email address already exists; if one does, Beacon does not link the two, and you continue with the sign-in method you first used. Beacon cannot promise that accounts are kept separate under every sign-in method: where you use Google or email sign-in with an address that already has an account, our authentication provider may treat them as the same account. To be able to remove Beacon’s access at Apple when you delete your account, Beacon keeps an Apple-issued token for your account, stored in encrypted form and used only for that purpose.
3.2 Profile information
Your Beacon profile may include your display name, @handle, About text, country or region, time zone, preferred language, primary and additional gaming platforms, avatar, and privacy settings. Some information is required to complete profile setup, while other fields are optional.
Beacon also stores your overall profile-visibility choice and field-level visibility choices. Depending on your settings, individual fields can be visible to Everyone on Beacon, Connections only, or Only Me. “Everyone” in this context means other authenticated Beacon members who are permitted to view your profile; it does not mean the public Internet.
3.3 Gamer DNA
If you choose to complete Gamer DNA, Beacon collects your answers about gaming motivations, team roles, competitive intensity, social gaming style, communication preferences, pressure style, social openness, genre preferences, availability, and connection goals. Beacon derives trait tags, a synopsis, and an ideal-match description from those answers.
Gamer DNA is optional. We use it to provide your gaming-personality snapshot and to support matching and recommendation features such as People Worth Knowing.
3.4 Games and platforms
Beacon stores games you add to your “Games I’m Playing” list and the platform or platforms you use for those games. This information supports discovery and matching. Game visibility follows your member privacy settings.
3.5 Connections, favourites, blocks and matching information
When you use Beacon’s social features, we store connection requests and relationship status, who initiated the connection, matching information associated with the connection, favourites, and blocks.
Favourites are one-directional and private: the person you favourite is not told that you favourited them. Blocks are also directional and are not disclosed to the blocked member. Beacon uses this information to operate relationships, messaging permissions, safety controls, recommendations and matching.
3.6 Private messages
When Connected members message each other, Beacon stores message content, sender information, timestamps, and thread information. Beacon also stores a short preview of the most recent message so conversation lists can be displayed.
Private messages are not end-to-end encrypted. They are protected by access controls and are transmitted over encrypted connections, but authorized infrastructure administrators or service providers may technically be able to access stored data where necessary to operate, secure or troubleshoot the service.
Beacon’s ordinary admin interface does not provide a feature for browsing members’ private conversations. If a member reports a conversation, Beacon may preserve up to the last 50 messages from that conversation as a frozen evidence snapshot for Trust & Safety review.
3.7 Reports, safety evidence and moderation
If you report a member or conversation, Beacon may collect the report reason, an optional written note, report timestamps and status, and a frozen evidence snapshot. For conversation reports, that snapshot may include up to the last 50 messages. For member/profile reports, it may include the profile information that was visible to the reporting member at the time of the report.
Beacon may also store the moderation outcome, reviewer information, internal administrative notes, and links between a report and resulting enforcement actions. This information is used to investigate reports, enforce Beacon’s rules, protect members, support appeals or review, identify repeat misconduct, and maintain an audit trail.
The reported member is not told who submitted a report. Internal admin notes and moderator identity are not displayed to members through the normal product.
3.8 Suspensions, bans and ban-evasion protection
Beacon stores account-status information and an audit history when an account is suspended, reinstated, banned or unbanned. Records can include reason codes, internal notes, dates, the administrator who took the action, and notification-delivery status.
If a currently banned member deletes their account, Beacon may retain a minimized enforcement record for up to 24 months. Beacon may also retain a one-way keyed cryptographic digest derived from the deleted account’s email address. Beacon does not retain the plaintext email in this ban-evasion record.
When a later signup produces the same keyed digest, Beacon may create a flag for human administrative review. This process does not automatically block or ban the new account.
3.9 Waitlist and invitations
If you join Beacon’s waitlist or receive an invitation, we collect your email address, primary platform, confirmation that you are 18 or older, and consent to receive waitlist and invitation communications. You may also choose to provide a preferred name, additional platforms, games, country or region, time zone, and feedback.
Beacon records your waitlist status, such as waitlisted, invited, activated, declined or departed. Invitation links use secure single-use tokens. Beacon stores a cryptographic hash of the invitation token rather than the raw token.
Beacon also records the IP address associated with waitlist application submissions and invite-token validation attempts for spam, abuse and rate-limit protection.
3.10 Technical and browser information
Beacon’s hosting and security providers necessarily process technical information such as IP addresses and request information when you connect to the service. Beacon deliberately stores IP addresses in its own application database only for the narrow waitlist rate-limiting purpose described above.
Beacon stores authentication/session tokens in your browser’s local storage so you can remain signed in. It also holds a referral code from a friend’s link for up to seven days, until the sign-up is submitted (section 3.13). Session storage is used temporarily, for that browser tab only, for invitation processing, for remembering the clan or member page you were trying to reach while you sign in (for up to two hours), for the acquisition source described in section 3.11, for a referral code from a friend’s link (section 3.13), and for non-personal interface functions such as restoring scroll position. Beacon’s application does not use advertising cookies, and does not set analytics cookies.
Beacon uses Cloudflare Web Analytics to understand, in aggregate, how many people visit Beacon’s pages, which pages they view, which websites send them, and broad technical information such as country, browser and device type. Cloudflare states that Web Analytics does not use cookies or local storage and does not track visitors across websites. Beacon uses it only for site-level statistics. Beacon does not link these statistics to your account or profile, and does not use them to identify individual members. Cloudflare processes request information, such as IP address, to provide this service under its own privacy terms.
3.11 Where you first came from (acquisition source)
If you arrive at Beacon through a link carrying campaign labels (for example, a link shared in an online community) or from another website, your browser holds those labels, and the hostname of the referring website (for example “reddit.com” — never the full address, page or search terms), in session storage for that browser tab only. If you do not create an account, Beacon saves nothing.
If you do create an account, Beacon saves those labels once, when your profile is first created, to understand which communities bring in genuine members. The first source is kept and is not changed later. It is never shown to other members, is not shared with advertisers or other third parties, is not used for advertising or to build a profile of you, and is deleted when you delete your account. Beacon does not store your IP address, device identifiers or the full referring address for this purpose. It is read only in aggregate form by authorised Beacon administrators.
3.12 Clan Voice (beta)
Clan Voice is a beta feature that lets members of a Clan talk in live voice rooms. It is available to the members of participating Clans. If you join a voice room, Cloudflare provides the live voice infrastructure (Cloudflare RealtimeKit). To deliver the conversation, Cloudflare processes your microphone audio, your Beacon display name and your Beacon member ID, together with technical connection information such as your IP address and when you joined and left. Your audio is sent live to the other participants in that room.
Project Beacon does not record Clan Voice conversations. The voice service is configured with recording turned off, and Beacon does not store or review voice audio.
Beacon stores only what it needs to run voice rooms: the rooms a Clan’s Owners and Officers create, which room you are currently in and when you were last active there, whether a moderator has removed you from a room (a removal prevents rejoining that room for 10 minutes and is recorded in the Clan’s audit log). Your browser remembers that you have seen the Clan Voice notice. Your browser asks for your permission before Beacon can use your microphone.
Members you have blocked, and members who have blocked you, can be in the same voice room. Beacon asks each participant’s own device not to play the other’s audio (client-side playback muting) and does not tell a blocked member that they were blocked. Because this muting happens on participants’ devices rather than on Beacon’s servers, Beacon cannot guarantee that a modified application cannot receive audio that the standard Beacon app would not play. Only join a voice room with people you are comfortable talking in front of.
3.13 Referral links and badges
If you share your personal referral link and a friend joins Beacon through it, Beacon records that your friend joined through your link. The record holds your member ID, your friend’s member ID, the date, and whether your friend has since confirmed their email address and completed their Gamer DNA. A friend counts toward your badges only once they have done both; until then they are shown to you only as part of a “pending” total.
When your friend follows your link, Beacon keeps your link’s short code in their browser until their account exists: in session storage for that browser tab and, for up to seven days, in local storage, so that it is not lost if they leave and come back or sign in with Google or Apple. If they sign up by email, the code is saved as part of their new account’s sign-up details. If your friend does not join, nothing is saved on Beacon’s servers, and the code is ignored after seven days. Once your friend joins, the code is removed from their browser as soon as their sign-up is submitted or Beacon has recorded it.
You see only totals: how many friends have qualified, how many are still pending, and your progress toward your next badge. Beacon does not show you who your friends are, their email addresses or anything else about them, and does not show your friend who referred them. Other members cannot see your referral link, your totals or your referral history.
When you reach a milestone of 2, 5, 10 or 50 qualified referrals, Beacon awards you a permanent achievement badge (Bronze, Silver, Gold and Diamond). Badges you have earned, but not your referral totals, appear on your Beacon profile for members who are allowed to see your profile. Badges you have not yet earned are never shown to others. A badge you have earned is kept even if a friend later deletes their account.
Beacon also keeps a short technical record of each attempt to attach a referral (the link’s code, the new member’s ID, the time, whether it worked, and any error) so that a referral that did not attach can be found and corrected. It contains no IP address and no email address. Authorised Beacon administrators can see referral totals, who referred whom, and this technical record, to run and protect the feature. Referral information is not shared with advertisers or other third parties and is not used to build a profile of you.
If you delete your account, your referral link, referral totals, badges and referral records are deleted. If your friend deletes their account, their referral record is deleted and your qualified total goes down by one; badges you have already earned stay.
4. How we use personal information
Beacon uses personal information only for purposes reasonably connected to operating, securing and improving the service, including to:
- create, authenticate and secure member accounts;
- create and display member profiles according to privacy settings;
- provide Gamer DNA, matching, discovery and recommendation features;
- operate Connections, favourites, blocks and private messaging;
- administer the waitlist, invitations and capacity controls;
- send account, security, waitlist, moderation and support communications;
- respond to support, privacy and legal requests;
- investigate reports, enforce Community Standards, manage appeals and protect members;
- prevent spam, abuse, fraud and ban evasion;
- maintain operational and security records; and
- comply with applicable legal obligations and protect Beacon’s legal rights.
5. When we disclose information
Beacon does not sell personal information. We disclose or make information available only where reasonably necessary to operate the service, at your direction, for safety and security, or where required or permitted by law.
5.1 Other Beacon members
Information you place on your profile may be shown to other authenticated Beacon members according to your profile and field-level privacy settings. Connections can see information you have chosen to make visible to Connections. Favourites remain private to you, and blocks are not disclosed to the blocked member.
5.2 Service providers
Beacon currently relies on the following service providers:
| Provider | Purpose | Information involved |
|---|---|---|
| Supabase | Database, authentication and private file storage | Account, profile, Gamer DNA, social, messaging, safety/enforcement data and avatars |
| Cloudflare | Hosting, edge delivery, security and DDoS/bot protection, aggregate visit statistics (Cloudflare Web Analytics), and live voice infrastructure for Clan Voice (Cloudflare RealtimeKit) | Web traffic and network-level information such as IP address, page visited, referring site, browser and device type; for Clan Voice, live audio, display name, Beacon member ID and connection details (see section 3.12) |
| Resend | Transactional email delivery | Recipient email address, subject and email content needed to send account, waitlist and moderation messages |
| Optional Google OAuth sign-in | Authentication exchange, email address and identity information needed for sign-in | |
| Apple | Optional Sign in with Apple (Beacon iPhone app) | Authentication exchange, email address (or private relay address) and identity information needed for sign-in, and the token exchange used to remove Beacon’s access when you delete your account |
| Wikidata / Wikimedia | Game-title search and catalogue lookup | Game-search text you submit; Beacon stores the resulting canonical game record, not the search query itself |
These providers may process information in jurisdictions outside Canada under their own infrastructure and contractual arrangements. Beacon’s primary Supabase production database is hosted in the United States (AWS us-east-2, Ohio). As a result, personal information processed outside Canada may be subject to the laws of the jurisdiction where it is processed.
5.3 Legal, safety and business requirements
Beacon may disclose information where reasonably necessary to comply with law, respond to lawful process, protect the rights or safety of members or others, investigate fraud or security incidents, enforce our agreements, or establish, exercise or defend legal claims. If Beacon’s business or assets are reorganized, transferred or acquired, information may be transferred as part of that transaction subject to applicable law.
6. Data retention
Beacon keeps personal information only for as long as reasonably necessary for the purposes described in this Policy, subject to safety, legal and operational requirements. Current automated retention rules include:
| Category | Current retention approach |
|---|---|
| Closed private-message threads | Eligible for deletion 90 days after the thread is closed. Active, never-closed conversations do not currently have an automatic expiry. |
| Reports resolved without enforcement | Eligible for deletion 12 months after review, unless linked to an enforcement action or subject to a retention hold. |
| Reports linked to suspension or ban | Eligible for deletion 24 months after the later of the report review date or relevant enforcement action, subject to retention holds. |
| Deleted-member enforcement tombstones / ban-evasion records | Eligible for deletion 24 months after the most recent relevant event, subject to retention holds where applicable. |
| Waitlist rate-limit IP/attempt records | Deleted after 90 days. |
| Departed waitlist applicants | Deleted 24 months after departure. |
| Declined waitlist applicants | Deleted 12 months after the decline date. |
| Waitlisted, invited and activated applicants | Retained while operationally necessary for the waitlist, invitation and access-control lifecycle. |
| Referral links, referral records, badges and the referral attempt log | Kept while the account exists and deleted when the account is deleted. A referral record is also deleted if the referred friend’s account is deleted. |
A retention hold may pause deletion of certain Trust & Safety records when preservation is reasonably necessary, for example for an active legal, safety or dispute matter. Once the hold is released, the ordinary retention rule applies.
When a declined waitlist application is deleted after 12 months, a later application using that email is treated as a new application.
7. What happens when you delete your account
Beacon provides self-service account deletion. Deleting your account removes your authentication account and most information directly associated with your membership, including your profile, avatar files, Gamer DNA, games list, Connections, favourites, blocks, admin notes, and current account-status records, subject to the exceptions below.
Deleting your account does not erase messages you already sent to another member. Those messages remain in the conversation and your sender identity is removed so you appear as a former member. This preserves the other participant’s conversation history and supports safety and evidentiary integrity.
Reports and frozen safety evidence may also remain for the retention periods described above. Direct account identifiers in those records may be removed when the related account is deleted.
If you signed in with Apple, deleting your account also asks Apple to revoke Beacon’s access and deletes the token Beacon kept for that purpose. If Apple cannot confirm the revocation, we will tell you, and you can remove Beacon yourself in your iPhone’s Settings (your name > Sign in with Apple > Project Beacon).
If you were an invited member, your waitlist record becomes “departed” and may be retained for up to 24 months. If you were currently banned when you deleted your account, Beacon may create the minimized enforcement and keyed-email-digest records described in Section 3.8 for up to 24 months.
8. Your choices and privacy controls
Beacon gives members controls to manage how their information is used and displayed. Depending on the feature, you can:
- view and edit your profile information;
- control overall profile visibility and field-level visibility;
- choose whether to complete Gamer DNA and retake it later;
- manage your games list, Connections, favourites and blocks;
- opt out of being included in recommended Fits;
- report members or conversations;
- delete your Beacon account through Settings; and
- contact Beacon for access, correction or other privacy requests that are not available through self-service controls.
Beacon does not currently provide an automated “download my data” feature. Requests for a copy of personal information or other privacy assistance can be sent to privacy@joinprojectbeacon.com. We may need to verify your identity before fulfilling a request.
9. Security
Beacon uses technical and organizational safeguards intended to protect personal information. These include private storage for avatars, Row Level Security and restricted database functions, server-side permission checks, role-based administrative access, rate limits, secure invitation tokens, and keeping privileged service credentials out of browser code.
No online service can guarantee absolute security. You are responsible for keeping your account credentials secure and for notifying Beacon if you believe your account or information has been compromised.
10. International processing
Beacon is operated from Ontario, Canada, but some service providers process or store information outside Canada. In particular, Beacon’s Supabase production database is hosted in Ohio, United States. Cloudflare, Google, Resend and Wikimedia may also process information through infrastructure in other jurisdictions.
When personal information is processed outside Canada, it may be accessible to courts, law-enforcement authorities or other government bodies under the laws of those jurisdictions.
11. Children and age eligibility
Beacon is intended for adults aged 18 or older. Members and waitlist applicants must confirm that they are at least 18. If we learn that an ineligible person has provided personal information contrary to our age requirements, we may take steps to remove the account or information as appropriate.
12. Advertising, analytics and marketing
Beacon does not sell personal information or use third-party advertising networks, behavioural advertising, cross-site tracking, or marketing pixels.
Beacon does use two limited measurement tools to understand whether it is reaching genuine gamers, as described in sections 3.10 and 3.11: Cloudflare Web Analytics (aggregate, site-level visit statistics, not linked to member accounts), and a one-time record of where a new member first came from, saved with their account and deleted with it. Neither is used for advertising or shared with advertisers.
Beacon sends required service-related communications, and required waitlist and invitation communications needed to operate access to Beacon (for example, your invitation or account activation notices). These continue regardless of the optional preferences described below.
Beacon also offers optional email communications, separate from the above and from each other:
- A general Project Beacon news and product-update preference — for example, new features, community events, and occasional Beacon news — available to members. This preference is off by default and can be turned on or off anytime from Account Settings.
- Occasional waitlist news or re-engagement messages, sent only to waitlist applicants who affirmatively agreed to waitlist communications when applying.
You can unsubscribe from optional waitlist communications or Project Beacon news and updates at any time using the link in those emails or, where available, from your account settings. Unsubscribing from one does not affect the other, and does not affect account, security, or other required service communications. If Beacon later introduces advertising, additional analytics, or new tracking technologies, we will update our practices and disclosures and obtain consent where required.
13. Changes to this Policy
We may update this Privacy Policy as Beacon evolves, as our service providers or features change, or as legal requirements develop. The current version will identify its effective date. Where a change is material, we will provide additional notice where required or appropriate.
14. Contact Project Beacon
For privacy questions, access or correction requests, or questions about this Policy:
- Privacy & Member Data: privacy@joinprojectbeacon.com
- For account or technical support: support@joinprojectbeacon.com
- For safety concerns or reports: report@joinprojectbeacon.com
- For legal notices or legal inquiries: legal@joinprojectbeacon.com
Project Beacon is operated from Ontario, Canada.