What you can look up
Given an identifier the individual has provided (typically an email address or phone number), User Information returns:- All login records tied to that identifier.
- Associated session data — start, end, device information.
- Module-specific metadata captured during sign-in (SAML attributes, self-provisioning fields, etc.).
- Sponsor / host relationships if the individual was sponsored as a visitor.
Responding to a data request
Verify the requestor's identity
Before producing data, confirm that the person requesting the data
is who they claim to be. This is an Organization policy matter,
not a Sign In feature.
If deletion is requested, delete or anonymize
Use the deletion action available from the search result. Deletion
removes the records; anonymization keeps the statistical footprint
but strips personal identifiers.
What you cannot delete
Some records must be kept for legal or audit reasons even under a data-subject deletion request:- Admin audit logs — records of who in your Organization took which action, retained for internal accountability.
- Aggregate statistics — post-anonymization counts that no longer identify any individual.
- Billing-relevant totals if applicable.
Scope
User Information operates per Sign-In Context. If the individual has data in multiple Contexts (for example, they’ve visited several venues within the same Organization), run the search separately in each Context.Interaction with retention
Data retention automatically removes records after a configured window. User Information is the on-demand override for situations where a specific individual wants their data gone sooner.Related
Data retention
The automatic retention window for all guest data.
Terms and conditions
Communicate guests’ privacy rights up front.

