Cookie Policy
Review version: 6 October 2026. Set the effective date when publishing.
1. Scope
This policy explains cookies and similar technologies on YASHA.bg, operated by YASHA-P EOOD, company number 128505543, 15 Oborishte Street, Yambol, Bulgaria. Contact: sales@yasha.bg; +359 899 887 095. For personal data processing and rights, see https://yasha.bg/page/9/politika-za-poveritelnost.html.
2. Technologies
Cookies are small records stored by your browser. They may last for a session or a longer period. We also use pixels, scripts, sessionStorage and localStorage. These technologies may process identifiers and activity information and are not necessarily anonymous.
3. Categories and choices
- Necessary: essential functions such as cart, login, security and remembering cookie choices. They cannot be disabled through the banner where strictly necessary for a requested service.
- Functional: additional features and preferences. Where not strictly necessary, they require the relevant consent.
- Analytics: understanding visits and shopping actions, including GA4, HubSpot analytics and our records supporting reliable ecommerce measurement. Activated after Analytics is allowed.
- Advertising: campaign measurement and audiences, including Meta Pixel. These require the relevant marketing consent.
Opening the site, scrolling or continuing to browse does not constitute consent for optional technologies. You can accept all, reject optional categories or make individual choices. Purchases remain possible without analytics or advertising consent.
4. CookieYes controls
CookieYes displays the banner and remembers your choices. Use the Cookie settings button/icon on the site to change or withdraw consent and save the new choice. Choices apply to the relevant browser and device; other devices may require separate choices.
Withdrawal stops future processing dependent on that consent but does not invalidate earlier processing or automatically delete all collected data. You may separately exercise applicable erasure rights. Use your browser's clear-site-data controls to remove remaining local records.
5. Services
Google Analytics 4 measures pages and events such as add to cart, begin checkout and purchase. Google Tag Manager manages tag activation. Our GA4 analytics is configured to activate after analytics consent.
HubSpot supports visit analysis and connections with forms and contacts. Its analytics code is linked to Analytics consent, which is separate from newsletter subscription.
Meta Pixel supports advertising measurement and audiences. Meta may link data with a Facebook or Instagram account. Server-side Meta Conversions API transmission is a separate process and is not a cookie.
*
6. Cookie names and durations
The actual set depends on allowed categories and used features. CookieYes details must reflect the actual configuration. The following working list explains key purposes and is not a complete technical audit:
- cookieyes-consent — remembering consent choices; necessary.
- _ga and _ga_* — GA4 user and session identifiers; analytics.
- hubspotutk, __hstc, __hssc and __hssrc — HubSpot identifiers and sessions where set by the enabled analytics code.
- _fbp and _fbc — Meta advertising identifiers where present; _fbc may depend on arrival through an advertising link.
- Store session and security cookies — cart, login and security functions as applicable.
*
7. Local ecommerce analytics records
With analytics consent, YASHA also uses these browser records:
- yasha_atc_pending_v1 — sessionStorage; product, size, quantity and timestamp used to confirm a cart change. An attempt is used for up to 2 minutes and removed when processed.
- yasha_checkout_v1 — sessionStorage; cart composition and timestamp to limit repeated begin_checkout events for an unchanged cart within 30 minutes.
- yasha_purchase_ids_v2 — sessionStorage; product identifiers, names, sizes and quantities to match the confirmed order. A record older than 30 minutes is not used; it is removed after successful submission.
- yasha_purchase_sent_v1 — localStorage; previously reported order numbers and timestamps to limit repeat submission. Up to 500 records are retained; records older than 90 days are removed when the checking mechanism next runs, not by automatic localStorage expiry.
Session records normally disappear when the tab session ends; browser session restoration may preserve them. The 2- and 30-minute periods are script validity limits, not guaranteed physical deletion at that exact moment. LocalStorage may remain until site data is cleared or the script processes it again. These records do not include name, telephone, email or address, but an order number may be personal data.
8. Browser controls and providers
You can delete or block cookies and site data in browser settings. Blocking all storage may disrupt essential functions; clearing it may reset remembered choices.
Providers may process information outside the EEA. The Privacy Policy explains recipients, safeguards and rights. Service information: https://policies.google.com/privacy, https://legal.hubspot.com/privacy-policy, https://www.facebook.com/privacy/policy/, https://www.cookieyes.com/privacy-policy/.
We update this policy as services and settings change. Questions: sales@yasha.bg.
