Privacy Policy

AnswerLattice handles account, team member, workspace, widget, hosted-help domain, and ticket details needed to operate the service.

It also handles product support content, knowledge-base imports, FAQs, changelog entries, safe page context that a customer chooses to send through the widget, and capped ticket debugging context when a ticket is created.

Knowledge intake sources can include selected public URLs, pasted support text, starter answers, and supported document text. Customers should avoid importing unnecessary personal data.

Page context should describe the product surface, route, feature, workflow, role, or plan needed to answer support questions. It should not include passwords, payment card data, secrets, private tokens, or unrelated personal information.

AnswerLattice uses workspace and support content to power help centers, hosted docs, approved answers, widget responses, ticket fallback, changelog relevance, readiness summaries, and support-gap review queues.

Operational logs and ticket debugging context are used to keep the service reliable, investigate reported failures, protect the service from abuse, and understand whether support knowledge is stale or incomplete.

AnswerLattice may use trusted infrastructure providers for hosting, authentication, storage, databases, email, analytics, and AI-assisted drafting. These providers are used only to operate the service.

AnswerLattice does not sell customer support content or widget conversation data.

Workspace owners can manage team access, widget settings, allowed origins, blocked routes, product details, support content, tickets, changelogs, and approved answers from the AnswerLattice dashboard.

Customers are responsible for choosing what content they import and what page context their product sends to AnswerLattice.

AnswerLattice keeps data for as long as it is needed to provide the service, support the customer workspace, meet operational needs, or satisfy legal requirements.

Imported source metadata and capped extracted text stay with the intake job so owners can review drafts and lineage. Raw file retention is not required for day-one browser-extracted intake.

Access controls, tenant separation, validation, and bounded payload handling are used to reduce accidental exposure and protect support data.

For privacy questions, contact hello@answerlattice.com.