Data Storage and Residency

Revvyz offers its customers two data storage options:

Customer-Managed Storage and Revyz-Managed Storage, as shown in the picture below.

1. Customer-Managed Storage (Bring Your Own Storage - BYOS)

This option allows you to store data from your Atlassian site in your own public cloud storage account, with Revyz supporting AWS and Azure public cloud.

Data Flow:

Authentication & Access: After installing the Revyz app on your Jira/Confluence site, Atlassian creates a unique dedicated user that enables the app to access your Atlassian environment data. The created user is unique to the app and the site.
Data Collection: Using unique tenant-isolated compute infrastructure, Revyz leverages this Atlassian-created user to securely retrieve data and metadata from your site via TLS 1.2 encrypted connection
1. Data includes Jira projects, issues, comments, attachments, Confluence spaces, pages, blogs, comments, attachments and associated configuration objects
Direct Transfer: All retrieved data is transferred directly without any staging of the retrieved data to your own cloud storage account using a Revyz user with limited permissions to read & write to your storage
Storage: Data resides exclusively in your public cloud environment (AWS S3 or Azure Blob Storage), maintaining your full control and ownership
Metadata Management: Revyz retains only app specific metadata about backup states and configurations to facilitate future backup or restore UI operations

Notes

Revyz is built on public cloud infrastructure provided by AWS, which is considered as a sub-processor for Revyz
Revyz does not use any other third party sub-processor (besides AWS) for any data operations such as data staging, processing, transformation & egress
The data may be momentarily held in the customer specific unique isolated compute instances’s memory before it is moved to its final destination
Data in motion is encrypted using TLS, Atlassian mandates a minimum of TLS 1.2
it is the customers responsibility to ensure that data is encrypted at rest. Most public cloud providers enable encryption of data at rest by default.
- Details on Revyz policies for encryption available here
- Reference: Amazon S3 Encrypts New Objects By Default
- Reference: Azure Storage Encryption for Data at rest
There are no storage limits, on the volume of data that you would like to store in your own storage.

2. Revyz-Managed Storage

With this option, your data is stored in Revyz's AWS account in one of our supported AWS data centers - see list below. One of the unique aspects of the Revyz architecture is that there is no communication between the data centers we support. Thus helping meet any stringent data residency requirements that require all data and meta-data to be resident within a given data center. Data at rest is encrypted and you can review our encryption methodology here.

Data Flow:

Authentication & Access: After installing the Revyz app on your Jira/Confluence site, Atlassian creates a unique dedicated user that enables the app to access your Atlassian environment data. The created user is unique to the app and the site.
Data Collection: Using unique tenant-isolated compute infrastructure, Revyz leverages this Atlassian-created user to securely retrieve data and metadata from your site via TLS 1.2 encrypted connection
1. Data includes Jira projects, issues, comments, attachments, Confluence spaces, pages, blogs, comments, attachments and associated configuration objects
Data Storage: Data retrieved is encrypted, and stored in Revyz's AWS S3 storage
1. Encryption of the data is on a per customer basis with separate and unique encryption keys for each customer / tenant
2. All backup data maintained within Revyz's secured infrastructure is stored in an encrypted manner at rest and data is always encrypted in-motion

Data Residency

Revyz as of today supports the following AWS regions for your backup data storage:

US - AWS US East – North Virginia ( us-east-1 )
EU - AWS Europe – Frankfurt ( eu-central-1 )
Asia Pacific - AWS Asia Pacific – Sydney ( ap-southeast-2 )
CANADA - AWS Canada Central– Canada ( ca-central-1 )
Asia Pacific - AWS Asia Pacific – Singapore ( ap-southeast-1 )

Data residency region is automatically picked based on where your Atlassian data resides or is pinned too. We follow following mapping:

Atlassian Data Location	Atlassian AWS regions	Revyz AWS region
Global	All Atlassian cloud in AWS region	US - AWS US East North Virginia ( us-east-1 )
Australia	Consists of AWS Sydney region	Asia Pacific - AWS Asia Pacific Sydney ( ap-southeast-2 )
EU	Consists of AWS Frankfurt and Dublin regions	EU - AWS Europe Frankfurt ( eu-central-1 )
USA	Consists of US East and US West regions	US - AWS US East North Virginia ( us-east-1 )
Germany	Consists of AWS Frankfurt region	EU - AWS Europe Frankfurt ( eu-central-1 )
Canada	Consists of AWS Canada Central region	CANADA - AWS Canada Canada ( ca-central-1 )
Singapore	Consists of AWS Singapore region	Asia Pacific - AWS Asia Pacific Singapore ( ap-southeast-1 )