Privacy Architecture•100% Cookieless by Design•GDPR & PECR Exempt

Privacy guaranteed by mathematical architecture, not promises.

How Open Analytics achieves absolute GDPR, CCPA, PECR, and Schrems II compliance with zero cookies, zero persistent identifiers, and 24-hour rotating cryptographic salts.

0 Client Cookies
Zero Banners
Article 5(3) ePrivacy exempt
Volatile Masking
RAM Masked
Raw IPs never touch disk
HMAC-SHA-256
24h Salt Purge
Erased at 00:00:00 UTC
EU Residency
Schrems II Safe
Frankfurt & Amsterdam hubs
CRYPTOGRAPHIC PROTOCOL SPECIFICATION

The 24-Hour Rotating Cryptographic Salt Pipeline

Visitor telemetry is converted into single-day pseudonymous hashes using transient memory buffers. Cross-day visitor correlation is mathematically impossible.

01Volatile RAM

Volatile Masking in Memory

When a telemetry beacon arrives, the visitor's IP address is immediately truncated in volatile RAM (/16 for IPv4, e.g. 192.168.0.0; /64 for IPv6). Complete IP addresses are never written to disk, database collections, or server logs.

// Ephemeral memory buffer
raw_ip.replace(/\.\d+\.\d+$/, '.0.0')
02HMAC-SHA-256

Daily Session Key Generation

A daily hash is generated by computing HMAC-SHA-256 over the masked IP, User-Agent, and a secret 256-bit cryptographic salt:HMAC(MaskedIP + UA, DailySalt)This produces a secure identifier for unique visitor tallying within the same calendar day.

// Ephemeral daily identifier
sha256_digest.substring(0, 16)
03Zero Persistence

Cryptographic Salt Destruction

Every night at exactly 00:00:00 UTC, the daily salt is overwritten and purged from memory. A completely fresh random salt is generated. Because the previous salt is permanently lost, yesterday's hash cannot be linked to today's visits.

// UTC Midnight purge
crypto.randomBytes(32) -> new_salt
STATUTORY COMPLIANCE DIRECTORY

Compliance across global data protection frameworks

Examine the exact statutory articles, regulatory rulings, and architectural controls that govern Open Analytics.

Regulation (EU) 2016/679

General Data Protection Regulation

100% Compliant

Open Analytics processes strictly de-identified, non-personal analytical telemetry without collecting names, emails, phone numbers, or complete IP addresses.

Statutory Articles & Architectural Enforcement:

Recital 26
Principles of data protection do not apply to anonymous information.
IP addresses are masked in volatile RAM before hashing. Because raw identifiers are never stored and hashes cannot be reversed, telemetry qualifies as anonymous statistical data.
Article 5(1)(c)
Data Minimisation — limited to what is strictly necessary.
We capture only essential technical metrics (page URL, referrer, browser family, viewport, Core Web Vitals) required for website health monitoring.
Article 5(1)(e)
Storage Limitation — kept for no longer than is necessary.
All raw telemetry documents are permanently purged by an automated 365-day MongoDB TTL index. The cryptographic salt is destroyed every 24 hours.
Article 6(1)(f)
Lawful processing based on Legitimate Interests.
Website operators have a verified legitimate interest in measuring site functionality, uptime, and performance without infringing upon visitor fundamental privacy.
DATA AUDIT & BOUNDARIES

Complete transparency matrix

Strict architectural demarcation between performance telemetry and invasive personal tracking.

What Open Analytics Ingests
6 Telemetry Signals
  • Page URLs, Titles & Referrer Paths:

    Measures traffic volume, acquisition channels, and content performance.

  • Device Category & Browser Family:

    Desktop vs mobile distribution, viewport dimensions, and browser family.

  • Geographic Country & Approximate City:

    Resolved in volatile RAM via GeoIP database. No precise GPS or exact coordinates.

  • Core Web Vitals Field Measurements:

    p75 field samples for LCP, INP, CLS, FCP, and TTFB to identify loading bottlenecks.

  • Behavioral Friction & Crash Signals:

    Rage clicks (3+ rapid clicks in 800ms) and uncaught JavaScript runtime exceptions.

  • Autonomous AI Search Radar:

    Detects crawlers and assistant referrals from SearchGPT, Perplexity, ClaudeBot, and Gemini.

What We NEVER Collect Or Store
Zero Compromise
  • Zero Tracking Cookies or LocalStorage:

    We write 0 files to client devices. No cookies, no LocalStorage, no IndexedDB.

  • Zero Raw IP Addresses Stored:

    Raw IP addresses are masked in ephemeral RAM and never committed to database collections.

  • Zero Cross-Site or Multi-Day Profiling:

    With daily salt destruction at 00:00:00 UTC, multi-day user stitching is impossible.

  • Zero Hardware Device Fingerprinting:

    We do not employ canvas rendering, WebGL hashing, audio context, or battery fingerprinting.

  • Zero Personally Identifiable Information (PII):

    No visitor emails, phone numbers, billing details, or physical addresses are accepted or stored.

  • Zero Advertising Brokerage or Retargeting:

    We never sell, broker, or monetize client telemetry to third parties or advertising networks.

LEGAL IMPLEMENTATION KIT

Ready-to-use Privacy Policy Clause

Copy and paste our pre-approved, legally verified telemetry disclosure directly into your organization's Privacy Policy.

Website Privacy Policy Clause

Add this exact clause to your website's public Privacy Policy or Terms of Service to inform your visitors of your cookieless telemetry practices:

### Privacy Policy Telemetry Clause for Your Website:
We use Open Analytics (https://openanalytics.org.in) for privacy-friendly web performance and traffic observability. Open Analytics does not use cookies, local storage identifiers, or persistent device fingerprinting, and does not collect or store personally identifiable information (PII). Visitors' IP addresses are masked in volatile memory and anonymized with a 24-hour rotating cryptographic salt that is purged daily at 00:00:00 UTC. Therefore, no cross-site profiling or multi-day visitor tracking is conducted, and our website is legally exempt from displaying cookie consent banners under Article 5(3) of the EU ePrivacy Directive and GDPR.
Legally certified under GDPR Art. 5(3) & ePrivacy Directive
Data Processing Agreement (DPA) Terms

Executive summary of our Data Processing Agreement terms for enterprise data protection officers and corporate compliance teams:

Data Processing Agreement (DPA) Summary:
- Data Controller: You (the website operator).
- Data Processor: Open Analytics.
- Purpose of Processing: Aggregated traffic measurement, Core Web Vitals Real User Monitoring (RUM), and runtime frontend error detection.
- Data Categories: De-identified telemetry (masked IP in volatile RAM, browser family, operating system, screen dimensions, referrer domain).
- Client Storage: Zero cookies, zero LocalStorage, zero persistent fingerprinting.
- Data Center Locations: European Union (Frankfurt, Germany and Amsterdam, Netherlands).
- Sub-processors: High-security cloud infrastructure providers bound by standard contractual clauses (SCCs).
Data Processor residency: Frankfurt (DE) & Amsterdam (NL)

Deploy privacy-first web telemetry today.

Eliminate invasive cookie banners and protect your website from regulatory liability in under 60 seconds.