Cookie Configuration & Session Architecture Index
ART. 01Cookie Architecture Philosophy
// CORE PRINCIPLE: HOLOPICKWISE deploys a deliberately minimal cookie and local storage architecture. Transient tracking tokens operate exclusively to preserve user interface options. No advertising cookies, cross-site tracking pixels, behavioral profiling identifiers, or third-party analytics tokens are deployed under any circumstances.
This Cookie Configuration and Session Architecture Index provides a comprehensive technical disclosure of every storage mechanism employed by the HOLOPICKWISE platform, structured to comply with applicable cookie disclosure requirements under the ePrivacy Directive and GDPR regulatory frameworks.
ART. 02Complete Storage Manifest
The following table constitutes the complete and exhaustive index of all local storage keys, session data tokens, and cookie identifiers deployed by the HOLOPICKWISE platform:
| Storage Key | Storage Type | Category | Purpose | Duration | Third Party |
|---|---|---|---|---|---|
hpw_cookie_ack |
localStorage | Records acknowledgement of cookie consent banner to prevent repetitive display on subsequent visits. | Persistent until cleared | ||
| Canvas Buffer | Memory (volatile) | Temporary in-memory storage of image pixel data during active processing session. Purged on page unload or manual clear. | Session-only | ||
| Object URL | Browser Memory | Temporary blob URL reference for file access. Immediately revoked via URL.revokeObjectURL() on session clear. | Session-only |
ART. 03Cookie Category Classification
ART. 04Session Architecture & Initialization
- Step 01 — Consent Check: The platform reads the
hpw_cookie_acklocalStorage key. If absent, the cookie consent banner is rendered. - Step 02 — Engine Init: The background removal engine initializes all DOM event listeners, canvas context objects, and file reader API bindings locally.
- Step 03 — Processing Sandbox: Upon file selection, the FileReader API loads image data into volatile browser memory. No network requests are initiated.
- Step 04 — Alpha Extraction: The segmentation pipeline executes within the canvas rendering context, manipulating pixel arrays in local memory.
- Step 05 — Output Generation: Processed PNG output is generated via toDataURL() and offered for download through a client-side anchor click. No server upload occurs.
- Step 06 — Memory Revocation: Upon session clear, all object URLs are revoked, canvas buffers are cleared, and volatile memory is released.
ART. 05Managing Your Storage Preferences
- Browser Settings: All major browsers provide native tools to view, manage, and delete cookies and localStorage data.
- Platform Clear Function: The Memory Management panel on the engine workspace provides a direct "Clear Buffer" control to purge all volatile session data.
- Incognito / Private Mode: Using the platform in a private browser session ensures all session data is automatically discarded upon window closure.
- Browser Extensions: Cookie management extensions provide granular control over storage permissions on a per-site basis.
ART. 06Policy Updates & Contact
This Cookie Configuration Index is updated whenever changes are made to the platform's storage architecture. Continued use following any update constitutes acceptance of the revised disclosure.
For inquiries, correspondence may be directed to: Aperture Matrix Way, Cluster Tower 8A, San Jose, CA 95110, United States.