Security

Personal data and GDPR

The personal data a VaultPanel panel keeps, where it goes and for how long, and how to answer access and erasure requests (GDPR and similar laws).

Last updated

This page is for whoever runs a VaultPanel panel: a company managing its own servers, or a hosting provider whose customers sign in to it. It lists the personal data VaultPanel keeps, where it goes, how long it is kept, and how to answer people who ask for their data or for it to be deleted.

It describes the software. It is not legal advice: what your obligations are depends on your country, your customers and your contracts. Have them checked by someone qualified.

Who is responsible

VaultPanel is self-hosted. The VaultPanel project receives nothing from your panel: no usage statistics, no error reports, and no check-ins. The panel and its agents talk only to each other and to the services you configure (below).

So for the personal data in your panel, you are the controller. If you host websites, email or apps for customers, you are usually also a processor for the personal data inside them (their visitors' data, their mailboxes). For that relationship, see the data processing agreement template that comes with VaultPanel (legal/dpa-template.md in the source).

What the panel stores about people

DataAbout whomWhereHow long
Name, email, role, language, time zonePanel usersusersUntil erased (see Answering requests)
Password, two-factor secret, recovery codesPanel usersusers, user_recovery_codesHashed or encrypted; until erased
Sessions: IP address, browser, timesPanel userssessions30 days after they end
API tokens: name, last use, last IPPanel usersapi_tokensUntil revoked and erased
Audit log: who did what, from which IP and browserPanel users, hosting customersaudit_logsForever by default. Set a period under Audit log (90 days to 10 years)
Assistant conversations (what was asked and answered)Panel usersassistant_messagesUntil the person deletes them, or is erased
Terminal sessions: who, which server, IP, times; recordingsPanel usersterminal_sessions, recording files90 days by default (set on the Terminal page)
Emails the panel sent (invites, resets, alerts)Recipientsemail_messages30 days
Hosting account: name, company, emailHosting customerscustomersUntil the account is removed and the person erased
Mailboxes: address, display name, password hash, mailPeople with email on your serversPanel database, mail serversUntil the mailbox is deleted
Webhook deliveries (event payloads)Possibly anyone named in an eventwebhook_deliveries30 days
Server metrics, jobs, alertsNot personal on their own; jobs record which account askedPanel databaseMetrics 7 days by default (VAULTPANEL_METRICS_RETENTION_DAYS), resolved alerts per VAULTPANEL_ALERT_HISTORY_DAYS, jobs kept
Websites, apps, databases, files, backupsWhatever your customers put in themYour servers, backup storageUntil deleted; backups per their schedule's "keep" count

Secrets (S3 keys, SFTP keys, backup keys, the AI provider's API key, database passwords) are stored encrypted with the panel's secret key, and job parameters that carry them are removed when the job ends.

Where data goes

Only when you turn the feature on:

FeatureRecipientWhat is sent
Panel email (System > Panel Email)Your SMTP providerRecipients' addresses, the message (invite and reset links, alerts)
AI assistant (System > Assistant Settings)Anthropic or the OpenAI-compatible provider you configure; nothing with Free model on this serverWhat the person types, and the server details the assistant reads to answer
Backups to storageYour S3-compatible bucket or SFTP serverBackups, encrypted before they leave the server (agent 0.42.0+); keep each storage's key
SSL certificatesLet's EncryptThe domain names, and the contact email you enter
DNS providers (DNS Zones)Cloudflare or NamecheapDomain names and check records
WebhooksThe URLs you addEvent payloads (which can include names, emails and resource names)
Billing API / WHMCSYour billing systemHosting accounts' names, emails and plans

Each of these is a recipient (and usually a sub-processor) you should name in your own privacy notice and agreements. Check where each one stores data if you transfer it out of the EU/EEA.

Answering requests

A copy of someone's data (access, portability, GDPR art. 15 and 20). People download their own under Account > Download my data. For someone else, open Users, open the person and click Export personal data. You get a JSON file with their account, sessions, API tokens, assistant conversations, terminal sessions, hosting account and their entries in the audit log. Passwords, two-factor secrets and token values are never included. Exports are recorded in the audit log.

Deleting someone (erasure, art. 17). On Users:

  1. Open the person and untick Active, then save.
  2. Open them again, click Erase personal data and confirm.

Their name and email are replaced, and these are deleted: sessions, API tokens, recovery codes, reset links, assistant conversations, preferences, and emails waiting to be sent to them. The audit log keeps what the account did, but not who they were: the name or email shown becomes "Erased person", and the IP addresses and browsers are removed. This keeps the record of what happened useful for security without identifying the person, and cannot be undone.

For a hosting customer, remove their hosting account on Customers first. That deletes their websites, apps, databases and mailboxes. Erasing their panel user then erases their contact details too. Their backups in storage are deleted with the backups (or expire per their schedule).

Their data in your own backups of the panel (vaultpanel backup) stays until those backups expire; say so in your privacy notice.

Correcting data (art. 16). People change their language and time zone themselves (Account > Preferences); an admin corrects their name on Users. An email address cannot be changed: invite the person again with the right address, then erase the old account.

Retention

  • Set the audit log period under Audit log (owners and admins). The database itself refuses to delete entries younger than the period, and never anything under 90 days, so a compromised panel cannot erase recent history. Unset, entries are kept forever.
  • Choose a period that fits your security and legal needs (one or two years is common) and state it in your privacy notice.
  • The other periods are in the table above.

Security

The measures behind "appropriate technical and organisational measures" (art. 32) are described in Security. Among them:

  • HTTPS throughout, with two-factor sign-in available and enforceable;
  • scrypt password hashing;
  • role-based access, with an append-only audit log;
  • secrets encrypted at rest;
  • backups encrypted before they leave the server;
  • agents run only signed, allowlisted operations.

Other laws

The same tools cover most privacy laws built on the same ideas, such as the UK GDPR, Brazil's LGPD, South Africa's POPIA, Kenya's and Nigeria's data protection acts, and the CCPA/CPRA in California. Their deadlines and wording differ (for example, one month to answer under the GDPR, 45 days under the CCPA).