Data Security Architecture, Zero-Surveillance & Client-Side Privacy Standards
What Grass Is This operates on a client-side execution model where all botanical identifications, square-footage entries, and fertilizer rate calculations run exclusively inside your browser DOM. No lawn measurements or geographic telemetry are transmitted, recorded, or monetized.
1. Zero-Telemetry Client-Side Engine Architecture
Unlike predatory agricultural software platforms that harvest residential geographic information system (GIS) boundaries and homeowner property data, What Grass Is This executes 100% of mathematical operations within the user’s local browser instance. When you adjust the rotary spreader dial slider or input lawn square-footage, the stoichiometric calculations occur via client-side JavaScript without server calls.
2. Ephemeral LocalStorage State & Deep-Link Privacy
Your diagnostic history and saved fertilizer trials are preserved exclusively inside your browser's encrypted localStorage sandbox. No central database, tracking cookies, or cross-site fingerprinting scripts are loaded. Deep-link sharing parameters (e.g. ?sqft=5000&targetN=1.0) are deserialized entirely in memory and never transmitted to analytical third parties.
3. Content Security Policy (CSP) & Subresource Integrity
Our Cloudflare Edge distribution enforces rigorous HTTP security headers, including strict Content Security Policy (CSP), HTTP Strict Transport Security (HSTS with max-age=31536000; includeSubDomains; preload), and X-Content-Type-Options: nosniff. All external typography assets are pre-connected to Google Fonts over TLS 1.3 with zero unauthorized third-party tracker scripts.