Encryption protects information at different stages of a file workflow. An encrypted connection protects data while it travels between systems. File-level encryption protects the contents independently of that connection, so a delivered file can remain unreadable until the recipient decrypts it with the required key. Understanding that distinction helps you match the protection to the requirement.

Administrators and integration developers use this section when connecting a client, exchanging encrypted files with a partner, or confirming that a workflow meets their organization's encryption policy. For example, agreeing to use an encrypted transfer protocol does not establish whether the partner also expects a GPG-encrypted file.

Connection compatibility depends on both sides. Clients must trust the relevant certificates and negotiate supported algorithms. Files.com requires modern, secure ciphers by default; enabling legacy options changes the site's compatibility and security tradeoff. Cipher guidance helps you identify what a connection uses before changing that policy.

For files that must remain encrypted after delivery, GPG (PGP) provides an additional layer separate from transport encryption and Files.com's default storage encryption. Plan who holds the keys and who needs to decrypt the result as part of the exchange, so encryption supports the intended workflow from sender to recipient.