Security & privacy

Make the data boundaries explicit.

Security and privacy depend on several connected controls: workspace scope, domain-bound installation, customer verification, provider ownership checks, mapped results and appropriate retention. No single check replaces all the others. An opaque browser token continues a technical conversation; a verified mailbox proves access to that mailbox; your business system decides whether the customer owns the requested record.

Use the identity and data-boundary guides when designing private operations, then review consent and retention separately. The marketing website’s optional analytics configuration is not automatically installed on customer websites. A cookie preference change stops future optional measurement but is not a general deletion interface. Identify external mailbox copies and provider records when handling data requests, and never place secrets or private customer records in shared Knowledge for convenience.