DEFENSIVE DATA PROTECTION SPECIFICATION

Privacy Policy & Scanner Data Handling

SiteScanAPI is built on a simple defensive premise: we analyze public HTTP headers and DNS configurations without invasive tracking, ad monetization, or private data harvesting.

Effective: October 26, 2026
Version 2.4 (RFC Compliance Edition)
Zero User Tracking
01•Architectural Scope

1. Scope & The Passive Architecture

SiteScanAPI ("SiteScanAPI", "we", "us", or "our") provides automated, passive security header audits, DNS-over-HTTPS (DoH) records validation, and perimeter posture diagnostics via our website and public REST API (GET /api/scan).

This Privacy Policy explains the nature of data processed when you interact with our platform. Because SiteScanAPI functions solely as a defensive diagnostic engine, we do not require account registration, passwords, credit card numbers, or administrative access credentials to evaluate public web endpoints.

Key Rule: We never execute intrusive penetration testing, fuzzing, or credential stuffing. We only evaluate the exact HTTP headers and DNS records that your public web server transmits openly to any connecting browser.
02•Telemetry & Targets

2. Information We Process

We process two categories of operational information:

A. Target Domain Information (Input by Users)

When a user initiates an audit, our edge nodes request public HTTP/HTTPS response headers from the specified Fully Qualified Domain Name (FQDN). We collect:

  • Public HTTP Response Headers (e.g., Strict-Transport-Security, Content-Security-Policy, Server, X-Frame-Options).
  • Public DNS Resource Records queried via RFC 8484 DNS-over-HTTPS (e.g., SPF TXT records, DMARC TXT records, CAA records).
  • TLS Handshake Negotiation parameters (e.g., TLS protocol version, cipher suite identifier, certificate expiration date).

B. Client Edge Telemetry (Your Connection)

When you access the SiteScanAPI web dashboard or REST endpoints, our Cloudflare edge network automatically processes standard HTTP request headers:

  • IP address (used exclusively for volumetric rate limiting and edge DDoS mitigation; anonymized after edge processing).
  • User-Agent and referring URL to properly format the response.
  • Timestamp and latency metrics to ensure global edge reliability.
03•Processing Purpose

3. Purpose & Processing

We process collected data under the following legitimate interests and operational purposes:

  • Security Posture Scoring: Calculating deterministic defensive scores against IETF and W3C specifications to help engineers patch missing HTTP security protections.
  • Automated Remediation: Generating tailored server configurations for Nginx, Apache, Caddy, Cloudflare, and Vercel.
  • Abuse Prevention & Availability: Throttling automated scrapers or abusive traffic that violates our 60 req/min fair-use threshold.

We do not sell, rent, monetize, or broker scanned data to third-party data aggregators or advertising networks.

04•Edge Caching

4. Caching & Public Scan Data

To protect scanned origin servers from unintended denial-of-service and to optimize edge performance, audit results are cached for 15 minutes at the Cloudflare edge layer.

Because HTTP response headers are public broadcasts by specification, audit results generated through SiteScanAPI may be accessible to other users who query the exact same target domain within that 15-minute window. We do not expose the identity or IP of the user who initiated the scan.

05•Zero Tracking Cookies

5. Cookies & Local Storage Policy

SiteScanAPI does not use marketing, profiling, or cross-site tracking cookies. We do not integrate Google Analytics, Meta Pixel, or ad tracking SDKs.

We utilize browser localStorage strictly for functional interface preferences:

KeyTypePurpose
themeFunctionalStores light or dark mode UI preference
auto_rollback_enabledFunctionalRemembers user toggle for top scroll helper
06•Infrastructure Partners

6. Infrastructure & Sub-Processors

We operate exclusively on verified enterprise cloud infrastructure to guarantee deterministic uptime and cryptographic data confidentiality:

Cloudflare, Inc.Global Edge Network

Executes serverless worker logic, handles anycast routing, provides DNS-over-HTTPS recursive resolution, and mitigates L3/L4 volumetric attacks. Data processed in the USA and European Union edge locations under Cloudflare Data Processing Addendum (DPA).

07•Lifecycle Durations

7. Data Retention Schedules

Data CategoryRetention PeriodDisposition Mechanism
Domain Scan Results15 MinutesAutomatic TTL edge eviction
Rate Limiting Counters60 SecondsIn-memory sliding window reset
Edge Access LogsMax 14 DaysAutomated Cloudflare log purge
Contact Form Submissions90 DaysEncrypted archive rotation
09•Defensive Guardrails

9. Edge Security Protections

We practice what we preach: SiteScanAPI enforces maximum perimeter defenses including mandatory TLS 1.3, strict Content Security Policy directives, HTTP Strict Transport Security with preload flags, Cross-Origin Opener Policy isolation, and automated cryptographic key rotation.

10•Governance

10. Contacting the Data Protection Officer

For privacy inquiries, domain exclusion requests, or statutory compliance matters, please reach our Data Protection Office directly:

Data Protection Team: SiteScanAPI Security Governance
Security & RFC 9116: /.well-known/security.txt
Turnaround SLA: Statutory inquiries responded to within 48 business hours.