Glowwise, considered
Your choices deserve clarity.
How Glowwise handles browser preferences, local lists and private messages.
Last updated: 9 October 2026. Publisher: Imagine Utopia, founded by Aakash Kumar and Disa Bandhu. This policy describes this website’s implemented behaviour; it has not received legal review.
Browsing and infrastructure
The site runs on an Azure virtual machine behind Cloudflare. Network services necessarily process requests, including IP addresses, request paths and technical headers, to deliver and protect the website. Hosting and security services can hold operational records under their own service controls. We do not claim browsing is anonymous to those providers.
Optional Google Analytics 4 runs only after affirmative consent. We do not run advertising, session replay or a newsletter. Contact message text is never added to analytics events. Static resources and licensed fonts are self-hosted.
Lists stored in your browser
Saved products and comparison selections are stored locally using product identifiers and selected variants. They do not create an account or sync to another device. To display the list, the browser requests the selected public product records from Glowwise; request logs may therefore contain product identifiers, but never a stored contact message.
Clear your saved list, clear the comparison or remove this site’s browser data to delete those local records. If storage is unavailable, the tools explain that a temporary selection cannot persist.
Consent preferences
Cookie settings record your optional analytics choice. Before acceptance, no Google Analytics script, event request or analytics cookie is created by Glowwise. After acceptance, basic page views on recognised editorial, catalog and tool routes use the page title and path. Tool-use events record only fixed names for finder completion, adding a comparison, saving a product and opening a retailer. They do not include selected products, lists, budgets, answers or free text. Query strings, referrer URLs, contact/correction pages, search pages and free-text inputs are excluded. Enhanced measurement and advertising signals are off. Google necessarily processes technical connection information under its own privacy policy. Analytics cookies expire after 60 days; the property uses two-month user/event retention, while aggregated reports may remain longer. Reopen Cookie settings in any footer to reject or withdraw. Withdrawal removes accessible analytics cookies and reloads the page to unload the SDK. It does not retroactively erase data already received by Google. Essential browsing, saved products, comparisons and form security remain available. An older inactive preference does not activate the new service; a new affirmative choice is required.
Private forms
We collect the name, reply email, subject and message you submit. Corrections also include the affected page and supporting source. A reference and received/expiry timestamps help administrators handle the message. A short-lived essential cookie and matching signed form token protect submissions. The browser sends the token and the form fields to this site; they are not published in a public URL.
Validation, a hidden spam field and a connection-based limit help prevent abuse. Rate-control keys use a salted hash of the connection IP and hour, retained for up to two hours; the original IP is not stored in the inbox record. Network providers may separately process IP addresses.
Who can access messages
Only WordPress administrators with the required management capability can access the private inbox. Messages are excluded from public REST interfaces, search, product exports and sitemaps. No email notification or automated reply is configured. We do not sell message data or add senders to marketing lists.
Retention and deletion
Live messages expire after 90 days and are permanently removed by the scheduled retention task while the server runs. Shutdown may delay the task until the next start. Administrators can delete a live message earlier after verifying an appropriate request.
Restricted recovery backups may contain older message records. They are retained for recovery and are subject to manual lifecycle review, rather than an unsupported claim of immediate erasure. A deletion request includes a review of affected backup copies before it is treated as complete. Copies retained temporarily for recovery must not be restored into active use without applying recorded deletions. There is no claim of an automatic 90-day backup erasure.
Request access or deletion
Use Contact, state “Privacy request” in the subject and include your prior reference using the same reply email. We must verify the request before releasing private data or deleting someone else’s record. Please avoid sensitive identity documents. A successful form receipt confirms storage, not that the request has already been fulfilled.
External destinations and changes
Retailer and research links lead to other websites with their own privacy and commercial terms. Glowwise does not control their checkout or tracking. This policy will be updated if the website’s behaviour changes; optional services must receive an appropriate consent review before activation.