How We Use Cookies

Cookies are small text files that websites place on your device when you visit them. They help the site remember things about your visit — like whether you are logged in or which theme you prefer.

Not all cookies are the same. Some disappear when you close your browser (session cookies), while others stick around until they expire or you delete them (persistent cookies). Some are set by Tickify directly (first-party), and others come from services we rely on (third-party).

This page explains exactly which cookies Tickify uses, why we use them, and how you can control them.

Essential cookies handle the basics — keeping you logged in, remembering which workspace you are working in, and storing your cookie consent choice. Without them, the platform would not work.

We use Supabase for authentication, which sets its own session cookies to manage your login state securely. These tokens are cryptographically signed and transmitted over HTTPS only.

• User authentication and session persistence
• Workspace context so you land in the right place
• Theme preference (light or dark mode)
• Cookie consent storage so we do not ask you repeatedly
• CSRF protection and security tokens

Analytics cookies help us understand how people use Tickify so we can improve the experience. They tell us things like which pages are visited most, where users encounter errors, and how people navigate between features.

We use Google Analytics for this purpose. All data is collected in aggregate — we do not use analytics cookies to identify individual users or build personal profiles.

Analytics cookies are optional. You can opt out at any time through your browser settings or the Google Analytics Opt-out Browser Add-on.

We do not build advertising profiles. We do not sell data to ad networks. We do not participate in retargeting programs. There are no Facebook pixels, no Google Ads tags, and no third-party trackers embedded in the platform.

Our business model is straightforward: you pay for a subscription, and we provide the service. We have no incentive to monetize your attention or browsing habits.

Here is a complete list of cookies Tickify sets or allows on your device:

In addition to cookies, Tickify uses your browser's local storage to keep things running smoothly. Local storage works similarly to cookies but is only accessible by our application — it is never sent to servers automatically with each request.

We use local storage for:

• Caching workspace data for faster page loads and instant navigation between views
• Storing draft content (like ticket replies) so you do not lose work if you accidentally close a tab
• Keeping UI state preferences such as sidebar collapse, table sort order, and filter selections
• Authentication token storage managed by Supabase

You can clear local storage at any time through your browser's developer tools or by clearing site data in your browser settings.

You have full control over which cookies are stored on your device. Here is how:

Blocking all cookies will break core functionality. Specifically:

• You will not be able to log in or stay authenticated
• Your workspace and theme preferences will reset on every visit
• The cookie consent banner will reappear each time you visit

Blocking only analytics cookies has no impact on the platform's functionality. Everything continues to work normally — we just lose visibility into aggregate usage patterns.

We update this page when we add, remove, or change the cookies Tickify uses. If we introduce a new category of cookies beyond what is described here, we will notify you and request your consent before setting them.

The effective date at the top of this page reflects the most recent revision. For questions about past changes, contact us at the email below.

Have questions about cookies, local storage, or how we handle data on your device? Reach out.