Cookie Policy

This policy lists every cookie atyantik.com sets, checked against the code that runs the site on the date shown above. There are two of them. Both are set by this site rather than by anyone else, and both are set only in response to something you do. Neither is used to measure your reading, to build a profile of you, or to recognise you anywhere other than here.

Every cookie this site sets

1. __Host-anima-csrf, when you submit a form.

• When it is set: at the moment you submit a form, and at no other time. Reading this site sets nothing. If you never send us anything, this cookie never exists.
• What it is for: it proves your submission came from a page we served. Without it, another site could post to our form on your behalf.
• What it holds: a random value that matches one in the page you are on, and no information about you.
• How long it lasts: 24 hours.
• How it is protected: no script can read it. It is sent only over an encrypted connection, and your browser never sends it to another site.

We set this one without asking, and here is the reasoning. It is needed to deliver the thing you just asked for, which is sending us your message. A cookie in that position requires no consent under the rules we follow. Asking permission for it would be theatre, because refusing would only stop the form working.

2. atyantik_consent, when you answer the cookie banner.

• When it is set: only when you choose. Accepting writes it, refusing writes it, and ignoring the banner writes nothing at all.
• What it is for: it remembers what you decided, so the banner stops asking.
• What it holds: a version number, the date and time you chose, and two yes-or-no values, one for analytics and one for marketing. There is no identifier in it, no name and no address. It is the same short string for everyone who makes the same choice on the same day.
• How long it lasts: thirteen months, after which we ask again.
• How it is protected: it is sent only over an encrypted connection and is never sent to another site. Unlike the cookie above, a script on this site can read it. The panel that shows your current choices has to read it back to you.

This one is also set without asking, for a reason worth stating plainly: it is the record of your answer, including an answer of no. A refusal we needed permission to remember is a refusal we could not act on, and you would be asked the same question on every page.

What this site does not set

• No analytics cookie. Pages are counted by Cloudflare Web Analytics, which sets no cookie and stores nothing in your browser. It records that a page was viewed and how long it took to load; it does not record how far you scroll or where you stop, and it cannot recognise you on a later visit.
• No advertising cookie and nothing that hands your visit to an advertising network.
• No third-party cookie of any kind. Both cookies above are set by this site. No other organisation sets a cookie through these pages.
• No tag manager, measurement pixel, session recorder or heat map. Apart from the cookieless page counter and the bot check at submit time, the only script this site loads is its own.
• Nothing that follows you elsewhere. Neither cookie is used to link what you do here with anything you do on another site.

The choice you are offered

The banner offers two categories, and both start switched off. Each governs tools that would store something on your device or read something back from it.

• Analytics would let a measurement tool set a cookie or use your browser's storage to follow how you read across pages and visits.
• Marketing would let advertising tools recognise a return visit.

Nothing sits behind either category today. No tool of either kind is installed on this site, so turning both on right now would change nothing about what runs. We are not describing tools that are waiting for your permission, because there are none.

The page counter is outside the switch, and here is why. Cloudflare Web Analytics runs for every visitor because it sets no cookie and stores nothing on your device, which is what the switch exists to control. It counts page views and load times and nothing else. If we ever add a tool that does store something, it will sit behind the Analytics switch above and this page will say so before it runs.

The switch was built before anything it controls, deliberately. A tool added later arrives to find the switch already off, along with a refusal already recorded for anyone who gave one. Building it alongside the first tool would open a gap instead. The tool runs for a while, and the switch does not yet exist. Such a gap is invisible once it has passed.

What happens if you do nothing

Silence counts as no. Analytics and marketing stay off unless you switch them on, and every unclear case resolves the same way. All of these mean off:

• you have not answered the banner yet
• your stored answer cannot be read, whether it was damaged or altered
• your stored answer was given against an older version of this policy, which happens when we add a category. Agreeing to two things is not agreeing to a third
• your stored answer is more than thirteen months old

In each of those we ask you again, and nothing is allowed while we wait.

If your browser already refuses

Two settings let your browser refuse on your behalf before any site asks: Do Not Track, and Global Privacy Control. If either is switched on, we treat it as a refusal, analytics and marketing stay off, and the banner does not appear at all.

No cookie is stored in that case either. You have already answered. A banner would ask you to say it twice. A stray click could then undo what you meant.

Refusing is as easy as accepting

The banner shows three controls side by side: accept all, reject all, and manage preferences. They are the same size and the same style, sitting in one row. Refusing everything takes one click, exactly as accepting everything does.

This is checkable rather than a promise. Open any page, look at the banner, and count the clicks.

The banner also does not cover the page or trap you inside it. You can read this policy and our privacy notice before deciding. A box sitting on top of the documents that explain it makes that hard.

Changing your choices

Whatever you chose, you can change it at any time, including after accepting everything.

That opens the same panel the banner uses, with your current choices already filled in. Saving replaces the stored record, and switching something off takes effect immediately. A link to /cookies/#cookie-preferences from anywhere opens it the same way.

The panel is part of this site's own script. With JavaScript switched off you will see no banner and be given no choice. In that state, nothing that would need your permission can run either.

Deleting cookies yourself

Every browser lets you see the cookies a site has stored and delete them, usually under privacy or site settings. You do not need us for that, and you do not need to tell us.

• Delete atyantik_consent and your stored answer goes with it. The banner asks again on your next visit, and analytics and marketing are off in the meantime.
• Delete __Host-anima-csrf and nothing breaks. A fresh one is issued the next time you submit a form.

Blocking all cookies in your browser leaves this site readable in full. The one thing that stops working is submitting a form, because the check that a submission is genuine has nowhere to put its value.

Changes to this policy

The date at the top is when this document was last checked against the code that runs the site. It describes how the site behaves on that date and makes no claim beyond it.

If we add a cookie, or if anything starts running behind the analytics or marketing category, this policy is rewritten before that happens rather than afterwards. Adding a category also resets every stored answer, so you are asked again rather than counted as having agreed to something you were never shown.

Questions

Our privacy notice covers what happens to anything you send us through a form. It also covers how long we keep it, and how to get it back or deleted. The rules for using this site are in our terms of use.

For anything else about cookies, or to exercise a privacy right, send a request through our contact form and choose the privacy option. We publish no email address for this. One form is the only way anything reaches us, so every request gets an identifier, a timestamp and a route the moment it arrives.