Cookie Policy
Cookie Policy
Last updated: April 2, 2026
GrayLeads does not currently use a traditional analytics or advertising cookie stack in the repository. Instead, it relies mainly on browser localStorage for essential product behavior, and some third-party cookies may still be set by Google when users authenticate with Google or use map-related functionality. This page also covers the Europe and Germany context for consent and device storage.
1. What this policy covers
This policy covers first-party browser storage used by GrayLeads and the limited third-party cookie scenarios evident from the current codebase. It does not create new categories of cookies that are not actually implemented. For users in the EU, EEA, and Germany, it also explains how GrayLeads approaches consent under GDPR, ePrivacy-style rules, and Germany's TDDDG for non-essential storage.
2. Storage and cookies detected
| Key or technology | Type | Purpose | Duration |
|---|---|---|---|
| grayleads-auth | localStorage | Persists signed-in user state, access token, refresh token, and business-mode workspace context. | Until logout or until the browser storage is cleared. |
| omnilead-admin-sync | localStorage | Synchronizes certain admin updates across browser tabs. | Until overwritten or the browser storage is cleared. |
| grayleads-cookie-consent | localStorage | Stores the visitor's consent banner preference. | Until preferences are changed or browser storage is cleared. |
| Google service cookies | third-party cookies | May be set by Google when a user connects a Google sender account or interacts with Google Maps features. | Controlled by Google, not by GrayLeads. |
3. Essential storage
GrayLeads requires certain browser storage to function correctly. Without it, sign-in persistence, workspace switching, and consent preference storage may not work properly. These items are treated as essential because they support core account and product behavior.
In Europe and Germany, GrayLeads treats these items as necessary for the requested service. The current codebase does not show first-party analytics, advertising, or remarketing storage that would need separate consent before GrayLeads itself sets it.
4. Optional third-party cookies
The codebase integrates Google Maps and Google OAuth. Depending on how the browser interacts with those services, Google may place or read its own cookies. GrayLeads does not directly control Google\'s cookie inventory or retention rules.
- Google sender-account connection flows can involve Google-controlled cookies during OAuth.
- Map rendering or Google service requests can involve Google-controlled cookies or similar technologies.
5. What GrayLeads does not currently use
- No first-party analytics SDKs were detected in the current repository.
- No ad pixels, remarketing tags, or cross-site advertising scripts were detected in the current repository.
- No cookie-based payment checkout flow was detected in the current repository.
6. Your choices
- You can clear or block localStorage through your browser settings, but doing so may sign you out or break workspace persistence.
- You can use the GrayLeads consent banner to record an essential-only preference. This is the control surfaced by the current repository for Europe and Germany visitors.
- You can review and manage Google cookie behavior through your browser and Google account settings.
7. Changes and contact
GrayLeads may update this policy if it adds analytics, advertising, or other storage technologies in the future. Questions can be sent to contact@softwareforge.agency.