Cookie Policy
Effective: April 27, 2026
We keep cookies to a minimum. WerOrg sets only essential and functional cookies — no analytics, no advertising, no cross-site tracking on the Operator dashboard or our public marketing pages.
Operators can add their own analytics or marketing scripts (e.g. Google Analytics, Meta Pixel) to their storefront via Dashboard → Settings → Tracking scripts. Those scripts run on the Operator’s subdomain or custom domain only. The Operator is the data controller for any cookies their scripts set; their own privacy policy applies.
Cookies we set
| Name | Purpose | Duration | Type |
|---|---|---|---|
| sb-access-token / sb-refresh-token | Supabase Auth session for Operator dashboard sign-in (magic-link flow). | Access: 1 hour. Refresh: 30 days. | essential |
| wer-signup-step1 | Holds your name/email/subdomain between step 1 and step 2 of the signup wizard. | 1 hour, then auto-expires. | essential |
| __stripe_mid / __stripe_sid | Set by Stripe Checkout when you subscribe or open the Customer Portal. Fraud prevention. | Up to 1 year. | essential |
| cart | Storefront-side cookie holding the Seller’s in-progress device cart so they can add multiple devices in one session. | 24 hours. | functional |
How to control cookies
You can clear or block cookies in your browser settings. Blocking the essential cookies above will sign you out of the dashboard, prevent checkout, and break the signup wizard. The functional cart cookie can be blocked — the Seller will lose any in-progress cart but can re-add devices.
Because we don’t set analytics or advertising cookies, there’s no consent banner to dismiss. If we ever add cookies that aren’t strictly necessary, we’ll add an opt-in prompt and update this page.
Questions? [email protected] · See also our Privacy Policy.