Privacy policy

Last updated: 20 November 2026

Who is responsible

The controller of your personal data is BlueStork, Andromeda 7, 3225 VA Hellevoetsluis, the Netherlands(KvK 83369988). Questions about your data: support@maxitemplates.com.

In short

  • This site sets no cookies and loads no advertising pixel or script from Meta or Google. If you arrive by clicking one of our ads on Facebook or Instagram, our own server tells Meta about a few shop steps (see “Ad clicks from Meta” below). Campaign tags and Google ad click codes travel in page addresses and are attached to a purchase in Paddle; Google Ads downloads purchases with a Google click code once a day, without email addresses, names or IP addresses (see “Ad clicks from Google” below). We also keep daily totals of shop steps and campaign tags, without visitor identifiers. We do not save campaign tags in cookies or browser storage.
  • Our own pages store nothing in your browser.
  • Fonts and images load from this domain only.
  • The same applies to our services site, services.maxitemplates.com: it sets no cookies and has no form.

One exception applies to this shop, not to the template: our support and review forms run a bot check from Cloudflare, so those pages load one script from them. It sets no cookie. The checkout page (/checkout/) loads the payment form of Paddle, our reseller, from their servers (see below). Other shop assets load from this domain. Your purchased configurator works offline; its optional version check and the Update button contact maxitemplates.com as described below.

Visiting the site

The site is hosted by Cloudflare. To deliver pages and protect them against attacks, Cloudflare processes technical data of each request, such as your IP address, the address requested, and your browser’s User-Agent. Cloudflare acts as our processor. Legal basis: our legitimate interest in running a secure website (Art. 6(1)(f) GDPR).

Social media links

The footer on this site and our services site links to MaxiTemplates profiles on Instagram and Facebook. The icons are part of our own website. Until you click a social media link, nothing is loaded from or sent to Meta, and these links set no cookies. After you click, Meta’s privacy policy applies on their sites.

Daily shop step counts

On maxitemplates.com, our own small script counts a template page opened with campaign tags, clicks on its live demo and trial configurator links, and checkout page opens for a known template. Configurator link clicks from a template page and from a live demo are counted separately. Opening a trial configurator is counted once per page view, with or without campaign tags; changing settings or refreshing its preview does not count another opening. Live demos also count opens with campaign tags and clicks on their buy links. For template pages opened with campaign tags it also counts how far the page was scrolled (25, 50, 75 and 100 %), whether it stayed visible for 15 and 60 seconds, and whether a live demo or configurator button appeared on screen — each at most once per page view. These are step counts, not unique visitors or completed purchases. A click does not confirm that the demo or configurator opened; configurator openings are counted as a separate step. The About page also counts each page view and 15 and 60 seconds of visible time, once per page view, with or without campaign tags. These steps use shop in place of a template name and are not sent to Meta. Guide pages (/docs/) count the same way — each page view and 15 and 60 seconds of visible time, once per page view; these steps use docs in place of a template name, record which guide was opened instead of a campaign content tag, and are not sent to Meta. The new live-demo configurator clicks and trial configurator openings are not sent to Meta either. No counts are sent from our services site.

The template list (/templates/), when opened with campaign tags, also counts the page open, scrolling to 25, 50, 75 and 100 %, and 15 and 60 seconds of visible time — each at most once per page view. These steps use list in place of a template name and are not sent to Meta.

Our own Cloudflare Worker receives only the step name, template, utm_campaign and utm_content (and, after a Meta ad click, the click code described below). It stores daily totals in our Cloudflare D1 database, grouped by UTC day and those four fields, and a second set of the same daily totals also split by country. The country is the two-letter country code that Cloudflare derives from the IP address of the request; we store only that code, never the IP address. It creates no visitor identifier and stores no IP address, User-Agent or time of an individual step. Worker request logging is disabled. Cloudflare still receives the network request to deliver the service. The script sets no cookie and writes nothing to localStorage or sessionStorage.

Totals cover the current UTC day and the preceding 89 days. A scheduled daily cleanup removes older totals at 03:15 UTC. The password-protected overview shows the same 90-day period. We use these totals to understand which campaigns and countries lead to shop steps and how often the About story is opened and stays visible.

Ad clicks from Meta

When you click one of our ads on Facebook or Instagram, Meta adds a click code (fbclid) to the page address. Only in that case, our step-count script also sends that click code to our own Cloudflare Worker. The Worker then sends the step directly from our server to Meta (Meta Conversions API): the step (template page viewed, live demo, configurator, free download or checkout clicked, or 60 seconds on the page), the template, the click code, your IP address, your browser’s User-Agent and the time. Meta uses this to match the step to the ad click, measure our ads and show them to people more likely to be interested.

