Security & Privacy

Your files are locked before they reach us.

Drive encrypts every file on your device with a key we never hold. Confidential Compute runs in VMs whose memory the processor encrypts. Where we can still see something, we say so below.

  • 30 s

    Between storage-proof audit rounds

  • 10 of 30

    Pieces needed to rebuild any file

  • SEV-SNP

    On every VM, database, cluster node and runner

Product by product

What we can't see. And what we can.

For every product, what stays encrypted and out of our reach, and what we can still see.

  • Drive

    Out of our reach

    File contents. Each file is encrypted in your browser or app before upload, with a key opened by your unlock password. We can't reset that password.

    What we can see

    File names, folder paths, sizes and dates, so search and browsing work across your devices.

  • Share links & comments

    Out of our reach

    We can't read the shared document or its comments. The link's key sits after the #, and browsers never send that part to a server.

    What we can see

    The file name, plus view counts, watch time, reactions and who commented. A chat preview, if you turn it on, is stored unencrypted.

  • Object Storage

    Out of our reach

    Your data on the storage nodes. Each chunk is encrypted with AES-256-GCM under its own key, and nodes only ever hold encrypted pieces.

    What we can see

    Object contents as our gateway encrypts and decrypts them, so Object Storage isn't end-to-end. Bucket and object names.

  • Confidential Compute

    Out of our reach

    VM memory, which the AMD processor encrypts (SEV-SNP), and the disk, encrypted inside the VM. The disk unlocks only after the VM passes attestation.

    What we can see

    That a VM runs, its size and activity, and traffic metadata. We also run the key broker that releases disk keys.

  • Managed Database, Managed Kubernetes, GitHub Actions Runners

    Out of our reach

    We have no shell on database or cluster nodes. Your kubeconfig is sealed to a key made in your browser, and each runner job gets a fresh VM.

    What we can see

    Encrypted copies of each database password and backup key, kept so we can recover instances and run restores.

  • CDN

    Out of our reach

    Cached content and your certificate keys. Cache nodes are confidential VMs, and TLS ends inside them.

    What we can see

    Client addresses, host names, sizes and timing at the edge. A zone makes its bucket prefix public, so treat what it serves as public.

  • Hub

    Out of our reach

    Private namespaces stay closed to others: only your credentials, or a scoped key you create, can pull from them.

    What we can see

    What you push, since Hub isn't end-to-end encrypted. New namespaces start public, so anyone can pull until you switch them to private in Manage.

How it works

Four protections. Each one documented.

  1. Encrypted before upload

    Drive encrypts each file in your browser, desktop app or phone, so we only receive ciphertext. Sharing re-encrypts a fresh copy with a new key.

  2. Keys that stay with you

    Your unlock password opens your file key. Your 12-word recovery seed is shown once, and we can't recover either for you.

  3. Spread across 30 independent nodes

    Each file is erasure-coded into 30 pieces on 30 independent nodes. Any 10 rebuild it, and no single node holds enough to do so.

  4. Disk keys after attestation

    Each VM proves what it runs with a report signed by the AMD processor. Only then does the key broker release its disk key, encrypted to that VM.

Verify

Evidence you can check.Without asking us.

On-chain records

The placement map and storage-proof results are published to the Hippius chain, along with a usage hash for each hour of compute.

Storage proofs

Storage nodes are challenged on random chunks in audit rounds every 30 seconds, and answer with a zero-knowledge proof. Hipstats shows the network live.

Attestation evidence

Each VM's page shows its attestation result and, while the evidence is kept, the raw AMD report to check offline.

Trust model

Where you still rely on us.

You rely on us for

The software we approve

We build and allowlist the VM images, run the key broker and key vault, and write each VM's boot configuration.

The code in your browser

The console does the encryption in your browser. You rely on it doing what it says.

Encryption doesn't cover

Metadata

That your VM runs, how busy it is and where its traffic goes. In Drive, file names, sizes and dates.

Availability

A server owner can always stop or slow down a VM, or switch the machine off.

Lost keys

If you lose your unlock password and your recovery seed, your files are gone. We have nothing to reset.

Account security

Account controls for you and your team.

  • Sign-in options

    Google, GitHub or Apple, or a 12-word access key with no email attached.

  • A separate unlock password

    Files open with their own password, kept apart from your sign-in.

  • Roles per product

    Give each member Viewer, Operator or Admin access, product by product.

  • An audit trail

    Every change a member makes is listed with who, when and the IP address.

  • Instant revoke

    A revoked share link stops working at once, and its encrypted copy is deleted.

  • Account deletion

    Delete it yourself from Settings, with a 7-day grace period.

FAQ

Questions, answered.

No. Each file is encrypted on your device before upload, and only you hold the key. We do see file names, folder paths, sizes and dates, which is how search and browsing work across your devices.