Cookie Policy

1. Introduction

This Cookie Policy explains how EventKP GmbH ("EventKP", "we") uses cookies and similar technologies on eventkp.com, app.eventkp.com, customer event websites where our scripts are embedded, and admin interfaces (collectively, the "Sites").

It should be read with our Privacy Policy. Where consent is required under the ePrivacy Directive and GDPR, we request consent via our cookie banner before placing non-essential cookies.

You can change preferences at any time through the cookie settings link in the footer or your browser controls.

2. What Are Cookies?

Cookies are small text files stored on your device when you visit a website. They help sites remember logins, preferences, and aggregated usage patterns. Similar technologies include local storage, session storage, pixels, and SDK identifiers.

First-party cookies are set by EventKP. Third-party cookies are set by partners such as analytics or payment providers when their services load on our pages.

Session cookies expire when you close your browser. Persistent cookies remain until deleted or until their expiration date.

3. Strictly Necessary Cookies

These cookies are required for core functionality and cannot be disabled through our banner without breaking the service. Legal basis: legitimate interest and/or contract performance.

Examples: authentication session tokens, CSRF protection, load balancer affinity, security challenge cookies (e.g., Turnstile), and cookie consent storage to remember your choices.

Without these cookies, you cannot log in, save drafts, or complete checkout securely.

4. Functional Cookies

Functional cookies remember choices such as language, theme (light/dark), locale routing, and dismissed UI notices. They improve experience but are not strictly necessary.

Legal basis: consent where required, otherwise legitimate interest for basic personalization tied to your account settings.

Retention: typically up to 12 months unless cleared earlier.

5. Analytics Cookies

Analytics cookies help us understand how visitors use marketing pages and product funnels—page views, feature adoption, error rates, and campaign performance. We use aggregated data to improve onboarding and reliability.

Where required, analytics cookies are placed only after consent. We configure IP truncation and data minimization where supported.

You may withdraw consent via cookie settings; previously collected aggregated data may remain in statistical form.

6. Marketing and Advertising Cookies

With consent, we may use marketing cookies to measure ad conversions, attribute signups to campaigns, and avoid showing repetitive ads. We do not use invasive cross-site profiling on guest RSVP flows without explicit disclosure.

Event organizers using EventKP should configure their own tracking on custom event sites responsibly and disclose it in guest-facing notices.

Withdraw consent at any time through cookie settings or vendor opt-out tools where applicable.

7. Cookies on Customer Event Websites

Event websites published through EventKP may load EventKP scripts for RSVP forms, analytics (if enabled by the organizer), media embeds, and security. Organizers are responsible for guest-facing cookie notices and consent where legally required.

Essential RSVP cookies enable form submission and fraud prevention. Optional analytics on event sites follow organizer settings.

Guests should review the organizer's privacy notice for details specific to each event.

8. Third-Party Cookies

Payment processors (e.g., Stripe) may set cookies during checkout. Embedded videos or maps may set third-party cookies governed by those providers' policies.

We review subprocessors for data protection commitments. Third-party policies are linked from our trust documentation where available.

9. Managing Your Preferences

Use the "Cookie settings" link in the footer to update categories. Browser controls can block all cookies, but core features may fail.

Mobile app WebViews follow the same policy when accessing EventKP web properties.

For questions: [email protected].

10. Updates

We may update this policy when we add features or subprocessors. Material changes are announced with a new effective date.

Version history is available in the Legal Content Center. Last expanded under S55F production standards.

session_id (strictly necessary, session): maintains authenticated admin sessions. consent_state (strictly necessary, 12 months): stores banner decisions. locale (functional, 12 months): remembers language preference. theme (functional, 12 months): light/dark mode.

_ga / _gid (analytics, Google, 24 months / 24 hours): usage statistics when consented. _fbp (marketing, Meta, 90 days): conversion measurement when consented.

Exact names may evolve; this policy describes categories and purposes. An updated machine-readable cookie list may be published separately.

12. RSVP Flow Cookies

Guest RSVP forms may set short-lived cookies to prevent duplicate submissions and protect against bots. These are strictly necessary for form integrity.

13. Admin Interface

Admin dashboards set additional functional cookies for editor state and unsaved draft warnings.

