Data Protection and Sharing

Protecting a file means understanding where its contents go and who can use each copy. Storage encryption, an encrypted connection, recipient authentication, and file-level encryption each protect a different part of that journey. None, by itself, describes the whole exchange.

This section supports decisions about sending files outside your organization, publishing content, choosing encryption, and meeting data-handling requirements. The relevant boundary may be a person's account, a shared mailbox, a browser origin, a storage region, or possession of a private decryption key. Choose the controls that govern the relationship you actually need.

Copies, Processing, and Recipients

A Remote Server Mount can keep the authoritative files on another system while Files.com transfers or processes their contents. A snapshot creates a separate copy. An AI feature can send file contents and tool results to the services carrying out the requested work. The location of the original file therefore does not establish every place its information will be handled.

The same applies to recipients. A Share Link can give a visitor access without a Files.com user account. Public Hosting can publish content independently of a user's folder permissions. Once a person downloads a file, removing the original access does not retrieve that copy. Plan the data's intended use and lifetime as part of the sharing decision.

Controls With Different Purposes

Transport encryption protects a connection. Storage encryption protects retained data. GPG encryption can keep a delivered file unreadable without the recipient's private key. Authentication establishes which account, credential, or mailbox is being used; permissions and sharing settings determine the available content and actions.

Browser controls have another role. They govern how a website loads, embeds, or reads content in a visitor's browser. A browser policy is not a replacement for server-side access checks, and two folders served under one hostname can share browser capabilities even when their URLs and passwords differ.

Assess the complete route from source to recipient, including processing and temporary storage, before relying on a single setting to meet a data-handling requirement. Regional storage and routing guidance provides the configuration context for geographic requirements.