1. Short summary

The service uses cookies and similar technologies mainly for sign-in, session continuity and secure application operation.

Product analytics is optional. If enabled, it sends only limited operational events without names, contacts, addresses, prices, notes or project content.

After consent, the public website may measure an anonymous page visit and clicks on main links. Online card payment opens only where explicitly enabled and when the user starts a payment or billing action.

2. Essential cookies

  • Sign-in cookies and user sessions.
  • Cookies or similar technical data needed for security and sign-in protection.
  • Technical storage needed for correct application function and navigation.

3. Functional and third parties

Some screens may load external services only after a specific feature is used. A map service is used for address completion if enabled. Text translation through an external service runs on the server and is not browser analytics.

Payment provider pages may open only when online payments are enabled and the user starts a payment or billing action. The provider’s cookies and local storage are governed by its own documentation and appear only in the payment flow.

Guest website and public RSVP pages may work with technical link or token identifiers that serve a specific household or form response.

4. Analytics and marketing

Product analytics is intended only for basic understanding of service usage. It is disabled by default.

Anonymous public website analytics starts only after consent in the public-page banner. It stores only the consent choice and an anonymous visitor identifier.

If product or public web analytics is enabled, it must not contain names, e-mails, phones, addresses, notes, form answers, private links, prices or free text. Automatic session recording, heatmaps, Google Analytics and advertising pixels are not part of the current setup.

5. How to control cookies

  • Essential sign-in cookies are needed for sign-in and the application may not work without them.
  • The user can block or delete cookies in browser settings, but this can remove sign-in or break application functionality.
  • Optional anonymous public web analytics can be rejected in the public-page banner. If rejected, public website visits are not measured.