Peachie

In its default configuration Peachie writes a session cookie, a CSRF token and a small cache marker on the published site. The editor itself also sets cookies for the signed in operator session. None of these cookies track visitors across domains and none are written for advertising purposes. They fall under the strictly necessary exemption and do not require prior consent.

Only if you activate non essential trackers. A vanilla Peachie site uses only strictly necessary cookies and can publish a cookie policy without a banner. Enabling Google Analytics, Meta Pixel, Hotjar or any social media embed turns those trackers into non essential cookies and triggers the obligation to deploy a Consent Management Platform with opt in.

Article 6(1)(b) GDPR (performance of the service contract) covers the editor and the publication of pages. Article 6(1)(f) GDPR (legitimate interest) covers the aggregated analytics displayed in the Peachie dashboard. Forms submitted by visitors collect data under the operator privacy notice, typically consent for newsletters and contract performance for service requests.

No transfer outside the EEA takes place in the default configuration. The CMS and the assets live on European cloud regions. A CDN may serve cached static files from edge locations worldwide but the origin remains in the EU and no personal data is stored at the edge. Operators who add a US analytics tool, payment processor or newsletter platform have to document those downstream transfers themselves.

A DPIA is generally not required for a brochure site, a blog or a simple lead form. A DPIA becomes relevant when the operator adds large scale visitor profiling, an ecommerce checkout that combines payment, identity and behavioural data, or a member area handling sensitive content. The Peachie usage itself remains low risk and infrastructure level.

Sign the Data Processing Agreement Peachie offers and list the platform in the record of processing. Publish the privacy and cookie policies as Peachie pages. Use the native form blocks instead of embedding third party forms for low risk lead capture. Only add a cookie banner when you switch on a non essential integration and map every enabled integration to its lawful basis.

Direct alternatives include Webflow, Squarespace, Wix, Strikingly and Carrd. EU oriented builders include Pixpa, SimpleSite, Jimdo and Hostinger Website Builder. Open source options include Webstudio, Plasmic and headless stacks built on Payload CMS, Strapi or Ghost. Choose based on hosting region, design freedom and the depth of integrations you need.

List each new tracker that the integration introduces, with name, purpose, retention and third party. Update the lawful basis (consent for all non essential cookies), the transfer information (especially for US tools) and the privacy notice. Republish the cookie policy through Peachie, refresh the Consent Management Platform configuration and rerun a cookie scanner to verify the inventory.