Cookie policy
Last updated 3 November 2026.
What does this site store on my device?
On every page, one item, and only after you have answered the cookie question: a record of the answer you gave. On the order page only, Stripe, which takes the payment, also sets two cookies to detect payment fraud. Nothing else is stored unless you have turned it on.
There are no advertising cookies, no social media pixels and no third-party analytics on this site.
| What | Type | Purpose | Kept for |
|---|---|---|---|
adora-consent | Local storage, first party | Remembers whether you accepted or rejected analytics, so you are not asked again on every page | Until you clear it or change your choice |
__stripe_mid | Cookie, set by Stripe on the order page | Lets Stripe recognise the device across payments, to detect fraud | 1 year |
__stripe_sid | Cookie, set by Stripe on the order page | Lets Stripe detect fraud during one visit | 30 minutes |
Local storage is not technically a cookie, but it does the same job of keeping something on your device, so it is covered by the same rules and listed here.
The two Stripe cookies are strictly necessary to pay safely, so they need no consent under article 22.2 of the Spanish e-commerce law (Ley 34/2002, LSSI). Stripe sets them only when you open the order page, never on the rest of the site. The payment form itself runs on Stripe's servers and follows the Stripe cookie policy.
Do you use analytics?
We count page views, and we do it without storing anything on your device and without learning anything about you.
When you open a page, your browser tells our own server three things: which page, which site you arrived from (the domain only, never the search you typed), and whether your screen is phone-sized. Those go into a running total. Two people reading the same page on the same day add one each to the same number.
The same counter also adds up presses of four buttons on the EUIPO fee calculator: the first change you make, the quote button, the clearance search button and the copy link button. Each press adds one to a running total for that button, with the same three things and nothing else.
There is no cookie, no identifier, no profile, and no third party. We cannot tell your visits apart from anyone else's, and neither can anybody else. Nothing is sent to Google, Meta or any analytics company.
That is why this needs no consent: consent under the ePrivacy rules is about storing or reading things on your device, and we do neither.
If we ever add analytics that does track individuals, it will sit behind the cookie banner and appear in the table above before it is switched on.
Do I have to accept?
No. Rejecting costs you nothing: every page works the same either way, and there is no feature behind the banner. The reject button sits next to the accept button and is exactly as easy to press.
How do I change my mind?
Use the Cookie choices link in the footer of any page. It clears the record and asks again. You can also clear site data in your browser settings, which has the same effect.
What about the enquiry and order forms?
The enquiry form does not use cookies. The order page uses only the two Stripe cookies,
__stripe_mid and __stripe_sid. What either form does with the details you type is a
separate question, answered in the privacy policy.
Why is this policy so short?
Because the site is. Most cookie policies are long because the site is carrying analytics, advertising, embedded video, chat widgets and social buttons, each dropping its own identifiers. This one carries none of that.
If that changes, this page changes with it, and the date at the top moves.