On 5 February 2026 ANSPDCP, the Romanian data protection authority, fined S.C. Tensa Art Design S.A., operator of the online optics store lensa.ro, 101,794 lei. The authority stated the equivalent as EUR 20,000. One visitor had complained about tracking and behavioral advertising cookie modules on the site. ANSPDCP opened an investigation, asked the company for information, and got no reply. The sanction cites GDPR article 83(5)(e) with article 58(1)(a) and (e): the provisions covering failure to comply with a supervisory authority's request.
That detail carries the lesson. The cookies opened the file. The unanswered letter set the amount. Below: the case, the six other Romanian cookie decisions published around it, the law they rest on, and a checklist you or your developer can run in twenty minutes with a browser. Our in-house lawyer reviewed this article before publication. It carries no legal advice for your own setup. For a binding opinion, ask a lawyer who has seen your site.
The TL;DR
- 01 On 5 February 2026 ANSPDCP fined the operator of lensa.ro 101,794 lei after one visitor complained about tracking cookies. The sanction rests on the company's failure to answer the authority.
- 02 Seven Romanian cookie decisions from June 2025 to June 2026 all started with a single complaint. Fines ran from 5,000 lei to 101,794 lei.
- 03 Law 506/2004 article 4(5) requires prior consent and clear information. Article 13 sets 5,000 to 100,000 lei, or up to 2% of turnover for companies above 5,000,000 lei in revenue.
- 04 Thirteen checks, about 90 seconds each: what fires before consent, reject parity, consent records, withdrawal, embeds, Consent Mode v2, and who reads the regulator's mail.
What happened at lensa.ro
ANSPDCP has sanctioned S.C. Tensa Art Design S.A. three times.
22 April 2024: 9,941 lei (EUR 2,000). Unsolicited marketing SMS, with no lawful basis under GDPR article 6 for using that phone number.
10 April 2025: EUR 15,000. EUR 10,000 under article 6(1)(a) for SMS marketing without valid consent, plus EUR 5,000 under articles 12(1) to (4), 15 and 17 for mishandling the same person's access and erasure requests.
5 February 2026: 101,794 lei, stated as EUR 20,000. The first of the three to concern the website itself.
The complaint described "module cookies de urmarire si publicitate comportamentala" on lensa.ro: tracking and behavioral advertising cookie modules. ANSPDCP confirmed the modules were present, then used its article 58(1) powers to request information from the operator. Nothing came back. That silence is the operative basis of the fine.
The corrective measure is narrow and telling: send ANSPDCP the response it owed the investigation. The published decision carries no banner remediation deadline.
Read the sequence as a business owner. A banner defect costs half a day of developer time. An unanswered request moves the file into a different GDPR article, with a different ceiling, and puts documented non-cooperation on the record. The cheapest control in this article costs nothing: somebody has to read the mailbox.
Seven cookie fines, one pattern
Seven ANSPDCP decisions published between June 2025 and June 2026 concern cookies and website tracking.
| Date | Operator | Fine | What the authority found |
|---|---|---|---|
| June 2025 | Personal website of a public figure | 30,000 lei + 20,286 lei (about EUR 10,000) | Tracking modules installed without consent or prior notice; contact form users left uninformed |
| 3 September 2025 | Individual site operator | 37,000 lei | Cookies beyond technical necessity placed before consent; ad and monetization modules running from September 2023 to April 2025 |
| October 2025 | There's an AI for That SRL | 30,000 lei (about EUR 6,000) | Non-essential cookies stored without clear, complete information and without explicit consent |
| 14 October 2025 | Coral Travel & Tourism Services SRL | 5,000 lei | Non-essential cookies stored without prior consent; ANSPDCP ordered a clear and visible consent banner |
| 22 December 2025 | iHunt Technology Import-Export SA | 20,000 lei (about EUR 4,000) | Cookie modules placed before consent could be given, with incorrect and incomplete information |
| 5 February 2026 | Tensa Art Design SA (lensa.ro) | 101,794 lei (EUR 20,000) | Complaint about tracking and behavioral advertising cookies; the operator ignored the authority's request |
| 26 June 2026 | Aviziero SRL | 5,000 lei | Cookies beyond technical necessity; cause traced to an outdated third-party consent plugin |
Every one of these files opened the same way. A visitor filed a complaint. No proactive sweep, crawler or industry audit appears in the published decisions. The real exposure on a Romanian website is one irritated visitor with ten minutes and a complaint form.
Six of the seven cite Law 506/2004, article 4(5): consent, and clear and complete information given first. The lensa.ro decision is the exception in its operative part, where the sanction rests on the GDPR non-cooperation articles.
The amounts stay inside the band set by article 13, described below. Published cookie fines run from 5,000 lei to 101,794 lei.
The June 2026 decision belongs above a developer's desk. The fine sat at the floor of the band, 5,000 lei. ANSPDCP traced the failure to a cookie-consent plugin from a third-party supplier that had not been updated. The operator had a consent tool installed. The tool was stale, and the cookies fired anyway. The company has since moved to a certified solution and published a reply to the coverage.
What the law actually requires
Romanian law governs the act of storing something on a visitor's device. The GDPR governs what consent has to look like.
Law 506/2004, article 4(5). Storing information, or gaining access to information already stored, on a user's terminal equipment is permitted on two conditions: the user has consented, and the user has first received clear and complete information under article 12 of the same law. Article 4(6) exempts storage or access carried out exclusively to transmit a communication, plus what is strictly necessary to deliver a service the user explicitly requested. Article 13 sets the penalties: 5,000 lei to 100,000 lei, rising to 2% of annual turnover above 5,000,000 lei in revenue.
GDPR article 4(11) defines consent as a freely given, specific, informed and unambiguous indication of the user's wishes, expressed by a statement or a clear affirmative action. Recital 32 adds that silence, pre-ticked boxes and inactivity produce no consent. Article 7 carries the operational rules: the controller must demonstrate that the user consented (7(1)), a consent request inside a longer document has to be clearly distinguishable (7(2)), and the user may withdraw at any time, by means as easy as those used to give it (7(3)).
Planet49, Court of Justice of the EU, 1 October 2019 (C-673/17). A pre-ticked checkbox the user has to deselect produces no valid consent. Two further holdings matter here: the requirement applies whether or not the stored information is personal data, and the prior information has to state how long the cookies last and whether third parties gain access.
EDPB Guidelines 05/2020 on consent. Cookie walls fail the freely-given test, so consent obtained by blocking access until cookies are accepted is invalid. Scrolling or swiping never amounts to consent under any circumstances.
EDPB Cookie Banner Taskforce report, 17 January 2023. Five practices were flagged: no refusal option on the first banner layer (a majority position, with a minority of authorities disagreeing); pre-ticked boxes on any layer; refusal offered only as a plain text link inside a paragraph; color and contrast choices that push "accept all" forward, assessed case by case; and no accessible way to withdraw consent afterwards.
The 20-minute checklist
Open your site in a fresh incognito window with DevTools on the Application tab (Storage in Firefox). Thirteen checks, roughly ninety seconds each.
1. Nothing fires before consent
Non-essential cookies and tracking scripts stay dormant until the visitor accepts. This is the failure named in nearly every decision above.
How to check: read Cookies and Local Storage before touching the banner. Anything past a session cookie is a finding.
2. Reject is as prominent as accept
The refusal control sits on the first banner layer, at the same size and weight as acceptance. Refusal buried in a settings panel was flagged by most EU supervisory authorities.
How to check: screenshot the first layer on a phone. A second click to reach "reject" is a finding.
3. No pre-ticked boxes
Every category toggle starts in the off position. Planet49 settled this in 2019 and Recital 32 says the same.
How to check: open the preferences panel on a fresh visit and photograph the toggles before touching anything.
4. Categories are granular
Analytics, marketing and personalization get separate toggles. Consent has to be specific under article 4(11), so one switch covering everything fails.
How to check: count the toggles. A single control for everything beyond strictly necessary is a finding.
5. "Strictly necessary" is honest
The exemption covers what the requested service cannot run without: a cookie holding cart contents across page loads, a session token, a security cookie detecting repeated failed logins. Analytics, remarketing and A/B testing sit outside it.
How to check: justify each entry on your necessary list in one sentence.
6. Consent records exist, with timestamps
Article 7 puts the burden of proof on you. A usable record holds the consent identifier, the timestamp, the categories accepted, and the banner version shown.
How to check: export the last 30 days. If nothing exports, you can prove nothing.
7. Withdrawal is as easy as consent
Article 7(3) gives the right to withdraw at any time, by means as easy as giving. A persistent floating icon or a permanent footer link does the job.
How to check: from a deep page, reopen preferences and switch marketing off in two clicks.
8. Banner and policy are in Romanian
Consent has to be informed, and information a Romanian visitor cannot read informs nobody. Serve the banner and the cookie policy in Romanian, other languages alongside.
How to check: set the browser language to Romanian and reload.
9. The policy lists every cookie
Name, purpose, storage duration, and the third parties with access. Planet49 named duration and third-party access as part of the prior information.
How to check: compare the policy against the cookies your browser shows after accepting everything. Gaps appear after every plugin change.
10. Embeds are gated
YouTube players, Google Maps frames, chat widgets and social feeds set cookies or identifiers the moment they load. They belong behind the consent gate, usually as a click-to-load placeholder.
How to check: open a page with a video, refuse everything, and watch the Network tab.
11. Consent Mode v2 sits on top of a banner
Consent Mode v2 tells Google tags how to behave based on signals your banner collects. It asks the visitor nothing and stores no consent record. Running it without a banner gives you a signal layer and zero consent.
How to check: confirm the default state is denied and that your banner writes the state the tags read.
12. The consent tool is current
In the June 2026 decision the authority traced the failure to an outdated consent plugin from a third-party supplier. Plugin version is a compliance control.
How to check: compare the installed version against the vendor's current release, then repeat monthly.
13. Someone owns the regulator's mailbox
ANSPDCP writes to the contact details it can find. The lensa.ro file shows the price of an unanswered request. Name a person, route the published address to an inbox read weekly, and keep the policy contact details current.
How to check: send a test message to that address and see who replies.
The draft amendment to Law 506/2004
In April 2026 the Romanian legal press discussed a draft amendment to Law 506/2004, aimed at a stricter transposition of Directive 2002/58/EC. Three requirements stand out:
- A refusal option equally visible and accessible as full acceptance, at the first interface layer.
- An explicit ban on dark patterns: pre-ticked or default-on boxes, confusing wording, and refusal buttons deliberately made smaller or less visible than "accept".
- Withdrawal of consent at least as simple as granting it.
Penalties described in the draft match article 13 as it stands.
Treat this as a draft. As of September 2026 we have not confirmed its parliamentary stage, and we quote no bill number until we can verify one. Every requirement in that draft already matches how the EDPB taskforce and the Romanian decisions read the law in force.
How we run this site
apexdigital.ro loads no third-party scripts and sets no tracking cookies. There is no analytics tag, no advertising pixel, no embedded player writing identifiers into your browser, which is why this site shows no cookie banner. The DevTools check in item 1 takes thirty seconds on this page.
Client measurement is a different job and we build it consent-first: tags start denied by default, the banner writes the signal the tags read, and the tracking plan is tested twice, with consent granted and refused, before launch. Conversion Tracking & Analytics covers that build at €1,400 over 7 days. Consent tooling drifts with every plugin release, which is what the June 2026 decision punished, so the maintenance retainers keep it current: Essentials Maintenance at €200/mo and Standard Maintenance at €550/mo.
Run the 13 checks with us.
We test your banner, your tags and your consent log twice, with consent granted and refused, and hand you the findings in writing.
Frequently asked questions
Is Google Consent Mode v2 enough on its own?
No. Consent Mode v2 adjusts how Google tags behave according to the consent state your banner collects. It asks the visitor nothing and stores no consent record. You still need a banner with a real refusal option on the first layer, granular categories, and an exportable consent log.
Do I need a banner if I only use Google Analytics?
Yes. Law 506/2004 article 4(5) covers storing information on a user's device whatever the tool. Analytics cookies fall outside the strictly necessary exemption, because the visitor requested the page and never requested the measurement. Romanian decisions from 2025 and 2026 sanctioned sites whose only defect was early tag firing.
Can I block access until the visitor accepts?
A cookie wall produces no valid consent. EDPB Guidelines 05/2020 state that consent is not freely given when access to a service depends on accepting cookies. The same guidelines rule out scrolling and swiping, since neither is a clear affirmative action. Refusing has to leave the visitor with a usable site.
How large can the fine be?
Article 13 of Law 506/2004 sets 5,000 lei to 100,000 lei for article 4 violations. Companies with annual turnover above 5,000,000 lei face up to 2% of that turnover. Romanian cookie decisions published between June 2025 and June 2026 range from 5,000 lei to the 101,794 lei imposed on lensa.ro.
Who actually triggers an ANSPDCP investigation?
One person. Every Romanian cookie sanction published between June 2025 and June 2026 began with a complaint from an individual visitor, and the decisions say so explicitly. No proactive sweep appears in the published files. A customer, a competitor or a visitor can open a case with one complaint.
Does the banner have to be in Romanian?
Consent is valid when it is informed, and information the visitor cannot read fails that test. For a site aimed at a Romanian audience, serve the banner and the cookie policy in Romanian. ANSPDCP correspondence arrives in Romanian too, so keep the policy contact details monitored.
Sources
- ANSPDCP press release, 5 February 2026 (lensa.ro sanction)
- JURIDICE.ro, ANSPDCP sanctions Lensa over cookie modules
- JURIDICE.ro, April 2025 sanction of the same online optics store
- JURIDICE.ro, September 2025 operator sanctioned over cookie modules (37,000 lei)
- JURIDICE.ro, October 2025 tour operator sanctioned over cookie modules
- StartupCafe.ro, October 2025 AI application directory fined over cookies
- JURIDICE.ro, December 2025 operator sanctioned over cookie modules
- JURIDICE.ro, June 2026 property-management platform sanctioned (outdated consent plugin)
- StartupCafe.ro, June 2025 personal website fined over cookies and contact form
- Law 506/2004, consolidated text (articles 4 and 13)
- JURIDICE.ro, April 2026 analysis of the draft amendment on cookie consent
- CJEU, Planet49 (C-673/17), judgment of 1 October 2019
- EDPB Guidelines 05/2020 on consent under Regulation 2016/679
- EDPB Cookie Banner Taskforce report, adopted 17 January 2023
Measurement built consent-first.
Tags denied by default, a banner that writes the signal, a consent log you can export. That is how we set up tracking for every client.