Legal

Privacy Policy

Effective date: October 8, 2026. Added cookieless website and documentation measurement.

How Nodus, Inc. handles personal information.

We use account, billing and workload information to provide Nodus. Console usage analytics and masked session replay are optional. You can use the service without allowing them.

Information needed to run Nodus

We collect account details such as your name, email and company, sign-in and API authentication information, and billing contacts. We process the commands and files you submit, workload status, usage, logs and results to run your workloads and return their output.

We use this information to operate and secure Nodus, bill for usage, communicate about your account and improve reliability. Turning optional analytics off does not stop the service records needed to operate your account and workloads. We do not sell personal information.

Cookies and browser storage

We do not use advertising cookies. The site and console use browser storage to keep you signed in and remember your preferences:

• Appearance. A preference cookie remembers your light or dark choice for one year across the site and console. New visitors see light mode.
• Sign-in and preferences. Local storage keeps your console session token, account display information, recent run labels and preferences between page loads. Tabs share the session token. Signing out revokes it and clears the console session. Session storage holds temporary sign-in and invitation information. API keys are not stored as console sessions.
• Analytics choice. Local storage remembers your analytics preference and PostHog consent state. Analytics session identifiers stay in page memory. When you are signed in, we save your analytics choice to your account and restore it when you return, including in another browser. The automatic prompt appears after sign-in. Once you choose Allow analytics or No thanks, we remember your answer and do not automatically ask again. Browser analytics stay off until a pending choice is confirmed.

Clearing site data removes stored browser preferences. Signing out or clearing site data does not turn off a saved account analytics choice. Use Analytics preferences in console Settings while signed in to change that choice.

Website measurement and optional console analytics

The public website and documentation use automatic cookieless PostHog measurement for page visits, referring domains and selected navigation clicks. Website measurement sets no analytics cookies and uses no local or session storage. PostHog estimates daily audiences using a changing server-side hash of the project, hostname, IP address and browser user agent; it strips the IP address before event processing. These estimates do not identify visitors across days or devices.

Website measurement excludes names, email addresses, form contents, URL query strings and fragments, and session recordings. Only recognized campaign labels are included. Do Not Track and Global Privacy Control disable website measurement. Clicking a link does not prove an account was created, a meeting booked or capacity reserved. Website measurement is separate from console account analytics.

In the console, optional analytics and masked session replay start only after you choose Allow analytics. We use PostHog to understand how people use Nodus and where they encounter problems.

• Usage analytics. Screens visited, active time, action outcomes, browser and device information, and error categories with sensitive details removed.
• Account activity. Account creation, workload acceptance, confirmed command starts, workload outcomes and confirmation that your first payment method is ready. These events can be sent after you close the browser.
• Masked session replay. Navigation and timing. Console content, sign-in areas, account details and assistant conversations are blocked. Text and form inputs are masked.

Analytics uses account, team and workload identifiers that can connect events to your account. We do not send your name, email, card details, credentials, commands, files or workload output in these events. Replay does not record console logs or network request and response bodies. Page URL query strings and fragments are excluded, and IP addresses are removed from ingested analytics events.

Your choice covers your own activity, not your teammates' activity. An earlier browser-only permission requires a new choice before account analytics starts.

Turning analytics off

You can decline analytics or turn it off through Analytics preferences in console Settings or on the sign-in page. Turning it off stops browser collection and clears the active analytics identity immediately. When signed in, we also save the change to your account to stop future account analytics.

If the account change cannot be saved, the console retries without reopening the prompt. Open Analytics preferences in Settings to check the status or retry your choice. Account analytics may continue until the change is confirmed. Turning analytics off does not delete events already sent. You can request deletion using the contact details below.

We respect Do Not Track and Global Privacy Control signals. These stop browser analytics and, when detected while you are signed in, also request that account analytics be turned off.

Service providers

We use service providers for:

• Hosting, content delivery and storage. Operating our website and service, delivering content and storing account, workload, billing and audit records.
• Account authentication. Handling sign-in and authenticating your account.
• Analytics and replay. Optional product analytics, error reporting and masked session replay use a United States processing region.
• Payment processing. Handling payments and invoicing. Full card numbers and security codes are handled by our payment processor. Nodus stores limited payment information such as card brand, last four digits and expiry.
• Assistant services. Processing conversations and relevant workload context when you use the hosted console assistant.

We also use compute providers to run workloads. Workload data is processed on that infrastructure as needed to execute your requests.

How long we keep information

• Session replay. Replays are retained for 30 days.
• Analytics events. These follow our PostHog project retention settings, separately from the 30-day replay limit. You can contact us to request deletion.
• Analytics delivery records. Queued account events expire after 24 hours. Routine cleanup removes finished delivery records older than 30 days. Minimal identifiers remain to prevent duplicate reporting.
• Service records. We retain account, billing and audit records as needed to operate and secure Nodus and meet legal obligations.

Access, correction and deletion

Email [email protected] from the address on your account to request a copy, correction or deletion of your personal information, including analytics data. We confirm receipt and explain any records we need to keep for billing, security or legal obligations. You can also ask us to revoke your API keys. See our security page for more information.

Changes

If we change this policy we will update the effective date above and note what changed. Material changes will also be sent to the email on your account.

Contact

[email protected] · Nodus, Inc., San Francisco & New York