Customer Isolation
Files.com separates customers' data and configuration while running on shared infrastructure. Access to one customer's site does not grant access to another customer's site.
Each operation must be authorized for the site and resources it affects, including access to file contents and background work performed on the customer's behalf.
This is logical separation through access controls. Sharing a service or storage system does not give customers access to each other's data, and creating a Site or Workspace does not allocate dedicated physical infrastructure.
For independent assurance, the SOC 2 reference describes the examination's scope and how to request the report.
Authorized Connections Between Sites
Customers can authorize connections between their Sites to exchange files. Being an administrator of one Site does not by itself authorize access to an unrelated Site. Access Across Sites and Storage explains the permissions and controls that apply when customers choose to connect their Sites or expose connected storage.
Subdomain Reuse
A Files.com subdomain is an address assigned to a site, not a permanent identifier of the customer who first used it. Claiming a previously used subdomain does not transfer the former site's files, users, or permissions.
Connections to that address can nevertheless reach a different customer's site after the name is reassigned.
Preserve an old address while people or integrations still rely on it, and update their destinations before releasing it. A familiar address alone does not establish that it still belongs to the same customer. Custom Subdomain explains availability, expired-trial reassignment, preservation, and release.
Custom Domains and DNS Control
Adding a Custom Domain associates a hostname, such as files.example.com, with a Files.com Site. An available hostname can be saved before its DNS is configured; saving it does not verify that the person controls the domain. Each hostname can be assigned to only one Site at a time, so another Site cannot add a hostname already assigned to yours.
Files.com does not require a separate ownership-verification step when saving a Custom Domain because making the address work requires control of its DNS configuration. Saving a hostname in Files.com does not change its DNS or redirect an existing website. Whoever manages the domain's DNS must point the hostname at the correct Files.com destination before visitors using that address can reach your Site. A hostname still pointing to a different service continues to reach that service.
For a Files.com-managed SSL certificate, Files.com checks the DNS configuration and the certificate authority validates the domain before issuing the certificate. Saving the hostname alone does not obtain a valid certificate. Custom Domain setup explains the required DNS and certificate configuration.