Last updated: October 19, 2026

This policy explains how TheHaxorNews handles information when you read our website, subscribe to updates, contact us or use an authorised staff account.

It covers thehaxornews.com and its first-party website features. Services you reach through advertisements, external links or embedded content have their own privacy practices.

1. Who we are and how to contact us

TheHaxorNews is the publication responsible for the first-party activities described here. Contact us through the contact page with “Privacy request” in the subject.

2. Information we use and why

Reading and using the website

Delivering pages and protecting forms requires processing connection information such as your IP address, browser information, requested address and request time. Session records may contain IP and browser information; hosting, security services and error logs may also hold technical request information. This is separate from the optional analytics database described below.

Article popularity totals use a temporary keyed value derived from connection information to limit repeated counts. That deduplication value expires after one hour. The total remains associated with the article, not a named reader, and is separate from optional detailed traffic measurement.

Newsletter subscriptions

We collect your email address, signup and consent records, subscription status and delivery records. Submitting the newsletter form with your consent activates your subscription immediately. We send email alerts when new articles are published in any category; no email confirmation is required. Each newsletter includes an unsubscribe link; unsubscribing stops future newsletter sends, although a message already being processed may still arrive. You do not need to subscribe to read public articles.

Messages and enquiries

The contact form collects your name, email address, subject and message to handle your enquiry, assess a correction or respond to a request. Required fields are needed to process the form. Do not include passwords or unnecessary sensitive personal information.

Browser notifications

If you enable notifications, we store a push subscription endpoint and the keys required to deliver messages through your browser's push service. These identify a browser subscription, not a public profile. You can disable notifications using the website's notification controls or your browser's site permissions.

Staff accounts

For authorised contributors and administrators, we process account details, public author profiles, roles, password hashes, security settings, sessions and activity records. These support authentication, publishing permissions and accountability. Author names and biographies may appear publicly with published work.

3. Optional audience measurement

When you accept optional cookies, our first-party analytics can record the page or article opened, visit times, approximate active reading time, scroll depth, device and browser categories, referring website hostname and approximate country.

A random browser identifier is renewed daily. The server stores keyed daily identifiers rather than the original browser identifier. These records are pseudonymous estimates, not verified people: they do not tell us a visitor's name or exact location. This analytics database does not retain raw IP addresses, complete browser user-agent strings or full referring URLs. Technical processing elsewhere on the site may still use connection data as described in section 2.

When configured, Cloudflare supplies approximate country information; otherwise it may be unavailable. Logged-in staff visits, recognised bots and browser Do Not Track or Global Privacy Control signals are excluded from this optional first-party measurement. Live counts and reading time are estimates and pause when a page is hidden or becomes idle. These signal exclusions do not describe every external advertising provider's behaviour.

4. Cookies and browser storage

  • Essential sessions and form protection: session cookies and security tokens support sign-ins, form submissions and abuse prevention. The application session lifetime is 120 minutes of inactivity.
  • Your preferences: browser storage remembers your theme and cookie choice until you change them or clear site data.
  • Optional measurement: the daily browser identifier is used only after optional consent and is removed when you withdraw that consent through our controls. An unused stored value can remain on your device until the next visit or until you clear it.
  • Optional advertising: configured advertising scripts load after you accept optional cookies. Providers may set their own cookies or similar identifiers.

Use Cookie choices in the footer to review your choice, or . Select Essential only to stop future optional measurement and advertising script loading. This does not automatically erase previously collected records or cookies already set by another provider; you can also clear site data in your browser. Blocking all cookies may prevent some forms or sign-ins from working.

5. Advertising, links and embedded content

Direct company banners link to advertisers' websites. Opening a banner takes you to a separate service with its own privacy policy. Displaying a locally hosted banner does not itself require sending your newsletter address to the advertiser.

