Privacy Policy
| Category | Summary |
| Data collected | Form submissions plus standard technical data |
| Use of data | Responding to messages, improving content, basic analytics |
| Sharing | Not sold, not transferred to third parties for marketing |
| Cookies | Used for site function and aggregate analytics |
| User control | Data can be reviewed, modified, or deleted on request |
Information We Collect
The site collects two categories of data: information visitors actively submit, and technical information that gets logged automatically when any device connects to a web server.
Personal Data
Personal data on the site comes exclusively from visitors who choose to provide it. The contact form is the only mechanism through which a visitor would normally submit identifying information, and the form requests only what’s needed to respond: a name and an email address, plus the message body.
The name and email are used to address the response and to deliver it. The message body is whatever the visitor chose to type. If a visitor includes additional personal information inside the message, like phone numbers, location details, or account names from other services, that content sits in the editorial inbox alongside everything else, but it doesn’t get extracted, indexed, or used for any purpose beyond the response itself.
The site does not maintain user accounts. There is no registration. There are no logins. There are no profiles tied to individual visitors. Each form submission is treated as an independent piece of correspondence rather than as input to a persistent user record. After the conversation concludes, the message remains in the editorial archive for reference, and a deletion request from the original sender will remove it from there.
Non-Personal Data
Technical data gets logged automatically whenever any browser connects to the site. This is standard for essentially every website on the internet and is required for basic operations to function. The data includes the visiting IP address, the device type and operating system, the browser version, the language settings, the time of the visit, the page or pages visited, and the referrer that brought the visitor to the site. When a search engine sends a visitor here, the search query is generally not visible due to encryption protocols used by the search engine itself. When a link from another site sends the visitor here, the originating page may be visible.
This data is used in aggregate. Individual visitor records are not assembled into profiles, and no effort is made to connect technical logs back to identifiable individuals. The aggregate is what’s useful for understanding which articles get read, which pages have problems on specific browsers, and where the audience is generally located.
The site does not request precise location data. Approximate location can sometimes be inferred from an IP address at a city or regional level, which is what most analytics tools use to show geographic distribution of traffic. Precise GPS-level location is never requested or collected.
How We Use Information
The data collected has a small set of practical uses. Anything outside that set isn’t part of how the site operates.
Communication
Personal data submitted through the contact form is used to respond to the message. That response goes to the email address provided. If a follow-up exchange develops, the data remains in use for as long as the conversation is active. After it concludes, no further use happens, and the data sits in the archive without being reused for marketing, list-building, or any other purpose.
The site does not run a newsletter. There is no mailing list. A form submission does not subscribe the sender to anything. The site will not send unsolicited marketing emails to addresses that came in through the contact form. The only emails that ever go out are direct responses to the message that came in.
Website Improvement
Aggregate technical data informs editorial decisions. If an article gets very few readers, that’s a signal it might need a different approach or might be covering a topic readers don’t actually care about. If a specific browser version produces unusually high error rates on the site, that’s a signal to test the site against that browser and fix whatever’s broken. If readers from a specific country make up an unexpected share of traffic, that’s a signal to consider whether the editorial focus should adjust to serve them better.
None of this analysis involves looking at individual visitors. The aggregates are visible. The individual records that contributed to those aggregates are not extracted or analysed at the per-visitor level, with the rare exception of debugging specific technical problems where a single error report needs to be traced to its root cause.
Data Sharing
The site’s approach to data sharing is simple. The data does not get shared.
No Third-Party Sharing
The personal data submitted through the contact form does not get sold to anyone. It does not get transferred to data brokers, marketing partners, advertising platforms, or any third party for the purpose of monetisation. The site does not generate revenue from selling reader data, and the editorial team does not view the data as a commercial asset.
Aggregate analytics data may pass through a standard analytics provider, the same way most websites use a third-party analytics service rather than building their own. Where this happens, the data sent to the analytics provider does not include identifying information about individual readers, and is configured to limit retention periods on the provider’s side. Specifics of which provider is in use, when one is in use, are available on request through the contact form.
Legal Requirements
Data may be disclosed in response to lawful requests from authorities with jurisdiction over the site. This includes court orders, valid subpoenas, and legal processes from regulatory bodies operating within their authority. Such disclosure happens only when legally required, and where possible the affected user gets notified, except when the legal request itself prohibits notification.
The site does not voluntarily share user data with authorities outside of these specific legal mechanisms. Casual requests, informal inquiries, or pressure short of a binding legal process do not trigger disclosure.
Cookies and Tracking
Cookies are part of how websites function on modern browsers. The site uses them in a limited way, focused on practical site operation rather than tracking individual visitor behaviour across the broader internet.
What Are Cookies
A cookie is a small text file that a website asks the visiting browser to store. The browser sends the cookie back to the site on subsequent visits, which lets the site recognise that the same browser has been there before. Cookies don’t contain executable code and can’t directly modify the device they’re stored on. They’re a recognition tool.
Different cookies serve different purposes. Some cookies last only for the duration of a single visit and get deleted when the browser closes. Others persist longer to remember preferences across visits, like which language the visitor selected or whether they accepted a notification banner.
How We Use Cookies
The cookies used on the site fall into two categories. The first category is functional cookies that help the site operate correctly. These remember choices that affect display, like language preference, and store session information for visits that span multiple page loads.
The second category is analytics cookies that contribute to the aggregate technical data described earlier. These help the site count unique visitors over time without requiring those visitors to identify themselves. The cookie distinguishes one anonymous browser from another anonymous browser, but doesn’t tie either of them to a real-world identity.
The site does not use third-party advertising cookies. There is no ad network reading reader behaviour to build advertising profiles, because the site does not run ads. Visitors who block cookies entirely can use the site, although some functional features may not work as smoothly without them. Most modern browsers offer cookie management controls in their settings, and any visitor who wants to limit cookies has straightforward control over them at the browser level.
Data Security
Reasonable measures protect the data the site holds. No website on the internet can guarantee absolute security, and it would be dishonest to claim otherwise. What the site does is apply standard practices that reduce risk to a reasonable level.
Protection Measures
The site operates over HTTPS, meaning data in transit between visitor browsers and the site server is encrypted. This prevents network observers from reading message content as it travels. Server-side, the site uses standard hosting infrastructure with the security configurations appropriate for the type of data handled.
Access to the editorial inbox is limited to team members who need it for their work. Each team member with access uses their own credentials. Logs of access exist for accountability. The editorial workflow does not require the message data to be accessed by anyone outside the editorial team, and routine processing does not involve external parties.
Security Limitations
Despite reasonable measures, no security setup is unbreakable. Sophisticated attacks on hosting infrastructure, vulnerabilities in third-party software, or social engineering targeting team members are all possibilities that no protective measure fully eliminates. The site does its best to maintain a strong security posture and update practices as new threats emerge, but it cannot guarantee that data stored or transmitted will never be compromised.
In the event of a security incident affecting reader data, the team will respond as transparently and quickly as practical, including notifying affected readers where notification is required by law or by reasonable judgment.
User Rights
Visitors have meaningful rights over the data the site holds about them, and exercising those rights is not designed to be difficult.
Access and Deletion
A visitor who submitted information through the contact form has the right to request a copy of the data the site holds about them. The team will provide this on request through the contact form, with reasonable verification that the request comes from the actual data subject rather than from someone else.
The right to deletion is similar. A visitor can request that data tied to them be removed from the site’s archives. Such a request will be honoured, with the same reasonable verification of identity. After deletion, the data is no longer accessible to the editorial team, and no further use of it can happen. Deletion may take a short period to propagate through backups and archives, but the result is permanent removal from active records.
Control Over Data
The most basic form of data control is choosing what to share in the first place. Visitors who want to communicate without providing identifying information can use a generic email address that doesn’t reveal their real identity, can write under a pseudonym in the name field, and can avoid including personal details in the message body. The site cannot recognise data it never received.
For data already submitted, the deletion mechanism described above is the primary control. For ongoing communication, simply ceasing to respond to the conversation closes the active use of the data, although the historical record of the exchange remains until specifically deleted.
Third-Party Websites
The site contains links to other websites, including bc.game itself and various other resources referenced in articles. These external sites operate independently and have their own privacy practices.
External Links
When a visitor clicks a link that leads to another site, that visitor leaves the protection of this privacy policy and enters whatever data handling environment the destination site provides. The new site can have its own cookies, its own data collection practices, and its own privacy terms that may differ significantly from the standards applied here.
No Responsibility
The site cannot take responsibility for what happens on third-party sites it links to. This is not an evasion. It’s a structural reality of the open web. Each website operator is responsible for their own privacy practices, and visitors who care about how their data is handled should review the privacy policies of any site they spend significant time on.
Changes to This Policy
The privacy policy may need updates over time as practices evolve, regulations change, or new tools get adopted that affect how data flows.
Updates
When the policy gets updated, the new version is published on this page with a revision date noting when the change took effect. Major changes that affect reader rights or significantly alter the categories of data collected will be noted clearly at the top of the policy when published. Continued use of the site after a policy update constitutes acceptance of the updated terms.
Visitors are encouraged to check this page periodically if data handling matters to them, particularly after significant time has passed since their last read.
Contact
Questions about this privacy policy, requests for data access, deletion requests, or any other privacy-related concern can be raised through the contact form on the site. Tagging the message subject as “privacy” helps the team route it correctly, although untagged messages will eventually reach the right place too.