Data Residency
Data Residency in emSigner
Overview
emSigner is designed to support data residency and regulatory compliance across multiple geographies. All customer data is stored and processed within the data residency zone associated with the customer’s subscription.
Supported Data Residency Zones
emSigner currently supports the following residency zones:
United States
Europe
United Arab Emirates (UAE)
India
Indonesia
Each zone operates on a logically and physically isolated infrastructure to meet local data protection and regulatory requirements.
How Data Residency Is Determined
The email ID used during login is used by emSigner to determine the default data residency zone applicable to the user.
This mapping is based on how the user’s subscription is provisioned and tagged in the system.
Multiple Residency Zones on a Subscription
If a user’s organization has a subscription that is enabled for more than one data residency zone, emSigner will:
Prompt the user on screen during login or access
Allow the user to select the appropriate residency zone for that session
This ensures users always work within the correct regulatory and operational boundary.
Where Your Data Is Stored
All data associated with a subscription is stored exclusively within the selected data residency zone, including:
Documents and uploaded files
Signing transactions and envelopes
Audit trails, logs, and completion certificates
Metadata related to users and workflows
Data does not move across regions unless explicitly provisioned through a separate subscription or contractual arrangement.
Key Points to Note
Data residency is enforced at the subscription level
Users cannot access or view data outside their assigned residency zone
Residency selection (where applicable) does not affect document integrity or legal validity
Need to Change or Add a Residency Zone?
If your organization requires:
A change in data residency, or
Enablement of additional residency zones
Please contact emSigner Support or your Account Manager to evaluate availability and compliance requirements.
Last updated