1. Introduction and scope
This Cookie Policy explains which cookies and similar technologies Sendaro uses, what they are for and how you can manage them.
This policy applies to Sendaro’s own websites – the marketing site sendaro.bg (and www.sendaro.bg) and the web app at app.sendaro.bg. The technologies that Sendaro’s embedded checkout uses on merchants’ own websites are described separately in section 8.
Operator of the websites and cookies: Vladov Komers EOOD, UIC 203224076, VAT No. BG203224076, Byala, Ruse Province, email support@sendaro.bg, tel. +359 884 963 484.
Please read this policy together with our Privacy Policy and Data Processing Agreement (DPA): /legal/privacy.html and /legal/dpa.html. Last updated and version: 19 November 2026.
2. What cookies are
Cookies are small text files that a website stores on your device (computer, phone, tablet) through your browser. They are used to make the website work, to remember your choices and – on some websites – to track behaviour.
Cookies are either ‘first-party’ (set by the domain you are visiting) or ‘third-party’ (set by another domain). In terms of lifetime, they are either session cookies (deleted when you close your browser) or persistent cookies (kept until they expire or are deleted).
This policy also covers similar technologies for storing data in the browser – for example local storage (localStorage), which Sendaro uses in the embedded checkout (section 8). The consent rules apply equally to cookies and to such technologies.
3. Legal framework
In Bulgaria, storing and reading information on your device is governed by Article 4a of the Electronic Commerce Act (ZET) and Article 5(3) of Directive 2002/58/EC, in conjunction with Regulation (EU) 2016/679 (GDPR). The applicable rule is Article 4a of the ZET, not Article 261 of the Electronic Communications Act (which governs direct marketing messages by email/SMS).
The principle: strictly necessary cookies do not require consent (ZET Article 4a(4); Opinion 04/2012 of the Article 29 Working Party – WP194). All others – analytics, marketing, advertising, partner attribution and other tracking cookies – require prior, active and informed consent BEFORE they are set.
According to the case law of the Court of Justice of the EU (Case C-673/17, Planet49), pre-ticked boxes are not valid consent, and continuing to browse or scroll is not consent. Refusing must be as easy as accepting.
4. Strictly necessary cookies
These cookies are needed for the service to work and for you to stay logged in. They do not require consent.
- Name:
-
vsx_session - Domain:
- app.sendaro.bg
- Category:
- strictly necessary
- Type:
- signed HttpOnly cookie with a limited lifetime (Secure, SameSite=Lax)
- Purpose:
- keeps the merchant logged in and maintains their session after successful authentication.
- Name:
-
vsx_shopper - Domain:
- app.sendaro.bg (portal for end customers/order tracking)
- Category:
- strictly necessary
- Type:
- signed HttpOnly session cookie
- Purpose:
- keeps an end customer logged in while they view their orders.
If you block these cookies, logging in will not work. Lifetimes: vsx_session – 7 days; vsx_shopper – about 25 minutes.
5. The sendaro_ref partner cookie
This cookie is set when a visitor opens a partner link in the form app.sendaro.bg/join/CODE. It stores a referral code so that a later sign-up can be attributed to the relevant partner in the partner programme (‘last click’ attribution within 90 days).
- Name:
-
sendaro_ref - Provider:
- first party (Sendaro)
- Category:
- marketing / partner attribution
- Type:
- persistent
- Lifetime:
- 90 days
- Purpose:
- stores a referral code so that a referral can be attributed to a partner.
Although this cookie is first-party and is used only for the partner programme, legal analysis (WP194; ICO guidance, 2024; CNIL, 2022) classes referral/affiliate cookies as marketing/tracking cookies that require prior consent. Neither the fact that it is first-party nor its lifetime (90 days) changes this conclusion. sendaro_ref is therefore NOT ‘strictly necessary’ or purely ‘functional’ in the legal sense.
That is why the server sets sendaro_ref only after explicit consent (‘Accept’) in the cookie banner. Without consent, a sign-up can still be attributed to the partner through the code in the link itself or in the ‘ref’ field of the sign-up form – the code is then recorded only at sign-up, as part of the service requested.
6. No analytics or advertising cookies on our websites
On Sendaro’s own websites (sendaro.bg and app.sendaro.bg) we do not use analytics, advertising or social cookies to track behaviour, nor any A/B testing tools. Nor do we use ‘first-party’ analytics (which under WP194 would also require consent).
The only exception to strictly necessary cookies on our websites is the partner cookie sendaro_ref (section 5), which is legally classed as a marketing cookie – so we treat it separately and address the question of consent.
7. External resources: Google Fonts
This is not a cookie, but it is a related issue that we disclose openly. The fonts on all our pages are loaded from our own server (self-hosted). The visitor’s browser does NOT connect to Google servers, and their IP address is not transferred to a third country because of a font.
Why we do this: a ruling of LG München I (3 O 17493/20, 2022) held that loading Google Fonts from a CDN without consent, which passes the IP address to Google, is an unlawful transfer of personal data. That is why we host the fonts ourselves.
The fonts are our own woff2 files, loaded via @font-face from our domain.
8. Embedded checkout technologies (on merchants’ websites)
Sendaro’s core service is an embedded checkout on merchants’ websites. On those websites, the data controller is the merchant, and Sendaro acts as processor. This policy covers Sendaro’s own websites; the technologies below run on the relevant merchant’s domain, and the merchant must reflect them in its own cookie notice and, where needed, obtain consent.
- Name:
-
vsx_customer_v2 - Type:
- local storage (localStorage)
- Retention:
- ~180 days
- Purpose:
- remembers the details entered in the checkout (name, phone, email, address) for convenience on the next order. The customer can clear them with a button in the checkout.
- Name:
-
sd_my_orders_v1 - Type:
- local storage (localStorage)
- Retention:
- until the customer removes them
- Purpose:
- signed tokens for orders placed from this device, so the customer can see them in ‘My orders’ (app.sendaro.bg/moi). They contain no personal data and are removed with the button on the page or with ‘Not me’ in the form. Strictly necessary for the service the customer has requested.
- Name:
-
sd_buyer - Type:
- cookie (HttpOnly)
- Retention:
- 30 days
- Purpose:
- signing in with a phone number in ‘My orders’ after a code sent by SMS. Phone sign-in is not switched on yet, so the cookie is not set.
- Name:
-
sd_order_form_v1 - Type:
- local storage (localStorage)
- Retention:
- ~180 days
- Purpose:
- in the order form of a seller without a website (app.sendaro.bg/@name), remembers the name, phone number, nickname and delivery details entered, so they need not be typed again on the next order. The record is stored only on the customer’s device. The customer can clear it with the ‘Not me’ or ‘Forget them’ button.
- Name:
-
vsx_shopper_<shop> - Type:
- localStorage
- Retention:
- until logout/expiry
- Purpose:
- token for optional automatic login of a returning customer to their account (not used with Shopify). Set only after the customer logs in or asks for this.
- Name:
-
vsx_sid - Type:
- localStorage
- Purpose:
- random identifier for recovering abandoned carts – once the customer enters details, a lightweight signal (beacon) is sent to Sendaro (name, phone, email, items), and when an order succeeds the session is marked and the identifier replaced. By its nature this is tracking/marketing, not a strictly necessary technology → on the merchant’s website it requires prior consent. The technology runs on the merchant’s website, where the merchant is the data controller – the merchant obtains consent and reflects it in its own cookie notice. The list above is current as of the date of this document.
The embedded checkout also reads cookies set by the merchant’s platform (for example the shop’s _csrfToken and, with Simvoly, simvoly_cart) in order to submit the order. These cookies are set by the merchant’s platform, not by Sendaro.
9. Whether a consent banner is required
The app.sendaro.bg application itself uses only a strictly necessary session cookie for logging in. For this function, under Article 4a(4) of the Bulgarian Electronic Commerce Act and WP194, no consent or banner is needed – this information page is sufficient.
For pages that set sendaro_ref (section 5), and for abandoned carts through the embedded checkout (vsx_sid, section 8), the position is different: these technologies are marketing/tracking technologies and require prior consent. For these cases there is a consent banner: sendaro_ref is set only after an explicit ‘Accept’. For the embedded checkout on the merchant’s website, consent is obtained by the merchant, who is the controller there.
The banner makes refusing as easy as accepting: no pre-ticked boxes, and access is not blocked if you refuse (in line with the Planet49 ruling).
10. How to manage cookies
You can review, delete and block cookies at any time in your browser settings. From there you can also clear the data in local storage (localStorage).
Usual paths: Chrome and Edge – Settings → Privacy and security → Cookies; Firefox – Settings → Privacy & Security; Safari – Settings → Privacy. For details, see your browser’s help centre.
Please note: if you block or delete strictly necessary cookies, logging in to app.sendaro.bg may stop working. Deleting cookies and local storage may also reset your saved choices (for example, autofill details in the checkout).
11. Changes to this policy
We may update this policy when the cookies and technologies we use, or the law, change. The current version and the date of the last change are shown at the top of the document. We will announce significant changes prominently on the website.
12. Contact and supervisory authority
Questions about this policy or cookies: support@sendaro.bg (no Data Protection Officer has been appointed).
If you believe your data is being processed unlawfully, you have the right to lodge a complaint with the supervisory authority – the Commission for Personal Data Protection (CPDP), www.cpdp.bg.
For more on how personal data is processed, see the Privacy Policy; for the merchant–platform relationship, see the Data Processing Agreement (DPA).




