Privacy Policy

NodeAI is a control plane. Your prompts travel through NodeAI's servers to a GPU node that you connect and control, and the reply travels back the same way. Because NodeAI routes and records the conversation, NodeAI can read your prompts and the model's replies, and stores them so that conversations survive a reload and so you can audit which node served what.

NodeAI is not end-to-end encrypted, and it is not a zero-knowledge service. If you need inference that NodeAI itself cannot see, NodeAI is the wrong tool today.

Account. Your email address, your name if you give one, a hash of your password, and session records. Authentication is handled by better-auth; NodeAI never stores your password itself.

Conversations. The text of prompts you send and replies the model produces, in order, with the model used, the node that served each turn, that node's trust tier, and any tool calls the model made. Notices are stored too — for example that a reply was regenerated on another node after the first one failed, or that older messages were dropped to fit a model's context window.

Routing and audit records. For each turn: the model requested, the node chosen, the reason it was chosen (including the signals compared), the trust floor and sensitivity label applied, estimated cost and latency, and how many times the turn failed over. Security-relevant actions are recorded separately: node registration, trust changes, quarantine, revoke, policy changes, API-key creation and revocation, and every OAuth authorization, token issue, refresh and revocation.

Nodes you connect. The identifier and label you give a node, its GPU model, VRAM, driver version, which models its runtime serves, its context window, whether it supports tool calling, its provider and region if you set them, and measured performance: latency, throughput, reliability and reported GPU load. Node credentials are stored only as hashes.

Credentials. API keys and OAuth access and refresh tokens are stored only as SHA-256 hashes, never in a form NodeAI could show you again or replay. For API keys a short non-secret prefix is kept so you can recognise a key in the list.

Connected applications. When you authorize an app such as Claude or ChatGPT: which application, which permissions you granted, when you granted them and when it last used the connection.

Feedback and evaluations. If you rate a reply or run an evaluation set, the rating, the cases and their results are stored.

Your password in readable form; your API keys or OAuth tokens in readable form; node credentials in readable form. NodeAI collects no advertising identifiers, runs no third-party analytics or tracking scripts, and sells nothing to anyone.

NodeAI does not train any model on your data, and does not send your prompts to any AI provider other than the nodes you connect yourself.

Some data has an explicit lifetime enforced by the software:

• OAuth authorization codes expire after 60 seconds and are single-use.
• OAuth access tokens expire after 1 hour; refresh tokens after 30 days.
• Node and device credentials expire after 30 days and rotate before then; a pairing code expires after 5 minutes.
• The chunks used to move a reply between NodeAI servers are deleted as soon as the reply finishes. They are transport, not transcript.

Everything else is kept until it is deleted on request. To be precise rather than reassuring: NodeAI currently runs no scheduled job that deletes old conversations, routing records, audit events or node metrics, and there is no self-service account deletion in the product yet. Expired tokens stop working immediately but their rows are not yet purged.

If you want your data removed, email [email protected] and it will be deleted. Self-service deletion and automatic retention limits are planned; this page will be updated when they ship, and not before.

NodeAI runs on Vercel (application hosting) and Neon (PostgreSQL database). Both process data on NodeAI's behalf as infrastructure providers.

The GPU nodes that run inference are yours. If you rent one from a provider, that provider operates the machine your prompts are executed on; NodeAI has no relationship with them on your behalf. Choosing where your nodes run, and labelling their trust tier, is how you control that.

When you connect an application over OAuth — Claude, ChatGPT, or your own — that application receives the permissions you approved and whatever it asks for through them. What it then does with a reply is governed by that application's own privacy policy.

A connected application can be disconnected at any time from Connection → Connected apps. Its access stops on the next request: NodeAI checks the grant on every call rather than trusting a token until it expires. Disconnecting one application does not affect your account, your API keys, or any other application.

An API key can be revoked from the same screen and stops working immediately.

A node can be quarantined, which takes it out of routing and moves any reply it is serving to another eligible node, or revoked, which destroys its credential and blocks it from reconnecting.

For account or conversation deletion, email [email protected].

Traffic to NodeAI is served over HTTPS. Passwords, API keys, OAuth tokens and node credentials are stored as hashes. Access to your fleet is scoped: an application you connect receives only the permissions you approved, and administrative actions such as revoking a node require a permission that connectors are never granted by default.

To report a vulnerability, email [email protected]. Please do not open a public issue first.

If this policy changes materially, the date at the top changes and the change is described here. Questions: [email protected].

NodeAI is operated by NodeAI. This policy describes the software as deployed at the date above; it is not legal advice.