1. What the service is for
KRUSPIN is a work application for professional planners, event teams and venues that need to manage a wedding or event project in one place. It helps manage guests, RSVP, accommodation, seating, timelines, tasks, vendors, budget items, files, notes and the guest website.
These terms describe the current operation of the service and the relationship between the operator, the customer, and application users.
2. Accounts, roles and access
- Basic access uses a one-time e-mail code. The application uses sign-in cookies and verification e-mails.
- A workspace can have an owner, admins and team members. A project can have planner roles, client access, collaborators and read-only access.
- The customer is responsible for inviting only people who should have access to the data and for matching permissions to their real project work.
- Shared RSVP links and guest website links can be forwarded outside the original recipient. Treat them as access to selected data.
3. Data and content entered by the customer
The customer can upload or enter personal data about clients, guests, vendors, team members and other event participants. This may include names, contacts, RSVP, allergies and dietary restrictions, accommodation, seating, notes, finance overviews, files, photos and operational instructions.
The customer must have its own legal basis for this processing and must provide the required information to the affected people under applicable law or contracts with its clients.
4. Private project vs. public content
- Project data is private by default and available only to authorized users in the workspace or project.
- The customer can deliberately publish or share selected content: the guest website, RSVP form, invitations, exports, files or client access.
- Internal notes, finance items, vendor details and operational data are not public unless the customer exports, shares or exposes them in a specific feature.
- The guest website is public or guest-accessible only when the customer publishes it or sends out the link.
5. Integrations and external services
Depending on configuration, the application uses external infrastructure and services for database, e-mail, files, maps, translations and monitoring. The current overview is described in the Data Processing document.
The customer must not promise clients or guests features that are not available for the account, such as automatic full data export, self-service account deletion, product analytics or self-service card payment.
KRUSPIN may use automated or AI-assisted processing for features started by the customer or user, and for security, support, quality control, service improvement and optimisation. This typically includes translations, text suggestions, summaries, import cleanup, search, error detection and product analytics. We do not use project data to train a general public AI model without a separate agreement.
6. Availability, changes and limitations
The service may change based on feedback, security fixes and further product development.
KRUSPIN is not legal, accounting or tax advice. Finance and vendor modules are operational project overviews, not an accounting system.
7. Payments and commercial terms
The public pricing assumes an introductory offer for one workspace and manual invoicing unless another payment method is explicitly agreed with the customer.
Self-service card payment is available only when it is expressly enabled for a specific account. Paid features, tax details, and the billing process are governed by the applicable offer or contractual agreement.