NexloLabs CloudSign in

Privacy

A plain-English explanation of which data NexloLabs Cloud stores, which data is encrypted, and what we deliberately never see.

What we store

  • Your email address (to sign you in, verify your account and send security emails).
  • An Argon2id hash of your password — never the password itself.
  • Key-wrapping blobs and salt needed so your device can re-derive your encryption keys (these are ciphertext we cannot open).
  • Encrypted files, folders and filenames — i.e. the ciphertext itself.
  • Account metadata: storage used, storage limit, role, creation time, session records, audit events.

What is encrypted on your device

  • File contents — encrypted with AES-256-GCM using a fresh per-file key.
  • File names and folder names — encrypted with your master key.
  • The keys themselves are wrapped client-side and are never transmitted in a usable form.

How files are processed

  • Your browser reads the file, encrypts it chunk by chunk, and only then uploads it.
  • Downloads are the reverse: we stream ciphertext back and your browser decrypts it locally.
  • The server only ever stores and returns ciphertext.

Information NexloLabs does not need

  • Plaintext file contents.
  • Readable file names or folder structures.
  • Your password, your encryption keys, or your recovery key.

Important practical limits

  • Your email address is needed for account recovery and is therefore visible to us.
  • File sizes and upload times are visible to us as technical metadata.
  • Because files are encrypted, we cannot scan them — and we cannot help recover them if your keys are lost.

This page describes the technical data flows of NexloLabs Cloud. For the formal legal documentation please refer to Privacy Policy, Terms of Service and Imprint.