Privacy & data boundaries

Local files and external tools

KOS stores context in files. That does not mean every connected workflow stays local. Your agent, sync service, plugin or integration may send information to an external provider under its own configuration and terms.

Before granting access, decide which folder and task the tool needs. Use synthetic data for setup tests.

Classify before sharing

Missing access classification should be treated as restricted. Internal context is not automatically suitable for a public repository, website, support issue or model prompt. Review both the document contents and linked sources before sharing.

Never put credentials in memory, handoff files, prompts or public examples. Keep installation records and user-specific profiles out of public documentation bundles.

Approval has a scope

Permission to read a project does not automatically authorize sending email, publishing files, changing unrelated folders or installing extensions. A Power-Up’s declaration is a request to inspect, not evidence that all requested permissions are appropriate.

Before reporting a problem

Share the minimum relevant error, edition/version and reproducible steps. Remove names, paths that identify people, tokens, private notes and attachments. Use the support guide to prepare a sanitized report.