# ThreatWall Privacy Notice

Version: 2026-09-08

Status: pre-release template requiring privacy-counsel and data-mapping review before production use.

ThreatWall [LEGAL ENTITY / CONTROLLER DETAILS] processes account identifiers, authentication and session data, organization membership, service configuration, target URLs, scan evidence and findings, audit events, billing references, support communications, and operational telemetry.

We use this information to provide and secure the service, authenticate users, execute authorized scans, produce reports, administer subscriptions, prevent abuse, troubleshoot incidents, and meet legal obligations. The applicable legal bases depend on the relationship and jurisdiction and must be completed by counsel: [CONTRACT / LEGITIMATE INTEREST / CONSENT / LEGAL OBLIGATION].

Service providers may include hosting, object storage, email delivery, identity, payment, monitoring, and customer-selected integrations. Publish the approved subprocessors, locations, transfer mechanisms, and change-notice process at [SUBPROCESSOR URL]. ThreatWall does not store full payment-card details when a hosted payment provider is used.

Retention is controlled by the subscribed plan and documented service settings. Security audit records may be retained longer than scan artifacts for accountability. Backups and legally required holds may expire on a separate schedule. Complete exact periods after validating production operations.

Depending on applicable law, individuals may request access, correction, deletion, restriction, objection, portability, or withdrawal of consent. Requests and complaints should be sent to [PRIVACY CONTACT]. Identity verification may be required. EU/UK users may contact their supervisory authority.

Security incidents affecting personal data are handled under the incident-response plan and applicable notification deadlines. This notice will identify material changes by a new version date.

Contact/controller/DPO: [COMPLETE BEFORE LAUNCH]
