Current position
ExpoLeadZ does not currently load advertising, behavioral tracking, or optional public-site analytics. The visible analytics data attributes in product markup are inert and no analytics provider is connected. As a result, we do not display a consent banner merely for necessary authentication and security technology. If optional analytics or advertising is introduced, it must remain blocked until any consent required by law is obtained, with Reject as easy as Accept.
First-party browser inventory
| Name | Provider | Purpose | Duration | Category |
|---|---|---|---|---|
sb-ukjrytvzkgfpcxklnkoq-auth-token and numbered chunks such as .0, .1 | ExpoLeadZ / Supabase | Stores and refreshes the signed-in session. Chunk names appear only when the session needs more than one cookie. | Up to 400 days at browser level; the server-side session can expire or be revoked earlier, and sign-out removes it. | Strictly necessary authentication and security; first party. |
sb-ukjrytvzkgfpcxklnkoq-auth-token-*-code-verifier and related verifier index where an OAuth/PKCE flow requires them | ExpoLeadZ / Supabase | Completes and protects a one-time authentication flow. | Temporary flow state; removed or superseded when the flow finishes or expires. | Strictly necessary authentication and security; first party. |
Anonymous homepage, pricing, legal, support, signup, and login page views do not intentionally create an ExpoLeadZ analytics identifier. The web implementation does not write application data to localStorage or sessionStorage.
Stripe-hosted checkout
Checkout begins only after an authenticated billing manager confirms business use and chooses a plan. The browser then leaves ExpoLeadZ for a Stripe-hosted page. Stripe may use its own necessary cookies or storage for checkout, fraud prevention, payment security, and regulatory functions. Those are third-party technologies controlled by Stripe, can change independently of ExpoLeadZ, and are described in Stripe's current cookie and privacy information. ExpoLeadZ does not load Stripe advertising or tracking scripts on its public pages.
Mobile device storage
The ExpoLeadZ mobile app stores session material and pending offline capture queue data in encrypted local storage with encryption keys protected by the device secure store. It also stores an active workspace choice and limited capture drafts needed to resume work. This is app storage, not a browser cookie. Removing the app, signing out, or resolving queue items affects those records according to the implemented lifecycle.
Cookie settings
There are currently no optional ExpoLeadZ cookie categories to turn on or off. Necessary authentication and security cookies cannot be disabled through a preference panel because the signed-in service cannot operate without them. You can remove them by signing out or clearing site data in your browser. If optional technology is added, this permanent route will provide the required choices and withdrawal controls before it loads.
Questions
Contact contact@expoleadz.com with a cookie or storage question. See the Privacy Policy for broader processing and rights information.