— Legal

Privacy policy

Last updated: 12 August 2026 · Compliant with GDPR (EU 2016/679)

This website is a static informational site for Phantom Maze AI & Language Lab. We process the minimum amount of personal data needed for the site to work, to respond to messages you send us, and to send the newsletter you explicitly request.

The short version: we set no cookies, and nothing we use can recognise you on a later visit or follow you to another site. We do count page views, and we count how many readings reach the end of an essay and how many clicks head to the bookshop — all of it aggregate, and none of it able to point at you. If you choose to subscribe, we keep your email address only to send Phantom Maze news, after you confirm the request by email. We do not train language models on it, sell it, or give it to an audience platform. You can unsubscribe at any time.

1. Data controller

The data controller for this website is Phantom Maze AI & Language Lab. For any privacy-related request, contact us via the contact form.

2. What data we process

What you submit through the contact form:

If you join the newsletter, we process your email address, the language you chose, the page where you signed up, and the timestamps and confirmation status needed to operate the list. We do not collect IP-address logs at the application layer. The contact form is transmitted via TLS to our delegated form-handler (FormSubmit.co); the newsletter is stored on our own server. Hosting infrastructure (Cloudflare) may retain short-lived access logs for security and abuse prevention.

3. Legal basis & purpose

The legal basis for processing your contact-form submission is your explicit request to be contacted — Article 6(1)(b) GDPR (steps prior to entering into a contract or service relationship) combined with Article 6(1)(f) (legitimate interest in answering correspondence). The data is used only to reply to your message.

The legal basis for the newsletter is your consent — Article 6(1)(a) GDPR. We use a double confirmation email before activating a subscription, so a typed address alone is not added to the list. We use the address only for occasional Phantom Maze research and book news. You may withdraw consent at any time through the unsubscribe link in every newsletter.

We do not:

4. Retention

We keep contact-form submissions only as long as our conversation with you reasonably requires it, plus a short period for our own records. If you ask for deletion, we delete it.

Audience-measurement events (section 5) are kept by Cloudflare in unsampled detail for 7 days, after which only aggregated counts remain, available to us for up to 6 months. Nothing in those records identifies you, so there is nothing in them to delete on request; what we retain beyond that is a plain count of page views.

The reading and purchase-intent notices stored on our own server are kept without a fixed time limit, because they contain no personal data and their only value is as a series over time: knowing whether an essay published last year is still being read. Should that ever change — if we were to add any field that could point at a person — this policy would be rewritten before the change took effect, not after.

Newsletter addresses stay in the active list until you unsubscribe. Unconfirmed requests are deleted after 30 days. When you unsubscribe, we remove the address in clear text and retain only a one-way hash needed to honour the opt-out; it cannot be used to send you mail.

5. Third-party processors

6. Your rights under GDPR

If you are in the EU, you have the right to:

To exercise any of these rights, use the contact form and reference the email address you used. You can also leave the newsletter directly through its unsubscribe link.

7. International transfers

Some of our processors (Cloudflare, Google, Resend) are based outside the EU. They are bound by Standard Contractual Clauses and, where applicable, the EU–US Data Privacy Framework. Newsletter data is stored on our own server in Argentina; Resend receives only the address and content required to deliver the email.

8. Cookies

This site sets no cookies of its own. We use no tracking pixels and no advertising scripts. Our audience measurement (section 5: Cloudflare Web Analytics, and the reading counts on our own server) writes no cookie and no identifier to your device, so it cannot recognise you on a later visit, in a later session, or on another site. There is no cross-site or cross-session tracking here of any kind. Your browser may receive cookies only from third-party resources such as Google Fonts; those are not under our control.

To be exact about what the script does: it reads timing information your browser already holds about the page you are currently loading, and sends aggregate statistics to Cloudflare. Article 5(3) of the ePrivacy Directive covers access to your device, and it has no single EU-wide exemption for audience measurement; several national authorities (among them the Italian Garante and the French CNIL) accept measurement of this kind without consent when it meets strict conditions. We have configured this measurement to meet them: it is first-party and for this site alone, it produces aggregate statistics only, it writes no identifier of any kind, the provider does not combine the data with other sites or reuse it for its own purposes, and retention is as stated in section 4 — well inside the ceilings those authorities set.

The corresponding GDPR basis is our legitimate interest in knowing which of our essays are read — Article 6(1)(f) — weighed against a measurement that cannot single you out. Where we rely on legitimate interest you have the right to object (Article 21, section 6 below): write to us and we will tell you exactly what we hold, which for this measurement is an aggregate count with nothing attached to you.

If you would rather not be counted at all, blocking static.cloudflareinsights.com in your browser or extension is enough; the site behaves exactly the same. That is an additional option, not a substitute for the right above.

9. Changes to this policy

We will update this page when our practices change. The "Last updated" date at the top indicates when the policy was last revised. Material changes will be flagged on the home page for a reasonable period.