Privacy Policy

1. Who We Are

Node9 Security, Inc. ("Node9", "we", "us") builds an execution security layer for AI agents. Our Services include the Node9 SaaS dashboard, the open-source node9-ai CLI, and associated APIs. We act as the controller of personal information collected via our website and dashboard, and as a processor for workspace customer data. Contact: support@node9.ai.

2. What Node9 Does — and Does Not — See

Node9 intercepts AI agent tool calls at the proxy level. We evaluate the tool name and its arguments at the moment of execution against your workspace policies. We do not read, store, or transmit:

• AI conversational context, chat history, or LLM-generated text
• File contents, unless they are a direct argument to an intercepted tool call
• Network traffic, environment variables, or browser sessions

In local mode (node9 login --local), all policy decisions remain on your machine and no tool call data is sent to Node9 servers.

3. Information We Collect

• Account Data: Name, email address, and profile picture collected when you sign up via email/password or Google OAuth. Google OAuth is used for authentication only — we receive your email and public profile to create your account and nothing else.
• Workspace & Policy Data: Policy rules, API key metadata (keys are stored as SHA-256 hashes — plaintext is never retained), and workspace settings you configure.
• Agent Audit Logs (cloud mode only): When you connect Node9 to the cloud with an API key, tool name, parameters, decision outcome (ALLOW/BLOCK/PENDING), agent identity, hostname, and OS platform are sent to Node9 servers and retained for the life of the workspace (see section 7). In local mode (node9 login --local or no API key configured), no tool call data ever leaves your machine.
• Slack Integration: When you connect Slack for approvals, we store your OAuth token (AES-256 encrypted at rest) and use it only to send and update approval messages in the channel you designate.
• Technical Data: IP addresses and request metadata from connections to our API and website, used for rate limiting, security monitoring, and debugging. This applies only when your proxy communicates with Node9 servers (cloud mode).
• Hosted repository scan: when you scan a public repository at node9.ai/scan, we record which repository, when, the result, the site you arrived from (its host name only), your country as reported by our network provider, and whether the request came from a browser or an automated client. We do not store your IP address. To count distinct visitors we keep a one-way hash of your address and browser that changes every day and is deleted within seven days. If you are signed in, we record only that the scan came from a signed-in user, not which one.
• Sign in with GitHub: when you sign in with GitHub, we store your GitHub account id and login, and an access token (AES-256 encrypted at rest) that we use for one thing: to ask GitHub whether your account may write to the repository whose scan you are viewing. We read no repository content with it. The token is deleted when you disconnect GitHub from the repository page, and with your account. Your email address from GitHub is used only to create a new account; it never links your GitHub sign-in to an existing account.
• Repositories in your workspace: when a workspace admin adds a repository scan to the dashboard, or connects a repository through the node9 GitHub Action, the full findings of those scans (file, line, explanation and fix) are shared with the members of that workspace and kept with the workspace. The Action sends only the scan result and the identity GitHub signs for the run (repository, branch, commit and workflow run); node9 does not read the repository's source code. Results from private repositories are never shown on the public scan pages. Upload keys are stored as one-way hashes and can be revoked at any time; disconnecting a repository stops uploads and revokes its keys.

4. How We Use Your Data

• Evaluate AI agent tool calls against your workspace policies in real time.
• Send Slack approval notifications and allow/deny responses as you configure.
• Maintain tamper-evident audit logs for your team's security review.
• Authenticate your account and manage workspace access.
• Monitor service health, troubleshoot issues, and prevent abuse.

We do not use your data to train AI models shared with other customers. Your audit logs and policy data remain within your workspace context.

5. Google API Disclosure

Node9 uses Google OAuth solely for user authentication. When you sign in with Google, we receive only your email address and public profile (name and profile picture) to create and identify your account. We do not request, access, or use any other Google services or scopes.

Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Sign in with GitHub asks for your public profile and your email address (the read:user and user:email scopes) and no repository scope. The access token GitHub issues is used only to check whether your account may write to the public repository whose scan you are viewing (section 3). You can revoke it at any time from the repository page or from your GitHub settings.

6. Sharing & Sub-Processors

We share data only with essential service providers required to operate the Services:

• Google Cloud Platform (GCP) — hosting and infrastructure
• Neon / PostgreSQL — database storage
• Redis — session and queue management
• LemonSqueezy — payment processing (they handle billing data; their privacy policy applies)
• Slack — approval notifications when you enable the integration

We do not sell, rent, or share your data with advertisers or unrelated third parties.

7. Data Retention & Deletion

Audit entries are retained for the life of the workspace, on every plan, so the record of what your agents did stays complete. We limit what those entries contain rather than deleting them later: an entry our DLP gate flagged stores no command preview at all, and a labelled credential is masked in the preview of any entry that does store one. You may delete your workspace or account at any time from Settings. Upon deletion, workspace data is removed within 30 days and OAuth tokens are revoked immediately.

8. Security

We apply industry-standard security controls: AES-256-CBC encryption for OAuth tokens at rest, SHA-256 hashing for API keys, bcrypt (cost 10) for passwords, TLS for all data in transit, and row-level workspace isolation in the database. See our Security documentation for full details.

9. Your Privacy Rights

Depending on your location (GDPR / CCPA / UK GDPR), you have the right to access, rectify, export, or delete your personal data. To exercise these rights, contact us at support@node9.ai. We aim to respond within 30 days.

10. Changes

We may update this policy from time to time. If changes are material, we will notify you by email or via the dashboard. Continued use after the effective date constitutes acceptance.

11. Contact

Node9 Security, Inc. · Tel Aviv, Israel · support@node9.ai