Website Privacy & Visitor Disclosures
This policy details how Justified Systems ("we", "us", or "our") collects, processes, and protects visitor data across our web canvas (justified-systems.com). We operate under a foundational mandate of minimal data retention, radical transparency, and zero behavioral tracking.
Zero Behavioral Tracking Policy
We do not track visitors across the web. Our web canvas operates with zero third-party tracking cookies, zero Google Analytics, zero Meta/LinkedIn tracking pixels, and zero behavioral fingerprinting scripts.
Any state information stored in your browser (such as local interface preferences or the single-run animation state flag) remains strictly inside your client browser's local session storage and is never transmitted to external analytics providers or remote monitoring networks.
Support Forms & Ephemeral Telemetry Processing
When you submit an engineering inquiry or diagnostic report through our Technical Intake portal (/intake), the payload is transmitted securely over TLS 1.3 directly to our Cloudflare edge serverless workers.
Form payloads are formatted into an encrypted transmission dispatched directly to engineering (support@justified-systems.com) and are immediately purged from edge server memory (V8 isolates) following execution. We maintain zero persistent cloud databases storing visitor personal information or contact records.
Crowdsourced Hardware Benchmark Telemetry
Developers submitting benchmark runs generated by run_master_metrology.py transmit hardware execution parameters (GPU/CPU model, memory bandwidth, driver version, OS platform) and test probe timings.
- Verified Hardware Telemetry: Payloads passing our 3-gate anti-tamper filter (Ed25519 signature verification, script hash matching, and kinematic physical limits) commit anonymous silicon metrics to our public compatibility ledger (
KV_ANALYTICS:HARDWARE). Zero IP addresses, machine serials, or personal user identifiers are recorded. - Quarantine Protocol: Submissions failing verification are rejected with a sterile error code (
OPT-005) and logged to an isolated, temporary threat buffer (KV_ANALYTICS:QUARANTINE) for 30 days to protect the bounty pipeline against automated gaming attempts.
Merchant of Record Payment Processing
Commercial one-time major-version licenses, OEM distribution tiers, and project pass purchases are processed exclusively by our Merchant of Record partner, Polar.sh. When initiating checkout, payment card credentials (PCI-DSS Level 1 compliance), billing addresses, and tax collection (EU VAT/Sales Tax) are managed directly on Polar's infrastructure.
Justified Systems receives only cryptographic license fulfillment hashes, customer email addresses for license delivery, and verification receipts. Full credit card numbers, CVVs, and banking credentials never touch our servers.
Offline Client Metrology & Diagnostics Privacy
Pre-flight diagnostic scripts (such as check_metrology.ps1) and the master benchmark harness execute entirely on your local workstation. Hardware inspection metrics, GPU compute capability assessments, and driver compatibility evaluations remain confined to your local terminal session.
Diagnostic telemetry is only transmitted to Justified Systems if you explicitly append the --export flag to submit a technical issue ticket or submit benchmark receipts via the Technical Intake portal.
Runtime Substrate Zero-Telemetry Invariant
All distributed unmanaged runtime binaries (justified_engine.exe, justified_engine), Windows installers (justified_engine_setup.msi), dynamic C-ABI libraries (justified_core.dll, libjustified_core.so, libjustified_core.dylib), and companion weight vaults (.jef_bin) operate with zero telemetry instrumentation.
The runtime contains no phone-home mechanisms, no crash reporting telemetry beacons, and no socket-binding code. Cryptographic license validation (license.key) is performed 100% offline via asymmetric Ed25519 digital signature verification in RAM, ensuring zero external network egress during model inference.