Legal

Cookie policy

Voskis has no basket, no customer accounts and no analytics, so there is almost nothing to declare. This page states what a cookie is, what this site does and does not put in your browser, and how to check that for yourself.

Last updated: 11 September 2026

What a cookie is

A cookie is a small text file a website asks your browser to keep. It holds a name and a short value, and the browser hands it back on the next request to the same site. The mechanism is neutral. One cookie keeps a password entry valid for a few minutes; another records every page you open so an advertising network can recognise you somewhere else. The file name tells you nothing useful. The purpose does.

Two other techniques store or read data in the same way and are treated the same way in law. Local storage and session storage keep values in the browser without using a cookie header. Pixels and beacons are single-purpose requests to another company’s server, made by your browser while a page loads. Everything written below applies to all three.

What this site stores on an ordinary visit

Nothing that identifies you, and nothing that outlives the visit. That is a consequence of how the shop is built rather than a position we argue for:

• No basket. There is no cart software of any kind here, so there is no session cookie carrying a list of items from one page to the next. Your list is written in an email instead.
• No accounts. Customers do not register and there is no sign-in, so there is nothing to keep you signed in to.
• No analytics. No Google Analytics, no tag manager, no Meta pixel, no session recorder, no heatmap, no split testing. Visitor numbers are not measured on this site at all.
• No advertising or remarketing tags, and no audience list is built from anybody who reads these pages.
• No third-party embeds. No video player, no map frame, no social feed — each of which would set cookies of its own the moment a page loaded.
• No comment form, no search box, no newsletter pop-up and no chat widget.

An order runs entirely in writing. You send a list of items and a street delivery address — through the form on the contact page or by email — we reply the next working day naming what is in stock and one figure covering goods and delivery, and the driver collects that figure in cash when the box arrives. None of it asks a browser to remember anything. The steps are set out on how to order.

The narrow case: WordPress and its own cookies

This site runs on WordPress. WordPress can set a small number of cookies, and it is fair to name them, but every one belongs to somebody signing in to run the site rather than to somebody reading it.

Cookie	Set when	How long it lasts	What it does
wordpress_test_cookie	The WordPress login screen is opened	Until the browser closes	Tests whether the browser will accept a cookie at all, before a password is sent
wordpress_logged_in_… and wordpress_sec_…	A member of staff completes a sign-in to the administration area	2 days, or 14 days where the sign-in is set to be remembered	Keeps that person signed in and confirms the session is genuine
wp-settings-… and wp-settings-time-…	A signed-in member of staff changes a setting in the administration screens	1 year	Remembers screen preferences inside the admin area only

If you have never typed a password into this site, none of those cookies has ever been in your browser. There is no reason for a customer to: no customer area exists behind the login screen, and nothing on voskis.com will invite you to create one.

Typefaces are fetched from Google’s servers

The two typefaces on this site, Archivo and Public Sans, are requested from Google’s font servers as a page loads. That request sets no cookie in your browser. It does show Google the IP address your connection is using, the page that asked for the font, and the general description your browser gives of itself — as any request to another company’s server would. We name it because a third-party request deserves stating even when no cookie comes back. Block it with a content blocker if you would rather it did not happen; the page falls back to a system typeface and stays entirely readable.

Server logs are a separate thing

The hosting company keeps an ordinary access log while the site is being served: an IP address, the time, the page requested and the browser string. Those lines sit on the server, not in your browser, and no cookie is involved in producing them. They exist so a fault or an attack can be traced. The privacy policy names what those logs hold, how long the host keeps them, and the legal basis for keeping them.

If measurement is ever added

This may not hold for ever. A shop can reach the size where it genuinely needs to know which pages are read and which are ignored. If Voskis reaches it, three things happen, in this order, and none of them happens quietly.

• This page is rewritten first. The tool is named, its cookies are listed by name, and the duration and the recipient of each one is stated. The date beneath the title changes at the same time.
• Consent is asked for before the first cookie is set, not while the script is already running. Refusing takes one click and is exactly as easy as accepting. No box is ticked in advance, and carrying on reading a page is not treated as agreement.
• Withdrawing is as simple as giving. The site works the same either way. Measurement is our convenience, not a condition of using the shop.

Until all three are in place, nothing on this site counts you.

Controlling this yourself

You do not need our permission, and you do not have to take this page on trust. Every browser lets you inspect what a site has stored, delete it, and refuse more of it.

Browser	Where the controls sit
Chrome	Settings › Privacy and security › Third-party cookies, and Delete browsing data
Firefox	Settings › Privacy & Security › Cookies and Site Data
Safari on Mac	Safari › Settings › Privacy › Manage Website Data
Safari on iPhone or iPad	Settings › Safari › Advanced › Website Data
Edge	Settings › Cookies and site permissions › Manage and delete cookies and site data

Two cautions apply to every site, not only this one. Blocking all cookies everywhere will break the sign-in on most services you use daily, so a blanket refusal is usually the wrong setting. And clearing cookies clears them for every site at once: you will be signed out of everything in that browser, not only of whatever prompted you.

The position under Spanish law

The rule that governs this is Article 22.2 of Spanish Law 34/2002 on information society services and electronic commerce, the LSSI-CE, which carries the EU ePrivacy Directive 2002/58/EC into Spanish law. It requires that storing information on a user’s device, or reading information already stored there, is done only after the user has been given clear information about it and has given consent.

The same article sets out an exception, and it is a narrow one: consent is not needed where the storage is strictly necessary to carry out the transmission of a communication, or to provide a service the user has expressly asked for.

Voskis leans on that exception hardly at all, because on an ordinary visit it stores nothing to lean on it with. The WordPress cookies in the table above do sit inside it: signing in to the administration area is a service the person concerned has expressly requested, and those cookies are the mechanism that delivers it. There is no third category on this site. That is why no consent banner appears here — the Agencia Española de Protección de Datos, which supervises the article in Spain, does not require a consent notice for storage that falls inside the exception, and a banner asking permission for cookies that are never set would tell you less than this page does. Introduce one non-essential cookie and the banner becomes obligatory, which is exactly the sequence described above.

Personal data is a different subject

Cookies and personal data overlap without being the same thing. What Voskis holds about you — your name, delivery address, email, and the order and invoice record behind them — is there because you typed it into an email to us, not because a browser handed it over. What we keep, how long we keep it, who else sees it, and how to have it corrected or erased are all in the privacy policy. Both documents operate under the GDPR, Regulation (EU) 2016/679, and Spanish Organic Law 3/2018, the LOPDGDD.

Changes to this page

This page is rewritten whenever the answer changes, and the date printed under the title tells you which version you are reading. Anything that begins storing data in your browser will be described here before it is switched on, rather than left for you to find afterwards.

Who publishes this site

voskis.com is operated by:

• FLOFUM, S.L.
• Calle Parcerisa 13, Local 1
• 08014 Barcelona, Spain
• CIF: B75621250
• support@voskis.com
• https://voskis.com

Ask about anything on this page by writing to support@voskis.com. There is no telephone number at FLOFUM, S.L., so email is the whole of it; the inbox is read Monday to Saturday, 9–6 CET, and answered on the next working day. The registration details sit on the legal notice, ordering is answered on questions, and contact tells you what to put in the email.