Where Google AdSense is enabled, Google and other advertising vendors may use cookies to select ads based on previous visits to this and other websites. Depending on the consent and advertising configuration, ads may be personalised. Learn about Google's use of information on partner sites and manage personalised advertising through Google My Ad Center. Other participating advertising vendors may have their own controls.

External videos connect to their provider when you choose to load the embed. The provider then receives connection information and may use storage under its own policy. Social sharing links and other external links likewise take you to services outside our control.

6. Service providers and disclosure

Hosting and infrastructure providers process information needed to run the website. Our configured email service processes subscriber addresses and messages for delivery. Browser push providers deliver requested alerts. If Cloudflare protection or Turnstile is enabled, Cloudflare may process connection and challenge information to detect abuse. Advertising and embedded-content providers receive information when their features load.

Access within the publication is limited by staff roles and operational need; the detailed audience dashboard is restricted to the owner. Subscriber lists are not offered for sale by the publication. We may disclose relevant information where required by law, to address abuse or to protect the rights and security of the website and its users. Advertising data practices should be assessed separately from the handling of newsletter lists.

7. Grounds for processing and international services

Where applicable data-protection law requires a legal basis, consent supports optional newsletters, audience measurement and optional advertising storage. Operating the website, responding to enquiries and preventing misuse may rely on legitimate interests in maintaining a useful, secure publication. Staff administration may also be necessary for an agreement, and some records may be required by law. The applicable basis depends on the activity and jurisdiction.

Service providers may process information outside your country. The location and protections depend on the providers actually used. Contact us for details of relevant providers, processing locations and applicable transfer arrangements. This policy does not imply that every country offers identical protections or that a particular transfer mechanism applies to every service.

8. How long information is kept

The application's routine cleanup schedule uses the following periods. Deletion is applied when scheduled maintenance runs; limited retention may be necessary to address a legal obligation or an active dispute.

  • Legacy unconfirmed newsletter registrations: removed after 7 days.
  • Active subscriptions: kept while subscribed; unsubscribed records are removed after 30 days.
  • Contact messages and sent or skipped email delivery records: removed after 90 days.
  • Detailed first-party traffic records: removed after 90 days.
  • Imported aggregate search-performance reports: removed after 365 days.
  • Staff activity records: removed after 180 days. Staff accounts remain while needed for authorised work and publication records.

Push subscriptions remain until removed through the website or identified as invalid during delivery. Changing browser permission alone may not immediately remove the server record. Session records become unusable after expiry and are cleared through session maintenance. Backup retention is separately configured, with a default of 14 days; deletions can remain in a backup until that backup expires. Infrastructure logs and provider records follow their own configured periods. Ask us if you need details for a particular record.

9. Your choices and requests

You can withdraw optional consent through Cookie choices, unsubscribe from newsletters and disable browser alerts. Withdrawal does not undo processing that took place before it.

Depending on applicable law, you may request access, correction, deletion, a portable copy, restriction or objection to certain processing. In particular, you may object to processing based on legitimate interests and to direct marketing where the relevant law provides that right. Use the contact details in section 1; explain the service involved and the request. We may need proportionate verification, and pseudonymous traffic records may not be identifiable from an email address alone.

We handle requests within the period required by applicable law and explain any lawful limitation. You may also complain to the relevant data-protection authority; UK readers can contact the Information Commissioner's Office, and EEA readers their local supervisory authority. The publication's first-party analytics does not make automated decisions with legal or similarly significant effects about you.

10. Security and younger readers

We use safeguards such as access controls, password hashing and form protection. No website or transmission method can guarantee absolute security. Please report suspected exposure through the contact page without sending exploit payloads or another person's private data.

The publication is intended for a general audience, not services directed at children. If you believe a child supplied personal information without appropriate permission, contact us so we can assess the request and remove information where appropriate.

11. Policy updates

We may update this policy as features, providers or legal requirements change. The date above identifies the latest revision. Where required, material changes will be communicated and fresh consent requested before a new optional use begins.