Cookie text
Who is responsible
Fraxylonplixonar, Elielinaukio 3, 00100 Helsinki, Finland, is the data controller for information processed when you use the consent layer and, where applicable, optional tools that load after permission. You can reach us at contact@fraxylonplixonar.world for questions that bridge cookies and your broader privacy rights; see also the privacy policy.
What we mean by “cookie” on this page
In this policy the word cookie includes traditional HTTP cookies, similar technologies placed through scripts, and local storage in your browser, such as the key we use to store your category choices. We describe them together because, from a consent perspective, they can all act as a persistent identifier of your device or browser when combined with other data.
Strictly necessary
These items are used to make the site work and to remember that you have visited the cookie banner, accepted or rejected options, and saved a granular choice. This record is strictly necessary to apply your request about optional categories, so the banner is not the same as optional analytics or marketing. If you clear site data, the banner reappears because we can no longer see your last selection.
Your choices on first visit and later
When you land on a page for the first time, you can choose to reject non-essential categories, to accept all, or to open the settings view and toggle Analytics and Marketing separately. A floating control allows you to return to these decisions later, subject to the same technical storage rules.
Analytics category
When you switch analytics on, we may load measurement code that helps us understand aggregate use, for example which sections of a long article are scrolled into view, whether navigation paths look intuitive, and whether performance problems appear in certain regions. We configure such tools to reduce the collection of personal identifiers, where the provider’s product allows, and we review processor agreements in light of the European data-protection framework.
Marketing category
When you allow marketing, we may place or read identifiers that help us to attribute visits to a campaign, to measure conversions at an aggregated level, or to frequency-cap creative. We do not use this category to send email without a separate sign-up, and you can turn it off at any time. Turning it off may not erase identifiers that third parties set until their own maximum lifetime expires, which is one reason you may also use browser level controls.
How long we keep the consent record
Technical consent settings live in the browser on your side. They remain until you clear all site data, until you use our controls to change the selection, or until we change the software key in a new policy version that makes older records obsolete, in which case you may be asked to decide again. If we deploy named first-party or third-party cookies in the future, we will list their purpose and a practical retention cap in a table on this page when we do.
Third-party recipients
Third parties that might read or set data after consent include analytics and advertising networks we choose, content delivery networks that serve static assets, and, when you use embeds, the operators of those features. We aim to select processors and partners who offer an appropriate legal mechanism for any transfer of personal data from the EEA, such as the European Commission’s standard contractual clauses or an adequacy decision, as documented in our contracts.
Your practical controls
Beyond our banner, you can use private browsing, block third-party cookies, install protective extensions, and delete data site by site. Some browsers group privacy controls in one section; others require per-site settings. If you block all storage globally, the consent experience may not function as expected and you may see repeated notices.
Updates
When we add a new type of non-essential technology, we will update this text and, where required, re-seek your consent. The “Policy as of” date in the header reflects the most recent material alignment between this text and the implementation on the website.
Quick check. The consent state is written to localStorage in your browser under a key specific to this site. It does not replace a server-side contract for paid services, which is described in commercial terms and the privacy policy where it applies.