Cookies & Storage Policy
Effective Implementation Date: June 5, 2026 | Last Updated: June 29, 2026
1. Introduction & Zero-Cookie Architecture
This Cookies & Storage Policy details the client-side data mechanisms maintained by Surge Systems ("we," "our," or "us").
In absolute alignment with the **EU Privacy and Electronic Communications Directive (ePrivacy Directive)** and the **GDPR**, our web architecture operates with a zero-cookie infrastructure. We do not write, request, or maintain persistent HTTP cookie files on our production servers or client browsers to track your engagement profiles.
2. Absolute Tracking & Profiling Refusal Statement
Because we do not deploy traditional tracking cookie strings, our platform does not engage in advertising, commercial retargeting, cross-site behavior profiling, or automated marketing tracing. Your code interactions and navigation paths across this portfolio remain isolated and completely anonymous.
3. Client-Side Web Storage Technologies
Instead of cookies, our web template uses standard HTML5 client-side data sandboxes to provide high-performance caching configurations. This architecture is defined across the following scopes:
- Local Storage (LocalStorage): A localized browser database that saves configuration variables inside your personal hard drive. We use this strictly to remember your user interface settings and log whether you have acknowledged our data disclosure banner. This data never leaves your device.
- Session Storage (SessionStorage): Volatile, localized memory instances that clear themselves automatically the second you destroy your active browser tab.
- Other Caching Infrastructure: We do not deploy hidden web beacons, invisible trackers, metadata tracking scripts, or pixel tracking files within our application layout layer or backend endpoints.
4. Granular System Caching Matrix
The following table catalogs the technical storage variables initialized across our client-side platform framework:
| Storage Variable ID | Engine Scope | Purpose Description | Data Persistence Lifecycle |
|---|---|---|---|
| `theme-preference` | LocalStorage | Persists user styling states to prevent visual white flashes on changing routes. | Persistent (Until Manual Clear) |
| `cookie-banner-acknowledged` | LocalStorage | Remembers that you have reviewed and closed our platform data storage alert box. | 1 Year |
5. Disabling Mandatory Local Browser Caching
If you adjust your browser privacy parameters to systematically reject all client-side storage keys or enforce an absolute sandbox wipe, our portfolio application will remain functional, but you will experience interface degradation.
Specifically, our website components will lose the ability to cache your choice of dark styling layouts (causing an immediate fallback to system default profiles upon every new click), and the system data banner will reappear on every layout initialization.
6. Managing Client Storage Controls
You retain absolute sovereign control over your browser's data memory. You can manually wipe all cached LocalStorage variables and clear state records instantly at any time by accessing your browser's built-in Settings panel, choosing Clear Browsing Data, and checking the option for Cookies and other site data.
7. Policy Infrastructure Updates
We reserve the right to deploy updates to this tracking breakdown to match adjustments in our frontend architecture or international framework compliance regulations. Any structural variations will be updated on this live endpoint alongside a revised modification timestamp located in the header.
8. Contact & Corporate Compliance Desk
If you require explicit legal or technical verification concerning our client-side storage boundaries or data minimization policies, please send your inquiry directly to our desk: privacy@surgesystems.com.