Developer Doc

Pass enough context to help. Do not pass private data.

The AnswerLattice widget uses safe page hints so approved answers match the screen. It does not need tenant IDs, user IDs, account records, tokens, or payment data.

Open install guide View quickstarts

Allowed

path, title, feature, workflow, role, locale

Forbidden

IDs, emails, phone numbers, tokens, secrets, billing data

Screenshots

User-uploaded or pasted only

Implementation notes

Keep the install small and verifiable.

AnswerLattice developer docs focus on the v1 widget contract, dashboard-owned route settings, safe browser context, and verification.

Allowed context

Use stable, high-level values that describe the current product page or workflow.

Send path and title for the current page.
Use product-safe feature, workflow, role, and locale values when available.
Update context after client-side route changes.

Do not send sensitive data

AnswerLattice should not receive private account, billing, auth, or customer-record payloads from the browser.

Do not send tenantId, storeId, tId, sId, userId, email, phone, or full name.
Do not send access tokens, cookies, JWTs, service keys, secrets, or payment data.
Do not pass raw customer records or private account metadata into widget context.

Screenshot boundary

Visual context is explicit user input, not automatic runtime capture.

Use upload or paste when the user chooses to attach a screenshot.
Do not scrape DOM, automatically capture the app screen, or attach restricted pages.
Keep blocked routes configured in the AnswerLattice dashboard.