Nicepage

What Nicepage is

Nicepage is a website builder available both as a desktop application and as a cloud based online editor. It lets users design and publish websites visually, exporting to formats such as HTML, WordPress and other platforms. The editor account and the online builder are cloud hosted, with infrastructure linked to the United States and Ukraine. Importantly, the compliance profile of a Nicepage project depends less on the builder and more on what the published site ends up loading for its visitors.

What data and cookies it collects

Generated Nicepage sites can load Google Fonts, Google Analytics and Google Tag Manager, which set analytics and sometimes advertising cookies and can contact Google servers on every page view. When the site owner enters a Google Analytics identifier, the analytics cookies track visitor behaviour, and loading fonts from Google can expose visitor IP addresses to Google. Nicepage also offers a cookie popup and the option to self host fonts, which lets a site run with no non essential cookies at all. The builder account itself processes the user account data of the person designing the site.

GDPR and ePrivacy implications

Under Art. 5(3) of the ePrivacy Directive, any analytics or advertising cookie set by a generated site requires prior consent. Loading Google Fonts directly from Google servers has been treated by some European courts as a transfer of the visitor IP address that needs a lawful basis, which is why self hosting fonts is the safer pattern. Processing of visitor data through analytics rests on consent under Art. 6(1) GDPR, with the site owner acting as controller. The builder vendor acts as a processor for the account data, so a data processing agreement applies there.

Consent requirements

If your published site uses Google Analytics, Tag Manager or any advertising tag, you must obtain consent before those scripts run and before their cookies are set. The Nicepage cookie popup should be configured to block non essential scripts until the visitor agrees, not merely to display a notice. Consent must be specific, informed and as easy to withdraw as to give. A site that self hosts fonts and uses no analytics can avoid the need for cookie consent entirely.

International data transfers

The Nicepage editor account and online builder are cloud hosted with infrastructure linked to the United States and Ukraine, both third countries under the GDPR, so account data may be processed outside the EEA under Standard Contractual Clauses. On the public site, loading Google Fonts, Google Analytics or Tag Manager can transfer visitor data to Google in the United States, covered by the EU to US Data Privacy Framework. Self hosting fonts and disabling analytics removes these transfers and keeps visitor data within your own hosting. A transfer impact assessment should document any remaining flows.

Practical compliance steps

Decide early whether your site really needs analytics, and if not, self host fonts and skip Google scripts to keep the site cookieless. If you do use analytics, enable the Nicepage cookie popup in a mode that blocks scripts until consent is given, and document the legal basis. Review the third party domains your published site contacts and record the Data Privacy Framework or Standard Contractual Clauses for any US transfer. Finally, sign a data processing agreement with Nicepage for the builder account and update your privacy and cookie policies to match what the live site actually loads.