Cookie policy

bizando.com uses no cookies. None: not technical, not analytical, not for profiling. The site stores nothing on your device — no cookies, no localStorage, no sessionStorage, no persistent identifier.

This page exists because the question is a fair one and the answer deserves to be verifiable, not because there is anything to declare.

The site is static: it has no restricted areas, no basket, no preferences to remember between visits. The four things that usually introduce cookies into a site like this one have been ruled out by choice:

• The typefaces are hosted on the site's own server rather than on an external service. Your visit generates no request to any third-party domain.
• Visit statistics are currently switched off. The tool envisaged, Plausible Analytics, works without cookies and without collecting personal identifiers: if it is activated, this page will say so, but no cookie will appear.
• Call booking is a link to an external service, not a component embedded in the page. No third-party script runs on bizando.com.
• There is no contact form. The contact details are direct: no data is sent to external services, from any page.

The notice at the foot of the page is purely informational. It is not a consent banner and it does not ask you to choose: there is nothing to authorise, because nothing is written to your device.

Bizando S.r.l., registered office at Via Tirso 90, 00198 Rome (RM), Italy, entered in the Rome Companies Register, tax code and VAT IT10804161007, REA RM-1256450, share capital €10,000.00 fully paid up.

The server hosting the site — Aruba S.p.A. infrastructure, with servers in the European Union — records the technical connection data needed to serve the pages and keep them secure. These are not cookies and they do not serve to recognise you: the detail is in the privacy notice.

If a third-party component that sets cookies is embedded in future — a booking calendar inside the page rather than as a link, for example — this page will be updated before activation and a genuine prior-consent mechanism will appear, with the component blocked until consent is given.