Cookie Policy
What is a cookie?
A cookie is a small text file a site stores on your device. Some sites also use local storage, which works the same way from your point of view: data written to your browser and read back later. This policy covers both, because the law does too.
Consent, and what silence means here
Nothing beyond the strictly necessary is written or loaded before you answer the banner. Silence counts as a refusal, not as permission: including on the very first render, before your previous answer has been read back. That rule is a single function in the codebase, and a test asserts that every third-party loader goes through it.
You can change your answer at any time from “Cookies” in the footer. Each switch saves immediately. We ask again after 180 days.
Everything the platform writes
This table is generated from the code that writes each value. A test fails the build when a cookie is added without a row here.
Keeps you signed in. Drops to 24 hours when you sign in without choosing to be remembered.
Holds the state of a connector authorization for the length of the redirect. Deleted as soon as you come back.
Stores your answer to the banner so it is not shown again. Necessary, because remembering a refusal requires storing the refusal.
The interface language you chose. Set server-side, carries no identifier.
Interface preferences: collapsed panels, chosen tabs, display settings.
First-touch attribution: UTM parameters and any referral code. This is what lets a referrer be paid a commission, which is why it waits for consent.
Anonymous visitor identifier set by our audience measurement provider, and passed to Stripe at checkout so a purchase can be attributed to a campaign.
Tag manager. Loads no measurement tag until analytics consent is granted: Consent Mode v2, default denied.
Audience and loading-performance measurement. Both products are cookieless and set no identifier.
Essential entries
Entries marked essential are required for the platform to work and cannot be refused. They serve authentication, connector authorization and recording your consent choice. They carry no marketing identifier.
BoostEcom Spy
The extension uses chrome.storage.local for preferences, session cache and optional tool payloads. Authentication cookies belong to www.boostecom.app, never to the extension's own origin. The Privacy Policy covers what it processes.
Managing your preferences
You can control all of this:
- The banner: choose “Cookies” in the footer to reopen your preferences and withdraw a category
- Browser settings: block or delete cookies from your browser preferences
- Local data: clear local storage from your browser's developer tools
- Account deletion: deleting your account removes the data associated with it
Deleting essential cookies signs you out and blocks access to the Services until you sign in again.
Third-party cookies
We set no advertising cookie and run no ad network. The only third-party entries are audience measurement tools, all behind consent. One exception is worth naming: the social-proof badge in the footer is an image served by a third party, so your browser contacts that provider to fetch it. It sets no cookie, but the request itself carries your IP address.
Contact
For anything about this policy, write to contact@boostecom.app
Last updated September 12, 2026