Last week a developer noticed that his Bluetooth headphones cut out every time he opened the AliExpress website. The explanation turned out to be more interesting than a simple glitch: the page was playing a sound nobody can hear, in order to recognise the visitor's device. The story may sound far away from a small company in Romania, but it concerns you directly, because the rules that apply there apply to your website too.
What happened, in short
Scripts on the AliExpress homepage used the browser's audio function to send a signal at zero volume through the sound card and measure the tiny differences in how each device processes it (gHacks). The result is a kind of fingerprint of the computer: stable over time and almost unique. Besides the audio, the same scripts collected information about the graphics card, the display, the hardware configuration and the way the browser behaves (gHacks). The Brave browser announced on 22 August 2026 that it blocks these scripts and that it has had protection against audio fingerprinting for more than six years (gHacks).
Here is the part that matters for you: this fingerprint needs no cookies. Nothing is saved on the visitor's computer, so the person cannot clear it from the browser settings. And if you ever thought "we don't use cookies, so we are fine", this is exactly where that reasoning breaks.
Why it concerns you, even with a small website
Almost none of the business owners I work with has ever written a tracking script. But almost all of them have added an analytics code, an advertising pixel, a chat widget, a form from an external provider or a map loaded by someone else. Every one of those is code written by another company, running on your page, seeing your visitors.
The test is simple and slightly uncomfortable: can you list right now, from memory, every third party script that loads on your company website? If you cannot, you do not know what data leaves your customers and where it goes. And in front of the authority, you are the one responsible, not the plugin vendor.
The law is not only about cookies
The European Data Protection Board has clarified that the European rule on storing information on a user's device covers not only cookies, but also tracking pixels, tracking links and device fingerprinting techniques (EDPB, Guidelines 2/2023). In other words, if you drop cookies and switch to fingerprinting, you have not escaped the obligations, you have only changed the method.
The practical rule stays the same: anything that is not strictly necessary for the site to work (statistics, advertising, remarketing) loads only after the person clicks "accept", not before. Many consent banners look good but load everything from the first second. That is not consent, that is decoration.
What the mistake costs in Romania
This is not a European theory. On 26 June 2026 the Romanian authority fined the company AVIZIERO S.R.L. 5,000 lei because its website used cookie modules that were not technically necessary, without proper information and without prior consent (JURIDICE.ro). The most useful detail for you is the cause: a cookie management plugin that its developer had stopped updating (JURIDICE.ro). It was not bad intent, it was neglected maintenance.
The general framework provides for fines between 5,000 and 100,000 lei, and for companies with turnover above 5,000,000 lei the penalty can reach 2% of turnover (Legi Internet). For comparison, the French authority fined Google 325 million euro and Shein 150 million euro in September 2025, also over cookie rules (CNIL). Your company will not get a fine of hundreds of millions, but 30,000 lei and two weeks of stress are perfectly realistic.
Be careful what data you give an AI while cleaning up
Your first instinct will probably be to open an AI assistant and ask it to look over your site. That is a good idea, with two conditions.
First: do not paste into the chat any files with real customer data (order lists, subscriber exports, addresses, phone numbers), and no access keys or passwords from configuration files. If you want an opinion on a piece of code, remove the keys first and replace real names with "client1", "client2". Anonymising takes two minutes and removes the ugliest category of risk from the discussion.
Second: if you add an AI chat to your site, that provider becomes a third party receiving your visitors' data. It has to be listed in your privacy policy, you need to know where it stores the data, and you need a processing agreement with it. A useful chatbot that breaks GDPR is still a problem, no matter how well it answers customers.
What to check today, in 20 minutes
Open your site in a private window and, before clicking any accept button, look in the browser console at the list of domains being loaded. Write them down. Any domain you cannot explain in one sentence comes off the site. Then check whether the banner really blocks the scripts until consent, update or replace any consent plugin older than a year, and put the real list into your privacy policy, not one copied from another website.
If you do only this much, you are already ahead of most company websites in Romania. And if the list of domains comes out longer than you expected, you have found exactly the reason it was worth looking.
Sources
- gHacks, AliExpress ran silent browser audio to fingerprint devices (24 August 2026)
- EDPB, Guidelines 2/2023 on the technical scope of Article 5(3) of the ePrivacy Directive
- JURIDICE.ro, Romanian authority sanction over cookies (June 2026)
- Legi Internet, the Romanian cookie law
- CNIL, fines for Google and Shein (September 2025)