When people start using a VPS, one of the first unspoken questions is usually about data.
Where does it actually live? And who can access it? This article answers those questions in a direct way, without legal language or infrastructure jargon.
Where your data lives
When you deploy a VPS on LumaDock, all data created inside that server lives in the availability zone you selected at deployment time.
That includes:
The operating system
Files you upload or generate
Databases and application data
Snapshots and backups tied to that VPS
Data does not move between locations on its own.
If you deploy in London, your data stays in London unless you intentionally move it elsewhere.
What controls data location
You control data location by choosing where to deploy your VPS.
LumaDock does not automatically copy your VPS data to other regions. There is no hidden replication across countries and no automatic cross-border transfers.
If you later create a VPS in another location, that server starts empty. Any data transfer between servers only happens if you set it up yourself.
Who can access your data
Inside your VPS, access is controlled by you.
Only people with valid credentials can log in to the server. That usually means SSH keys, passwords, or RDP access that you configure.
At the platform level, LumaDock does not log into customer servers, inspect files, or access application data as part of normal operations. Your VPS environment is isolated from other users and from routine platform management.
What LumaDock does see
There is a clear boundary between infrastructure and content.
LumaDock can see operational signals needed to keep the platform running. Things like whether a VPS is powered on, how much disk space is allocated, or whether a network interface is responding.
We do not see what files you store, what code you run, or what data your applications process.
Why this matters
Understanding this boundary helps with both trust and troubleshooting.
You know:
Where your data physically resides
That it does not move without your action
That access to the VPS is under your control
This makes it easier to reason about privacy, compliance, and internal security decisions without guessing how the platform behaves.
The simple model
You choose the location. You control access inside the server.
The platform keeps the infrastructure running underneath.
Once you understand that model, data handling on a VPS becomes predictable instead of vague.