Use identity only when your host application knows it
After the loader is initialized, host code can call AppsResolveWidget.identify with bounded values such as your internal user ID, email address, or display name. This can reduce repeated form entry, but the customer can still review the contact details submitted with a request.
Add useful page context
Use AppsResolveWidget.setContext for stable support clues such as product area, application version, plan name, or page type. The loader also supplies a safe page URL and title when page-context collection is enabled. Context helps rank relevant help articles and gives the reviewer a better starting point.
Never pass secrets or page contents
The widget runs in an isolated iframe and accepts only the allowlisted identity and context fields your integration supplies.
- Do not pass passwords, cookies, session identifiers, access tokens, private keys, card data, or form values.
- Do not copy the full DOM, clipboard, local storage, or arbitrary page text into context.
- Keep values short, intentional, and understandable to a support reviewer.
- Call reset when a signed-in customer changes or signs out on a shared browser session.
