Almost every business website in Bulgaria processes personal data: a contact form, an analytics tag, an embedded map or a newsletter sign-up. Two sets of rules apply. The EU's General Data Protection Regulation (GDPR) governs personal data in general, and Article 4a of the Bulgarian Electronic Commerce Act governs cookies and similar technologies. This guide explains what each requires from a typical business site and how we implement it.
The two laws and who enforces them
| Rule | What it covers | Authority |
|---|---|---|
| GDPR, Regulation (EU) 2016/679 | All processing of personal data: forms, accounts, analytics, email | Commission for Personal Data Protection (КЗЛД) |
| Electronic Commerce Act, Art. 4a | Storing or reading information on a visitor's device: cookies, local storage, pixels | Consumer Protection Commission (КЗП) |
| Personal Data Protection Act | Bulgarian additions to the GDPR, including the digital age of consent | Commission for Personal Data Protection |
Cookies: what Article 4a requires
Article 4a was added to the Electronic Commerce Act in 2011 to implement the EU ePrivacy rules. It allows information to be stored on or read from a user's device only if the user has been given clear and comprehensive information, in line with the GDPR, and has been given the option to refuse. Bulgarian practice, and the position of the data protection authority, is that non-essential cookies need prior consent: they must not load until the visitor agrees.
The Court of Justice of the EU confirmed in the Planet49 case (C-673/17) that a pre-ticked checkbox is not valid consent. Consent must be an active choice, and it applies to cookies whether or not the data stored is personal data.
Which cookies need consent
| Type | Examples | Consent needed? |
|---|---|---|
| Strictly necessary | Session, shopping cart, security, load balancing, the consent choice itself | No, but list them in the cookie notice |
| Preferences | Remembered language or region | Usually no, if set only after the visitor chooses |
| Statistics | Google Analytics, Matomo with cookies, Hotjar | Yes |
| Marketing | Meta Pixel, Google Ads, TikTok Pixel, retargeting | Yes |
| Embedded content | YouTube, Google Maps, Instagram feeds, booking widgets | Yes, if they set cookies; load them after consent or use a click-to-load placeholder |
What a valid consent banner looks like
- "Accept" and "Reject" are equally visible on the first layer. Hiding "Reject" in a settings screen is the most common mistake we see.
- Nothing non-essential loads before the visitor chooses, including analytics in "anonymous" mode if it sets cookies.
- Categories can be chosen separately, with no pre-ticked boxes.
- The visitor can change their mind at any time through a link in the footer. Withdrawing consent must be as easy as giving it (GDPR Art. 7(3)).
- You keep a record of each consent: when, which version of the banner and which categories.
If you use Google Ads or Google Analytics for visitors in the European Economic Area, Google's EU user consent policy also requires you to obtain consent and pass the visitor's choice to Google, which in practice means Consent Mode.
The privacy notice
Article 13 GDPR lists what you must tell people when you collect their data. On a business website this is the privacy notice, linked from every form and from the footer. It should say, in plain language:
- Who you are: the company name, address and registration number (ЕИК), and how to contact you about data.
- What data you collect through the site and why, with the legal basis for each purpose.
- Who receives it: your hosting provider, email provider, analytics or CRM, and whether any of them transfer data outside the EU.
- How long you keep each type of data.
- The visitor's rights (access, correction, deletion, objection, portability) and the right to complain to the Commission for Personal Data Protection.
Legal bases on a typical website
| Purpose | Usual legal basis (Art. 6 GDPR) |
|---|---|
| Replying to a contact or quote form | Steps at the request of the person before a contract, Art. 6(1)(b) |
| Fulfilling an online order | Performance of a contract, Art. 6(1)(b) |
| Invoices and accounting records | Legal obligation, Art. 6(1)(c) |
| Newsletter | Consent, Art. 6(1)(a) |
| Analytics and marketing cookies | Consent, Art. 6(1)(a), together with Art. 4a of the Electronic Commerce Act |
| Security logs and spam protection | Legitimate interests, Art. 6(1)(f) |
Contact forms
A form is the most common way a business site collects personal data, and the easiest to get right:
- Ask only for what you need to reply. Name, email and the message are usually enough; a phone number can be optional.
- Link the privacy notice next to the submit button. You do not need a consent checkbox to reply to an enquiry, because the legal basis is the person's own request; you do need one for a newsletter.
- Send the form over HTTPS and deliver it to a mailbox that only the right people can read.
- Delete enquiries that did not lead to work after a set period, such as 12 months, and say so in the notice.
We build forms this way on every site, and we never publish an email address on the page for bots to collect.
Children's data
Bulgaria set the digital age of consent at 14. If an online service offered directly to children relies on consent, a child under 14 needs the consent of a parent or guardian (Linklaters, Multilaw). This matters for schools, training centres, sports clubs and shops for young people.
Processors and contracts
Your hosting company, email provider, CRM and analytics vendor process data on your behalf. Article 28 GDPR requires a written data processing agreement with each of them. Most large providers include one in their terms; check that it exists and keep a copy.
If something goes wrong
A personal data breach, such as a hacked site leaking form submissions, must be reported to the Commission for Personal Data Protection within 72 hours of becoming aware of it, unless it is unlikely to result in a risk to people (Art. 33 GDPR). Good security makes breaches less likely: updates, strong passwords, backups and as little stored data as possible.
A short checklist
| Check | Done when |
|---|---|
| Cookie banner | Accept and Reject equally visible; nothing non-essential loads first |
| Cookie notice | Lists every cookie with purpose and duration |
| Footer link | Visitors can reopen cookie settings at any time |
| Privacy notice | Covers Art. 13 GDPR points in plain language, in every site language |
| Forms | Minimal fields, notice linked, HTTPS, retention period defined |
| Processors | Data processing agreements with hosting, email, analytics, CRM |
| Embeds | Maps, videos and widgets load after consent or on click |
This guide is practical information for planning a website, not legal advice. For specific wording, especially in regulated sectors, ask a lawyer to review your notices. Our launch guide includes these checks as part of every website launch.
Sources
- GDPR, Regulation (EU) 2016/679 (EUR-Lex)
- Electronic Commerce Act, Art. 4a (magistrat.bg)
- Electronic Commerce Act, English text (mtc.government.bg)
- CJEU, Planet49, C-673/17
- Commission for Personal Data Protection
- Linklaters: Data Protected, Bulgaria
- Multilaw: Data Protection Laws Guide, Bulgaria
- Google: EU user consent policy






















