Cookie policy

Necessary cookies make the site work and remember your choice in the cookie banner. They cannot be deselected, because the site cannot deliver what you ask for without them. They do not require consent.

Functional currently covers our support chat, Crisp. If you accept, the chat sets cookies with the prefix crisp-client, so that a conversation can continue if you change page or come back later. They expire after six months.

Statistics is empty today. Our visitor statistics are cookie-free and are therefore not part of the category – see the section below. If at some point we start using a cookie-based analytics tool, it belongs here and is only activated with your yes.

Marketing is also empty today. The category exists because we expect to advertise in the future and to measure the effect of it. If that happens, the cookies in question are only set once you have said yes here – not before.

Scripts in the three optional categories are loaded only after your consent. If you say no – or do not answer – they are not loaded at all, and no cookie is set. That is the difference between consent and a banner that asks for permission while the thing is already running.

You can always change your mind: press Cookie settings at the bottom of any page. If you switch a category off again, we delete the cookies it has set. If it concerns the chat, the page is reloaded so that the widget actually disappears. Your choice is stored for 12 months, after which we ask again – and we also ask again if we add tools that your earlier yes did not cover.

When you make your choice, we store an anonymous receipt of it so that we can document what consent was given to: a random ID known only to your browser, the version of the banner, your choices and the time. The receipt contains no IP address, no browser information and no account, and it is deleted after two years.

We measure how many people visit the site and which pages they read with Plausible Analytics. The tool was chosen because it does the opposite of most: it sets no cookies, stores nothing on your device, uses no fingerprinting and does not follow you from site to site. No profile is created about you, and data is not sold on.

We can see that a page was opened, from which country, on what kind of device and where the visit came from – never who you are. The statistics are anonymous and aggregated and cannot be traced back to an individual person. The data processing takes place in the EU.

The statistics are therefore not part of the consent banner: consent must be obtained when information is stored on or accessed from your device, and the visitor statistics do not do that. We ask about what actually places something on your device – and only about that.

If you log in to app.affilyflow.com or store.affilyflow.com, the cookies necessary to keep you logged in are set. The store dashboard also stores your language choice (Danish/English) in a cookie. Both are strictly necessary for the service and do not require consent.

The support chat (Crisp) is only loaded when you yourself press the chat button in the bottom corner. Only then does Crisp set its cookies, so that an ongoing conversation can continue while you change page.

When a visitor clicks an affiliate link, the visitor lands on the store's site with a click ID in the address. Affilyflow's tracking on the store's site – the Shopify app's pixel, the WooCommerce plugin or our tracking script – stores this ID in a first-party cookie (af_click) on the store's domain – not on ours. The cookie contains only the click ID and lives for 90 days, regardless of the program's cookie window: the window (between 14 and 90 days) is enforced on our server based on the time of the click. The tracking script writes the cookie again on every visit, but never beyond 90 days from the click.

The Shopify pixel and the tracking script also store the same ID in the browser's local storage (localStorage) together with the time of the click. It is deleted when 90 days have passed since the click. The tracking script can also store the store's ID (af_store) and, for older links, the affiliate's ID (af_aff) in the same way.

Together with af_click, the tracking script sets the cookie af_t, which contains only the time of the click and lives as long as af_click. With it, the store's own server can renew the cookie without extending it beyond 90 days from the click. If the store lets its own server store the click, the server sets af_click, af_t, af_store and af_srv (the value 1, 90 days from the click). af_srv only tells the tracking script that the server has set the cookie, so that the script does not write it again.

The tracking script also uses a few technical entries whose only purpose is to prevent the same purchase from being counted twice: af_sent in localStorage remembers up to 20 order numbers that have already been reported, for at most 30 days, and af_sent_s and af_lead_[store] in sessionStorage disappear when the tab is closed. The test cookie _af_d finds the broadest domain the cookie can be set on and is deleted again immediately.

The WooCommerce plugin sets af_clickfrom the store's own server (90 days). From version 1.10.0, it also sets afw_last_network(90 days) when the store has switched on "last click wins": the cookie contains only the name of the affiliate network that had the customer's latest click (e.g. affilyflow or partner-ads), so that the store only shows the winning network's sales pixel.

The tracking script can be set to wait for consent (data-consent="required"): then nothing is stored in the browser until the visitor has said yes to marketing. The Shopify pixel and the WooCommerce plugin do not ask for consent themselves – that belongs to the store's own cookie solution.

The sole purpose is to be able to attribute a later purchase to the click that created it. We do no tracking across sites or devices – the attribution rests on the click ID and nothing else. The cookie belongs in the store's own cookie notice; we make the documentation available here for the stores.

If you delete or block cookies in your browser, the stores' sites still work – attribution is simply not registered for your purchases. Logging in to our dashboards does, however, require the necessary login cookies.

Write to info@affilyflow.com.