Account4 minNoindex · follow
Review privacy and data boundaries
Find the approved legal pages and understand the documentation boundary around account and content data.
- Audience
- Customers evaluating or operating a workspace
- Prerequisite
- No account is required for the public legal pages.
- Outcome
- The correct legal source is used without treating product documentation as legal terms.
Last reviewed 2026-08-02 · Product Information · v2026.08
Use the approved legal sources
This documentation summarizes product navigation, not legal commitments.
Use safe workspace practices
Keep account credentials and private workspace information out of public links.
- 1Sign in through the current account route before opening private surfaces.
- 2Use Docs links with return paths instead of placing private state in a public URL.
- 3Do not paste credentials, provider tokens, or customer identifiers into public documentation URLs.
- 4Use the visible product controls for account and content actions.
Understand the documentation limit
No schema, retention policy, or legal treatment is changed here.
- Public Docs do not expose private app content.
- Truth diagrams contain no customer data or production identifiers.
- Questions about legal rights and obligations should be answered by the approved legal pages, not inferred from product labels.
Related documentation
Understand plans, trial, and billingUse the current published prices and capability disclosure without inferring unenforced Pro features.Handle sign-in and account access problemsUse only the current verified sign-in route; automated password recovery is not documented as available.Use current product terminologyTranslate current user-facing labels consistently and keep internal implementation language out of customer procedures.