Privacy, secrets and access
Know what is shared and where actions happen.
Reviewed 6 October 2026 · 2 min read
Import example project ↗Two named conversations, shared files, revisions and a preview.
Before you start
Helios, connected computers and external services have separate permissions. Private projects do not automatically make every integration private.
Transport encryption, encryption at rest and end-to-end encryption are distinct. Consult current privacy information for the actual data path.
Step by step
- Share only needed project folders.
- Use secret fields/environment configuration, not prompts or source files.
- Review memories, project sharing and connected accounts separately.
- Revoke unused access and verify it no longer works.
Try this
Example request
Check for committed credentials without printing secret values. Report locations and explain which integrations receive project data and how to disable them.
Check the result
- Secrets are absent from client bundles and public examples.
- Collaborator access matches role and project.
- Revocation stops the associated action.
If something goes wrong
If a secret leaked, deleting the file/message is insufficient; rotate it with the provider.
Do not infer a specific encryption guarantee from a general privacy label.
Your screen may differ by platform and version. Check availability or get help.