Security and data

Account-owned Social data is scoped by workspace and account identifiers. Ideas, feeds, settings, documents, Campaigns, schedules, posts, and caches should be read and written only for the selected account. Switching account clears local route state so stale data is not reused.

Copilot should answer page and workflow questions from structured route guides, live UI context, backend data sources, tool metadata, and current workspace or account context. It must not rely on hard-coded language keyword lists or stale model memory when route-specific knowledge is required.

Sessions preserve fast bootstrap behavior while enforcing idle and absolute expiry rules. Logout sync uses authenticated requests and must not place tokens in query strings. If you return after an expired session, the login page should explain why you were signed out.

Risky writes, provider actions, and publishing steps should require explicit confirmation where appropriate. AI Smart should block duplicate clicks, preserve billing and usage records, keep provider errors user-safe, and avoid writing internal failure details into user content fields.