Cookie Policy

What cookies and browser storage are#

A cookie is a small text record a website stores in your browser and reads back on later requests; browser storage (local and session storage) is similar but stays on your device and is not sent with requests. Glowwer uses both, for the purposes below. Some are set by Glowwer directly (first-party); some are set by the providers that run parts of the service (third-party). The Privacy Policy explains the personal information involved.

Strictly necessary#

These make the site work and keep it secure. They cannot be switched off without breaking sign-in or the anonymous preview, and they are not used for tracking across other sites.

glowwer_anon (first-party cookie, 7 days)

A random identifier for your anonymous session, set when you paste a website without an account, so the draft you started is yours when you come back. HttpOnly, sent only to glowwer.com. Cleared when the brand is claimed through the claim step after you create an account; if the brand is attached to your account another way, the cookie simply expires on its own after 7 days and does nothing meanwhile.

glowwer_returning (first-party cookie, 1 year)

Set after you sign in or create an account on this browser. It holds only the value “1” — no account, email, website or brand identifier — and lets the site send you to sign in, rather than start a new free preview, when you paste a website while signed out. HttpOnly, sent only to glowwer.com.

glowwer_connect_intent_… (first-party cookie, 10 minutes)

Set when you start connecting a social account; proves that the platform’s reply belongs to the connection you started. Scoped to the connection callback only and deleted when it completes.

Authentication cookies (set by our sign-in provider, Clerk)

Keep you signed in and protect your session against forgery. Their names and lifetimes are set by the provider and can change; they exist only to authenticate you to Glowwer.

glowwer_consent (first-party local storage)

Your cookie choice itself — whether analytics is allowed, when you decided, how (the banner, Cookie settings, or a browser privacy signal) and the policy version you decided against — so we do not ask again on every visit. It holds no identifier and is never sent to us.

Preferences (first-party browser storage)#

These remember how you like the product to look and what you have already seen. They never leave your browser.

glowwer-theme (local storage)

Light, dark or automatic appearance.

glowwer-sidebar-collapsed (local storage)

Whether you collapsed the navigation sidebar.

gw.click-to-edit.seen.v1 (local storage)

That you have seen the one-time “click to edit” hint, so it is not shown again.

gw-week-autostart-… (session storage)

That a week’s generation was already started in this tab, so reloading does not start it twice.

Analytics#

We use PostHog to understand how the product is used: page views and product events such as a brand started, a week generated or a post approved, under a pseudonymous identifier that PostHog stores in your browser (local storage only — it sets no cookie). Session recording is turned off. No advertising network receives anything.

Analytics runs only after you opt in. Until you accept, nothing is loaded and nothing is sent; if you decline, it stays off. Withdrawing later stops it at once and clears the identifier from your browser. You can change your choice at any time under Your choices on this page, or from Cookie settings in your account’s Settings.

Separately from your browser, our servers send a small number of brand-level events to PostHog as a brand is built and posts are approved or published — an internal brand identifier, counts and timings; never your name, email, message contents or the posts themselves. These carry no cookie and are not tied to a person profile.

Error and security monitoring#

We use Sentry to receive error reports when something breaks, and a small sample of performance traces. Its browser client may store a short-lived identifier to tie the parts of one error together. Session replay — recording what you see on screen — is not enabled. Reports carry technical details of the failure (the page, the browser, the stack trace) and the identifiers needed to reproduce it.

Content served by other providers#

Some images on the marketing pages are served from a third-party image host, and posts you connect or preview may load media from the platform they came from. Those hosts receive your IP address and browser details when the image loads, as any web image host does. On the website-reading screen, the add-a-brand reading screen and the font editor on Your brand, the fonts your brand uses are loaded from Google Fonts so the page can show them in your own typeface; Google receives your IP address and browser details for that request. Sign-in and payment screens are served by the providers that run them, under their own cookie policies.

Your choices, and how to reopen Cookie settings#

Change your analytics choice right here, from the cookie banner when it is shown, or from Cookie settings in your account’s Settings. Strictly necessary storage stays on because the site does not work without it.

If your browser sends Global Privacy Control or Do Not Track, analytics stays off without asking and the banner is not shown; you can still turn analytics on here if you want to. A choice you made yourself here is kept over a later browser signal, and this page says so. See the Privacy Policy for how we treat those signals more generally.

Changes and contact#

When we add or remove a cookie, we update this list and the date at the top. Questions: privacy@glowwer.com.