FAQ3 min readUpdated Aug 3, 2026

How does encryption work?

Files are encrypted with AES-256-GCM before storage; traffic to SeraCase uses TLS.

Overview

SeraCase protects materials in two layers. In transit, your browser connects over HTTPS/TLS. At rest, documents are encrypted with AES-256-GCM using per-file keys and authentication tags so stored objects are not readable as plain files.

Why this feature exists

Encryption is easier to trust when explained without jargon — and it matters for legal paperwork.

Step-by-step

  1. 1

    Upload as usual

    Add Documents handles encryption as part of the secure upload path. You do not need a separate encrypt step.

Best practices

  • Prefer uploading from a trusted network when possible.
  • Keep MFA on so encryption is paired with strong account access.

Productivity tips

  • Point counsel to Trust Center if they ask about technical controls.

Common mistakes

  • Confusing “encrypted” with “anonymous” — you still sign in to access your own files.

Frequently asked questions

How does encryption work?

Uploads use TLS in transit. Stored files use AES-256-GCM with unique IVs and authentication tags. Keys are not stored beside ciphertext. Platform backups add infrastructure-level encryption at rest.

Do I manage encryption keys myself?

No. Key handling is built into SeraCase’s secure upload and storage path so you can focus on your case.

Screenshots

Illustration placeholder — product screenshot coming soon.

How does encryption work? screenshot placeholder

Helpful links

Related articles

Was this helpful?