Data sovereignty in cloud storage means you — not the provider — hold legal and technical control over your files. It requires five things: files on hardware you own, encryption keys only you hold, access control with no silent third-party scanning, permanent deletion on your terms, and full auditability. Commercial cloud providers (Google Drive, iCloud, Dropbox) fail at least three of these. Gavety meets all five on hardware you already own.
What Is Data Sovereignty and Why Does It Matter Now?
Data sovereignty has traditionally been an enterprise and government concern. According to Nutanix’s healthcare report, 72% of healthcare IT professionals now name data sovereignty as a must-include factor in infrastructure decisions. The discussion has shifted from “is our data secure?” to “do we actually control it?”
Those are different questions. Security protects data from unauthorised outsiders. Sovereignty determines whether you — or someone else — are ultimately in charge of the data itself.
The same shift is happening for individuals, quietly and without a press release. When Google changed Google Photos from unlimited to capped storage, millions of users discovered that their archive of irreplaceable family photos was subject to a corporate decision they had no part in. When cloud providers update their terms of service, users can “agree” or lose access. When a government issues a legal order to a cloud provider, the provider complies — users find out later, if at all.
According to NIST, data sovereignty refers to the idea that data is subject to the laws and governance structures of the entity that holds it. For enterprise data, that’s usually the organisation that created it. For personal data in commercial cloud, it’s the cloud provider’s terms, jurisdiction, and business decisions — not yours.
Data sovereignty cloud storage means changing that equation: your files, on hardware you control, governed only by you.
The Five Requirements for True Data Sovereignty
Enterprise data sovereignty frameworks — from GDPR to CCPA to NIST guidelines — converge on five core requirements. Every one of them applies equally to personal data. Here is what each means in plain terms, and what it demands of your storage architecture.
Where Does Commercial Cloud Fail the Sovereignty Test?
This is not an argument that commercial cloud providers are negligent or dishonest. Google, Apple, and Dropbox all invest heavily in security. The point is more precise: their architecture is fundamentally incompatible with data sovereignty, regardless of their intentions.
| Sovereignty requirement | Gavety | Google Drive / iCloud |
|---|---|---|
| Data residency (your hardware) | ✓ Your device, your location | ✗ Provider data centres |
| Encryption key control | ✓ Only you hold keys | ✗ Provider holds keys |
| No silent third-party access | ✓ Gavety cannot read files | ✗ Provider scans for service ops |
| Permanent deletion on demand | ✓ Immediate, no retention period | ✗ 30-day trash + backend copies |
| Full access audit log (user-visible) | ✓ Logged on your device | ✗ Internal only, not user-visible |
| Remote access from any browser | ✓ Outbound tunnel | ✓ Native cloud |
| Works behind residential ISP CGNAT | ✓ No port forwarding needed | ✓ Cloud-hosted, always works |
| Uptime guarantee | Depends on your hardware uptime | ✓ Provider SLA (99.9%+) |
What Do Global Privacy Laws Say About Data Sovereignty?
Data protection legislation around the world is converging on the same principle: individuals should have meaningful control over their personal data. What differs is how each jurisdiction enforces it — and how far the law actually goes.
The EU’s GDPR (General Data Protection Regulation) gives individuals the right to access data held about them, the right to erasure (“the right to be forgotten”), and the right to data portability. It applies to any organisation processing data about EU residents, regardless of where that organisation is based. The CCPA/CPRA in California, PIPEDA in Canada, the UK GDPR, and Australia’s Privacy Act all follow similar frameworks. The EU’s NIS2 Directive adds sovereignty-level requirements for critical infrastructure.
Every major privacy law gives you the right to request access or deletion of your data from a fiduciary. None of them give you a technical guarantee that the data was not already processed, copied, or used before your request. The most direct way to exercise data sovereignty is not to file requests — it is to minimise what you give fiduciaries in the first place. Files stored on your own hardware are not subject to a data fiduciary’s processing decisions. The law is a legal floor; self-hosted storage is the architectural ceiling above it.
There is also a jurisdiction gap that no privacy law fully resolves. Data stored in a cloud provider’s data centres is subject to the laws of the country where those data centres sit — not necessarily your own country’s laws. The US CLOUD Act, for example, can compel US-based cloud providers to produce data stored anywhere in the world, regardless of the user’s nationality. Files on hardware in your own home are governed only by the laws of your jurisdiction.
How Gavety Delivers Data Sovereignty by Architecture
The critical word is architecture. Sovereignty cannot be delivered by a privacy policy or a contractual commitment. It must be built into how the system works at a technical level — so that even if Gavety wanted to access your files, it architecturally cannot.
Here is how each of the five requirements is met:
Data residency
When you install Gavety on a Raspberry Pi or any Linux device, your files stay on the storage drive attached to that device. Gavety’s software indexes them and makes them browsable. Nothing is uploaded to Gavety’s servers. The files physically exist only on your device, in your home or office.
Encryption in transit (key control in practice)
Remote access to your files travels through an outbound encrypted tunnel from your device to app.gavety.com. File contents are encrypted end-to-end between your device and your browser. Gavety’s relay sees connection metadata (the tunnel endpoints) but not the file contents traversing it. For additional at-rest encryption, adding LUKS full-disk encryption to your Linux device means your files are unreadable even if the physical drive is lost or seized.
Access control
Permissions are set per folder. You decide who can access what. Shareable links are token-secured and optionally time-limited. Revoking a link removes access immediately. Gavety’s systems have no access to your file contents — the architecture of the outbound tunnel means your file data never passes through any system that can read it except yours and your authorised recipients’.
Permanent deletion
When you delete a file on Gavety, it is deleted from your filesystem. There is no cloud-side retention period because there is no cloud-side copy. The file is gone when you delete it — not in 30 days, not “after we process the request”.
Auditability
Access logs are generated on your device by the Gavety agent — every file access, every shared link use, every login event. These logs live on your hardware and are visible to you. No access event is hidden in a provider’s internal system you can never see.
The distinction between architecture and policy is the most important concept in data sovereignty. A policy says “we won’t look at your files.” An architecture means they technically cannot. Gavety’s on-device model is an architectural sovereignty guarantee, not a contractual one. If Gavety changes its privacy policy tomorrow, your files on your hardware are unaffected.
Your Biggest Sovereignty Gap: Backups
This is the section most people skip — and it’s the section that matters most.
If you move your primary files to sovereign self-hosted storage but continue backing them up to Google Drive, iCloud, or any commercial cloud, you have not achieved data sovereignty. You have moved the entry point while leaving the back door open.
Backups contain the same sensitive data as your primary storage — often more of it, because backups are comprehensive. Enterprise data sovereignty frameworks have learned this lesson the hard way: a Sophos study found attackers targeted backups in 94% of ransomware incidents because backups are often held at cloud providers with weaker access controls than production systems.
Most discussions of data sovereignty focus on primary files. But if your backup is on Google Drive, then Google has a copy of everything you are trying to keep sovereign. True data sovereignty requires that every copy of your data — primary and backup — meets the same five requirements. The sovereign backup architecture for Gavety users is an rsync job from the primary SSD to a second physical drive, stored locally. Two copies, both on hardware you own, both in a location you control.
The practical implementation is straightforward: add a second USB drive to your Raspberry Pi and run a nightly rsync from your primary storage to it. This gives you redundancy — protection against drive failure — without surrendering sovereignty to a cloud backup provider. The full setup guide for Raspberry Pi cloud storage covers the rsync configuration.
How to Set Up Sovereign Cloud Storage With Gavety
What you need
- A Linux device — Raspberry Pi 4 (~$60), Pi 5 (~$80), an old laptop, or any Ubuntu/Debian machine
- A storage drive — USB SSD 1TB (~$50–$70) recommended for speed; USB HDD works at lower cost
- A Gavety licence — $15/yr, or $100 one-time lifetime deal
The install
curl -fsSL install.gavety.com | bashThe installer detects your hardware (ARM64 for Raspberry Pi, x86_64 for laptops), registers the Gavety agent as a systemd service that starts on boot, mounts your storage drive into the file manager, and creates the outbound tunnel to app.gavety.com. No NGINX. No SSL certificate management. No router configuration.
If your ISP uses CGNAT — common on residential broadband plans worldwide — the tunnel bypasses this automatically. No port forwarding rules, no router configuration. Your files are accessible from any browser anywhere in the world. For more on how the tunnel solves residential networking limitations: self-hosting without port forwarding.
After install
Log into app.gavety.com, set folder permissions, migrate your files from Google Drive using Google Takeout, and configure your backup rsync job. Total time: under two hours for a complete setup including migration.
Common Questions About Data Sovereignty Cloud Storage
No. The same five sovereignty requirements — residency, key control, access control, retention control, and auditability — apply equally to personal data. Your family photos, medical records, financial documents, and private correspondence carry personal and legal significance. The Electronic Frontier Foundation has documented extensively how data held by third parties carries weaker legal protections than data on your own device across most jurisdictions worldwide.
The practical difference is that individuals rarely have legal compliance deadlines driving the urgency. But the underlying principle is identical: your data should be subject to your control, not a provider’s policies and business decisions.
GDPR gives you legal rights over data that companies hold about you — the right to access it, correct it, delete it, and port it. These are meaningful rights, but they are not the same as data sovereignty. They give you a claim over data someone else holds; they do not prevent that data from being processed in the first place.
True data sovereignty goes further: your files are architecturally inaccessible to any third party, not just legally protected against misuse. GDPR is the legal floor. Storing files on hardware you own is the architectural ceiling. The two are complementary — GDPR protects data that reaches companies; self-hosted storage ensures most of it never does. For a full breakdown of how GDPR relates to self-hosted storage, the GDPR right to erasure guide at gdpr.eu is a reliable starting point.
No, and it would be dishonest to claim otherwise. Google Drive has data-centre-grade redundancy and uptime SLAs that a home device cannot match. If your Raspberry Pi loses power or your home internet goes down, remote access to your files is unavailable until both come back online.
Local access — from devices on your home network — always works regardless of internet connectivity. And for most users, the trade-off is manageable: power outages are typically brief, and the sovereignty and cost benefits outweigh the uptime difference for personal file storage. A basic UPS ($30–$50) resolves the concern for most short outages.
Frequently Asked Questions
What is the difference between data security and data sovereignty?
Security protects your data from unauthorised external access — hackers, malware, eavesdroppers. Sovereignty determines who ultimately controls the data — you or the provider. You can have highly secure storage that is not sovereign: Google Drive is extremely secure against external attackers, but Google controls the encryption keys, scanning policies, and retention schedules. Sovereignty requires that the provider be architecturally excluded from control, not just contractually committed to not exercising it.
Does achieving data sovereignty mean I have to give up Google Docs or collaborative tools?
Not entirely. The most practical approach for most people is selective sovereignty: move files that require genuine privacy — financial records, medical documents, personal photos, private correspondence — to Gavety. Keep a Google account for collaborative tools like Docs and Sheets where real-time editing and sharing with colleagues matters most. The two coexist without conflict. The goal is not to eliminate every cloud service — it’s to ensure that files requiring sovereignty are not on infrastructure you don’t control.
Does Gavety work on residential ISPs that use CGNAT?
CGNAT (Carrier-Grade NAT) is used by many residential ISPs worldwide to share a single public IP address across many customers. It is common on residential broadband in the US, UK, Europe, Asia, and most other regions. CGNAT blocks inbound port forwarding, which means tools like Nextcloud fail to provide remote access without a workaround.
Gavety’s agent creates an outbound connection from your device to app.gavety.com — not an inbound connection from the internet. Since CGNAT only blocks inbound connections, Gavety’s outbound tunnel works on any ISP, anywhere in the world. No port forwarding rules, no router configuration. See: self-hosting without port forwarding guide.
What privacy laws govern Gavety as a data processor?
Gavety acts as a data processor for account-level data (your email address, login credentials, billing information) and complies with applicable privacy regulations including GDPR for EU users, CCPA for California users, and equivalent laws in other jurisdictions. For file contents, Gavety is not a processor — your files never pass through Gavety’s infrastructure in readable form. Your files are on your hardware. Gavety’s relay routes the encrypted connection but cannot read the contents. The Gavety data protection page outlines the full breakdown of what data Gavety holds and what it does not.
What happens to my sovereign files if I stop paying for Gavety?
Your files remain on your hardware, exactly as they always were. Cancelling Gavety removes remote access through app.gavety.com — the outbound tunnel stops working. But your files are on a drive in your possession, in standard Linux filesystem format (ext4). Plug the drive into any Linux machine and your files are accessible. This is the sovereignty guarantee: cancelling a subscription affects access, not possession. Your data cannot be held hostage by a pricing decision.
Sovereignty is architecture, not a contract.
Gavety puts your files on hardware you own and routes access through a tunnel that cannot read them. Works on Raspberry Pi, any Linux device, and on any residential ISP — including those using CGNAT. No port forwarding. No router config.
Read the setup guide → Free for LAN use · $100 one-time licence · $20/user/year for remote access