Skip to main content
EVaultOne

Sovereignty & compliance

Your archive never leaves your country.

GCC banking regulators require customer data to stay in-country and expect banks to seek approval before outsourcing. EVaultOne is built around that: a separate platform in each country, two sites per country, and a ready-made pack to support your regulator submission.

Where we host

Each country runs as its own EVaultOne platform. Archives, indexes, databases and backups for a country stay inside that country — including the disaster-recovery copy at the second site.

CountryStatusNote
United Arab EmiratesLaunching firstTwo separate in-country data centres
QatarNext—
Saudi ArabiaPlanned—
BahrainServed from the UAESubject to customer's regulator approval
KuwaitPlanned—
OmanPlanned—

What stays in-country

Data residency is more than where the mail sits. Everything that describes, protects or gives access to your archive stays in your country too.

  • Archived content

    Every archived email, attachment and file, held in Enterprise Vault stores inside your country.

  • Indexes and databases

    Search indexes and the SQL databases that describe your archive. Metadata can be as sensitive as the content itself.

  • Backups and recovery copies

    Immutable backups and the disaster-recovery copy at the second in-country data centre.

  • Logs and audit trails

    Records of every administrative action and every access to your environment.

  • Administrative access

    Only named, vetted engineers, over secured and logged connections.

  • Your data at exit

    Exports at the end of the contract are delivered to you directly, with a chain-of-custody report.

Regulators and frameworks we map to

EVaultOne is designed around the outsourcing, cloud and data-protection rules that apply to GCC banks and government entities. For each framework, we map our controls and documentation to its requirements.

  • CBUAE (Outsourcing Regulation for Banks)
  • Dubai Electronic Security Center (DESC)
  • Qatar Central Bank (QCB cloud regulation)
  • Saudi Central Bank (SAMA)
  • National Cybersecurity Authority (NCA)
  • Central Bank of Bahrain (CBB)
  • UAE Personal Data Protection Law
We provide the evidence and documentation your compliance team needs. Regulatory approval remains your organisation's decision.

How we support your regulator submission

Regulator approval is your organisation's decision. Our role is to make the submission complete, accurate and easy to defend.

  1. 1

    Scope

    We help your risk team describe the arrangement: data types, volumes, locations and the delivery model you have chosen.

  2. 2

    Document

    You receive the approval support pack, prepared for your framework and your entity.

  3. 3

    Clarify

    Our specialists join your discussions with risk, compliance and internal audit, and help answer the regulator's questions.

  4. 4

    Evidence

    Once you are live, audit rights and evidence on request keep the arrangement supportable at every review.

Security controls

Security is built into how the platform is designed and operated, not added afterwards.

  • Encryption

    Archived data is encrypted in transit and at rest.

  • Controlled access

    Access only by named, vetted engineers using multi-factor authentication, with full audit logging.

  • Customer isolation

    An isolated Enterprise Vault environment for each customer on the EVaultOne platform. Regulator-tier customers have dedicated hardware.

  • Resilience

    Two separate in-country data centres, immutable backups and regularly tested restores.

  • Patching and vulnerabilities

    Security updates for Enterprise Vault, Windows and SQL are applied on a defined schedule, and vulnerabilities are tracked to closure.

  • Certification

    ISO 27001 certification is in progress. Certificates and audit reports will be shared with customers once issued.

Regulator approval support pack

Everything your compliance team needs to prepare an outsourcing or cloud submission, in one set of documents.

  • Architecture description

    How the platform is built, where each component runs and how customer environments are separated.

  • Data-flow and data-location statement

    Where your data travels and rests — during migration, in operation and at exit.

  • Security controls matrix

    Each control mapped to the requirements of your framework, with evidence references.

  • Business continuity and exit plan

    How the service recovers from failure, and how you leave with all of your data.

  • Audit rights clause

    Contractual rights for you, your auditors and your regulator to inspect the service.

  • Sub-processor list

    Every third party involved in delivering the service, and where it operates.

Request the pack