Formpipe uses cookies to improve how the website works for you as a visitor. To change your settings or for more information about cookies, click on 'Settings'.
Formpipe uses cookies to improve how the website works for you as a visitor. Here you can change and see information about what cookies are used. Turn on and off categories and save your choice. To learn more click 'Cookie policy'.
These cookies are essential for the website to operate correctly and cannot be disabled without ruining the usability of the website. We delete these cookies when you leave the website, where possible.
Name | Retention period | Information about the cookie | Disclosure of information to third party |
ASP.NET_SessionId | Used to maintain an anonymised user session by the server. | 1 session | No. |
cookie-consent-settings | Used to determine if the user has accepted the cookie consent, contains consent choises | 30 days | No. |
lidc | To promote data center selection | 1 day | Yes, LinkedIn |
li_mc | Used as a temporary cache to avoid database lookups for a member's consent for use of non-essential cookies and used for having consent information on the client side to enforce consent on the client side | 2 years | Yes, LinkedIn |
BIGipServer~EPWS~EPWSWEB103_HTTP_Pool | Determine pool | 1 session | Yes, EPiServer |
These cookies are used to track our visitors across our website. They can be used to build up a profile of search and/or browsing history for every visitor, or to better understand how the user uses the website so that we can improve it. Identifiable or unique data may be collected. Anonymized data may be shared with third parties.
Name | Information about the cookie | Retention period | Disclosure of information to third party |
_fbp | Used by Facebook | 90 days | Yes, Facebook |
AnalyticsSyncHistory | Used by LinkedIn | 30 days | Yes, LinkedIn |
bcookie | browser identification | 2 years | Yes, LinkedIn |
lang | Language preference | 1 session | Yes, LinkedIn |
li_gc | Used to store guests' consent to the use of cookies for non-essential purposes | 2 Years | Yes, linkedIn |
lms_analytics | Used to identify LinkedIn Members in the Designated Countries for analytics | 30 days | Yes, LinkedIn |
_guid | Used to identify a LinkedIn Member for advertising through Google Ads | 30 days | Yes, LinkedIn |
_ga | Used by Google Analytics to identify a visit. | 2 years | Yes, Google gains access to the information collected by the cookie. |
_gid | Used by Google Analytics to identify a visit. | 24 hours | Yes, Google gains access to the information collected by the cookie. |
_gat_gtag_[Property-ID] | Used by Google Analytics to identify if a visitor (web browser) is new or recurrent. | 1 minute | Yes, Google gains access to the information collected by the cookie. |
These cookies are used by third party to track and collect data to be used in advertisment. They can be used to build up a search and/or browsing history for every visitor. Identifiable or unique data may be collected.
Name | Information about the cookie | Retention period | Disclosure of information to third party |
ajn | Used by adnxs for marketing | 90 days | Yes, adnxs |
uuid2 | Used by adnxs for marketing | 90 days | Yes, adnxs |
IDE | Used by Google doubelclick | 2 years | Yes, doubleclick |
_gcl_au | Google adsense | 30 days | Yes, Google |
msd365mkttr | Dynamics marketing | 2 years | Yes, Microsoft |
NID | Google ads optimization | 6 months | Yes, Google |
__Secure-3PAPISID | Builds a profile of website visitor interests | 2 years | Yes, Google |
__Secure-3PAPISID | Builds a profile of website visitor interests | 2 years | Yes, Google |
__Secure-3PAPISID | Builds a profile of website visitor interests | 1 year | Yes, Google |
UserMatchHistory | Sync LinkedIn Ads ID | 30 days | Yes, LinkedIn |
lms_ads | Used to identify LinkedIn Members off LinkedIn in the Designated Countries for advertising | 30 days | Yes, LinkedIn |
Support
Whether you're looking for some
assistance or further information
regarding your solution, we're here
to help. Yes, take me there!
Sweden
Headquarters, Stockholm
Formpipe Software AB
Sveavägen 168, Stockholm
Box 231 31, 104 35 Stockholm
SE – Sverige
Tel: +46 8 555 290 60
Email
Linköping
Gasverksgränd 2, 582 22 Linköping
Tel: +46 8 500 072 25
Email
Västerås
Metallverksgatan 6, 721 30 Västerås
Örebro
Engelbrektsgatan 6, 702 12 Örebro
Denmark
Lautrupvang 1
2750 Ballerup
Tel: +45 3325 6555
Email
Germany
Formpipe Lasernet GmbH
THE SQUAIRE 12
Am Flughafen
60549 Frankfurt am Main
Email
UK, Cambridge
First Floor, Block A, Harston Mill,
Cambridge – CB22 7GG
Tel: +44 1223 872747
Email
UK, Nottingham
Unit 1, Isaac Newton Centre
Nottingham Science Park
Nottingham – NG7 2RH
Tel: +44 115 924 8475
Email
USA
Formpipe, inc.
1200 US Highway 22 E Suite 2000
Bridgewater, NJ 08807
Tel : +1 908 200 7937
Email
If your company collects personal data, you’ll be aware of the data privacy laws you’re required to follow. Don’t, and you risk the penalties that come with non-compliance. No matter where you are in the world, regulations likely include guidelines around data residency. We’re keen to help you meet your data residency requirements when you use Formpipe Cloud. But before we dive into how we do this, let’s explore what data residency is and why it is essential to get it right.
Data residency is the geographic location of an organisation’s data. It plays a key part in data privacy legislation, which details how organisations control and secure data stored across several countries or regions.
Conversations around data residency can get confusing, as several key terms are used interchangeably when they actually have important nuances. Before we move forward, let’s discuss the meaning of the terms data residency, data sovereignty, and data localisation. While data residency refers to the location of the data, data sovereignty refers to the laws and regulations that govern data based on its location. Data localisation, on the other hand, is the requirement that data created in a specific location must stay in that location.
Now that we’ve defined the key terms on this topic let's focus on the matter at hand: data residency. Taking data residency into account is business-critical for many reasons. For example, not knowing your data’s residency makes it difficult for you to assess your organisation’s risk. A lack of awareness may also mean you are unable to provide additional protections for your customers, such as following best practices and implementing the correct security procedures.
Generally, organisations carefully consider the matter of data residency for the following reasons:
Document management solutions tend to handle sensitive information subject to data residency laws, such as GDPR for companies within the European Union (or handling the data of EU citizens), which dictate where documents must physically reside. Companies choose data storage solutions to reduce the risk of non-compliance, which could result in large fines and significant reputational damage.
Knowing where your data resides allows you to also stay compliant with the relevant security regulations. For example, some countries, such as Germany and Switzerland, have strict laws around encryption. Storing your data in these locations can help you tick the right boxes when it comes to security requirements, showing your customers you take security seriously.
But legal compliance and security aren’t the only reasons to consider data residency. People are increasingly concerned about where their data is stored and how it is protected, expecting more data transparency from companies that use their data. To build trust with their customers, more companies are choosing to store data in specific locations to show commitment to user privacy and country-specific legislation.
Additionally, companies operating internationally may use several data centres in different locations to appeal to a wider customer base, especially those with strict data residency laws, such as Switzerland and the UAE.
Different countries have different regulations regarding data residency. For example, countries such as Switzerland and the United Arab Emirates have particularly strict data laws:
Switzerland has a strong reputation for financial services, partly due to its strong data protection laws. The Revised Federal Act on Data Protection (revFADP), which came into force on September 1st 2023, replaced the original FADP laws introduced in 1992. The revFACP was introduced to strengthen regulations due to technological advancements that have occurred since 1992, ensuring data protection in Switzerland harmonises with the GDPR requirements.
Although there is no general requirement to keep personal data stored in Switzerland, some sectors, such as finance, have to abide by much more stringent regulations. For example, the revFADP restricts cross-border transfers to countries that do not have an adequate level of data protection.
Additionally, certain types of sensitive data (such as financial and health data) may be subject to storage restrictions. Companies operating in Switzerland or handling the data of Swiss citizens must understand the sector-specific data residency requirements.
The United Arab Emirates strengthened its data protection laws in recent years. The Personal Data Protection Law came into force in January 2022. Drafted in partnership with major technology companies in the private sector, it emphasises transparency, fairness and legality in handling personal data.
The law allows for cross-border data transfers to countries with adequate levels of data protection, similar to legislation in the UAE. But that’s not all—data transfers to countries with different or no data protection legislation are also permitted, but only through signing agreements with foreign institutions and companies to comply with the UAE personal data protection law.
These two examples shine a light on why companies must take data residency into account, as building trust with customers and staying on the right side of the law in different jurisdictions are business-critical. Companies doing business in Switzerland, the UAE or other countries with strict data protection laws will find it much easier to comply with data residency regulations if they store data on residents within data centres located in those countries.
At Formpipe, we’re keen to help you meet data residency requirements. That’s why Formpipe Cloud, our document generation, delivery and archiving cloud solution, is hosted on Microsoft Azure.
Microsoft Azure organises data centres into designated market areas called geographies. Geographies typically span one or more data centres and are created to help users ensure data residency compliance. But that’s not all—Azure also allows data to be replicated across multiple regions. These regions serve as the primary location, your data’s residency, and secondary locations, which act as backups. If you’re interested, you can learn more about Azure geographies here.
Transparency is a big thing for us at Formpipe—it informs what we do and how we do it. Just as we created our cloud monitoring solution to give our customers more transparency, we believe you should know exactly where your data resides.
Formpipe Cloud provides next-level document generation, delivery and archiving through the cloud. If you want to move away from clunky legacy systems and spend more time focusing on your core business rather than infrastructure, Formpipe Cloud is the solution. There’s no need to worry about issues around data residency, because through Microsoft Azure, Formpipe Cloud is hosted in your chosen geography to make sure you meet the relevant regulations.
Please contact us to learn more about Formpipe Cloud. Alternatively, if you’d like to see Formpipe Cloud in action, book a live demo below to see the true value of our document generation, delivery and archiving solution.