Cookies are small files stored on your device. Similar technologies include local storage, session storage, pixels, SDKs, and server-side event logs. ChangeSentry uses them to keep the product secure, remember choices, measure performance where permitted, and understand how the site and dashboard are used.
We do not use advertising cookies. Optional analytics or performance tools are used only where permitted and, where required, after consent. The consent banner shown on your first visit lets you accept or reject non-essential cookies. You can change your choice at any time by clearing site data for ChangeSentry in your browser settings, which will re-show the consent banner on your next visit.
1. Strictly necessary cookies
Used for sign-in, session security, CSRF protection, fraud prevention, rate limiting, load balancing, cookie preference storage, and core dashboard operation. The service cannot function properly without these.
- Supabase authentication cookies: maintain authenticated sessions and security state for the dashboard and admin surfaces. Retention follows the session and authentication settings configured for the product.
- Server-side security and event logs: record request, error, queue, and abuse-prevention metadata needed to operate and secure the service.
2. Preference cookies
Used to remember choices such as cookie consent, interface preferences, viewed announcements, and settings that make the product easier to use across visits. These are optional where applicable.
- cookie-consent: a local storage value set to
acceptedorrejectedso ChangeSentry knows whether optional analytics may load.
3. Analytics and performance cookies
Used to understand aggregate website and product usage, diagnose errors, improve onboarding, and measure page performance. We do not use advertising cookies. These tools are consent-based where required by law and may include the following when enabled:
- PostHog: product analytics, feature adoption, pageview events, and performance signals.
- Google Analytics: aggregate website traffic and conversion analytics.
- Hotjar: performance and experience analytics where configured.
4. Cookie reference table
| Cookie / key | Provider | Category | Purpose | Duration |
|---|---|---|---|---|
| sb-*-auth-token | Supabase | Strictly necessary | Authenticated session and security state | Session / configured token lifetime |
| cookie-consent | ChangeSentry | Preference | Stores your cookie consent choice (accepted / rejected) | 1 year (localStorage) |
| ph_*, posthog_session | PostHog (posthog.com) | Analytics (consent-based) | Product analytics, feature adoption, session replay | Up to 1 year |
| _ga, _gid, _gat | Google Analytics (google.com) | Analytics (consent-based) | Aggregate website traffic and conversion measurement | _ga: 2 years; _gid: 24 h; _gat: 1 min |
| _hjid, _hjSession*, _hjSessionUser* | Hotjar (hotjar.com) | Analytics (consent-based) | Experience and performance analytics | _hjid: 1 year; session cookies: session |
Third-party analytics cookies are only set after you give consent. Their exact names and durations may change; refer to each provider's own cookie policy for the current list.
5. How to manage your choices
If a consent banner is shown, use it to accept or decline optional cookies. You can reset choices by clearing site data for ChangeSentry in your browser. Some browsers also let you block third-party cookies, limit tracking, or delete cookies when a session ends. Clearing site data may sign you out or reset product preferences.
Essential cookies remain active because they are required for authentication, security, abuse prevention, and service delivery. If you disable them, pages may not load correctly and the dashboard may not keep you signed in.
6. Similar technologies
ChangeSentry may also process server logs, worker queue metadata, notification delivery logs, error monitoring events, and IP-derived approximate location for security, troubleshooting, rate limiting, analytics, support, and legal compliance. These are not always browser cookies, but they serve similar operational purposes.
7. Examples of cookie purposes
- Maintaining a secure authenticated session.
- Remembering cookie consent or privacy choices.
- Protecting forms and APIs from abuse.
- Measuring aggregate page visits and feature adoption.
- Diagnosing errors, latency, and broken user flows.
8. Contact
For questions about cookies or consent choices, email privacy@changesentry.com, contact us through the contact page, or read the Privacy Policy.