Data & privacy · updated 2026-09-08
Where your data lives. Who can access it.
A rented environment still has an operator and a provider. This page says what each can and cannot see, in plain words. When something changes, this page changes first.
Your environmentIsolated per user. Nobody else's processes run inside it.
The GPUDedicated or shared depending on the plan. Your card always says which, before you start.
The physical machineOperated by an infrastructure provider we name, in a region we publish, before the pilot opens. Shared at the hardware level, like any cloud.
What Nodegrove seesGPU minutes, storage size, health checks, and your billing identity. The full list is published with the pilot.
What Nodegrove does not logYour prompts, outputs, workflows and files. Your apps keep their own history on your disk, and you can delete it.
BackupsWhat is backed up, where, and for how long is published before the pilot opens. Until then, assume your grove is a single copy and export what matters.
When you leaveExport everything, then delete. Your data is removed after a short grace period, and we say how long that is in writing.
What "private" means here, and what it does not
At home, private means data never leaves your network. On Nodegrove, private means three specific things: your environment is isolated, we do not log what you do inside it, and you can export and delete everything. It does not mean air-gapped, and it does not mean nobody could ever access the hardware. A provider operates the machines, and we name them before the pilot opens.
Open models by default
Your grove runs open models on its own GPU. Nothing you type is sent to a third-party model API unless you add your own key to an app on purpose.
Questions
Write to info@nodegrove.io. Every message is read by the person who runs this.