mirror of
https://github.com/OneUptime/oneuptime.git
synced 2026-04-06 00:32:12 +02:00
bdc40bcd59
- Updated error messages in errors.ejs to use hyphens instead of em dashes. - Modified meta description in index.ejs files to use hyphens. - Adjusted WhatsApp setup instructions in Index.tsx to replace em dashes with hyphens. - Changed footer description in footer.ejs to use hyphens. - Updated various markdown and HTML files to replace em dashes with hyphens for uniformity.
63 lines
3.2 KiB
Plaintext
63 lines
3.2 KiB
Plaintext
<header id="pagmt">
|
||
|
||
<h1>Data Residency for OneUptime Enterprise Customers</h1>
|
||
|
||
<p>OneUptime customers will be able to choose which country or region their data is stored while fulfilling corporate
|
||
policies and compliance requirements</p>
|
||
|
||
</header>
|
||
|
||
<section>
|
||
<h3>Introduction</h3>
|
||
|
||
<p>In the not too distant past, when on-premises software was the norm, data storage was simple. Your data lived
|
||
with
|
||
you. Today, cloud services make data residency more complicated. Global organizations are creating their own
|
||
internal policies for where data can be stored, while governments and third-party regulators are enforcing data
|
||
residency requirements.</p>
|
||
|
||
<p>Thousands of companies use OneUptime every day, but because data is primarily stored in the United States, many
|
||
organizations abroad remain on the sidelines. To bridge this gap-and make OneUptime available to more organizations
|
||
in highly regulated
|
||
sectors, such as financial services, government and health care-we’re delivering data residency for OneUptime. </p>
|
||
|
||
<p>Data residency will give global organizations more control over where their data is stored. We can deploy your
|
||
data to any of the Microsoft Azure, Aamazon Web Services or Google Cloud Platform, or On-Prem regions around the
|
||
world.
|
||
</p>
|
||
|
||
<h3>Data residency FAQ: What you need to know</h3>
|
||
|
||
|
||
<h5>With data residency, what type of data does OneUptime store?</h5>
|
||
<p>Data from OneUptime is stored at rest within a desired data
|
||
region. All data in OneUptime, whether in transit or at rest, is encrypted.</p>
|
||
|
||
<h5>Where does third party data reside data reside?</h5>
|
||
<p>The location of data from third-party apps your organization use with OneUptime is dependent on the
|
||
application partner’s policies.</p>
|
||
|
||
<h5>I’m an existing customer. Can I move my data to a new region?</h5>
|
||
<p>Yes! Existing customers can move their organization’s or projects data to new residency regions. Note, however,
|
||
that
|
||
the entire organization must be rooted in a single region.</p>
|
||
|
||
<h5>If I move my data to a new region, will anything else change?</h5>
|
||
<p>No. Your organization will enjoy the same OneUptime experience and features they use today.</p>
|
||
|
||
<h3>Data Security</h3>
|
||
<p>Data residency is the latest example of OneUptime’s continued investment on enterprise-grade security and compliance.
|
||
OneUptime meets and exceeds some of the most broadly recognized security standards and offers tools to help
|
||
customers
|
||
address their compliance requirements.</p>
|
||
|
||
<p>OneUptime’s security program certifies its service with ISO 27001, ISO 27017, ISO 27018, SOC 2 Type II, and SOC 3.
|
||
OneUptime also helps customers meet specific
|
||
industry regulations or international security and data privacy standards, including HIPAA and GDPR.
|
||
Its security program is committed to expanding coverage and incorporating new guidance and industry best
|
||
practices.</p>
|
||
|
||
<p>Data residency is currently available to all enterprise customers today. If you wish to contact us, please write
|
||
to us at enterprise@oneuptime.com</p>
|
||
|
||
</section> |