| Thank you for Signing Up |


WPEngine is one of the largest managed WordPress hosts in the world, with customers in more than 130 countries. The company’s headquarters are in Austin, Texas. We originally wrote this article in 2023 and have updated it to reflect important legal developments since then.
As a host that specializes in WordPress, WPEngine is the preferred choice among WordPress developers and marketing agencies because the framework includes a range of modern development environments and security features. Additionally, the 24-hour support team consists of trained WordPress experts with developer experience, who are known to have the necessary tools and knowledge to quickly resolve even more complex issues for their clients.
To meet the needs of the highly marketing-focused U.S. market, WPEngine is also known as a web host that adapts to new technologies early and offers corresponding server configurations. In particular, the focus on SEA/SEM/SEO and online marketing tools is extraordinary.
The success of the company is largely due to the fact that it primarily targets agencies, service providers, and B2B companies worldwide, rather than direct consumers. This target audience generally wants to offer a WordPress framework while leaving the technical responsibility to WPEngine and performing administration through a simple, secure, and easily understandable interface. The one-click procedures offered for securing, restoring, and managing multiple staging systems make WPEngine extremely attractive to developers and software companies. In Germany, for example, staging systems were long rather uncommon, as Germany is considered somewhat conservative in terms of software development. The open-source movement of the late 90s was only accepted in Germany many years later, and concepts such as Agile/Scrum only became widely known much later. It was only 10 years after WordPress’s big breakthrough that it began to be recognized as a professional CMS in Germany.
Over the years, WPEngine has established itself as a unique player in the U.S., competing with large mass-market providers such as GoDaddy and Bluehost, as well as with Automattic’s WordPress.com.
In September 2024, WPEngine became involved in a high-profile legal dispute with Automattic and WordPress co-founder Matt Mullenweg, who temporarily blocked WPEngine from WordPress.org resources such as plugin updates. In December 2024, a U.S. court granted WPEngine a preliminary injunction that restored its access. If you are considering WPEngine, it’s worth checking the current status of this dispute.
WPEngine and GDPR
When it comes to helping with and fulfilling GDPR compliance documents related to GDPR, WPEngine is not well-liked especially in the German sector, and is therefore viewed negatively by many Data Privacy Officers and German lawyers.
WPEngine is not alone in this, as Germany in general is known for viewing numerous products and services from the U.S. market with skepticism.
This is because, like many other U.S. companies, WPEngine is known for not meeting the GDPR requirements of German companies, and also not making separate efforts to convince skeptical German data protection experts.
It is not unusual for companies to ignore Germany as a sales market due to strong privacy debates. Although the German market is one of the largest in Europe, U.S. companies with global growth strategies have decided to disregard the German market, if privacy rules seem too cumbersome, impractical, or even harmful to them. Google Street View is a good example: Google didn’t update its Street View images in Germany for more than a decade and only resumed in 2023.
This behavior was not unusual and is understandable. For example, many U.S. companies, especially smaller ones, have been reluctant to sign complex, individually negotiated data processing agreements (DPAs). When looking more closely at the content of a DPA required by subcontractors in the EU, U.S companies see a number of obligations that they are not willing to take on. DPAs often require U.S companies to provide cryptically sounding GDPR concepts such as deletion concepts, the right to be forgotten, correction, data portability and information at the documented instruction of the controller upon request. Moreover, a DPA requires U.S companies to obligate their employees to confidentiality within the framework of GDPR and to familiarize them with the data protection provisions according to GDPR. It is understandable that a U.S company sees no sense in familiarizing its employees with foreign laws. This would be similar to a Chinese company expecting a German service provider to train its German employees in Chinese laws.
Furthermore, the American company is required not only to establish but also to regularly record GDPR-compliant control and security measures, to disclose them immediately upon request, and also to work together free of charge with German authorities.
From an American perspective, such contracts can sound absurd and unrealistic, and many smaller U.S. companies have not built up the resources to meet such culturally foreign demands. Large U.S. providers such as Amazon Web Services (AWS), Google, and Microsoft, on the other hand, have long offered standardized GDPR-compliant DPAs.
This is not helpful for companies that want to benefit from modern WordPress infrastructure, as long as the widespread opinion in Germany is that WPEngine is not GDPR-compliant.
For this reason, many German companies resort to alternative systems, which, however, are not even remotely comparable in terms of functionality, efficiency, simplicity, and above all server speed with the modern infrastructure of WPEngine.
As WPEngine gained more market share, the company found itself under increasing scrutiny from German data protection experts.
Therefore, in this article, we will take a closer look at WPEngine’s data protection provisions and offer assistance to make WPEngine usable for German companies despite GDPR.
Server Location
To avoid the discussion that the WordPress server is located outside the EU, we generally recommend choosing a German server. When creating a WPEngine account, the user has the option to determine the server location. In the German region, for example, WPEngine offers a server in Frankfurt, which can be identified as a Frankfurt server by the IP in the A-record, which is managed by Google Cloud.
Data Processing Agreement (DPA)
When we first researched this topic in 2023, WPEngine was not willing to sign individually negotiated DPAs, and a request to its legal team did not lead to a positive result.
Today, WPEngine provides a standardized Data Privacy Addendum that forms part of its customer agreement and includes the EU Standard Contractual Clauses for international data transfers. In addition, since July 2023, the EU-U.S. Data Privacy Framework has provided a new legal basis for transferring personal data to certified U.S. companies. Whether this satisfies your data protection officer is a different question, so we recommend reviewing the current documents with them.
If your data protection officer insists on an individually signed DPA, an alternative is to contract an external company for WordPress hosting. That company concludes a DPA with you and then commissions WPEngine as the web host.
It is problematic for Germans that https://wpengine.com/legal/privacy/ states that WPEngine stores web server logs. This means that despite an existing DPA and a server location in Germany, the U.S.-based company WPEngine may still have access to the IP addresses of website visitors.
The only glimmer of hope remains that ultimately, outsiders cannot tell who is storing what or whether anything is being stored at all. Because looking at only a Frankfurt IP address, it is not readily apparent that it belongs to WPEngine.
It is also not possible to determine whether WPEngine actually collects these IP addresses from the Frankfurt server or accesses them from the U.S. Due to WPEngine’s international presence, it is not possible to determine or prove that WPEngine accesses the IP addresses of German website visitors without their clear consent. And WPEngine is honest in stating that it may access such data.
Basically, the choice of WPEngine with a Frankfurt server may possibly protect against legal issues from German authorities and data protection agencies that file lawsuits against German companies, as traceability and provability are not given, provided that the server location is selected as Frankfurt. WPEngine’s statement that they generally allow access to IP addresses may not be clearly resolved in court in case of doubt, unless clear and verifiable evidence is presented that the access actually takes place from the U.S.
However, it is also understandable that this is a worrying situation for German Data Privacy Officers. After all, it is not the goal of data protection experts to rely on risks and gray areas or to base their decisions on existing non-provability.
Ultimately, the proof of whether and how data is collected from the U.S. is lacking. In case of doubt and in the event that WPEngine should make the headlines, however, this fact does not protect against an unpleasant lawsuit and a possible dispute with the suing party about what is provable and what is not. If German companies choose WPEngine as their web host and accept that risk, they will probably have to live by the saying: “We’ll cross that bridge when we get there.”
Personal Data at WPEngine
For those who run a website using WPEngine under the GDPR jurisdiction, it is essential to consider where personal data is stored within the WordPress install. While the server location at WPEngine might be Europe, especially German data protection experts argue that ultimately it is a U.S. company that has access to this data at any time.
To avoid this issue, it may be helpful to not store any data on the server and instead send contact inquiries and store data directly through a secure email connection. If no personal data is stored on the server, the GDPR becomes much less of an issue.
However, the only remaining disadvantage is the IP address of website visitors, which can still be stored in WPEngine’s logs. From the perspective of German data privacy authorities, this argument could still make WPEngine problematic from a data privacy standpoint.
Alternative Solutions using WPEngine
Headless WordPress
Another way to use WPEngine while complying with the European data privacy regulations is to operate a headless WordPress. With a headless WordPress, WordPress is hosted on WPEngine, but the website is mirrored on a European server.
Here’s how it works: WordPress is typically hosted on WPEngine, but the domain and URL are hosted on a different framework, such as a European server that complies with data protection regulations. Users then access the European server, where their IPs are stored without WPEngine having access to it. When users access the site, the content is loaded from the WPEngine server via REST URL or REST API.
This method is more complex, as it requires managing two servers and using frontend frameworks such as Next.js or WPEngine’s Faust.js. WPEngine also offers its own headless WordPress platform (originally called “Atlas”).
Static HTML
In conjunction with the headless methodology, it is possible to create websites as static HTML. Again, the entire website would still be hosted on WPEngine, but with the use of a headless WordPress framework, all data is created as pure HTML on a European server. Users then access the German server, where all data is stored, while WPEngine only delivers the data.
This concept also provides a significant speed advantage, as the entire website would be then loaded via HTML.
In the case mentioned above, however, a separation is necessary: HTML must be created on a European server. This methodology requires a somewhat more complex configuration, where two servers must be used. Again, headless WordPress frameworks or static site generators are necessary.
Host Alternatives to WPEngine
In our opinion, there is currently no real alternative to WPEngine in the European market. The company’s size and functionality are far ahead of its European counterparts. WPEngine offers collaboration between staging, development, and production, one-click backups for all three levels, and an advanced permission management system for developers, as well as a strong support infrastructure and a competitive price, making it a leading global provider.
European companies that want to use WPEngine must therefore use complex workarounds if data privacy is a stumbling block to their business objectives.
However, if you have to avoid WPEngine entirely, it is best to outsource the two main functions of WPEngine: staging and WordPress management. We recommend that European companies use another service provider to cover the staging level, especially if the website is development-driven.
HostEurope as a WordPress host
HostEurope’s Supreme package promises daily backups with a one-click restore, one-click staging, and 24-hour support. However, it is not to be assumed that the support has dedicated WordPress hosting experience, as WordPress is generally just one of many hosting packages offered and not their sole focus.
HostEurope is recommended by many data privacy officers, but it is owned by a U.S. company (GoDaddy), which makes it contradictory that WPEngine is considered problematic due to potential access to its European server (as described above) and HostEurope is deemed to be compliant with data privacy regulations. In both cases, U.S. companies have the ability to access IP log files.
In our experience, data privacy officers have different opinions and preferences that do not always align with GDPR. Unfortunately, I have often encountered data privacy officers who act according to the principle of confirmation bias, interpreting things in a way that fulfills their own personal expectations.
Many U.S. service providers therefore are now inclined to cease working with companies that are overly burdened with data privacy tasks.
Ionos (1&1) as a WordPress Host:
Ionos (formerly known as 1&1) offers WordPress hosting packages that include daily backups with 1-click restore, 1-click staging, and 24/7 support. However, it is not certain that their support team has specific experience with WordPress hosting since the company offers a variety of hosting packages beyond WordPress. Nevertheless, many data protection officers recommend Ionos (1&1) as a host. Ionos (1&1) is a German company and not a U.S. one, and therefore there is no concern about access to IP logs by American companies.
Raidboxes as a WordPress Host (not recommended):
Note: The following assessments of Raidboxes, WP Space, WP-Projects, and HostPress are based on our own experience when we wrote this article in 2023. Their offerings may have changed since then.
Although the company is known for complying with GDPR regulations, our personal experience with Raidboxes showed that their dashboard is underdeveloped and has many weaknesses. Additionally, the company is relatively small compared to giants like GoDaddy (HostEurope), and their support team left an unprofessional impression. Data losses and system failures seem to be commonplace.
WP Space as a WordPress Host (not recommended):
Unfortunately, WP Space does not offer 24/7 support, and the company’s size is unclear. It is assumed that WP Space is a small business. The functionality of their advertised staging environment is also unclear.
WP-Projects as a WordPress Host (not recommended):
WP-Projects did not offer 30-day backups, 1-click backup/restore, staging environments, or support. Additionally, their website listed neither their location nor their headquarters, making it difficult to identify the company behind it.
HostPress as a WordPress Host (not recommended):
One of the key players in the hosting market is HostPress, known for offering what initially appears to be a reliable dashboard with a daily backup feature. However, upon closer inspection, their backup approach reveals significant shortcomings. HostPress’s daily backup only covered the database, not the entire WordPress environment, including FTP data.
A full backup, including FTP data such as uploaded media (images, videos, and other files), was only performed every 14 days. This approach poses a serious risk: in the event of a complete data loss, any media uploaded in the 14 days prior to the last full backup could be permanently lost. This represents a critical vulnerability and highlights a fundamental flaw in HostPress’s disaster recovery and business continuity strategy. Such a backup plan is inadequate and fails to meet the standards expected for effective disaster recovery, where comprehensive and frequent backups are essential for minimizing data loss.
Germany’s Technological Challenges
As previously mentioned, in our opinion, no provider in Germany can offer the security and environment for WordPress that WPEngine does. This is due to the demanding requirements of a WordPress environment. One reason for this is Germany’s significant lag—by about 15 years—behind global technological advancements. While the USA leads the way, followed by Japan, Singapore, Sweden, the UK, South Korea, and China, Germany is struggling to catch up. The strict GDPR regulations further complicate matters, making it even more challenging for German companies to innovate in today’s highly competitive global landscape.
| Thank you for Signing Up |


by
Hello Dr. William Sen,
the article is really well done and i do totally share your experience, Germany is very much behind.
Anyway, lots of Wordpress hosting solutions aren't the high price worth. A professional maybe not have many benefits using it. I see the biggest advantage with intrgrated backup solutions, they still work even the site is down. But I prefer to fix iz with the shell, it won't take me a lot more time :)