Skip to content
Legal

Cookie Policy

Last updated 9 October 2026

This Cookie Policy explains how Anyma Studio uses cookies and similar technologies on this website. The short version: by default we use only what is strictly necessary. Two marketing tools, the Whop and Meta pixels, run only if you accept them in our cookie banner, and you can change your mind at any time.

What cookies are

Cookies are small text files a website stores on your device. Similar technologies, like local storage, work in much the same way. They can help a site load correctly, stay secure, and remember basic choices.

Our approach

We keep this site deliberately lightweight. The cookies and storage that are strictly necessary for the site to load, stay secure, function and remember your choices are always on. Under the national laws of the EU and EEA implementing Article 5(3) of Directive 2002/58/EC (as amended by Directive 2009/136/EC), storage that is strictly necessary to provide a service you have explicitly asked for does not require consent.

In the United Kingdom the equivalent rules are in the Privacy and Electronic Communications Regulations, restructured with effect from 5 February 2026, which set out their own list of purposes exempt from consent. Our strictly necessary storage falls within the exemption there too.

Everything else waits for your consent. Today that means two marketing tools, the Whop and Meta pixels described below. We do not use analytics cookies or social-media plugins.

Strictly necessary storage

This storage is always on, and is limited to essential purposes:

  • remembering the language you pick with the language switcher, in a cookie named “NEXT_LOCALE” that lasts a year;
  • remembering your answer to the cookie banner, in a cookie named “anyma_consent” that lasts six months; and
  • keeping the site secure and protecting the contact form from automated abuse.

Marketing: the Whop pixel, only with your consent

We advertise through Whop, and we use its pixel to find out which of our ads bring people to this site. It is off by default: it loads only after you choose “Accept” in the cookie banner, and nothing of it reaches your browser before that.

Once it runs, it stores a randomly generated visitor identifier in a first-party cookie named “_wuid”, which lasts two years, and keeps related identifiers in your browser's local and session storage under keys that begin with “_w”, such as “_wsc”. It also computes a device fingerprint — an identifier derived from characteristics of your browser and device, such as how it renders graphics and audio, its fonts, language, screen and hardware — and keeps it under “_wfp”. It sends Whop that identifier together with the address of each page you load, the page you came from, and technical details such as your browser, screen size and time zone. It also tells Whop when you start filling in our contact form and, when you send it, passes Whop the name and email address you entered, in plain text, with a reference number for your request, so that Whop can match the enquiry to the ad that brought you here. Your other answers and your message stay with us.

That data goes to Whop, Inc., of 300 Kent Ave #401, Brooklyn, New York 11249, United States, which handles it under its own privacy policy at whop.com/privacy. Our Privacy Policy explains our part in it.

You can withdraw your consent at any time from “Cookie Preferences” at the bottom of every page. Choosing “Reject” there stops the pixel, deletes what it stored on your device and reloads the page.

Marketing: the Meta pixel, only with your consent

We also advertise on Meta's platforms, such as Facebook and Instagram, and use the Meta pixel to find out which of those ads bring people to this site. It follows the same rule as the Whop pixel: it loads only after you choose “Accept” in the cookie banner, and nothing of it reaches your browser before that.

Once it runs, it stores a randomly generated browser identifier in a first-party cookie named “_fbp” and, if you arrived by clicking one of our ads, that ad's click identifier in a cookie named “_fbc”. Both last 90 days from your latest visit. It sends Meta those identifiers together with the address of each page you load, the page you came from, your IP address, technical details about your browser and device, and which buttons you click. If your browser also holds Meta's own cookies — because you are logged in to Facebook or Instagram, for example — Meta may link the visit to your account. And if you fill in our contact form, the pixel also sends Meta your name and email address, scrambled into a hash before they leave your browser, so that Meta can match the visit to an account of yours (Meta calls this “automatic advanced matching”).

That data goes to Meta Platforms Ireland Limited, of Merrion Road, Dublin 4, D04 X2K5, Ireland, which handles it under its own privacy policy at facebook.com/privacy/policy. Our Privacy Policy explains our part in it.

Withdrawing consent from “Cookie Preferences” stops the Meta pixel too: its cookies are deleted from this site and the page reloads.

The cookie banner

On your first visit, a banner asks whether to allow the Whop and Meta pixels; one answer covers both. “Accept” and “Reject” sit side by side and look the same. Closing the banner with the × counts as a rejection, and so does pressing Escape; scrolling or carrying on browsing does not count as consent. The rest of the site works the same whatever you choose.

We remember your answer for six months and then ask again. If you rejected, we will not ask again sooner unless the tools we use change.

Third-party content

Our fonts are served from our own site rather than a third party. We do embed one third-party component: Cloudflare Turnstile, the anti-bot check that protects our contact form. Its script loads on every page carrying the form, so Cloudflare receives your IP address and some technical signals about your browser. Turnstile is there to tell people from bots — Cloudflare states that it is not used for advertising, analytics or cross-site tracking — so we treat it as strictly necessary, on the same footing as the other security measures above.

One other third-party service runs here: Sentry, which tells us when a page on the site breaks. It sets no cookies and writes nothing to your device, so the consent rules — which are about storing or reading things on your equipment — do not reach it at all. It does receive a technical report when something goes wrong, and our Privacy Policy sets out exactly what is in one.

Vercel, which hosts the site, also gives us two measurement tools: Web Analytics, which counts visits to our pages, and Speed Insights, which measures how fast they load. Neither sets cookies or stores anything on your device. Web Analytics tells one visit from another with a code computed from your request, which Vercel discards after 24 hours, and Speed Insights does not tell visitors apart at all. Both produce only aggregate statistics about this site, for us alone, and neither follows you across other sites, so we run them without asking for consent, as we do Sentry. Our Privacy Policy lists what they record.

If we ever embed other third-party content that sets non-essential cookies — a video, a map or a scheduling tool, say — we will add it to the cookie banner and ask for your consent first, and we will update this policy.

Managing cookies

You can change your answer to the cookie banner at any time from “Cookie Preferences” at the bottom of every page. You can also control or delete cookies through your browser settings. Blocking strictly-necessary cookies may stop parts of the site from working.

Changes to this policy

We may update this policy from time to time. The current version is always on this page, along with the date it was last updated.