Data Collection Policy

This is a public community gaming-club website that visitors can read but not change. It publishes statistics and history for our EA Sports NHL Pro Clubs team. The project is currently operated by a single individual on a volunteer basis; that describes who runs it day to day, not a conclusion about its legal form or about which privacy law, if any, applies to it.

• There is no public account system. Members of our team can sign in with a Discord account, but only through an invite from the site's operator; nobody can register on their own — see "Accounts and authentication" below.
• There is no on-site form, upload, comment, or submission feature. You cannot submit content through this site, though you can still voluntarily send us information through project email — see the information categories below. Signed-in members can only change settings for their own player, such as how their player card looks.
• There is no advertising.
• No monetization or other commercial activity exists on this site, and none is planned. If that changes, we intend to carry out a fresh privacy review before any commercial activity begins.
• Our posture is no analytics and no nonessential tracking — see "Cookies, browser storage, and analytics" below.

We maintain the following categories of information, drawn mostly from EA's game services and our own team members' review and correction of that data:

• Gamertags and gamertag history. Current and prior gamertags used to identify players across matches over time.
• Approved display names and personas. Where a player's profile name is entered manually by our team rather than pulled verbatim from EA, that name is an operator-attested, member-approved display name or alias chosen for identification purposes. We do not request or verify legal names for player-profile identification. This does not mean legal-name or other personally identifying information is impossible to encounter elsewhere in what we retain: email correspondence, attachments, recordings, screenshots, or other raw evidence a person sends us or that we capture could incidentally contain someone's name or other information they choose to provide. We have not inspected every retained item to confirm this, and do not claim it is absent.
• Member agreement to publication. Current members of our club have verbally agreed that their gamertags, profiles, and statistics may be published and used as described in this policy. This is a record of the verbal agreement our operator understands members to have given; it is not written consent, legal clearance, or a statement that this agreement is legally sufficient under any particular law.
• Roster membership. Which players belong to our club, and for what periods.
• Match results and metadata. Scores, dates, game mode, and related match details for games our club played.
• Team and player statistics. Skater and goalie statistics compiled from match data.
• Derived hockey metrics, scores, summaries, and classifications. Values we calculate from the underlying match and player statistics — for example, performance scores and summary classifications — are also maintained as part of the statistical record.
• Opponent-club and opponent-player information. Because Pro Clubs matches involve two teams, our records necessarily include the opposing club's name and the opposing players' gamertags and statistics for the matches they played against us. This includes an EA-provided stable persona identifier for each player, so our records can link the same opponent's appearances over time.
• Raw EA-provided data. We store the raw data returned by EA's game services verbatim before we process it, so that we can correct or reprocess it later without having lost the original source.
• OCR (optical character recognition) extractions and related evidence. For some matches, we extract additional statistics from screen recordings using automated image/text recognition. This includes the extracted text values, supporting evidence, confidence information, review status, and records of where each extracted value came from.
• Source recordings, screenshots, and extracted video frames. Underlying video recordings, screenshots, and individual frames used as OCR source material or as an evidentiary record for the statistics we publish.
• Party voice chat captured in team recordings. Our gameplay recordings may incidentally include in-game party voice chat. This audio is captured only as a by-product of recording gameplay for our statistics and evidentiary purposes — we do not currently analyze it, use it for any separate purpose, or publicly display it. Current participants in our recorded sessions know that gameplay may be recorded and have verbally agreed to that. We do not claim that every possible future participant has agreed, and we do not claim that an opponent or other third party can never be present in a recorded voice channel. We do not publish where any participant is located. Recordings and any incidental audio they contain are kept under the retention approach described in "How long we keep information" below. We have not inspected every recording's contents and do not claim to know what any specific recording does or does not contain.
• Website operational and error logs. This site's hosting stack generates operational and error records in the course of operating and securing the site. Our own server keeps them in small, size-limited rolling logs, and our website software does not keep a separate record of each page visit. Our network and security provider (Cloudflare) may keep its own records. See "How long we keep information" below for how we treat logs under our control, and "Service providers and other parties" for logs controlled independently by our providers.
• Email correspondence sent to our project addresses, which may include the sender's email address, the sender's display name, message contents, attachments, and any evidence you provide to verify a request (for example, to establish that you control a gamertag you're asking us to correct or remove).
• Member accounts. For team members who sign in: the member's Discord user ID, Discord display name and a link to their Discord profile picture (if they set one; all refreshed each time they sign in), the player on our team the account is linked to, the account's role (member or admin), whether the account has been disabled, when it was created, settings the member chooses for their own player (such as their player card's theme), and sign-in session records. See "Accounts and authentication" below for what is not kept.
• A limited set of authentic source fixtures retained in our private GitHub repository, used for testing and development. See "Service providers and other parties" below.

• EA's Pro Clubs game and service interfaces, which return match, player, and club data.
• Recordings and screenshots captured by our own team members during our matches.
• Automated OCR processing of those recordings and screenshots.
• Manual review and correction by our team's operator(s) — for example, fixing a misread gamertag or approving a display name.
• Correspondence sent to our project email addresses.
• Discord, when a team member signs in — it tells us the member's Discord user ID and display name only.
• Ordinary requests made to our public website and the infrastructure and security processing that supports it.

This site is not affiliated with, endorsed by, or sponsored by Electronic Arts, EA Sports, the NHL, the NHLPA, or their affiliates. It is an independent, community-run project. A separate attribution and non-affiliation notice covers EA-sourced content and third-party marks in more detail; this policy is not that notice.

We use the information described above only to:

• Operate this public website.
• Display our team's history, games, rosters, and statistics.
• Produce, verify, and correct derived hockey statistics.
• Maintain a historical and evidentiary archive of our team's matches.
• Diagnose errors and keep the site's infrastructure secure.
• Develop, test, validate, and maintain this website and its data and OCR processing pipeline, including using a limited set of authentic source fixtures for testing, provenance, and regression verification.
• Let invited team members sign in and manage settings for their own player.
• Respond to privacy, correction, removal, and security-related requests.
• Maintain provenance and auditability — i.e., being able to show where a published number came from and correct it if it's wrong.

We do not use this information to measure website traffic or user behavior as an approved purpose at launch. See "Cookies, browser storage, and analytics" below for the current state of an analytics feature that conflicts with that posture and must be resolved before publication.

The public site displays gamertags, approved display names/aliases, roster membership, match information, statistics, opponent-club and opponent-player information, and derived metrics described above.

Our indexing policy: at present, every page of this site — including the home page, game pages, roster pages, and stats pages — asks search engines not to index it (a noindex instruction on every page and response), so the site is not intended to appear in search results and is shared by direct link. If we later allow indexing of public pages, we will update this policy first. Diagnostic and non-public surfaces are not meant to be indexed in any case.

Public display of statistics is distinct from our retention of private raw data and OCR evidence (recordings, screenshots, frames, confidence and review-state information): the raw evidence is not published; only the resulting statistics and match information are.

Visitors who do not sign in get no cookies from this site's own code, and our code does not use localStorage, sessionStorage, or indexedDB. When a team member signs in, our code sets two strictly necessary cookies:

• __Secure-better-auth.state — set when a member starts signing in with Discord. It protects that step against forgery and expires after about 5 minutes.
• __Secure-better-auth.session_token — keeps a signed-in member signed in. It holds a random session reference rather than personal information, cannot be read by the page's scripts, and expires after 30 days, renewed while the member keeps using the site. Signing out removes it.

This describes our own code; it is not a claim that no browser storage of any kind is ever used by any underlying framework, dependency, or infrastructure component.

Our hosting/security provider (Cloudflare) may, under some circumstances, use strictly necessary cookies or similar mechanisms as part of its edge security or challenge processing. We do not currently have specific, verified information about any individual cookie Cloudflare may set, so we are not naming one here.

We do not use analytics. Cloudflare Web Analytics, which was previously enabled in this site's Cloudflare configuration, has been turned off, and this site uses no advertising or other nonessential tracking.

We do not plan to show a cookie-consent banner while our posture is "no nonessential tracking," but whether a banner is legally required in any particular jurisdiction is a legal-review question, not one this policy resolves for itself.

Members of our team can sign in to this site. There is no public sign-up: an account can only be created through a single-use invite link that the site's operator makes for a specific team member, and each account is linked to that member's player. Sign-in uses Discord; this site has no passwords.

When a member signs in, Discord tells us only the member's Discord user ID, display name and profile picture (Discord's identify permission). We do not ask Discord for, receive, or keep the member's email address, and we do not keep any Discord access tokens. We keep a link to the member's profile picture, not the picture itself, so the site can show it to that member in its navigation bar; their browser then loads it from Discord. Nobody else is shown it, and a member without a custom picture sees a plain silhouette. Because our account software requires an email field, each account stores a placeholder address made from the Discord user ID that cannot receive mail.

We keep a record of each sign-in session (when it was created and when it expires) so the member stays signed in. We do not record the IP address or browser of a session. To protect sign-in from abuse, our server counts recent sign-in attempts per IP address in memory for about a minute; those counts are not written to our database.

Signed-in members can change settings for their own player, such as their player card's theme. The site's operator can create and cancel invites, disable an account, and change these settings for any player.

A member can ask us to delete their account at any time — see "Requests and corrections" below. Deleting an account removes the member-account record; it does not remove the member's match statistics, which the rest of this policy covers.

We use the following third-party services to operate this site. This section describes their role for us; it is not a formal legal classification of any provider as a "processor," "controller," or similar term, which remains a legal-review question.

• Cloudflare — our domain registrar and DNS provider, and the proxied edge/network layer (including our Cloudflare Tunnel) that routes traffic to our server and provides security processing (such as its managed security ruleset). Cloudflare's own edge-level log retention is not something we have independently verified; we describe it only in general terms until we do.
• Proton Mail — our email provider. All of our project addresses ([email protected], [email protected], and an internal-only address) deliver into a single Proton mailbox under one operator account. We do not use mail forwarding, a catch-all address, Proton Mail Bridge, a third-party mail client, or any export or separate backup of this mailbox's contents.
• GitHub — hosts our private source-code repository, which also contains a limited set of authentic data fixtures used for testing. This repository was public for part of its history; copies made by others during that period cannot be recalled by us.
• Backblaze — stores off-site backup copies of our database (see "How long we keep information" below).
• Healthchecks.io — monitoring that alerts us if our backups or data collection stop working. It receives only short status messages from our server, not information about visitors.
• Discord — the sign-in service team members use to sign in to this site. Discord tells us the member's Discord user ID, display name and profile picture link when they sign in, and a signed-in member's browser loads their own picture from Discord; visitors who do not sign in are never sent to Discord by this site.
• Electronic Arts (EA) — the source of the underlying game data and some visual assets referenced by this site. EA does not endorse, and is not affiliated with, this project.
• Our hosting infrastructure is community-operated from Alberta, Canada. We do not claim that every service we use stores or processes information only in Canada — see "Location and cross-border handling" below.

Fonts used by this site (Barlow and Barlow Semi Condensed) are downloaded and self-hosted as part of our build process rather than requested by your browser from Google at page-load time, based on how our font loading is currently configured.

• We keep gamertags, approved display names/aliases, match and statistics data, raw EA-provided data, structured database records, OCR evidence, and source recordings/screenshots/frames for as long as we reasonably need them for the purposes described in "Why we use this information" above — principally to maintain an accurate, verifiable historical and evidentiary archive of our team's matches, and for the other purposes listed there. We do not apply an automatic expiry to this category. This does not mean deletion is impossible, and it does not mean every item must always be kept: removal happens by manual operator action, including in response to a request (see "Requests and corrections" below). We have not adopted a scheduled periodic review of this archive. Describing retention this way is a description of our current practice, not a statement that indefinite retention has been legally reviewed or approved.
• Logs under our control are size-limited rather than kept for a fixed period: our server keeps a small rolling log for each part of the site and automatically overwrites the oldest entries.
• Logs controlled independently by service providers are subject to those providers' practices and retention periods.
• Member accounts are kept while the person is a member of our team and are deleted on request (see "Requests and corrections" below). A sign-in session is deleted when the member signs out and otherwise stops working after 30 days without use. Records of used, cancelled, or expired invite links are kept for the operator's reference.
• Correspondence sent to our project email addresses is retained under the following operator targets, reviewed at least annually:
  • Obvious spam or junk: approximately 30 days.
  • Routine correspondence: up to 12 months after the last action needed on it.
  • Privacy, correction, security, and incident-related correspondence (including evidence sent to verify a request — see "Requests and corrections" below): up to 24 months after the matter is closed.
  • Any of the above may be kept longer only while reasonably necessary for an active legal, dispute, investigation, or security purpose.
  These are our own manually-applied targets, not settings automatically enforced by our email provider.
• Our email provider's own internal retention behavior (for example, anything it retains independently of our mailbox) is not something we have independently verified.
• We keep automatic daily backup copies of our database. Copies on our own server are kept for about 12 months (daily copies for 14 days, weekly copies for 8 weeks, and monthly copies for 12 months); off-site copies with Backblaze are kept for about 90 days. Copies are sent to Backblaze over an encrypted connection. Corrections you request are reflected in new backups going forward; we do not individually rewrite existing backup copies, which instead expire on that schedule.

To ask about, correct, or otherwise raise a question about information we hold about you, contact the Privacy Contact for Boogeymen at [email protected].

• We aim to acknowledge requests within 7 days.
• We aim to resolve, or provide a substantive response to, requests within 30 days. Where a privacy law that applies to us sets its own deadline for a request, we intend to meet that deadline as well; our own targets above are meant to be at least as fast.
• We do not charge a fee for access or correction requests.
• We may ask for reasonable evidence that you control the gamertag or identity in question. We do not request government-issued ID by default.
• Access, correction, withdrawal, and removal are different things, and we treat them differently:
  • Access means asking what we hold about you.
  • Correction means asking us to fix an error or omission in information we hold about you. Where correcting information you raised is something we're required to do under a law that applies to us, we'll do it; if we decide not to make a correction you've asked for, and the law requires it, we will note your requested correction alongside the information we hold.
  • Withdrawal means telling us you no longer agree to something you previously agreed to (for example, a member withdrawing agreement to have new statistics published going forward). If you do this, we will explain what it means in practice, stop what we are required to stop, and tell you what we keep and why.
  • Removal is considered case-by-case, not automatic. Whether we remove, de-identify, or otherwise change information depends on applicable law and on our legitimate need to keep an accurate archival record of our team's history. We do not promise removal in every case, and we do not rule out that applicable law may require it in a given case. The fact that information was previously published by EA through its own game services is not, by itself, a reason for us to refuse a request.
• Because our records are about matches involving several people, some of what we hold about you may be mixed together with information about others. Where applicable law requires it, we will give you the parts that are about you and hold back the parts that would reveal someone else's information.
• Evidence you send us to verify a request is used only to verify and handle that request. We do not add it to our published statistics record. We do not promise to delete it immediately; where we keep it, it is kept under the same privacy/correction-correspondence retention category described in "How long we keep information" above.
• If a copy of our data (including from a period when our source repository was public) has already been taken by someone else, we cannot recall or delete that copy — our removal only affects what we ourselves publish and retain going forward.
• If a privacy law that applies to us gives you a right to ask a regulator to review how we handled your request, we want you to be able to use it. In Alberta, that regulator is the Office of the Information and Privacy Commissioner of Alberta (oipc.ab.ca). We mention this as the applicable route where Alberta's Personal Information Protection Act governs a request; mentioning it is not a statement that this project's activities are conclusively covered by that Act.

Team membership on this site is adult-only. No children are, or are planned to be, members of our club.

Some of the opponents we play against in matches may include minors. We do not know their ages, cannot verify them, do not collect them, and have no way to determine them from the information EA's game services provide. This site does not ask any visitor or opponent for age information, and does not offer submissions; sign-in is limited to invited members of our adult team.

Our club is community-operated from Alberta, Canada. We do not claim that every team member lives in Alberta, or in any other specific place — team members are located in various places, and we do not publish individual member locations.

Because we use Cloudflare, Proton Mail, GitHub, Backblaze, Discord, EA's services, and the ordinary infrastructure of the internet, information may be processed or transmitted outside Alberta or Canada as part of how those services work. We do not have verified information about the exact physical storage locations each of these providers uses, and we do not claim otherwise.

We make a reasonable effort to keep the information we publish accurate, and we investigate and correct it, where appropriate, when an error is reported to us or that we otherwise notice.

We take reasonable steps to protect the information we maintain, but no website or storage system can guarantee absolute security. If personal information we hold is lost, or accessed or disclosed without authorization, in a way that creates a real risk of harm to someone, we will carry out any incident reporting or notification that applicable law requires of us. This policy does not set out our internal incident-response procedure.

Our source code repository is now private, but copies made during any earlier public period cannot be recalled — see "Service providers and other parties" above.

We will post an on-site notice when we make a material change to this policy, and this page will always show the date it was last updated at the top.

Contact:

• General, privacy, data, and correction requests: Privacy Contact for Boogeymen, [email protected]
• Security vulnerability reports only: [email protected]