M·A mark microanalytics
legal · cookie policy

The cookie policy is short —
there aren't any.

No banner, because there is nothing to consent to — this site stores nothing on your device and reads nothing from it.

01 —

The register

NameProviderPurposeExpires
Cookie register · rev 01 · 0 entries — nothing to declare
localStorage — empty · sessionStorage — empty · IndexedDB — empty · third-party requests — none

First-party: none. Third-party: none. "Strictly necessary": also none — necessary would still be listed.

02 —

Why there's no banner

The rule — in Romania, Law 506/2004, art. 4, the ePrivacy transposition ANSPDCP enforces — requires consent before a site stores or reads anything on your device. We don't store and we don't read, so there is nothing to ask permission for. A banner here would be furniture.

Consent walls exist because sites do things that need consenting to. The fix is not a better banner.

03 —

How we count traffic, then

Server-side, in aggregate. Our host (here.now) counts requests as they arrive at the server — views, visitors, countries, and which declared crawlers came by. No script runs in your browser for this, and nothing follows you to another site.

The full data story is in the privacy notice — privacy.html.

04 —

Don't take our word for it

We audit other people's sites against their cookie policies for a living. Audit ours:

// open DevTools — F12, or ⌥⌘I on a Mac
// Application → Cookies → https://microanalytics.ro — empty
// Network → reload — no analytics endpoints, no pixels, no tag manager
// view-source — no gtag(), no fbq(), no dataLayer

The same check, automated and against your own cookie policy, on your own site:

run the free audit →

05 —

If this ever changes

The day this site needs a cookie, this register gains a row, the privacy notice gains a section, and — if the law requires it — a consent banner appears before the cookie does, not after.

LAST UPDATED — 23 AUGUST 2026 · REV 01