Event software handles real people, attendee lists, payments, check-ins, messages, feedback, and operational records. This page gives buyers and organizers the practical version of the trust story before they read the formal legal documents.
Organizer-controlled event data
Organizers decide what their event collects, publishes, imports, exports, and sends. Bewitt processes that event data to provide the platform.
GDPR and DPA ready
Bewitt provides a Privacy Policy, Cookie Policy, Terms, and Data Processing Agreement for customers who need processor terms.
Stripe-backed payments
Bewitt uses Stripe for checkout and payment infrastructure, with pricing and commissions explained before organizers pay.
1. Trust at a glance
Bewitt is built for events where the current state needs to be easy to trust: who registered, who has access, who checked in, what changed in the agenda, what participants submitted, and what should be reported after the event.
This page is not a replacement for the formal legal documents. It is a buyer-friendly guide to the areas people most often ask about before using Bewitt for a real event.
2. GDPR and DPA
Bewitt is established in the Netherlands and is designed with GDPR responsibilities in mind.
For most event data, the event organizer is the data controller and Bewitt acts as the data processor. The organizer decides why participant data is collected and how the event uses it. Bewitt processes that data to provide, secure, support, and improve the service under the applicable agreement.
Customers who need processor terms can use the Data Processing Agreement. The Privacy Policy explains controller and processor roles in more detail.
3. Participant data
Participant data can include registrations, imported lists, access status, check-ins, agenda activity, feedback, ratings, quiz answers, networking activity, reward redemptions, and event-related reports.
The organizer controls the event setup, event content, participant communications, registration fields, privacy notices, access rules, exports, and lawful basis for event-specific processing.
Bewitt does not sell personal data. Participants should usually contact the event organizer for event-specific privacy questions, because the organizer normally controls the event relationship. Bewitt can assist organizers when Bewitt acts as processor.
4. Payments
Bewitt uses Stripe for payment infrastructure, including checkout flows for event deposits, balances, adjustments, tickets, store items, domain fees, and related payments where those features are enabled.
Pricing is shown before payment. Self-service events use a base fee, event-day fee, and participant fee. Ticket and event-store sales may include Bewitt commissions plus payment processor fees.
Organizers remain responsible for event-specific payment decisions such as ticket prices, refund rules, tax obligations, event cancellation policies, and attendee communication unless Bewitt has agreed otherwise in writing. See Pricing and the Terms for the formal details.
5. Cookies and analytics
Bewitt uses essential cookies for platform functions such as sessions, authentication, security, preferences, and cookie consent choices.
The public website may also use analytics and experience tools, such as Google Analytics or Contentsquare, when enabled and disclosed. These help Bewitt understand public-page usage, improve conversion paths, and spot usability issues.
The Cookie Policy explains cookie categories, consent behavior, and how analytics preferences are handled.
6. Emma AI assistant
Emma helps visitors and organizers orient around Bewitt, event setup questions, demo paths, custom quote paths, support questions, and product guidance.
Emma conversations may include the messages you send, page context, entry point, suggested actions, request metadata, and form details when you choose to submit a demo, custom quote, or support-style request through an Emma flow.
Emma is not a confidential legal, medical, or financial advisor. Avoid sending unnecessary sensitive information. For account-specific, privacy, billing, or urgent support issues, use a human contact route so the team can handle the context directly.
7. Domains and SSL
Events can start on a Bewitt-hosted subdomain. Organizers can also request a custom event domain when the event should live under their own brand.
Custom domains require DNS setup, verification, and domain activation. Bewitt handles the platform-side domain configuration and SSL certificate setup where supported by the domain flow.
The organizer remains responsible for choosing the event domain, controlling DNS access, keeping event content accurate, and making sure participants receive the correct event link.
8. Security practices
Bewitt applies practical technical and organizational measures to protect the platform and event data. These include encryption in transit, access controls, role-based permissions, authentication controls, logging, monitoring, backups, and operational procedures for incident response.
Security is shared. Organizers are responsible for managing their own users, passwords, exported files, devices, event permissions, third-party tools, and participant communications carefully.
No online service can guarantee perfect security, but Bewitt treats security as part of the product rather than an afterthought.
9. Support
Bewitt supports organizers through the contact routes that match the situation: demo requests, custom quote requests, direct email, support cases inside the organizer experience, and account-specific follow-up where appropriate.
For time-sensitive event situations, include the event name, date, participant count, affected workflow, and what changed. That context helps the team triage faster.
You can contact Bewitt at [email protected].
10. Legal documents
The trust page is the plain-language guide. The formal documents remain the source of legal detail:
11. Contact
For trust, privacy, security, payment, or data-processing questions, contact:
BewittNetherlands
Email: [email protected]
If your question is about a specific event, include the event name or link so Bewitt can route the request properly.
