Privacy notice
SkinIndex shows ads from Google AdSense. Google and its partners may use cookies and other identifiers to serve those ads, and Google's consent dialog asks for your permission first. SkinIndex itself sets a cookie only when you sign in to a member account. For visitor statistics we use Fathom Analytics, which sets no cookies, and for product analytics PostHog in cookieless mode. The chatbot at the bottom of the page is loaded from the Revdot service and is described further down. On the English pages, a script from Skimlinks may turn links to online stores into affiliate links; it is described further down. A member account is optional, and the whole site works without one. Below is exactly what is collected and why.
Updated October 19, 2026
Controller
KV Beauty Oy — info@mileniaofficial.com
What we collect
The site logs anonymous usage events: which page was viewed, which product was opened, what was searched for, which filters were used, which product was saved or added to a comparison, and which store link was clicked. Each event stores:
- the event type and a timestamp
- the page path, and the product, store, or category identifier when the event concerns one of them
- the search term, if the event is a search
- a campaign tag, if you arrived through a campaign link, and the traffic source, meaning the domain of the site you came from
- a session identifier: a random value created in your browser that disappears when you close the tab
From the product finder we log the skin type, the skin concern, the product types chosen, and the number of results, without a session identifier.
We do not store IP addresses with usage events. The server reads the address from the request to limit how many events one visitor can send, but the address never reaches the event log. The events also contain no name, no email address, no member account identifier, and nothing else that could identify you. If you create a member account, the next section describes what it holds.
Member account
A member account is optional. It keeps the products you save with you when you switch devices or browsers, and lets you put products together into routines and fill in a skin profile. When you create an account, we store:
- the name and email address you give when you sign up
- a hash of your password, used to check your sign-in. We never store or see the password itself.
- whether your email address has been verified, and the account's language
- your sign-in sessions: when each one expires, plus the IP address and browser user-agent string, which are used to keep the account secure
- the identifiers of the products you save, with the time each was saved
- the routines you build: each routine's name and time of day (morning, evening or other), the identifiers of the products you add to it in their order, and the notes you write for them
- your skin profile, if you fill it in: the ingredients you avoid, your preferences (fragrance-free, no drying alcohol, no watchlist ingredients), a monthly budget with its currency, and the stores you choose
- your price alerts, if you switch any on: the product identifier, when you switched it on, the language (which decides whose stores' prices are followed), the last price checked with its currency, and when you were last notified
Routines and the skin profile are your own conditions for putting together and narrowing products. They are not health data or an assessment of your skin, and we draw no conclusions about your skin from them.
The legal basis is contract (GDPR Article 6(1)(b)): you created the account yourself, and the data is needed for it to work. The IP addresses and browser details of sessions are processed on the basis of legitimate interest (Article 6(1)(f)), because they are how misuse of an account is investigated.
The data is kept until you delete the account. A sign-in session expires once it has not been used for 30 days. The email verification link expires after 24 hours and the password reset link after one hour. You can delete your account at any time with the Delete account button on the account page: the account, your saved products, your routines, your skin profile and your price alerts are deleted at once. You can also ask the controller by email to delete it.
If you do not sign in, the products you save stay only in your browser's storage, as before. When you sign in, the list saved in your browser is merged into your account once.
We send email in three situations only: to verify your address after you sign up, when you ask for a new password, and when the price of a product you saved drops and you have switched on a price alert for it yourself. A price alert email goes to a confirmed address only, at most once a week for the same product, and one day's drops come in one email. It names the product, the old and new price, the store, and links to the product page. You can switch price alerts off on your account page, and taking a product off your saved list takes its price alert with it. We send no newsletters, and your address is never used for marketing. The messages leave our own server through Brevo's SMTP relay, so Brevo (Sendinblue SAS, Paris, France) processes the recipient address and the message content on our behalf, under Brevo's data processing agreement. Brevo keeps the data in the EU. The legal basis is the same contract as for the member account.
Visitor statistics
To count visitors we use Fathom Analytics, a statistics service from the Canadian company Fathom that does not use cookies. Your browser loads Fathom's script and sends Fathom a record of the page view: the page address and the site you came from. Like any web request, it also carries your IP address and your browser's user-agent string, from which Fathom works out your browser, device type, and country. According to Fathom, requests from the European Union are handled on its EU servers, where the IP address is deleted before the anonymized data is stored on Fathom's servers in the United States. We see only totals in Fathom, never individual visitors. The legal basis is the same legitimate interest as for our own usage events.
Product analytics (PostHog)
To improve the service we also use PostHog, an analytics service from the US company PostHog Inc. We use PostHog's EU cloud, where the data is hosted in the EU, in Frankfurt. The data travels through our own domain, and PostHog runs in cookieless mode: it sets no cookies and stores nothing in your browser.
PostHog receives the same usage events as our own log: page views and page exits, searches, filter use, saving products and taking them off your saved list, adding products to a comparison, and store link clicks. Each event carries the page path, the product, store, offer, or category identifier, the search term, and the campaign tag and traffic source, but not our session identifier. PostHog's library adds basic browser and device details, such as the browser, operating system, screen size, and the address of the previous page.
For members, three more events go to PostHog that our own log does not record: creating a routine (its time of day), adding a product to a routine (the product identifier), and saving the skin profile (how many ingredients and stores it lists, which preferences are on, and whether a budget is set). PostHog never receives ingredient names, the budget amount, or routine names.
Likewise, three events about price alerts and alternatives go to PostHog: switching a price alert on and off (the product identifier), and swapping a routine step for a similar, lower-priced product (the identifiers of the new and the swapped product). No prices and no email address are attached to them.
Like any web request, the requests also carry your IP address and your browser's user-agent string, from which PostHog works out an approximate location. According to PostHog, cookieless mode tells visits apart with an identifier PostHog computes from these details on its own servers. If you are signed in to a member account, the account's internal identifier and its language are attached to the events. PostHog never receives your email address or your name.
PostHog processes the data on our behalf. It is not used for advertising, and you are not tracked across other sites. The legal basis is the same legitimate interest as for our own usage events.
Advertising
The site shows ads from Google AdSense. Google (Google Ireland Limited) chooses and serves the ads, not us, and each one is labeled “Advertisement”. When a page loads, your browser loads Google's ad script, and Google receives what any web request carries: your IP address, your browser's user-agent string, and the address of the page.
Google and its advertising partners may store and read cookies and other identifiers in your browser. They use them to deliver ads, measure how ads perform, detect fraud and abuse, and, if you agree, personalize ads to your interests. Google's consent dialog asks for your permission the first time you visit. You can accept or decline, and you can change your choice at any time with the Cookie settings button at the bottom of every page.
If you do not consent, Google shows only limited, non-personalized ads, or none at all. The legal basis is your consent (GDPR Article 6(1)(a)). Google acts as an independent controller for advertising, and the data may also be processed outside the EU, for example in the United States. Requests about data Google processes go to Google. How Google uses information from sites that use its services.
Chatbot
At the bottom of the page there is a chatbot you can ask about products, ingredients and prices. The chatbot is Revdot, a service of Ecosta OÜ, and it loads in its own frame (an iframe) from Revdot's server mf.revdot.ai. It loads only after the page's own content. The chatbot is told which page you are on and what language the page is in. Like any web request, Revdot also receives your IP address and your browser's user-agent string.
If you write to the chatbot, your messages and the replies are processed in Revdot's service. You do not need to give your name or contact details in the chat. The chatbot sets no cookies. Under Revdot's own address it stores in your browser a user identifier, which stays until you clear your browser data, and the conversation, which disappears when you close the tab. Revdot also collects its own usage statistics on how the chatbot is used.
Affiliate links on English pages (Skimlinks)
The English pages of the site (addresses starting with /en/) load a script from Skimlinks, a service of Taboola. When you click a link that leads to an online store, the script may turn it into an affiliate link that passes through Skimlinks' server. If you then buy something, SkinIndex may earn a commission from the store. The price you pay stays the same. The Buy buttons on product pages are not affected: they go through our own affiliate network, as described below.
Skimlinks sets its own cookies in your browser and may process your IP address and the link you clicked, in order to record the click and any commission. It processes this data under its own privacy policy. Skimlinks' privacy policy. The Finnish and Swedish pages do not load the script.
What is stored in your browser
The ad cookies and Skimlinks' cookies are described above. SkinIndex itself stores data in your browser in three ways:
- A sign-in cookie, only if you sign in to a member account: a cookie whose name starts with skinindex keeps you signed in until you sign out or the session goes unused for 30 days. Next to it is a signed cookie, valid for five minutes, that spares the server from checking your session in the database on every page load. Scripts on the page cannot read either of them (httpOnly). They are strictly necessary for the sign-in you ask for, so no consent is needed for them. If you do not sign in, SkinIndex sets no cookies.
- Session storage (sessionStorage): the session identifier, the campaign tag, and the traffic source. The identifier is a random string that says nothing about you, and all three disappear when you close the tab. They are sent with usage events to our own server.
- Local storage (localStorage): the products you save and your comparison list. They stay on your device until you delete them. When you open your saved products or a comparison, your browser fetches their details from our server by product identifier. Saving and comparing are logged as usage events. For a visitor who is not signed in, the list exists only in the browser; a member's saved products are also stored in the account.
When you click Buy, the first eight characters of the session identifier travel to the affiliate network in the tracking link, as described below. The campaign tag and the traffic source are also sent to PostHog with usage events, as described above. Apart from that, nothing the site itself stores in your browser is shared with a third party or used for advertising.
Why
We collect usage events to improve the service: which searches find nothing, which guides are read to the end, whether the store links work. The legal basis is legitimate interest (GDPR Article 6(1)(f)): monitoring and improving how the service works. Our own event log is not linked to a person and is not used for profiling or advertising. In PostHog, a member's events are linked to the account's internal identifier, but they too are used only to improve the service, never for advertising or for decisions about you. That is why this interest does not override your privacy.
Going to a store
When you click Buy, you go to the store's site through an affiliate network's tracking link. From that point on, the store's and the network's own privacy policies apply to you, not this one. The link carries a reference to the network made of the page language, the campaign tag, the product identifier, and the first eight characters of the session identifier, so that we can tell where a click and any purchase came from. The network reports clicks and purchases to us by that reference; we never receive your name, contact details, or payment details. The affiliate disclosure explains this in more detail.
Retention and location
Usage events are kept for at most 24 months and then deleted; the same limit applies to the events collected in PostHog. Member account data is kept until you delete the account. Our own event log and the member accounts are stored on servers in the EU, and PostHog's data in its EU cloud in Frankfurt.
We use these processors: the platform that hosts the website, the database service, Brevo (sending email), Fathom Analytics (visitor statistics), and PostHog (product analytics). All of them process data only on our behalf. Brevo processes the email data in the EU. Fathom's anonymized visitor statistics are stored in the United States, as described above.
Google is not one of our processors: it decides for itself what it processes for advertising and for how long, as described under Advertising.
Your rights
You have the right to know what has been stored about you, to ask for it to be corrected or deleted, and to object to its processing. You can also lodge a complaint with a data protection supervisory authority, in particular in the country where you live or work, or where you think the infringement took place (GDPR Article 77). You can delete your member account yourself on the account page; other requests can be sent to the controller by email.
There is one limit we should be clear about: because the usage events contain nothing that identifies you, we usually cannot find “your” rows in the log. We will not create an identifier just to find them, because that would create exactly the kind of data we deliberately do not collect. Events collected in PostHog while you were signed in as a member can be found by the account's internal identifier, and we delete them on request. Products and comparisons you save without signing in are in your own browser's storage, so you can delete them yourself by clearing this site's data in your browser.
Changes
If we ever collect anything beyond what is described above, this page will be updated before the change takes effect, and the date at the top will show when.