Customer and event boundaries
Data access is checked within defined customer, organization, and event boundaries on the server. Access to one event does not automatically authorize access to another event’s attendee information.
Security and Governance
Protecting your attendees’ personal information.
Jade combines authenticated access, server-side permissions, customer and event data boundaries, and privacy safeguards to protect personal information throughout your registration and housing operations.
Identity and data protection
Safeguards around who can reach attendee data.
Identity, permissions, and event access are checked separately. Signing in establishes who a user is; authorization determines which records and actions they can access.
Authenticated sessions
Jade uses authenticated sessions and signed tokens carrying the user’s identity, access scope, and capabilities. Mobile sign-in uses Azure AD B2C with PKCE to protect the authentication process.
Participant sign-in safeguards
Participants explicitly select “Sign me in” after email-link verification. Expired and previously used links are handled, and session-identity checks help prevent a confirmation page from showing another attendee’s details.
Payment, monitoring, and integrations
Security across your event operations.
Secure processing and privacy controls
Map payment and data flows to verified gateways, privacy requirements, and compliance frameworks before launch. Jade supports secure payment workflows and administrative controls for your event.
Monitoring before and during show days
Technical health views, alerting, and escalation paths help your team spot issues before they become bigger problems.
Integration planning from the start
Plan data flows between registration, housing, CRM, the mobile app, reporting, and other event systems. Include access and privacy requirements when defining what information is shared.
AI access and participant privacy
Data protections apply to conversational tools, too.
Jade’s chat and voice interfaces check access within the relevant customer and event. Chat-thread checks restrict access when the required scope cannot be established.
The assistant works within the permissions available to the user for supported tasks.
Policy checks for recommendations
Participant AI recommendations require acceptance of the configured AI policies before suggestions are generated.
Privacy in audience profiles
Audience-profile analytics suppress groups of fewer than five people to reduce the risk of identifying individuals through small demographic groups.
Ask about AI data handling →Role-based access
Permissions for each team and partner.
Set user permissions, configuration boundaries, and approval rights across your operational team.
Organizers
Assign access around team responsibilities and the events they support, including attendee information and event configuration.
Exhibitors
Exhibitor lead access is tied to their company, so booth teams work with their own lead records.
Hotel contacts
Portal invitations and rooming-list permissions are separate. Grant or revoke rooming-list access for each hotel contact.
Audit trails and human review
Every important change is logged.
Track database updates, field changes, configuration edits, and user actions with clear activity history.
Event configuration has version history, with tools to compare versions and roll back configuration.
Your team approves what goes live.
Review AI-assisted configuration changes before publishing. Drafts and publication keep configuration review separate from release to attendees.
Check the effect of each operational action, since some changes take effect immediately.
Privacy and retention
Manage personal information across supported records.
Privacy workflows extend beyond the main attendee record, with defined handling for personal information, financial records, and accountability evidence.
Retention by data category
Retention policies operate within platform limits. Customer and event policies can shorten retention, with separate handling for financial requirements and active legal holds.
Authorized privacy administration
An authorized administrator handles subject anonymization through a dedicated workflow. This includes removing personal names from supported invoice and credit-memo snapshots while preserving necessary financial totals and staff accountability.
Privacy processing records
Privacy export and erasure certificates report processing coverage and limitations, helping your team understand which supported records were included.
Common questions
Details for your security review.
How does Jade protect access to attendee information?
Authenticated sessions establish identity. Server-side authorization checks permissions and customer and event boundaries before allowing access. Participant sign-in and session checks also help reduce accidental disclosure.
Does using the assistant provide broader data access?
Chat and voice interfaces apply scoped access checks. The assistant carries out supported tasks within the user’s available permissions. Contact the Jade team for feature-specific questions about AI providers and data processing.
Does a hotel portal invitation include rooming-list access?
No. A hotel contact needs a separate rooming-list access grant, managed by your housing team.
Does every change wait for publication?
Draft and publishing controls apply to event configuration. Some operational actions take effect immediately, so review the action and the records it affects.
How long is event data retained?
Retention depends on the data category and applicable policies. Financial requirements and legal holds may affect timing. Ask about the categories and requirements relevant to your event.
Does anonymization remove every copy of personal data?
Privacy processing records describe the coverage of the supported workflow. Downloaded exports and information shared with external recipients or other systems require separate consideration. Discuss your data flows and subject-request requirements with the Jade team.
Who should we contact for an IT or security review?
Send your security questions and review requirements through the question form. Include the modules, integrations, and AI features you are considering.
Talk with the Jade team
Discuss how Jade protects your event information.
Bring your security, privacy, payment, and integration requirements.
