Skip to main content

Regional Requirements

Files.com provides configuration options that control where your data is stored, where it can be accessed from, and where it is routed during transmission. Evaluate these controls together with temporary processing, logs, and connected systems when your organization has data sovereignty or geographic boundary requirements.

Files.com Editor

To support co-editing among users located in different geographies, the Files.com Editor environment uses temporary storage and processing in our USA region regardless of the region in which files are stored permanently.

Files.com manages this temporary storage automatically, and files are not retained in the USA beyond an editing session.

Logs

All logs on Files.com are stored exclusively in the USA region, including retained logs of AS2 messages (which contain file contents.) AS2 log retention periods can be configured independently, allowing you to configure a short retention period of these contents in the USA region.

We believe that the value of a unified global search for logs across regional use justifies the choice of having all logs in a single global region.

Other Systems

To be fully restricted to a region, all other connected remote systems must also reside in your chosen region. This includes identity providers, remote storage solutions, notification services, and any connected iPaaS.

Whether you can restrict these third-party services depends on the region. Contact your third-party vendors to find out what regional configurations are available.

Configuring the Region

Configure storage, Remote Server routing, and client connections for your chosen region, while accounting for the processing and connected systems described above. An additional, optional step restricts the countries your users can connect from.

First, configure your top-level Root Folder to be stored in your desired region. Other folders inherit this region unless specifically overridden. Review any overrides: regional connection settings do not relocate folders stored elsewhere, and reaching those files still involves their storage region. Remote Mount storage remains in the location of the external system.

With your top-level Root Folder set to your desired region, configure the Remote Servers settings to restrict the routing of data to your desired region.

To restrict traffic from your end-users to the correct region, configure the Global Acceleration setting to use your desired region.

If your obligation also covers where users connect from, configure Allowed Countries to specify only countries within your region. Take this step only when the requirement is explicit, because country detection relies on approximate IP geolocation and can block legitimate users who travel or connect through a VPN that exits elsewhere.

When another Files.com site uses your site's API key for a native Files.com Remote Server, your site's Global Acceleration setting does not pin that connection to your region. Your Allowed Countries and Disallowed Countries lists do not apply to it either. The folders' storage regions and the key's access limits still apply, but those settings do not establish a regional connection restriction for this integration. Disable use of your site's API keys by native Files.com Remote Servers if your requirements cannot permit that connection.