The data on your VPS stays in the availability zone you chose when you deployed it. Inside the server, you control who has access, and LumaDock sees only what it needs to keep the platform running.
Where your data lives
Everything created inside the VPS is stored in that availability zone, including:
The operating system
Files you upload or generate
Databases and application data
Snapshots and backups tied to that VPS
Data doesn't move between locations on its own. If you deploy in London, your data stays in London unless you move it yourself or ask us to migrate the VPS to another region.
What controls data location
You control data location by choosing where to deploy your VPS. Knowing this makes privacy, compliance and internal security decisions easier, because you don't have to guess how the platform handles your data.
LumaDock doesn't automatically copy your VPS data to other regions. There is no hidden replication across countries and no automatic cross-border transfer.
If you later create a VPS in another location, that server starts empty, and data reaches it only if you transfer it yourself.
Who can access your data
Inside your VPS, you control access. Only people with valid credentials can log in to the server, usually with SSH keys, passwords or Remote Desktop access that you set up.
At the platform level, LumaDock doesn't log in to 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 can see
There is a clear boundary between infrastructure and content. LumaDock can see the operational signals needed to keep the platform running, such as the power state of a VPS, how much disk space is allocated and if its network interface is responding.
We don't see what files you store, what code you run or what data your applications process.