No Meta script, pixel or cookie is loaded on this site, and nothing is stored in your browser. Visits that do not come from a Meta ad are never sent to Meta. We do not store the click code, IP address or User-Agent ourselves; our daily totals stay as described above. Meta processes the data under its own privacy policy; for this measurement Meta and we are joint controllers under the Meta Business Tools Terms. Legal basis: our legitimate interest in measuring and improving our advertising (Art. 6(1)(f) GDPR). You can object at any time by writing to support@maxitemplates.com, and you can manage how Meta uses data for ads in your Facebook or Instagram ad settings.

Ad clicks from Google

When you click one of our Google ads, Google may add a click code (gclid, or gbraid / wbraidon iPhone) to the page address. Our site carries it between our pages, public demos and trial configurators in the address, like campaign tags. It keeps only letters, numbers, hyphens and underscores, up to 255 characters per code. We do not save it in cookies, localStorage or sessionStorage. When you open the payment form, we pass the code to Paddle as custom data attached to your order. It is not sent to our step-count service or stored in daily totals. Paddle retains it with the transaction under its ownprivacy policy and retention rules.

After a completed purchase with a Google ad click code, our server stores the click code, purchase time, amount excluding tax and currency. Google Ads downloads eligible purchases from our server once a day over an HTTPS connection to measure which ads lead to purchases. The file includes only purchases with a gclid, the conversion name, purchase time, amount excluding tax and currency. It contains no email address, name, IP address or other buyer details. Our daily cleanup deletes these stored click and purchase records once they are more than 90 days old. Purchases more than 90 days old and fully refunded purchases are excluded from the file. A refund does not retract a conversion that Google has already imported. Codes gbraid and wbraid are stored but are not included in this file. No Google script or cookie is loaded on this site. Legal basis for this advertising measurement: our legitimate interest in measuring and improving our advertising (Art. 6(1)(f) GDPR). You can object at any time by writing to support@maxitemplates.com.

The configurator’s version check

A configurator you bought asks once, when you open it, whether a newer version exists: it fetches the file maxitemplates.com/verzia.json. The request contains nothing about you — no cookie, no licence key, no information about your site. But, as with any visit to a web page, our server sees your IP address when the request arrives. We don’t use it for anything else. You can turn the check off in the configurator; see configurator updates.

The support form

When you send the support form, we receive what you entered: your email address, optionally your name, the template and its version, your order number, your browser, the address of your site and your message. It is passed on by a small program at Cloudflare (a Worker) as an email to support@maxitemplates.com and is not stored in any database. You receive one automatic confirmation at the address you entered, and nothing else is ever sent to it from the form.

To stop abuse, the form also counts messages per IP address for one hour; the count is then deleted. The form has a hidden field and a check of how fast it was sent. Neither collects any data about you — they only tell a robot from a person.

Moreover, the form is protected by Cloudflare Turnstile — a check that the form is being filled in by a person and not by an automated script. It is loaded from the server challenges.cloudflare.com when you open the Support page. In doing so Cloudflare processes your IP address, information about your browser (the User-Agent header and the fingerprint of the encrypted TLS connection) and the page on which the check runs. Without a successful check the message is not sent.

Cloudflare acts as our processor. According to its own policy it also uses the same data to improve its detection of robots — to that extent it is a controller itself. The legal basis is our legitimate interest in protecting the form from abuse (Art. 6(1)(f) GDPR).

Turnstile sets no cookie. It does store one technical record in your browser’s storage (localStorage) under the domain challenges.cloudflare.com. It is set by Cloudflare, not by us, serves only to protect the form — a purpose for which no consent is required — and stays there until you clear your browser’s storage.

We use your message to answer you. Legal basis: your request (Art. 6(1)(b) GDPR, or our legitimate interest in answering questions). We keep the correspondence as long as it is needed for your question and any follow-up.

Buying a template and receiving downloads

Purchases are handled by Paddle, our reseller and merchant of record. Paddle collects your payment and billing details as an independent controller under its own privacy policy; we never see your card details.

