Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
Zeta Producer is a German desktop website builder and CMS that publishes static HTML sites with no built in tracking, making privacy compliant websites straightforward.
Zeta Producer is a desktop content management system developed by the German company Zeta Software GmbH. It runs locally on the operator computer and generates static HTML, CSS and JavaScript files that are uploaded to a web server. Because the published output is static, the platform itself does not run server side tracking or collect visitor data.
For a European audience this is significant: a site built with Zeta Producer starts from a privacy friendly baseline, and any data processing is introduced only when the operator chooses to add external services such as analytics, fonts or embedded media.
By default a static Zeta Producer website sets no cookies and collects no personal data beyond the server access logs that any web host records. The optional cookie consent widget shipped with the software may store a small preference cookie that remembers a visitor choice, and that cookie is strictly necessary and does not track behaviour.
Cookies and personal data appear only when the operator adds third party components, for example Google Analytics, Google Fonts loaded from a remote server, or embedded YouTube and Vimeo videos. Each of those components brings its own cookies, identifiers and data flows that must be assessed separately.
Under the GDPR, the operator of the published website is the data controller. Zeta Producer as a local tool is not a processor of visitor data, since it never receives that data. The strictly necessary preference cookie used by the consent widget falls under the exemption in Article 5(3) of the ePrivacy Directive and does not require consent.
As soon as the operator adds analytics or marketing cookies, those storage operations require prior consent under Article 5(3) of the ePrivacy Directive, and the related processing needs a valid legal basis under Article 6 of the GDPR.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
No consent is required for a plain static site that uses only the strictly necessary preference cookie. Consent becomes mandatory when the operator activates optional cookies or loads external content. In that case the consent must be freely given, specific, informed and unambiguous, and visitors must be able to refuse as easily as they accept.
Zeta Producer itself transfers no visitor data outside the European Economic Area. Transfers arise only from third party services the operator chooses to embed. Where such services route data to the United States or other third countries, the operator must rely on an appropriate transfer mechanism such as the EU US Data Privacy Framework or standard contractual clauses.
Keep the published site lean: host fonts locally, avoid unnecessary external embeds, and use the built in consent widget to gate any optional cookies. Maintain an accurate cookie policy and privacy notice, document the legal basis for every component you add, and review the site whenever you introduce new third party services.
Websites using Zeta Producer must obtain user consent under GDPR regulations.
DPIA considerations
A data protection impact assessment is generally not required for Zeta Producer itself, since the desktop software publishes static pages and processes no visitor data. A DPIA may become relevant only if the operator adds high risk components such as large scale analytics, profiling or third country transfers through external services embedded in the published site.
Sample consent text
This website uses only strictly necessary cookies required for its basic operation. Optional cookies for analytics or embedded media are set only after you give your consent. You can change or withdraw your choice at any time in the cookie settings.
Third-party domains contacted
zeta-producer.comgoogle-analytics.comfonts.googleapis.comyoutube-nocookie.comCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| cookie_consent | Strictly necessary | 12 months | Stores the visitor cookie consent choice set through the built in consent widget so it does not reappear on every visit. |
| PHPSESSID | Strictly necessary | Session | Server side session cookie that may be set by the hosting environment for dynamic features; identifies the session and contains no tracking data. |
| _ga | Analytics | 2 years | Only present if the operator adds Google Analytics. Stores a randomly generated client identifier used to distinguish visitors. Requires prior consent. |
| YSC | Marketing | Session | Only present if the operator embeds YouTube videos. Set by YouTube to remember user interactions with the embedded player. Requires prior consent. |
Zeta Producer collects user analytics data — you legally need a consent banner. Try FlowConsent free.
A static site published with Zeta Producer sets no tracking cookies by default. The only cookie that may appear is a strictly necessary preference cookie from the optional consent widget, which remembers a visitor cookie choice. Any further cookies come from external services the operator adds.
No consent is needed for a plain Zeta Producer site that uses only the strictly necessary preference cookie. Consent becomes required as soon as the operator activates optional analytics or marketing cookies, or embeds external media that sets cookies.
For strictly necessary operation the legal basis is the operator legitimate interest under Article 6(1)(f) of the GDPR. Any optional cookies or external content require consent under Article 6(1)(a) of the GDPR together with Article 5(3) of the ePrivacy Directive.
Zeta Producer itself does not transfer visitor data abroad, since it publishes static files locally. Transfers to the United States or other third countries only occur through external services the operator embeds, such as Google Analytics or hosted fonts.
A data protection impact assessment is normally not required for Zeta Producer itself because it processes no visitor data. A DPIA may be needed if the operator adds high risk processing, such as large scale analytics, profiling or systematic third country transfers, through embedded services.
Keep the published site lean, host fonts locally, and gate every optional cookie behind the consent widget. Publish an accurate cookie policy and privacy notice, document the legal basis for each component, and review the site whenever you add a new third party service.
Comparable privacy friendly static site tools include WordPress with static export, Hugo, Jekyll and other static site generators. The compliance advantage of any static approach is that the build tool processes no visitor data and the published site starts from a clean baseline.
List the strictly necessary preference cookie and every cookie introduced by services you embed, with their purpose and duration. Update the policy whenever you add or remove a component, and make sure the consent widget reflects the current set of optional cookies.