Cookie policy
Last updated September 1, 2026.
1. Overview
This page lists every cookie and browser storage item TixTally itself sets, what each one is for, and how long it lasts. We keep this list short on purpose: we do not run advertising cookies, and our product analytics run entirely on our servers rather than in your browser (see Analytics and monitoring below). This policy is part of our Terms of service.
2. Essential cookies
These keep the Service working and cannot be turned off without breaking sign-in. We do not ask for consent to set these, because the Service cannot function without them.
| Name | Purpose | Duration |
|---|---|---|
| __Secure-tixtally.session_token | Keeps you signed in to your TixTally account. Set only after you sign in; HttpOnly, so no script on the page can read it. | Up to 3 days |
| admin_session | Set only in the rare case that a TixTally support person is working inside your account at your request, so that we can return them to their own account afterwards. Every action taken this way is recorded in your organization's audit log. | For that session only |
3. Functional storage
This is browser local storage, not a cookie — it is never sent to our servers, and it only affects how the page looks in your own browser.
| Name | Purpose | Duration |
|---|---|---|
| theme | Remembers whether you last chose light or dark mode. | Until you clear it |
4. Third-party cookies (Stripe)
When you pay for a ticket, or when an Organizer connects a Stripe account, we load Stripe's own scripts to handle the card form and identity verification. Stripe sets a small number of its own cookies on those pages (commonly named m, __stripe_mid, and __stripe_sid) to detect fraud and keep payments secure. These are set and controlled by Stripe, not by us; their exact durations are set by Stripe and disclosed in Stripe's own cookie and privacy documentation. We do not add any advertising or tracking cookie of our own alongside them.
5. Analytics and monitoring
Product analytics run entirely on our servers. We use PostHog to understand how the product is used (for example, that an event was published or an order completed), but the tracking calls happen server-side, in our own code, never in your browser — PostHog sets no cookie on this site today.
Error monitoring runs in your browser. We use Sentry to catch and diagnose bugs. It collects technical details about an error when one happens (such as the page you were on and your browser version) and sends them to us directly. It also samples a fraction of ordinary visits for performance timings, so we can tell a slow page from a broken one, which means some data reaches Sentry when nothing has gone wrong. In its current configuration on TixTally, Sentry does not set a persistent cookie or store an identifier in your browser.
6. Managing cookies
Every browser lets you view, delete, or block cookies through its settings. The cookies we set ourselves are the two in the table above, and both exist to keep you signed in, so blocking or deleting them simply signs you out; it does not affect a Buyer's ability to complete a purchase, which relies on Stripe's own cookies while the payment form is open. Blocking Stripe's cookies may prevent the payment form from loading at all, since Stripe requires them for fraud prevention.
7. Changes to this policy
If what we collect changes — a new integration, a new provider — we will update this page and the date at the top of it.
8. Contact
Questions about this policy can go through the same channel as anything else: Help & support in the TixTally dashboard.