> For the complete documentation index, see [llms.txt](https://docs.nimbalyst.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nimbalyst.com/open-safe-private-secure/security.md). # Security How Nimbalyst handles files, sessions, and credentials, with open source code your security team can audit and encryption for shared data. This page covers how Nimbalyst approaches security: open source code you can audit, SOC 2 Type 2 certification, and encryption for shared team data. ### Open Source: Audit the Code Yourself Nimbalyst is open source. The full source code is published at [github.com/nimbalyst](https://github.com/nimbalyst), so you (or your security team) can review exactly how the app handles your files, sessions, credentials, and network traffic. ### Nimbalyst is SOC 2 Type 2 Certified Nimbalyst holds a SOC 2 Type 2 certification: an independent auditor has examined our security, availability, and confidentiality controls and verified they operated over time, not just on the day of the audit. Compliance is monitored continuously between audits. Current certifications, subprocessors, and policies are published on the [trust page](https://nimbalyst.com/trust/), and the [security feature page](https://nimbalyst.com/features/security/) covers how data is handled in the app. ### Nimbalyst Teams Data Security Nimbalyst Teams is a shared layer over each teammate's local Nimbalyst installation and locally configured agents. Only files and Tracker items explicitly shared with a team enter the team collaboration flow. * **Cloudflare infrastructure**: Shared team data flows through Nimbalyst's Cloudflare sync service. * **Encrypted in transit and at rest**: Team documents, Tracker data, and collaboration updates are encrypted while moving across the network and while stored. * **Isolated per team**: Team data is stored in team-specific infrastructure and access requires an authenticated, authorized membership. * **Server-managed team keys**: Nimbalyst-hosted Teams manages encryption keys so authorized web, CLI, and agent experiences can access team work. Hosted team data is encrypted but is not zero-knowledge. * **Separate personal sync**: Personal device sync uses end-to-end encryption with keys that stay on your devices. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.nimbalyst.com/open-safe-private-secure/security.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.