1. Website and merchant stores are different
The CustomerHub marketing website, the C:Hub merchant admin and a merchant’s storefront account do not use the browser in exactly the same way. This notice distinguishes those contexts. A merchant’s Shopify theme, installed apps and consent tools can introduce additional storage and tracking governed by the merchant’s own notices.
2. This website and demo
This website does not include advertising pixels or third-party marketing analytics scripts. Its contact form keeps a temporary security token and the form contents in page memory while you complete it; it does not save those enquiries in browser cookies or local storage. In production, the form also sets an essential first-party cookie named __Host-chub-form. This contains a random session identifier used to protect submissions, is unavailable to page scripts, is sent only over HTTPS with same-site restrictions, and expires after two hours. It contains no enquiry text and is not used for advertising. It uses locally served fonts, images and sample demo assets. Hosting services can receive technical request information and may use security-related browser mechanisms.
The interactive account demo uses fictional store/customer data. Parts of its account renderer may use browser storage for functional state. Following a Shopify installation link, external help guide or another website brings you under that service’s own practices.
3. Storage used by the account app
| Use | Examples | Duration and control |
|---|---|---|
| Account/session operations | Sign-in recovery, logout/reload state and related session handling. | Depends on the browser mechanism and account flow; some state is session-based. |
| Product history | Recently viewed and saved-from-cart product information and synchronization markers. | Local storage can persist until cleared or replaced by the app or browser. A fixed expiry is not asserted here. |
| Account presentation | Profile-image references and account display state. | Depends on the feature and browser storage; clearing it may reset the display or preference. |
| Usage markers | Initial-load or login markers used in feature-use reporting. | Depends on the marker and browser context; these must be assessed with the merchant’s privacy/consent setup. |
These uses can involve cookies, local storage or session storage. Calling a technology “local storage” does not mean privacy or consent requirements cannot apply.
4. Choices and consent
You can use browser settings to clear site data or restrict storage. Doing so may remove product history, reset preferences or affect account functions. For choices on a merchant’s store, use that store’s privacy controls or contact the merchant.
Merchants must assess the purpose and applicable consent or exception requirements for the technologies they enable, including connected apps. This notice does not classify every C:Hub marker as strictly necessary or establish that every store has a working consent integration.
5. Changes and questions
The notice should be updated when website tracking, hosting or account storage changes. Contact support@customerhubapp.com with a C:Hub storage question, or the store directly about its broader Shopify configuration. See the Privacy Policy for information-handling and request details.
Questions about this document?
support@customerhubapp.com