Privacy Policy
Effective 28 October 2026. This page describes the data Proxmox AI actually stores, read from its database schema and its code rather than from a template.
proxmox.ai.id.
Who is responsible
This service is operated by Nur Hamim. Questions about your data: hamimistimewa@gmail.com.
What is collected
Account
- Email address and name — to identify you and to send invitations and password-reset links.
- Password — stored only as a hash, never in its original form.
- Two-factor secret, if you turn it on.
- Sign-in sessions — with IP address and time, so you can see and revoke active sessions.
API keys and machines
- API key — stored as a SHA-256 hash. The key itself is shown once at creation and never stored, so we cannot show it to you again either.
- Last-used IP address for each key.
- Machine identity, for a key pinned to machines: a random id the installer generates, stored as a SHA-256 hash, together with the first and last IP it was seen from. The id itself stays on your machine.
- Machine label — the installer builds this automatically from your system username
and hostname (for example
nurhamim@macbook) so you can tell which machine is asking for approval. It is sent to the platform. Pass--device-nameto set a different one if you would rather not send that.
Audit log
Every confirmed change is recorded: who pressed Confirm, when, from which IP address, with what parameters, and the outcome. This record is the point of the product — without it there is no accountability for what an agent did.
Infrastructure data
Node names, VM names and IDs, CPU and RAM figures, storage status, and backup coverage. All of it is read from your own Proxmox VE installation. Your Proxmox credentials are stored encrypted and are never given to an AI model.
Assistant conversations
Messages you send to the in-dashboard assistant are stored so the history can be reopened. You can delete them yourself at any time from the AI assistant page.
What is never collected
- No advertising cookies, tracking pixels, or third-party analytics.
- The contents of files inside your VMs are never read.
- The plugin and the MCP server send nothing to any address other than
proxmox.ai.id. - We do not read environment variables on your machine looking for credentials belonging to other
services. The only variables read are the plugin’s own
PROXMOX_AI_*settings.
AI models
If your organization enables the in-dashboard assistant, your question and the relevant infrastructure data are sent to the model provider that organization configures with its own API key. That transfer is governed by the provider’s policy. Without such a configuration, nothing leaves the platform. The MCP server never calls a model at all; it only offers tools to your AI client.
How long it is kept
| Data | Retention |
|---|---|
| Generated reports | 180 days, then deleted automatically |
| Expired sign-in sessions | cleared 30 days after they expire |
| Audit log | kept while the organization exists — it is the accountability record |
| Accounts, API keys, machines | until you delete or revoke them |
| Assistant conversations | until you delete them |
When an organization is deleted, all of its data goes with it.
Separation between organizations
Each organization is separated at the database level by PostgreSQL row-level security. One organization can never read another’s data, through the API or through an AI agent.
Your rights
You can request a copy of your data, ask for corrections, or ask for deletion by contacting hamimistimewa@gmail.com. Most of it you can do yourself from the dashboard: revoke a key, remove a machine, delete a conversation, end a session.
Changes
If this policy changes, the date above is updated and material changes are announced in the dashboard.