Cookie Policy

1. What this policy covers

This policy explains how Eventicly uses cookies and similar technologies such as local storage and session storage. These tools help the service stay secure, remember choices, keep accounts signed in, protect RSVP flows, and understand product usage.

2. Necessary cookies and storage

Necessary cookies and storage are required for Eventicly to work and cannot be switched off through Cookie settings.

• -Authentication and session cookies used by Better Auth to keep signed-in users authenticated and protect account access.
• -Security, routing, rate-limit, and infrastructure data needed to serve the app, public invitation pages, and API requests.
• -Consent storage used to remember cookie choices and avoid repeatedly showing the same notice.

3. Preference cookies and storage

Preference cookies and storage help Eventicly remember product and interface choices so the experience is more consistent when you return.

• -Dashboard sidebar state is stored in a first-party cookie so the dashboard can reopen with the same sidebar preference.
• -The sending composer may store the last used template identifier in local storage for the signed-in dashboard experience.
• -Theme and interface preferences may be stored locally by app UI libraries or browser APIs.

4. Analytics cookies and storage

Analytics cookies and storage help us understand how people use Eventicly and where the product can improve.

• -Marketing analytics may include page views, visitor sessions, campaign source, device category, browser, approximate region, and interaction events.
• -Product and public invitation analytics may include page views, section or story views, RSVP form views and starts, CTA clicks, heartbeat duration, and RSVP submit success.
• -Analytics records may include landing page, layout, guest or household token attribution when available, device category, browser, operating system, and timestamps.
• -Server-side request metadata such as IP address may be used for rate limiting, and user agent may be used to derive coarse device metadata.

5. Marketing cookies and storage

Marketing cookies and storage may be used to measure launch campaigns, understand which channels introduce people to Eventicly, and support more relevant follow-up communications.

6. Service providers

Some cookies or similar technologies may be set or processed by service providers when they are needed to operate Eventicly features.

• -Resend may process email sending data when Eventicly sends email communications.
• -Twilio may process SMS sending data when Eventicly sends text messages.
• -Cloudflare R2 or S3-compatible storage may process media upload and delivery data.
• -Hosting and infrastructure providers may process request metadata needed to serve, secure, and monitor the application.

7. Managing choices

You can use Cookie settings in the footer to update optional categories for marketing pages. You can also clear cookies and site data in your browser settings. Necessary cookies and storage remain required for account, dashboard, RSVP, and security features.

8. Changes to this policy

We may update this policy when product features, providers, or storage behavior changes. Material changes will be reflected by updating the date below.