If you arrive through a campaign link, we carry its utm_source, utm_medium, utm_campaign and utm_content tags between our pages, demos and trial configurators in the address only. We keep only letters, numbers, hyphens, underscores and dots, up to 100 characters per tag. When you open the payment form, we send these tags to Paddle as custom data stored with the purchase, so we can see which campaign led to it. No campaign identifier is created, and no tag is saved in cookies, localStorage or sessionStorage. Please do not put personal information in campaign tags.

The payment form opens on our checkout page (/checkout/). Only that page loads Paddle’s script (paddle.js) from cdn.paddle.com and shows the form in a frame from paddle.com; no other page of this site does. From that moment Paddle processes your IP address, browser details and what you enter in the form under its own privacy policy, and Paddle may store data in your browser for the checkout. We set no cookie on that page ourselves.

Our delivery service at Cloudflare receives purchase and refund notifications from Paddle. It stores Paddle identifiers for the customer, transaction, product and price, the licence type, a hash of the licence key and data used to derive that key, the feature releases received, the update count and refund status. It also stores hashes of personal download tokens, their expiry dates and use counts. During a download, it also keeps a short-lived reservation identified by the licence, which is released when the transfer finishes or fails. We keep these records to deliver the purchase and provide lifetime updates; the service does not keep a customer email database.

To send your purchase download, it retrieves your email address from Paddle. If you request a replacement link, the service uses the email address you entered to look up purchases in Paddle, and sends links only to the purchase address. No link is shown on this site.

Legal basis: performance of the contract (Art. 6(1)(b) GDPR). Cloudflare processes the delivery data and sends the delivery emails. Records that the law requires us to keep for accounting are kept for seven years.

Product news by email

At checkout, Paddle shows an unticked box for agreeing to receive product updates and offers from MaxiTemplates by email. Only if you tick it does Paddle record your consent with your customer record; we may then email you at your purchase address about new templates, updates and offers. Without the tick, we use your email address only to deliver your purchase and to answer you. You can withdraw consent at any time by replying to such an email or writing to support@maxitemplates.com, and we stop. Legal basis: your consent (Art. 6(1)(a) GDPR).

Clicking Update and protecting downloads

The automatic version check described above sends no licence key. Only when you click Update does your configurator send its licence key and version to our delivery service. The key checks your entitlement and counts feature releases on the server. It is never saved in my-website.json or in the website you build.

The service sees your IP address. To limit requests, it stores a keyed hash of the IP address rather than the address itself. A request for a replacement link also uses a keyed hash of the email address. IP limits use one-hour windows; the email limit uses a one-day window. When a request is checked against a limit, expired counters have a 2% chance of being removed. The service records technical events without full licence keys, download tokens or email addresses. Legal basis for abuse protection: our legitimate interest in running a secure service (Art. 6(1)(f) GDPR).

Reviews

Our review form verifies your purchase using your licence key. The key is sent in the request body, never in the page address or to our step counter. We compare its hash with the delivery record; we do not store the key with your review. We store the licence identifier, template, rating, review text (up to 600 characters), public name or nickname (up to 60 characters), optional HTTPS website link, publication consent, submission date and moderation status and date in Cloudflare D1. No email address or IP address is stored with a review. Abuse limits use a keyed hash of the IP address for one-hour windows.

Cloudflare Turnstile protects the review form too, with the processing described under “The support form”. The page loads its bot-check script when opened. We publish a review, name, rating, date and optional website link only with your consent and after checking it. Reviews are from verified licence holders. We publish critical reviews as well as praise and offer no rewards. A pending review can be replaced using the same licence key; to change or delete a published review or withdraw consent, emailsupport@maxitemplates.com, the contact address in our footer. Reviews stay until you ask for removal or they are no longer relevant. Legal basis for publication: your consent (Art. 6(1)(a) GDPR); for verification and abuse prevention: our legitimate interest in authentic reviews and a secure form (Art. 6(1)(f) GDPR).

For purchases made after this feature is activated, we retrieve the purchase email address from Paddle about seven days after purchase and send one optional request for an honest review, including any reservations. Refunded or revoked purchases are skipped. We store only the transaction identifier and the sending time to prevent repeat requests; the address is not saved in D1. Cloudflare sends the email. There is no reward and no follow-up reminder. Legal basis: our legitimate interest in gathering feedback about a purchase (Art. 6(1)(f) GDPR). You can object by emailing support@maxitemplates.com.

Your rights

You can ask us for access to your data, its correction or deletion, restriction of processing, or a copy of it, and you can object to processing based on our legitimate interest. Write to support@maxitemplates.com. You can also complain to the Dutch data protection authority, the Autoriteit Persoonsgegevens.