Legal
Cookie Policy
This policy explains how Entry (entry.events) uses cookies and similar storage technologies.
Last updated: 23 February 2026
1. What Are Cookies
Cookies are small text files that websites store on your device when you visit them. They help the site remember information about your visit — such as whether you are logged in — so that your next visit is easier and the site is more useful to you.
In addition to traditional cookies, modern web applications also use localStorage and sessionStorage, which are browser-based storage mechanisms that work similarly to cookies but are accessed only by client-side code. localStorage persists until you explicitly clear it, while sessionStorage is automatically cleared when you close the browser tab.
Throughout this policy, when we refer to “cookies” we mean all of these technologies unless we state otherwise.
2. How We Use Cookies
Entry uses cookies and similar technologies for the following purposes:
- Essential functionality — authenticating admin users, securing login flows, and maintaining sessions.
- Functional features — persisting your live-chat session so you can return to an ongoing conversation without having to re-introduce yourself.
- Analytics — when implemented in the future, we may use analytics cookies to understand how visitors interact with our site so we can improve the experience.
3. Cookie Inventory
The following table lists all cookies and storage items currently used on entry.events. The * character represents a wildcard that varies per Supabase project.
| Name | Type | Purpose | Duration | Provider |
|---|---|---|---|---|
sb-*-auth-token | Cookie (Essential) | Authenticates admin users and maintains login session across requests. | Session / 1 hour | Supabase |
sb-*-auth-token-code-verifier | Cookie (Essential) | Secures the OAuth authentication flow using PKCE (Proof Key for Code Exchange). | Session | Supabase |
entry-chat-state | localStorage (Functional) | Remembers your chat session (conversation ID, name, email) so you can return to an ongoing conversation. | Persistent until cleared | Entry |
entry-chat-triggered:* | sessionStorage (Functional) | Tracks whether a proactive chat message has been shown on a specific page to avoid repeating it. | Browser session | Entry |
__vercel_live_token | Cookie (Essential) | Authenticates access to Vercel deployment preview environments. | Session | Vercel |
4. Future Cookies
In the interest of transparency, we want you to know that Entry may add additional cookies in the future, including:
- Analytics cookies (e.g., Google Analytics) to help us understand how visitors use our site so we can improve the experience.
- Advertising cookies (e.g., Meta Pixel) to measure the effectiveness of our advertising campaigns.
Before any analytics or advertising cookies are activated, we will update this policy, notify users, and obtain consent where required by law. No such cookies are in use today.
5. Essential vs Non-Essential Cookies
Strictly necessary (essential) cookies are required for the site to function. They enable core features like authentication and security. These cookies cannot be disabled without breaking fundamental functionality such as logging in.
Functional cookies enhance usability but are not strictly required. For example, the chat session storage means you do not have to repeat your name and email if you return to a conversation, but the site will still work without it.
Currently, all cookies and storage items used on entry.events are either essential or functional. We do not use any tracking, advertising, or profiling cookies at this time.
6. How to Control Cookies
Most web browsers allow you to control cookies through their settings. You can usually find these under “Privacy”, “Security”, or “Cookies” in your browser preferences. Here are direct links for the most popular browsers:
Please note: disabling essential cookies will prevent you from logging in to the Entry admin dashboard. Clearing functional storage may reset your chat session.
localStorage and sessionStorage items can be viewed and cleared through your browser's developer tools (usually accessible via F12 or right-click → “Inspect” → “Application” tab).
7. Third-Party Cookies
Some cookies on entry.events are set by third-party services that we rely on to operate the platform:
- Supabase — provides authentication and database services. Supabase sets the authentication cookies listed above. See the Supabase Privacy Policy.
- Vercel — provides hosting and deployment infrastructure. Vercel may set a cookie for preview deployments. See the Vercel Privacy Policy.
We do not currently use any third-party advertising or tracking cookies. If this changes in the future, we will update this policy and obtain consent where required.
8. Your Rights
Depending on your jurisdiction, you may have the right to access, correct, delete, or restrict the processing of your personal data — including data collected through cookies. These rights may apply under the EU General Data Protection Regulation (GDPR), the UK GDPR, the California Consumer Privacy Act (CCPA), the Australian Privacy Act, and other applicable privacy laws.
For full details on your rights and how to exercise them, please see our Privacy Policy.
9. Changes to This Policy
We may update this Cookie Policy from time to time to reflect changes in our practices, technology, or legal requirements. Any changes will be posted on this page with an updated “Last updated” date. We encourage you to review this page periodically.
If we make significant changes — such as introducing analytics or advertising cookies — we will provide prominent notice and obtain consent where required by law.
10. Contact
If you have any questions about this Cookie Policy or how we use cookies, please contact us at hello@entry.events.