Security & Data Privacy

An honest description of how EventIntro protects your data today. We describe what we actually do — not aspirational certifications we don't yet hold.

How your data is protected

• Passwords are hashed with bcrypt. We never store or can read your password.
• Data in transit is encrypted over TLS.
• Hosting is on Microsoft Azure; the application and database run in Azure infrastructure.
• Access control — communities and events are private by default. Only members of a specific community can see each other's profiles.
• Abuse protection — CSRF protection and rate limiting are enabled on the application.

Who owns the data

Attendee profile data is owned by the attendee, not the host. Attendees can edit or remove their profile information at any time, and hosts can export their community's data. We do not sell personal data, and we do not use attendee profiles to train any third-party model.

Third-party subprocessors

EventIntro relies on a small number of services to operate: Microsoft Azure (hosting and storage), SendGrid (email delivery), LinkedIn (optional profile import), and third-party LLM providers (profile enrichment from survey responses). Survey responses are processed by those LLM providers to build match profiles. The current subprocessor list is available on request.

What we don't claim

EventIntro is a young platform. We don't currently advertise formal compliance certifications (such as SOC 2); if that changes, we'll say so here rather than imply it. For the full detail on what we collect and why, see the privacy policy.

Have a security or data-handling question for a buyer-diligence review? Get in touch — we answer these directly.