Privacy and cookies policy of WPPoland.com
This Privacy Policy explains how WPPoland processes personal data of users of wppoland.com, the contact form, and related communication channels.
At a glance (information under Article 13 GDPR)
- Controller: Mariusz Szatkowski, WPPoland Mariusz Szatkowski, ul. Starowiejska 16/2, 81-356 Gdynia, Poland, email: [email protected]. The controller has not appointed a data protection officer because the conditions of Article 37 GDPR are not met; data matters are handled by the controller personally.
- Purposes: answering your enquiry and preparing a quote, performing the contract, handling consumer withdrawal statements, invoicing and tax duties, website security, defending legal claims. Legal bases are in §3.
- Recipients: the providers the website and correspondence cannot run without (hosting, email, form handling, bot protection), bound by data processing agreements or acting as separate controllers (§5). Details and transfers outside the EEA: §5 and §6.
- Retention: for as long as the enquiry or contract is handled, then until claims are time-barred and for the period tax law requires (§7).
- Your rights: access, rectification, erasure, restriction, portability, objection, and a complaint to the Polish authority (UODO) or the authority where you live, in the UK the ICO and in Ireland the Data Protection Commission (§8).
- Is it required: no, but without an email address your enquiry cannot be answered. The controller makes no automated decisions and does no profiling.
§1. Data controller and contact
The data controller is Mariusz Szatkowski, operating as WPPoland Mariusz Szatkowski, ul. Starowiejska 16/2, 81-356 Gdynia, Poland, Tax ID (NIP): 7393037445.
Contact for privacy matters:
- e-mail: [email protected]
- postal address: WPPoland Mariusz Szatkowski, ul. Starowiejska 16/2, 81-356 Gdynia, Poland
§2. Scope and definitions
- This policy applies to users of
wppoland.comin all language versions. - Definitions:
- Service: the website
wppoland.com. - User: a natural person using the Service or contacting the Controller.
- GDPR: Regulation (EU) 2016/679.
- Service: the website
§3. Purposes and legal bases
I process personal data only where I have a legal basis:
- Contact and handling inquiries (form/e-mail):
- Art. 6(1)(b) GDPR (steps prior to entering into a contract),
- Art. 6(1)(f) GDPR (legitimate interest: communication and inquiry handling).
- Performance of a contract with the Client (carrying out the work, communication during the engagement, invoicing under the contract):
- Art. 6(1)(b) GDPR.
- Handling consumer statements of withdrawal and consent to start a service before the withdrawal period ends (forms on the Service):
- Art. 6(1)(c) GDPR (legal obligation under consumer law).
- Security and stability of the Service (logs, abuse protection, form verification by Cloudflare Turnstile):
- Art. 6(1)(f) GDPR.
- Traffic analytics and Service development:
- Art. 6(1)(f) GDPR (legitimate interest in traffic statistics). My first-party analytics is cookieless and collects no personal data: it records the event name, the page path and descriptive labels such as a CTA source or UTM campaign, with no IP address, name or e-mail address, and does not track you across sites. For funnel analysis (for example how many people start and finish the contact form) I additionally use PostHog in cookieless mode. PostHog receives your IP address with the request, uses it only to build an anonymous hash valid for one day and does not store it with the event. You can object by enabling a Do Not Track or Global Privacy Control signal in your browser: I then send no events to my own analytics or to PostHog. Details in §6, §7 and §9.
- Embedded YouTube videos and Google Maps:
- Art. 6(1)(a) GDPR (your consent, given in the cookie settings or with the button next to the video; you can withdraw it at any time).
- Compliance with legal obligations (e.g., tax/accounting):
- Art. 6(1)(c) GDPR.
- Establishing, exercising, or defending legal claims:
- Art. 6(1)(f) GDPR.
§4. Categories of data
- Data provided by the User via form or e-mail, such as name, e-mail address, message content, and any other data submitted voluntarily.
- Automatically collected technical data: IP address, device type, operating system, browser, connection time, server logs, and cookie identifiers.
§5. Forms and processors
- The contact form, the quick estimate form and the download form send data to a server function of the Service running on Cloudflare, which forwards it by e-mail to the Controller through Resend (processor). Resend receives what you type into the form (e.g. name, e-mail address, message, project type, website address, timeline, budget) and data on where the visit came from (page paths, UTM parameters, campaign click ID). The Service stores no submissions in any database: they go only to the [email protected] mailbox. On submission, my first-party analytics records the enquiry reference number, the project type and the visit source, without your name, e-mail address or message. Resend privacy policy: https://resend.com/legal/privacy-policy.
- When Resend is unavailable, the same data are sent through Web3Forms. The withdrawal form and the consent-to-start form send their data (name, address, e-mail, order number, contract date, the statement itself) directly from your browser to Web3Forms. Web3Forms acts as a technical provider (processor or separate controller under its own terms). Web3Forms privacy policy: https://web3forms.com/privacy.
- Cloudflare Turnstile (Cloudflare, Inc.) checks that a person, not a bot, fills in the contact, quick estimate and download forms and the website check. It processes the IP address, browser data (e.g. user agent and TLS fingerprint) and the result of the check; my server function sends Cloudflare the verification token and the IP address. Cloudflare is a processor for protecting the forms and a separate controller for improving its bot detection. The legal basis is Art. 6(1)(f) GDPR (protection against spam and abuse). Turnstile privacy terms: https://www.cloudflare.com/turnstile-privacy-policy/.
- The Controller processes data received from the forms for the purposes described in this policy.
§6. Data recipients and transfers outside the EEA
- Recipients:
- Cloudflare, Inc. (USA): hosting and CDN, the form server functions, my first-party analytics, Cloudflare Web Analytics (cookieless page view and load time statistics) and Turnstile; processes IP addresses, request data and form data; processor (for Turnstile also a separate controller, §5).
- Resend (USA): sending form e-mails; processor.
- Web3Forms: fallback form delivery and the consumer forms; processor or separate controller.
- PostHog Inc. (USA, data stored in PostHog Cloud EU in Frankfurt): funnel analytics; processor. PostHog privacy policy: https://posthog.com/privacy.
- Google Ireland Limited and Google LLC (YouTube, Google Maps): embedded videos and city maps, loaded from
youtube-nocookie.comandgoogle.com/mapsonly after your consent. Google receives the IP address, browser data and which video is played, and acts as a separate controller. Google privacy policy: https://policies.google.com/privacy.
- Cloudflare, Resend, PostHog and Google LLC participate in the EU-U.S. Data Privacy Framework. Transfers to them in the USA rely on Commission Implementing Decision (EU) 2023/1795 on the adequate level of protection, and additionally on Standard Contractual Clauses (SCCs). Transfers to Web3Forms outside the EEA rely on Standard Contractual Clauses (SCCs).
- Data are disclosed to public authorities only where legally required.
§7. Retention periods
- Contact data: for the period necessary to handle an inquiry and follow-up communication, then for the limitation period for claims (typically up to 3 years unless a longer period is required by law).
- Data processed due to legal obligations (e.g., accounting/tax): for statutory retention periods (typically 5 years from the end of the relevant tax year).
- Analytics data: my first-party analytics stores no personal data (§3); you can opt out via a Do Not Track or Global Privacy Control signal. Events sent to PostHog, stored without the IP address, are kept for 1 year.
- Server logs and security data: for as long as necessary to ensure security and investigate incidents, typically no longer than 12 months unless needed longer for legal defense.
- Data processed under legitimate interest: until an effective objection is raised or the purpose ceases.
§8. User rights
Users have the right to:
- access personal data,
- rectify data,
- erase data,
- restrict processing,
- data portability (where applicable),
- object to processing based on Art. 6(1)(f) GDPR,
- withdraw consent at any time (without affecting lawfulness before withdrawal),
- lodge a complaint with a supervisory authority: the President of the Personal Data Protection Office (UODO) in Poland (ul. Stawki 2, 00-193 Warsaw), which is the lead authority for the Controller, or the authority where you live, in the UK the Information Commissioner’s Office (ICO) and in Ireland the Data Protection Commission.
Requests can be sent to: [email protected]. I respond without undue delay, usually within 1 month from receipt. For complex requests, the deadline may be extended by up to 2 additional months, and I will inform you of the reasons. I may request identity verification before completing a request.
§9. Cookies and similar technologies
- The Service uses:
- necessary cookies and browser storage (operation and security, theme switcher, your choice in the cookie settings),
- functional cookies (embedded YouTube videos and Google Maps, only with your consent, point 3).
- Analytics is first-party: the Service sends lightweight usage events to its own same-origin endpoint, which records only the event name, the page path, and declared properties (for example a CTA source). It is cookieless, stores no IP address, sets no tracking cookies, and does not track Users across sites. It runs under my legitimate interest, and events are not sent when the browser sends a Do Not Track or Global Privacy Control signal. Until you close the tab, the Service keeps the source of your visit (e.g. UTM parameters and landing page) in the browser’s session storage and attaches it to a form submission. The Cloudflare Web Analytics script measures page views and load times, also without cookies. In addition, the Service loads the PostHog script in cookieless mode: it stores no cookies and nothing in browser storage. To tell visits apart, PostHog computes a hash of the IP address and browser data on its servers with a salt that changes daily, then discards the IP address, so the same person cannot be recognised on a later day. It records page views, clicks and form steps, without the text typed into fields. Session recording is off. Do Not Track and Global Privacy Control signals also switch PostHog off.
- YouTube videos load from
youtube-nocookie.comonly after you turn on the Functional category in the cookie settings or click the button next to the video. City maps from Google Maps on city pages likewise load only after consent. Once a video or map loads, Google may store its own cookies or data in your browser. - Non-essential technologies are used based on User consent where required by law.
- Consent can be changed or withdrawn in cookie settings and browser settings.
§10. Security and incidents
- I apply technical and organizational safeguards appropriate to risk, including HTTPS, access control, and security monitoring.
- In case of a personal data breach, I act in accordance with GDPR, including notification to the supervisory authority where required (typically within 72 hours of becoming aware of the breach).
- I do not use solely automated decision-making, including profiling, that produces legal effects concerning users or similarly significantly affects them.
§11. Policy updates
- This policy may be updated due to legal, technological, or organizational changes.
- The current version is always available on
wppoland.com. - Material changes are communicated on the Service.
§12. Personal data on clients’ websites
When caring for a client’s website or shop, WPPoland may have access to personal data the client collects from its own users, for example orders, customer accounts and form messages. The client is the controller of that data. WPPoland processes it only on the client’s instructions, as a processor, under a data processing agreement signed before access is granted (Article 28 GDPR). The care terms, including what happens in a data breach, are in §17 of the terms and conditions. People whose data is held on a client’s website should send their requests to that client.
Legal notice
WPPoland Mariusz Szatkowski
ul. Starowiejska 16/2
81-356 Gdynia, Poland
E-mail: [email protected]
Image credits
The photographs of Mariusz Szatkowski used on this website were taken by Marta Weronika Pawłowska.



