Last updated: September 20, 2026. Access policy for agency servers - exactly how NextaPanel connects to infrastructure you provide, and what that access does and does not mean.
NextaPanel is a management tool that runs on top of servers an Agency already owns or controls. Unlike traditional hosting, we do not provide the server itself - you connect your own, and NextaPanel uses SSH access you grant to turn it into a working host for your Clients' sites, databases, email, and backups. This policy explains exactly what that access means in practice, what we do with it, and what happens if you ever disconnect a server.
This policy supplements our Terms of Service, in particular Section 7 ("No Responsibility for Hosted Content") and Section 4 ("The Service"), and should be read alongside them.
When you add a server to your NextaPanel account, you provide its connection details directly - host/IP address, SSH port, SSH username, and either an SSH key or a password. NextaPanel uses these credentials strictly to establish an SSH connection to your server in order to provision it and carry out the actions you request from your dashboard.
We never connect to a server that has not been explicitly added to your account with credentials you supplied, and we never attempt to discover, scan, or connect to infrastructure you have not registered with us.
Every connection NextaPanel makes to your server exists to power a specific feature available in the dashboard. At a high level, that access is used for:
This list describes the categories of access our features use, not a technical inventory of what's installed on your server. Access under each category is only ever exercised when triggered by an action from your Agency or Client dashboard, as described in the next section.
We do not access your server on our own initiative, at any time, for any reason outside of what is described in this policy. Every connection NextaPanel makes to your server happens because you, your team, or one of your Clients performed a defined action from the Agency or Client dashboard - for example, adding a site, installing a database, rotating a password, restarting a container, or reading a resource metric.
Access is always scoped to the specific role and feature being used. An action available to a Client account (such as managing their own site's files) does not grant broader server access than that feature requires; it does not, for example, expose other Clients' data on the same server. We do not run background access, unscheduled maintenance connections, or any action your account did not request.
NextaPanel does not take responsibility for the data stored on your server. The server, and everything on it, belongs to and is controlled by you as the Agency - we simply provide the dashboard and tooling that lets you and your Clients manage that data, within the access you've granted, through defined features and actions. Backups, data integrity, and the security of the underlying server outside of what NextaPanel itself provisions remain your responsibility.
This is consistent with our Terms of Service: NextaPanel is a tool, not the owner or operator of your infrastructure.
The SSH key or password you provide for a server is stored encrypted and is used only to establish the connections described in this policy. It is never shared with, or made visible to, another Agency, and is not used for any purpose beyond operating the features of your own account.
You can disconnect a server from your account at any time. The moment you do, NextaPanel completely forgets it: the stored connection credentials are discarded, and every tool, service, and background action we perform against that server - monitoring, container auto-heal, scheduled backups, and anything else - stops immediately.
Disconnecting does not delete your data. Your server, its files, and everything installed on it remain exactly as they were at the moment of disconnection. NextaPanel simply has no further access and takes no further action - nothing is remotely wiped or altered as part of disconnecting. That state persists untouched until you choose to add the server back to your account, at which point management resumes from where it left off.