ThreatPoint.co.uk THREAT INTELLIGENCE & RISK
Return to Site
LEGAL POLICY • PECR REGULATION 6 • UK GDPR ART 6(1)(F)

Privacy, Cookies & Telemetry Policy

How ThreatPoint processes client-side local storage and security telemetry under UK data protection law. Designed with privacy by default: zero marketing trackers, zero cross-site tracking, and no intrusive consent banners.

Last Updated: November 2026 • Jurisdiction: United Kingdom (ICO) • Status: Active & Enforced

Why you don't see a cookie banner on ThreatPoint

Under the UK Privacy and Electronic Communications Regulations (PECR Regulation 6) and UK GDPR guidance from the Information Commissioner's Office (ICO), websites that store or access information on a terminal device strictly for technical delivery, transmission, or security do not require consent banners.

We do not deploy behavioural advertising pixels, third-party social trackers, cross-site cookies, or non-essential analytics. As a cybersecurity service provider, we practice minimal, purpose-bound telemetry.

Terminal Equipment Transparency

1. Cookies & Local Storage Schedule

The following storage items are utilized exclusively to secure network requests, authenticate sessions, and protect client endpoints against CSRF and automated attacks.

Identifier / Key Storage Type Provider Specific Technical Purpose Duration
__Host-tp_csrf Cookie threatpoint.co.uk Protects API payloads and contact forms against Cross-Site Request Forgery (CSRF). Session
tp_session_id Cookie threatpoint.co.uk Maintains cryptographic session validation for authenticated client API portals. 24 Hours
__cf_bm / cdn_sec Security Cookie Cloud CDN Edge DDoS bot-challenge token; distinguishes human users from automated attack crawlers. 30 Minutes
tp_theme_pref localStorage threatpoint.co.uk Stores client contrast, typography, and accessibility display choices locally. Persistent
How to manage cookies in your browser: You can purge or reject cookies anytime via your browser settings. Blocking essential security tokens may prevent access to authenticated customer consoles or form validation.
Core Security Operations

2. Fraud Prevention & IP Reputation

ThreatPoint analyzes technical connection indicators to defend web properties against automated exploits, credential stuffing, carding attacks, and malicious bot traffic.

ThreatPoint as Data Controller

We act as a Controller for telemetry captured directly on our own infrastructure, sensor network, public endpoints, and website (threatpoint.co.uk). This data is processed to defend our perimeter and construct baseline IP risk reputations.

ThreatPoint as Data Processor

When enterprise clients query our API with IP addresses or transaction metadata, we act as a Data Processor under a formal Data Processing Agreement (DPA). We evaluate the payload against threat intelligence models solely on the client's documented instructions.

Categories of Technical Data Processed

We collect solely network identifiers and machine-generated protocol metrics. We never collect Special Category Data (UK GDPR Article 9) or attempt to resolve IP addresses to real-world residential postal records:

Network Identifiers IPv4/IPv6 addresses, Autonomous System Numbers (ASN), ISP / carrier tags, and reverse DNS.
Protocol Telemetry TLS cipher parameters, HTTP request headers, User-Agent strings, and timestamped request intervals.
Risk Signals Known association with open proxies, Tor exit nodes, hosting provider ranges, and automated scraper clusters.
UK GDPR Article 6(1)(f)

3. Lawful Basis: Legitimate Interests

We process technical personal data under our Legitimate Interests (Article 6(1)(f) of the UK GDPR). Preventing cyber-attacks and securing computer systems are explicitly acknowledged as legitimate interests under European and UK data protection frameworks:

Recital 49 • UK GDPR
"The processing of personal data to the extent strictly necessary and proportionate for the purposes of ensuring network and information security... constitutes a legitimate interest."
Recital 47 • UK GDPR
"The processing of personal data strictly necessary for the purposes of preventing fraud also constitutes a legitimate interest of the data controller."

Our Legitimate Interests Assessment (LIA) verifies that machine-level analysis of IP traffic poses negligible risk to the fundamental freedoms of individual users, while providing critical security benefits across interconnected digital ecosystems.

Storage Limitation (Art. 5(1)(e))

4. Data Retention Schedule

Technical logs are rotated and purged automatically on strict timeframes according to operational sensitivity.

Telemetry Category Operational Purpose Retention Window Disposition Method
Raw HTTP & Edge Ingress Logs Attack mitigation, triage & troubleshooting 30 to 90 Days Automated cryptographic overwrite & purge
Active Firewall & Rate-Limiting Rules Brute-force and bot mitigation state 7 to 30 Days Automatic dynamic de-listing
IP Reputation & Proxy Scores Reputation trend evaluation Rolling 180 Days Purged or degraded to subnet aggregates
Aggregated Threat Indicators Botnet signatures, high-risk CIDRs Indefinite (Anonymised) Non-personal statistical summaries
Chapter III UK GDPR

5. Data Subject Rights & Objection

Individuals in the United Kingdom and EEA possess statutory rights regarding personal data, including the right to request access, rectification, erasure, and restriction of processing.

Right to Object (UK GDPR Article 21) & Delisting

Where we process an IP address under legitimate interests, you have the right to object or request a reputation re-evaluation. If you believe your IP address has been incorrectly classified or is suffering a false-positive flag:

Note: Under Article 21(1), processing may continue if compelling legitimate security grounds are demonstrated (such as addressing active, ongoing volumetric DDoS attacks or automated vulnerability probing).

You also have the right to lodge a complaint with the UK supervisory authority: Information Commissioner's Office (ICO) →