1. Cookies vs. Local Storage
Because GoValidate.ai is built to process data client-side in the browser, we rely heavily on browser-based local storage sandboxes (such as LocalStorage and the Origin Private File System) rather than traditional server-side cookies. This ensures your private data stays on your machine and allows high-performance processing of large files.
2. Browser Storage & Data Buffers
We use the following client-side technologies to make the validation workspace functional:
- Origin Private File System (OPFS): When processing large datasets, the app utilizes the browser's OPFS API to create highly optimized local database buffers. This allows the app to validate and reconcile files exceeding standard memory limits without uploading raw rows to our servers. These files are stored in your local browser profile and deleted when you clear your browser site data or close the active project workspace.
- LocalStorage: We store workspace state configurations, user display preferences, and feature flags in your browser's local storage. This allows us to restore your active workspace state when you return. LocalStorage is persistent but can be deleted through your browser settings.
- SessionStorage: Used to maintain temporal state objects (such as current navigation references) within a single tab session. SessionStorage is automatically cleared when you close your browser tab.
3. Tracking Cookies & Telemetry Session Identifiers
We use first-party cookie identifiers and local storage variables solely to track application usage, traffic patterns, and optimize user experience:
- Anonymous Identity Keys: We assign random, unique session identifiers (such as `anon_id` and `session_id`) stored in browser storage. These keys distinguish unique page visits and funnel steps to measure conversion rates, and they are automatically deleted after 90 days.
- User Authentication Session: When you log in, standard secure session cookies are issued to maintain your authenticated status while using the services.
- Redaction Security: These cookies and tracking variables contain only system status IDs and anonymous telemetry values. They never contain raw names, email addresses, credit cards, or passwords.