RunMyCrew uses a minimal set of first-party storage entries to operate the product. We do not use advertising cookies, third-party analytics that profile you, or any cross-site tracking pixels. This policy lists every entry, its purpose, its lifespan, and how to control it.
First-party storage
| Name | Type | Purpose | Lifespan |
|---|---|---|---|
runmycrew-auth-token | localStorage | Authenticated session JWT. Required to use the product. | Until logout / expiry |
runmycrew-theme | localStorage | UI theme preference (light / dark / system). | Persistent |
runmycrew-scheme | localStorage | Color-scheme palette preference. | Persistent |
runmycrew-workspace-v2 | localStorage | Last-active workspace id (so you land in the right place). | Persistent |
runmycrew-editor-layout | localStorage | Workflow editor panel sizes / collapsed state. | Persistent |
runmycrew-runs | localStorage | Recently viewed runs cache (rendering only). | Persistent |
Third-party
We do not embed third-party advertising tags. Where we use third-party services, they may set their own cookies:
- Stripe— required for payment processing on the billing page. Stripe’s cookies are governed by Stripe’s Privacy Policy.
- Google Identity Services— only loaded when you click “Sign in with Google.” Google may set cookies on its own domain during the OAuth handshake; see Google’s cookie policy.
- Cloudflare — DNS and TLS-edge service. May set a
__cf_bmcookie for bot mitigation; never used for tracking.
How to control
- Clear browser data for
runmycrew.comandapp.runmycrew.comat any time. - Sign out from Settings → Account to remove the auth token.
- Block third-party cookies entirely in your browser. Stripe and Google sign-in may stop working as a side effect; the rest of the Service is unaffected.
Contact
Cookie-related questions: privacy@runmycrew.com