14. Checkout

Stripe and similar providers set fraud prevention cookies during subscription checkout.

15. Opt-Out Links

Google Analytics opt-out: tools.google.com/dlpage/gaoptout. Industry opt-out pages may apply to advertising partners when used.

16. Contact

Cookie questions: [email protected].

17. Duration and Refresh

Persistent cookies are refreshed on each visit while active. Session cookies expire when the browser session ends. Consent renewal may be requested periodically to reflect regulatory or product changes.

18. Similar Technologies

Local storage may cache editor drafts and theme preferences. Pixels in emails measure open rates only when you use tracked templates and applicable law permits.

19. Browser Controls

Major browsers provide cookie management settings. Refer to documentation for Chrome, Firefox, Safari, and Edge. Mobile OS settings may limit cross-app tracking separately from browser cookies.

20. Children

We do not knowingly place profiling cookies on child-directed experiences. Organizers hosting family events must configure guest flows responsibly.

21. Policy Updates

Material cookie policy changes trigger banner re-prompts where legally required.

We store cookie consent decisions with timestamps to demonstrate compliance during audits. Records are linked to browser identifiers, not directly to account profiles unless you are logged in.

23. First vs Third Party

First-party cookies are set on EventKP domains. Third-party cookies may appear when embedding external videos, maps, or social widgets on event pages—organizers should disclose these in guest notices.

24. Do Not Track

Browsers may send Do Not Track signals; EventKP responds by limiting non-essential analytics where technically feasible but does not treat DNT as sole legal basis for consent in the EU.

25. Mobile WebViews

If you access EventKP through embedded WebViews in partner apps, cookie behavior follows WebView settings and this policy.

Event organizers enabling analytics or embeds on guest-facing pages must disclose those technologies in guest privacy notices and obtain consents where required.

RSVP forms should avoid non-essential third-party scripts until guests have appropriate notice and choice.

Organizers may contact [email protected] for configuration guidance on minimizing guest tracking.

Cookie preference centers on marketing sites do not automatically propagate to custom event domains; configure guest notices per event.

Essential session cookies expire at browser close. Consent cookies typically persist twelve (12) months. Analytics cookies follow vendor documentation when consented, often up to twenty-four (24) months unless withdrawn earlier.

Short-lived cookies may associate a browser session with a partially completed RSVP to prevent duplicate submissions and protect against automated abuse.

Check-in staff devices using admin interfaces rely on authenticated session cookies separate from guest-facing flows.

Vendor and agency dashboards use session cookies for authentication and CSRF protection. Marketplace quote threads may store UI state cookies to preserve draft messages during multi-step workflows.

These cookies are strictly necessary for secure marketplace operations and are not used for cross-site advertising profiles.

A small text file placed on your device by websites you visit, commonly used for sessions, preferences, and analytics. Cookies may be first-party or third-party depending on which domain sets them.

Expires when you close your browser; often used to maintain logged-in state during a visit to admin or marketing properties.

Remains for a defined period or until deleted; used for remembering language, theme, or consent choices across return visits.

First-Party Cookie

Set by the website you are visiting directly, such as eventkp.com or your custom event domain when served by EventKP infrastructure.

Set by a domain other than the one you are visiting, often associated with embedded content, payment widgets, or analytics partners.

A user interface element requesting permission for non-essential cookies and similar technologies where required by ePrivacy and GDPR.

Local Storage

Browser storage used for draft editor state and UI preferences; not transmitted automatically with every HTTP request unlike cookies.

Tracking Pixel

A small image or script beacon used to measure email opens or campaign conversions when permitted by law and disclosed to users.

30. EventKP Cookie Scope Statement

EventKP operates marketing websites, authenticated SaaS applications, customer-published event microsites, RSVP forms, vendor marketplace interfaces, and agency workspaces. Each surface may use cookies differently: marketing pages emphasize consent-gated analytics; admin apps require session cookies; guest RSVP flows minimize non-essential tracking.

Organizers remain responsible for disclosing optional analytics or embeds they enable on event pages. EventKP provides configuration to reduce third-party scripts but cannot control organizer-added custom HTML without review.

We periodically review cookie inventories against this policy and update the Legal Content Center version history when subprocessors or categories change materially.