Legal
Privacy Policy
Last updated 15 July 2026
1. Who this applies to
EventNexis is operated by NexisHub. This policy covers two kinds of people: administrators and members of a customer organization (an “organization workspace,” such as St. Kizito Event Manager), and guests whose information an organization registers for an event.
2. What we collect
For organization members, we collect an email address, name, and authentication data via our identity provider (Clerk).
For event guests, an organization may register: full name, phone number, email address, a photograph, category, and free-text notes. This data is entered by the organization, not by the guest directly, and is scoped entirely to that organization's workspace.
3. How data is isolated
Every record in EventNexis belongs to exactly one organization. Organizations cannot access each other's data — this is enforced at the database query level, not only in the interface. Within an organization, guest contact details and photographs are visible only to members whose role grants that access; ushers scanning guests at the door can verify identity without a general read grant to the full guest list.
4. Invitation tokens and QR codes
Each invitation carries a random, unguessable 256-bit token. The token itself contains no guest name, phone number, or other personal data. Scanning it reveals only what is needed to admit the guest. Public invitation-verification requests are rate-limited to resist guessing.
5. Where data is stored
Application data is stored in a managed PostgreSQL database (Neon). Uploaded files — guest photographs, organization logos, and generated invitations — are stored in object storage (Vercel Blob), separate from the application server. Authentication is handled by Clerk.
6. Retention and deletion
Guest, invitation, and check-in records are retained for the organization's use of the platform, since attendance history has ongoing reporting value and must survive event archiving. An organization owner may request deletion of a specific guest's personal data (name, phone, email, photo) by contacting us; underlying attendance records are retained in de-identified form to preserve accurate totals.
7. Exports and reports
Organizations can export guest, attendance, and audit records as CSV or PDF. Exports are scoped to the exporting organization only and are themselves logged in that organization's audit trail.
8. Contact
EventNexis is currently in a pilot phase. For questions about this policy or a specific data request, contact us through the sign-in page or your organization administrator.
