Legal

Privacy Policy and Personal Data Protection Notice

Version: 1.4
Effective Date: 15 November 2026
Last Updated: 15 November 2026 (Version 1.4: added Section 3.8 regarding one-off B2B commercial communications to corporate entities under Article 14 GDPR and Article 6 ECA and our opt-out suppression list; corresponding updates to the introduction and sections 2.1, 6, 8, and 9)

This Privacy Policy explains how ВИВАН ХЕЛТ ПРОДЖЕКТС ООД (Vivan Health Projects Ltd.) ("we", "us", "our"), collects, uses, and protects your personal data when you visit our corporate website https://vivanheltprodjekts.com/ (including its English and Bulgarian pages), when you submit an offer request, when you interact with our AI chat assistant or voice demo assistant on the website, when you contact us through our official business channels on Facebook Messenger and WhatsApp Business, and when you receive a one-off B2B commercial communication from us at a publicly listed contact address of a corporate entity (Section 3.8).

This document is prepared in accordance with Regulation (EU) 2016/679 (General Data Protection Regulation – GDPR), the Bulgarian Personal Data Protection Act (ЗЗЛД), the Bulgarian Electronic Commerce Act (ЗЕТ), and Regulation (EU) 2024/1689 (the EU Artificial Intelligence Act).


1. Who is the Data Controller?

The data controller is:

  • Name: ВИВАН ХЕЛТ ПРОДЖЕКТС ООД (Vivan Health Projects Ltd.)
  • Company ID (EIK): 204317046
  • VAT number: BG204317046
  • Registered address: Sofia 1000, Sveta Troitsa, bl. 376, ent. G, fl. 2, ap. 76, Bulgaria
  • Managers: Viktoria Aleksandrova Aleksieva and Valentin Ivanov Kirilov
  • Contact email for privacy and data protection inquiries: valentin.kirilov@vivanheltprodjekts.com
  • Website: https://vivanheltprodjekts.com/

We are not required to appoint, and have not appointed, a formal Data Protection Officer (DPO) under Article 37 GDPR. For any questions regarding your personal data or to exercise your rights, please write directly to the email address above.


2. Scope of this Policy and Distinction from Our Software Products

  1. When this policy applies: This policy applies where we act as an independent data controller for visitors to vivanheltprodjekts.com, for prospective clients requesting an offer or contacting us about our services (websites, web and mobile apps, KPI dashboards, AI assistants, AI agent departments, SEO, and website care), for users who message our AI assistant or team via the website chat, Facebook Messenger, or WhatsApp Business, and where we send one-off B2B commercial communications to publicly listed contacts of corporate entities (Section 3.8).
  2. Our standalone software products: Our standalone software products — SnapReceipt (https://snapreceipt.net), Taskinger (https://taskinger.app), and Mamino (https://mamino.app) — are governed by their own dedicated Privacy Policies and Terms of Service published on their respective domains.
  3. Where we act as a Data Processor for business clients (Article 28 GDPR): When we build, host, or maintain a website, software application, or AI assistant for a business client (such as a medical or dental clinic or a company), our client is the data controller for its customers' or patients' personal data, and Vivan Health Projects acts as a data processor under a written Data Processing Agreement pursuant to Article 28 GDPR.

3. What Personal Data We Collect, Why, and on What Legal Basis

The website vivanheltprodjekts.com has no user accounts, no login area, and no visitor database. We process only the following categories of data depending on how you interact with us:

3.1. Offer Requests (via the website form or the chat assistant) and Direct Business Correspondence

  • What data we process:
    • Your name (required field, up to 120 characters);
    • Email address and/or phone number (you must provide at least one reply channel — email or phone — depending on your chosen contact preference; the other is optional);
    • Company or organisation name (optional, up to 160 characters);
    • Selected services, indicative timeline, preferred contact method (email, phone, or either), and optional project description;
    • Technical metadata attached to the submission: website language (EN or BG), whether the request was sent from the chat assistant's lead card, and the exact timestamp of your consent.
  • How the request is handled technically: When you press send, your browser submits the form fields to our serverless function in the European Union (Belgium, europe-west1), which formats them into a single email sent to our company mailbox (valentin.kirilov@vivanheltprodjekts.com). The website does not store the submission in a database after the email is sent. To prevent automated spam, the function checks a hidden honeypot field and accepts up to 5 requests per hour from one IP address. When that limit is exceeded, the IP address is written to the function's technical log (see Section 3.4).
  • Purpose: Solely to review your inquiry, contact you via your chosen channel (email or phone), discuss your requirements, and prepare a tailored written offer.
  • Legal basis:
    • Article 6(1)(b) GDPR – taking steps at your request prior to entering into a contract;
    • Article 6(1)(a) GDPR – your explicit consent given when submitting the form to retain the correspondence while handling the inquiry and for up to 12 months after the last contact if no contract is concluded;
    • Article 6(1)(c) and Article 6(1)(f) GDPR – where a contract is concluded: compliance with statutory tax and accounting obligations (under the Bulgarian Accountancy Act and the Tax and Social Insurance Procedure Code) and our legitimate interest in establishing, exercising, or defending legal claims.
  • Whether providing data is required (Article 13(2)(e) GDPR): Providing your name, at least one selected service, and at least one valid reply channel (email address or phone number) is necessary for us to review your request and send you an offer. Without these details, the form cannot be submitted.

3.2. Website AI Chat Assistant (vivanheltprodjekts.com)

  • AI transparency disclosure (Article 50(1) of Regulation (EU) 2024/1689 – EU AI Act): The "Vivan Chat Assistant" on our website is an automated artificial intelligence system. You are clearly informed in the chat header and greeting that you are interacting with an AI assistant. It answers questions strictly from the published pages of vivanheltprodjekts.com and the official descriptions of our products. It does not provide medical, legal, or tax advice, cannot negotiate discounts, and cannot enter into binding commitments on our behalf.
  • What data is processed during a chat:
    • The question you type (up to 500 characters per message), the active website language (EN or BG), and up to the last 6 turns of the current conversation in your open browser window (up to 600 characters per turn) so the assistant can understand follow-up questions.
    • Your question and conversation context are sent through our server function in the EU (europe-west1) to Google Cloud Vertex AI in the European Union (eu multi-region) (Google Gemini models and the gemini-embedding-2 semantic search model), which generates the answer on our behalf as a data processor.
  • Do we store the conversation?
    • No. We do not store your chat conversations in a database, and Google Cloud (Vertex AI) does not use your questions or the assistant's answers to train its models. For answered turns, our server logs record only anonymous operational counters (language, number of retrieved page chunks, model ID, and response time in milliseconds), without the conversation text and without your IP address.
    • Single exception (unanswered questions / gap log): When the assistant cannot answer a question from the published pages, we log only that single question (truncated to 200 characters) in Google Cloud Logging for up to 30 days so that we can add the missing answer to our website. Before logging, our code automatically strips email addresses ([email]), web links ([link]), and any sequence of 6 or more digits such as phone numbers or company/personal IDs ([number]). Please note that if you type a person's name in plain words inside your question, it may remain in that log entry until it is automatically deleted after 30 days; therefore, please do not enter personal, confidential, or medical data into the chat.
  • Per-IP rate limiting: Your IP address is checked only transiently in the server function's memory (up to 20 questions per hour per IP) to prevent abuse and protect the daily inquiry cap. We do not log your IP address alongside chat questions (for Google Cloud's standard infrastructure logs, see Section 3.4 below).
  • Legal basis:
    • Article 6(1)(b) GDPR – taking pre-contractual steps at your request when you ask about our services, pricing, and terms;
    • Article 6(1)(f) GDPR – our legitimate interest in providing accurate automated answers about our services, improving our website pages based on contact-scrubbed unanswered questions (kept for up to 30 days), and protecting the service against abuse.

3.3. Communication and AI Assistant on Facebook Messenger and WhatsApp Business (from November 2026)

When you message us on the official Vivan Health Projects page on Facebook Messenger or on our WhatsApp Business number:

  • How the channel works and AI transparency (Article 50(1) of Regulation (EU) 2024/1689):
    • The same Vivan AI assistant (powered by Google Cloud Vertex AI in the European Union) replies in these channels and clearly informs you in its first reply that you are speaking with an AI assistant.
    • The assistant answers inquiries about our services, prices, and terms within Meta's standard 24-hour customer service window after you message us.
    • Human handoff (Human-in-the-loop): When the assistant has no answer to your question, or when you write that you want to talk to a person (for example "human"), it tells you that a person from our team will reply and creates an internal task for our team.
  • What personal data we receive and process via the Meta platform:
    • On Facebook Messenger: your Page-Scoped User ID (PSID), the text of the messages you send, and the ID of each message.
    • On WhatsApp Business: your phone number, the text of the messages you send, and the ID of each message.
    • We do not read or store your Facebook or WhatsApp profile name. To messages that are not text (photos, voice messages), the assistant replies that it accepts text only.
  • Where and how Messenger and WhatsApp data is stored:
    • While the AI assistant answers automatically, the message is processed via our EU server function (europe-west1) and Google Cloud Vertex AI in the EU (eu), without being used to train AI models. Message IDs (so that we never answer the same message twice) and the last 6 turns of the conversation (for context) are kept only in the server function's memory, for up to 24 hours after your last message, and are lost when the function restarts. They are not written to a database.
    • When a conversation is handed over to a person on our team, the channel, your ID (Messenger PSID or WhatsApp phone number), the time, the reason for the handoff, and the last 6 turns of the conversation are recorded as an internal task for our team in our task management system (Taskinger, hosted on Google Cloud / Firebase in the European Union), and the thread remains visible in our official Meta business inbox so our team can reply to you.
    • We do not send unsolicited marketing messages outside the 24-hour customer service window following your inquiry, unless you have given prior explicit opt-in consent.
  • Purpose and legal basis:
    • Article 6(1)(b) GDPR – answering your inquiry and taking steps at your request prior to entering into a contract;
    • Article 6(1)(f) GDPR – our legitimate interest in responding promptly to inquiries through the messaging channels our prospective clients choose to use;
    • Article 6(1)(a) GDPR – your explicit consent, if you opt in to receive follow-up notifications outside an active inquiry.

3.4. Technical Security Logs and Anonymous Cookieless Campaign Measurement (UTM)

  • Hosting and server function security logs: Our website and serverless functions are hosted in the European Union (Belgium, europe-west1) on Firebase Hosting and Cloud Functions provided by Google Ireland Ltd. As with any web server, when you load a page or call a function, Google's infrastructure automatically records your IP address, request timestamp, requested URL path, HTTP status code, and browser/device information (User-Agent) in technical logs for up to 30 days.
    • Purpose and legal basis: Ensuring network and information security, preventing abuse (DDoS, automated attacks), and troubleshooting, based on Article 6(1)(f) GDPR (legitimate interest pursuant to Recital 49 GDPR).
  • Anonymous cookieless campaign measurement (UTM counter): When you visit our website via a link from one of our articles or social media posts carrying standard campaign parameters (utm_source, utm_medium, utm_campaign, utm_content), we increment only an aggregated anonymous daily counter (by UTC date and the campaign parameters, in Firebase Firestore in the EU). This counter does not set or read any cookies or device storage, does not record your IP address, User-Agent, or any unique identifier in the counter database, and does not profile visitors (while Google Cloud's standard 30-day technical security logs described above are never used for marketing analytics or linked to the campaign counter).

3.5. Measuring Our Facebook and Instagram Ads (Meta Pixel) – Only With Your Consent

  • When loaded: Only if you explicitly click “Accept” in the cookie banner on our website. Until you grant consent (or if you choose “Decline”), the website does not load any tracking scripts or elements from Meta's servers.
  • What happens technically: Your browser loads the Meta pixel script from connect.facebook.net and sets the _fbp cookie on our domain (and if your visit originates from clicking an ad with an fbclid parameter, the _fbc cookie as well). On every page load, the pixel transmits the loaded page URL and the “PageView” event to Meta, and upon successful submission of the offer request form, the “Lead” conversion event. The content of the submitted form (name, email address, phone number, company name, or message text) is not sent to Meta. Together with these events, your browser transmits standard technical metadata accompanying every internet request (IP address, browser and operating system details – User-Agent), as well as the values of the _fbp and _fbc marketing cookies. If you are logged in to your Facebook or Instagram profile in the same browser, Meta may associate the visit with your profile under its own privacy policies.
  • Purpose: Solely to measure and statistically evaluate whether our advertising campaigns on Facebook and Instagram drive website visits and actual offer inquiries, as well as for algorithmic optimization of ad delivery across Meta's platforms. We do not currently use website visitor data to build custom audiences for retargeting (Website Custom Audiences).
  • Legal basis: Your prior voluntary consent pursuant to Article 6(1)(a) GDPR and Article 4a(1) of the Bulgarian Electronic Commerce Act (ЗЕТ).
  • Joint controllership (Article 26 GDPR): For the operations of collecting data through the pixel on our website and transmitting it to Meta Platforms Ireland Limited, we and Meta Platforms Ireland Limited (Merrion Road, Dublin 4, Ireland) act as joint controllers within the meaning of Article 26 GDPR pursuant to Meta's contractual terms: Meta Controller Addendum. Pursuant to the essence of this arrangement:
    • Vivan Health Projects Ltd. is responsible for providing the information required under Article 13 GDPR to visitors and obtaining their valid prior consent in accordance with GDPR and the Electronic Commerce Act;
    • Meta Platforms Ireland Limited is responsible for enabling and fulfilling the rights of data subjects under Articles 15–20 GDPR with respect to personal data retained by Meta following transmission;
    • You may exercise your rights under the GDPR against either controller, with Meta Platforms Ireland Limited serving as the primary contact point for data held by Meta.
    • Following receipt of the data, Meta processes it as an independent controller for its services in accordance with the Meta Privacy Policy (https://www.facebook.com/privacy/policy).
  • How to withdraw consent: You may change or withdraw your consent at any time by clicking the “Cookies” button at the bottom (footer) of any page on the website and selecting “Decline”. Upon decline, we immediately delete the _fbp and _fbc cookies from your browser on our domain, update your choice in local storage, and the pixel ceases to load on subsequent visits. The withdrawal of consent does not affect the lawfulness of processing based on consent prior to its withdrawal (Article 7(3) GDPR).

3.6. Interactive AI Voice Demo Assistant (/bg/demo-glasov-agent/, in Bulgarian)

When you visit the voice agent demonstration page on our website and choose to speak with our conversational voice AI assistant:

  1. AI and Voice Recording Transparency (Art. 50(1) Regulation (EU) 2024/1689, Art. 32(2) Bulgarian Constitution, and Art. 248 ECA):

    • Before you activate your microphone, a clear disclosure box is displayed on the screen informing you that you are speaking with an artificial intelligence system and that the call is recorded and transcribed.
    • In its very first spoken sentence, the agent explicitly provides an audio disclosure: "Hello! I am the sample AI receptionist of an auto repair shop, a demo agent by Vivan, and our call is recorded and transcribed for demonstration purposes.".
    • The voice assistant simulates an invented sample business scenario (auto repair service). It does not have the capacity or legal authority to enter into binding agreements, process payments, or deliver professional advice.
  2. Categories of Personal Data Collected and Processed:

    • Voice audio stream & recording: Your voice is captured in real time via your browser's microphone and transmitted to technology provider ElevenLabs, Inc. (USA) for Speech-to-Text conversion, response synthesis, and Text-to-Speech audio generation.
    • Call transcript: A complete verbatim text transcript of the spoken exchange between you and the agent.
    • Appointment booking and message details: If you test the booking or messaging capabilities, the agent collects the information you provide: your name, phone number, requested service/reason, and preferred time slot.
    • Technical call metadata: Call start/end timestamps, call duration, technical session identifier, and your browser's IP address (received by ElevenLabs when your browser connects; the page load itself is logged under Section 3.4).
  3. Storage Locations and Retention Periods:

    • Booked slots and messages: Stored in Google Cloud Firestore (European Union, Belgium europe-west1 region) for up to 30 days, after which they are permanently deleted automatically.
    • Audio recordings and transcripts in ElevenLabs: Processed by technology provider ElevenLabs, Inc. (USA) and retained in the secure dashboard of the paid subscription plan of the company's manager (Valentin Kirilov), utilized for the technical operation of this demonstration, for up to 30 days for system debugging and speech recognition quality checks, followed by automatic deletion.
    • Email summaries via Resend: Upon call termination, a serverless function generates a call summary and transcript and sends an internal notification to Vivan's corporate mailbox (valentin.kirilov@vivanheltprodjekts.com) via Resend, Inc. (USA). The email is retained in our mailbox for up to 12 months as pre-contractual commercial correspondence under Section 3.1.
    • AI Model Training: No. In the settings of the demonstration account within ElevenLabs, the option to use customer data for model training has been explicitly switched off (in the account's "Data use" menu), and Google Cloud's commercial terms for our serverless functions strictly exclude customer data from foundation model training. Consequently, voice audio streams and transcripts from this demonstration are not used to train or improve AI foundation models or neural networks.
  4. Purposes of Processing:

    • Delivering the real-time interactive voice AI demonstration;
    • Capturing sample appointment bookings and messages;
    • Technical quality assurance and error monitoring;
    • Safeguarding infrastructure against automated abuse and spam.
  5. Legal Grounds:

    • Article 6(1)(a) GDPR in conjunction with Article 32(2) of the Bulgarian Constitution and Article 248 ECA — Your explicit prior consent, provided by clicking "I agree, start demo call" and granting browser microphone access;
    • Article 6(1)(b) GDPR — Taking steps at your request prior to entering into a contract (testing voice agent capabilities for your business or leaving contact details for an offer);
    • Article 6(1)(f) GDPR — Our legitimate interest in preventing server abuse (overall request limits on our server functions).

3.7. Publishing Videos to Our YouTube Channel (YouTube API Services)

  1. What We Use YouTube API Services For: We use YouTube API Services (the YouTube Data API v3 and the YouTube Analytics API) solely to upload, schedule, and manage video content on our company's official channel Vivan Health Projects (@vivanhealthprojects) via a social media management platform (Postiz) hosted on our own server at subdomain social.vivanheltprodjekts.com. The system is restricted to internal business use and is operated exclusively by authorized members of our team. Website visitors and external third parties do not have access to the system and do not connect their YouTube or Google accounts to it.
  2. Categories of Data Accessed and Processed: We access only data pertaining to our own corporate channel and the connected Google account of our authorized team administrator:
    • Administrator Profile Data: Google user ID, name, and profile picture (the email address is requested as part of the default OAuth scope but is neither read nor stored);
    • Channel Metadata: Channel title, handle (@vivanhealthprojects), logo/avatar, and total subscriber count;
    • Published Content Data: Video titles, descriptions, tags, and thumbnails of videos uploaded by our team;
    • Statistical and Analytical Metrics: Public performance metrics of our own videos (view counts, likes, and comment counts) and aggregated daily channel metrics from YouTube Analytics (total views, watch time, average view duration, and subscriber growth dynamics). The system does not access, collect, or store personal data of video viewers, comment contents, playlists, closed captions, or data from third-party channels.
  3. Legal Basis (Art. 6(1)(f) GDPR): Processing of identification details of the team member who connects the channel's Google account is carried out pursuant to our legitimate interest in administering, operating, and growing the company's official video marketing presence through authorized personnel.
  4. Storage Locations and Third-Party Sharing: The OAuth authorization credentials (access and refresh tokens) and the metadata listed above are stored securely within the Postiz database on our own virtual private server (VPS) for as long as the channel remains connected. We do not sell, rent, or share these data with third parties or advertising networks.
  5. No Visitor Cookies or Device Tracking: In connection with our use of YouTube API Services on our server, we do not place, access, or utilize cookies, tracking pixels, or other local storage technologies on the devices of visitors to the vivanheltprodjekts.com website.
  6. YouTube Terms of Service and Google Privacy: The operation of YouTube API Services complies with the YouTube API Services Developer Policies. By using this integration, our team agrees to be bound by the YouTube Terms of Service. Google processes YouTube-related data in accordance with the Google Privacy Policy.
  7. Access Revocation and Data Deletion:
    • Access granted to the system can be revoked at any time directly through the Google Account Security Settings page (under "Third-party apps with account access").
    • Upon revocation of access via Google security settings, the authorization token is immediately invalidated by Google, terminating the system's access. We manually delete the channel's database record (stored OAuth tokens and cached API metadata) from our system's database within 30 calendar days, in accordance with the YouTube API Services Developer Policies. When a channel is removed or disconnected within the Postiz dashboard, we manually delete its record within 7 calendar days.
    • The team member who connected the account may also request manual erasure of any associated profile data at any time pursuant to Section 8 of this Policy.

3.8. One-Off Unsolicited B2B Commercial Communications to Corporate Entities (Article 14 GDPR and Article 6 ECA)

When we contact a corporate entity by email regarding our professional website and software development services (and the recipient follows the link to this Policy included in the legal footer of our email):

  1. Corporate Recipients Only and When Personal Data Is Involved (Recital 14 and Art. 4(1) GDPR):
    • We send a strictly one-off B2B commercial communication (within the meaning of Article 6 of the Bulgarian Electronic Commerce Act, Regulations 22–23 of the UK Privacy and Electronic Communications Regulations 2003 – PECR and Regulations 7–8 of the UK Electronic Commerce Regulations 2002 for the United Kingdom, and the U.S. CAN-SPAM Act, 15 U.S.C. § 7704 for the United States) exclusively to incorporated legal entities: in Bulgaria – commercial companies (OOD, EOOD, AD, EAD, cooperatives); in the United Kingdom – active corporate subscribers (Ltd, PLC, LLP); in the United States – corporate entities (LLC, Inc., Corp., LLP, PC, PLLC). We never send unsolicited commercial emails to consumers (natural persons), sole traders / sole proprietorships (ET), unincorporated partnerships, or liberal professions, nor to recipients in jurisdictions requiring prior express opt-in consent even for legal entities (such as Germany and Austria).
    • As a rule, we write only to generic corporate contact addresses (info@, office@, contact@, reception@, enquiries@, hello@, or a public free-mail address named after the company itself), which constitute data of a legal person outside the material scope of the GDPR pursuant to Recital 14 GDPR. However, insofar as a Bulgarian company's official correspondence address filed in the public Commercial Register may contain a manager's name or personal email, or insofar as an identifiable natural person stands behind a small company's generic address (or replies from an individual corporate address to opt out), we provide full transparency under Article 14 EU GDPR (and Article 14 UK GDPR for UK recipients) through the legal footer inside the email itself (first layer) and this subsection (second layer).
  2. Categories of Data Processed and Publicly Accessible Sources (Art. 14(1)(d) and Art. 14(2)(f) GDPR):
    • Categories of data: Corporate name, legal form, and company registration number (UIC in Bulgaria or Company number in UK Companies House); publicly listed corporate contact email address (and, if an opt-out reply is sent from another corporate address of the company, the address requesting the opt-out); objective technical observations regarding the company's public website (whether a website exists, real-user mobile loading speed from the public Google Chrome User Experience Report – CrUX, mobile layout availability, HTTPS security, and machine-readable structured data); and the exact date and timestamp of our mandatory verification against the Bulgarian Commission for Consumer Protection (CPC) opt-out register under Article 6(2) ECA.
    • Publicly accessible sources: All data originates strictly from official or publicly accessible sources: (a) the public Commercial Register and Register of Non-Profit Legal Entities maintained by the Bulgarian Registry Agency (for Bulgaria) and the public Companies House register (find-and-update.company-information.service.gov.uk to verify legal form and Active status in the United Kingdom; personal officer addresses in Companies House filings are never extracted); (b) the company's own public website; (c) the company's public listing on Google Business Profile or the open map databases OpenStreetMap / Overture Maps; and (d) the public electronic opt-out register maintained by the Commission for Consumer Protection (CPC) under Article 6(2) ECA (kzp.bg), checked on the day of sending. We never purchase marketing lists from data brokers and never scrape personal employee emails from social media or LinkedIn.
  3. Purposes, Dispatch Method, and Legal Basis (Art. 14(1)(c) & (e) and Art. 14(2)(b) GDPR):
    • One-off B2B business outreach: Processing for initial verification and sending the single outreach email is based on Article 6(1)(f) and Recital 47 of the EU GDPR (and UK GDPR) – our legitimate interest in introducing our web and software development services once, in a non-intrusive manner, to corporate entities whose public web presence indicates a specific technical need. Emails are sent manually and individually from our corporate mailbox (valentin.kirilov@vivanheltprodjekts.com, operated via Google Workspace by Google Ireland Limited as described in Section 5, item 1) and do not contain hidden open or click tracking pixels. If there is no reply, we never send follow-up emails or reminders.
    • Compliance with statutory opt-out registers and maintaining our permanent suppression list: Checking the CPC register and permanently recording opted-out email addresses and domains on our internal suppression list are carried out under Article 6(1)(c) and (f), Article 17(3)(b), and Article 21(3) EU GDPR / UK GDPR, in conjunction with Article 6(2)–(3) of the Bulgarian ECA, Regulation 23 of the UK PECR, and 15 U.S.C. § 7704(a)(4) (U.S. CAN-SPAM Act) – to comply with our legal obligation never to message recipients who have objected or opted out and to demonstrate accountability (Article 5(2) GDPR).
    • Where a company replies requesting a proposal or call: Any subsequent requested correspondence is handled as pre-contractual business correspondence under Section 3.1 based on Article 6(1)(b) and (f) GDPR.
  4. Retention Periods and Unconditional Right to Object (Art. 14(2)(a) & (c) and Art. 21(2)–(3) GDPR):
    • Where no reply is received, the sent one-off email and the internal verification record (containing the checked public business details and the exact timestamp of the CPC register check) are retained for up to 12 months from dispatch (solely to demonstrate compliance with Article 6(2) ECA before supervisory authorities and to prevent sending a second email to the same company), after which they are deleted.
    • You have an absolute right to object free of charge at any time to processing for direct marketing purposes under Article 21(2)–(3) EU GDPR / UK GDPR by replying to the email with “Opt-out” or “Unsubscribe” (or „Отказ“) or by writing to valentin.kirilov@vivanheltprodjekts.com. Your objection is honoured immediately (and for U.S. recipients, immediately and in all cases within the 10-business-day statutory period under CAN-SPAM), and the company's email address and domain are added permanently (indefinitely) to our internal suppression list so that no future commercial communication is ever sent to that address or domain (or, if you explicitly request complete erasure without retention on the suppression list, all records are erased pursuant to Section 8, item 7).

4. Cookies and Local Storage on Your Device (Article 4a of the Electronic Commerce Act)

The website vivanheltprodjekts.com uses Meta marketing cookies (_fbp, and upon ad referral, _fbc), and only if you explicitly accept them in the cookie banner (Section 3.5). Without your explicit consent, the website does not load third-party marketing scripts, pixels, or cookies. We do not use analytics cookies.

Cookie Provider / Domain Purpose Retention period
_fbp Meta Platforms Ireland Limited (set on our first-party domain) Stores a unique browser identifier upon visit following consent so Meta can measure visits and offer requests resulting from our ads and optimize their delivery 90 days from last visit (or until deleted upon consent withdrawal)
_fbc Meta Platforms Ireland Limited (set on our first-party domain) Records the unique ad click identifier from Facebook or Instagram (the fbclid parameter) to attribute the visit to a specific ad campaign 90 days from last visit (or until deleted upon consent withdrawal)

If you are logged in to your Facebook or Instagram account in the same browser, your browser also transmits cookies from Meta's domain (such as fr) with network requests to Meta's servers, which are governed entirely by Meta under its Cookie Policy (https://www.facebook.com/privacy/policies/cookies/).

Apart from that, only the following strictly necessary technical items are stored in your browser (the first two categories in sessionStorage, which is cleared automatically when you close the tab, and the third category in localStorage):

  1. Light or dark theme preference (vivan-theme): Stores only your chosen visual theme (light or dark) when you click the theme switch so your choice persists across pages.
  2. Whether the intro animation and the chat assistant's start screen have already been shown (vivan-intro-seen, asst-booted): So that they do not repeat on every page.
  3. Your cookie banner choice (vivan-consent): Stores your choice (“Accept” or “Decline”) and the date of your decision in localStorage for up to 6 months so that we do not prompt you with the banner on every page navigation. This setting can be modified or cleared at any time via the “Cookies” button in the footer.

The chat conversation itself is not stored in your browser: it lives only in the memory of the open page and is gone when you reload the page or move to another one.

Under Article 4a(4) of the Bulgarian Electronic Commerce Act (ЗЕТ) (transposing Article 5(3) of Directive 2002/58/EC), this browser storage (as distinct from the optional _fbp and _fbc marketing cookies above) is strictly necessary to technically provide features you explicitly request and to respect your cookie preferences. It is not used for profiling and does not transmit personal data. You can clear local storage and cookies at any time through your browser settings.


5. Data Recipients, Processors (Article 28 GDPR), and International Transfers

We do not sell or rent your personal data. Data is shared with a third party (Meta Platforms Ireland Limited) for marketing purposes in one case only: if you explicitly accept Meta marketing cookies in the website cookie banner (Section 3.5).

To operate the website, communication channels, and ad measurement, we collaborate with the following trusted partners (data processors under Article 28 GDPR, and for the Meta pixel, a joint controller under Article 26 GDPR):

  1. Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland):
    • Role: Cloud infrastructure provider in the European Union — Firebase Hosting, Cloud Functions (europe-west1, Belgium), Cloud Firestore in the EU (for internal team tasks and the anonymous campaign counter), Google Cloud Vertex AI in the eu multi-region (for the AI chat assistant), and Google Workspace (for our company email valentin.kirilov@vivanheltprodjekts.com), as well as YouTube API Services (YouTube Data API v3 and YouTube Analytics API) for publishing and managing video content on the company's official YouTube channel (Section 3.7).
    • Location and transfer safeguards: Server functions and Vertex AI models run in European Union data centres (europe-west1 and the eu multi-region). Where incidental support access outside the EEA by Google LLC (USA) may occur, it is covered by the European Commission's Standard Contractual Clauses (Article 46(2)(c) GDPR) and Google LLC's certification under the EU-U.S. Data Privacy Framework (Article 45 GDPR).
  2. Resend, Inc. (2261 Market Street #5039, San Francisco, CA 94114, USA):
    • Role: Processor providing technical transactional email dispatch: (a) for offer inquiries submitted through our website forms; (b) for delivering summaries and transcripts generated by the interactive voice demo to Vivan's team mailbox.
    • International Transfers: Transfers to Resend in the United States are governed by a Data Processing Addendum and the European Commission's Standard Contractual Clauses (SCCs) under Article 46(2)(c) GDPR.
  3. Meta Platforms Ireland Limited (Merrion Road, Dublin 4, Ireland) and Meta Platforms, Inc. (1 Meta Way, Menlo Park, CA 94025, USA):
    • Role: (a) When you choose to message us via Facebook Messenger or WhatsApp Business – Meta routes messages across its platform (acting as an independent controller for your user profile under its privacy policies at https://www.facebook.com/privacy/policy and https://www.whatsapp.com/legal/privacy-policy-eea, and as a processor for WhatsApp Business Cloud API messages under the WhatsApp Business Data Processing Terms); (b) when you accept Meta marketing cookies on the website (Section 3.5) – joint controller with us pursuant to Article 26 GDPR for collecting and transmitting event data via the Meta pixel under the Meta Controller Addendum, and an independent controller following transmission for its advertising systems.
    • International transfer safeguard: Transfers from Meta Platforms Ireland Limited to Meta Platforms, Inc. (USA) rely on the European Commission's adequacy decision for the EU-U.S. Data Privacy Framework (Article 45 GDPR) and the Standard Contractual Clauses (Article 46(2)(c) GDPR).
  4. ElevenLabs, Inc. (169 Madison Ave, Suite 2484, New York, NY 10016, USA):
    • Role: Third-party technology provider (data recipient under Article 4(9) GDPR) delivering conversational speech synthesis, real-time voice recognition, and agent orchestration (ElevenLabs Conversational AI / Agents), operating via the company manager's paid subscription plan utilized for this demonstration.
    • International Transfers & Safeguards: Audio streaming and transcription processing occur in ElevenLabs data centers in the United States. International data transfers are legally secured under the European Commission's adequacy decision pursuant to Article 45 GDPR via ElevenLabs, Inc.'s active certification under the EU-U.S. Data Privacy Framework (verified participant on the official public register: https://www.dataprivacyframework.gov/list).

Apart from the processors listed above, data may be disclosed only to competent public authorities (such as the National Revenue Agency, the Commission for Personal Data Protection, or courts) when strictly required by applicable law.


6. How Long We Keep Your Personal Data

We follow the storage limitation principle (Article 5(1)(e) GDPR) and retain data only for as long as necessary for the respective purpose:

Category of data Retention period
Offer requests and business correspondence (by email, phone, or conversations handed over to our team from the website chat, Messenger, or WhatsApp) For as long as the inquiry is being handled and up to 12 months after the last contact, unless you request earlier deletion or a contract is concluded.
Client contract and invoicing records (where a contract is signed) For the duration of the contract and 5 years after its termination (statutory limitation period for contractual claims under Article 110 of the Bulgarian Obligations and Contracts Act), and 10 years for accounting registers and invoices starting from 1 January of the year following the accounting period (Article 12(1)(2) of the Bulgarian Accountancy Act and Article 38(1) of the Tax and Social Insurance Procedure Code).
Website AI chat assistant conversations Not stored by us after the reply is generated (kept only in the open page until you reload or leave it).
Unanswered questions to the AI assistant (gap log with emails, phone numbers, and links removed) Up to 30 days in Google Cloud Logging, then automatically deleted.
Technical server security logs (including IP address at Google Cloud) Up to 30 days, then automatically deleted.
Meta marketing cookies (_fbp, _fbc) (only with “Accept”) Up to 90 days from your last visit in your browser, or immediately until you withdraw consent via the “Cookies” button in the footer (the cookies are then deleted from your browser). Data received by Meta is retained under Meta's privacy policy.
Saved cookie banner choice (vivan-consent) Up to 6 months in your browser's local storage (localStorage), after which we prompt you again, or until you change it via the “Cookies” button in the footer.
Voice demo booking and message entries (name, phone, slot) Up to 30 days in secure Cloud Firestore in the EU, after which they are permanently deleted automatically.
Voice audio recordings and transcripts in ElevenLabs Up to 30 days following the call for diagnostic quality checks, followed by automatic deletion.
Email call summaries and transcripts in Vivan's mailbox Up to 12 months as pre-contractual commercial correspondence, unless earlier deletion is requested.
YouTube API Services data (OAuth tokens, channel and video metadata) For as long as the channel is connected to the publishing tool on our server; upon access revocation via Google, the token is immediately invalidated by Google, and the database record (tokens and cached metadata) is manually deleted by us within 30 calendar days (within 7 calendar days when the channel is removed in Postiz) pursuant to the YouTube API Services Developer Policies.
One-off B2B commercial communications and CPC register verification log (Section 3.8, where no reply is received) Up to 12 months from dispatch to demonstrate compliance with the statutory verification under Article 6(2) ECA and prevent sending a duplicate email to the same company, after which they are deleted (if the company replies expressing interest in an offer, the retention period for business correspondence in the first row of this table applies).
Opt-out suppression list of email addresses and domains (suppression list, Section 3.8) Permanently (indefinitely) for the opted-out email address and corporate domain only, pursuant to Article 6(3) ECA and Articles 6(1)(c) and (f), 17(3)(b), and 21(3) EU GDPR / UK GDPR, solely to ensure technically that no future commercial communication is ever sent to that address or domain.

7. Your Rights under the GDPR and How to Exercise Them

Under Chapter III of the GDPR, you have the following rights, which you may exercise free of charge at any time by writing to valentin.kirilov@vivanheltprodjekts.com:

  1. Right of access (Article 15 GDPR): To obtain confirmation as to whether we process your personal data and receive a copy of it.
  2. Right to rectification (Article 16 GDPR): To request the correction of inaccurate data or completion of incomplete data.
  3. Right to erasure – "right to be forgotten" (Article 17 GDPR): To request the deletion of your personal data where it is no longer needed for its purpose, where you withdraw your consent, or where you object to processing.
  4. Right to restriction of processing (Article 18 GDPR): To request that we restrict processing while accuracy or legitimate grounds are verified.
  5. Right to data portability (Article 20 GDPR): For data you provided based on consent or contract, to receive it in a structured, commonly used, and machine-readable format.
  6. Right to object (Article 21 GDPR): To object at any time to processing based on our legitimate interests (Article 6(1)(f) GDPR).
  7. Right to withdraw consent (Article 7(3) GDPR): Where processing is based on your consent, you may withdraw that consent at any time by emailing valentin.kirilov@vivanheltprodjekts.com (and for marketing cookie consent, at any time directly via the “Cookies” button in the website footer), without affecting the lawfulness of processing prior to withdrawal.
  8. No automated individual decision-making (Article 22 GDPR): We do not use your personal data for profiling or for automated decision-making that produces legal effects concerning you or similarly significantly affects you.

We respond to all requests without undue delay and within 1 month of receipt pursuant to Article 12(3) GDPR.


8. User Data Deletion Instructions (including for Facebook Messenger and WhatsApp)

In accordance with Article 17 GDPR and Meta Platforms' requirements for User Data Deletion Instructions, any user who has submitted an inquiry through our website or messaged our AI assistant or team on Facebook Messenger or WhatsApp Business can request the complete deletion of their data from the systems of Vivan Health Projects Ltd. in any of the following ways:

  1. By email (direct deletion request):
    • Send an email to valentin.kirilov@vivanheltprodjekts.com with the subject line "Data Deletion Request" (or "Изтриване на лични данни").
    • Please state the channel you used to contact us: your email address, your phone number (for WhatsApp), or the name/profile from which you messaged us on Facebook Messenger.
  2. Directly inside Facebook Messenger or WhatsApp:
    • Write "human" in the chat and ask for your data to be deleted. The conversation is handed to a person on our team, who carries out the request.
  3. Deleting the conversation in your app:
    • You can also delete the conversation thread in your Messenger or WhatsApp app. This removes it from your device; the data we hold is deleted as described in points 1 or 2.
  4. What we delete and within what timeframe:
    • Upon receiving your request, we permanently delete all records stored in our systems linked to your Page-Scoped User ID (PSID), phone number, or email address: internal team tasks in Taskinger, offer request correspondence, and messages in our business mailbox (except where a contract has been signed or an invoice issued that must be kept by law under the Bulgarian Accountancy Act).
    • Deletion is completed without undue delay, typically within 5 business days and no later than 30 calendar days from receipt of your request, after which we send you a written confirmation that your data has been erased.
  5. Deletion of Voice Demo Data:
    • If you have interacted with our voice demo assistant and dictated personal details (such as your name or phone number), you may request immediate deletion by emailing valentin.kirilov@vivanheltprodjekts.com with the subject line “Voice Demo Data Deletion Request”.
    • Please specify the phone number or name you provided during the call.
    • Within 5 business days, we will permanently delete the entry from Cloud Firestore, remove the call log from ElevenLabs, and delete the summary email from our corporate inbox.
  6. Revocation and Deletion of YouTube API Services Data:
    • You may revoke the publishing system's (Postiz) access at any time directly via the Google Security Settings page.
    • Upon revocation, the authorization token is immediately invalidated by Google, and the integration database record (tokens and cached metadata) is manually deleted by our team within 30 calendar days pursuant to the YouTube API Services Developer Policies. To request additional or expedited erasure of profile records, the administrator may send an email to valentin.kirilov@vivanheltprodjekts.com pursuant to item 1 above.
  7. Opt-Out (Objection) and Deletion of Data from a One-Off B2B Commercial Communication (Section 3.8):
    • If you have received a one-off B2B commercial communication from us, you may at any time reply with “Opt-out” or “Unsubscribe” (or „Отказ“) or email valentin.kirilov@vivanheltprodjekts.com.
    • Upon receiving an opt-out, we immediately cease all contact, remove the message from active outreach records, and retain only the email address and corporate domain on our permanent suppression list pursuant to Articles 21(3) and 17(3)(b) EU GDPR / UK GDPR and Article 6(3) ECA so that we never message you again. If you explicitly request complete erasure from the suppression list as well under Article 17(1)(c) GDPR, we erase all records within 5 business days.

9. Right to Lodge a Complaint with a Supervisory Authority

If you believe your data protection rights have been infringed, you have the right to lodge a complaint with the competent Bulgarian supervisory authority under Article 77 GDPR and Article 38 of the Bulgarian Personal Data Protection Act:

  • Commission for Personal Data Protection (CPDP / КЗЛД)
  • Address: 2 Prof. Tsvetan Lazarov Blvd., Sofia 1592, Bulgaria
  • Phone: +359 2 91 53 519; +359 2 91 53 555
  • Email: kzld@cpdp.bg (complaints sent by email must be signed with a Qualified Electronic Signature – QES, submitted via the Secure Electronic Delivery System, or filed in paper form)
  • Website: https://www.cpdp.bg

Corporate recipients in the United Kingdom to whom the UK GDPR applies (Section 3.8) also have the right to lodge a complaint with the UK supervisory authority: the Information Commissioner's Office (ICO) (https://ico.org.uk, tel. +44 303 123 1113).


10. Children's Data and Special Categories of (Sensitive) Data

  1. Business-to-Business (B2B) services: The website vivanheltprodjekts.com and our services are intended for businesses, medical and dental practices, and adults (18 years and older). We do not knowingly collect personal data from individuals under 18 (or under the age of 14 for digital consent under Article 25c of the Bulgarian Personal Data Protection Act). If we become aware that such data has been submitted without basis, we delete it immediately.
  2. Do not send medical or patient data through our forms or chat: Although we build software and websites for clinics and healthcare providers, the offer request form and the chat assistant on vivanheltprodjekts.com (as well as our Messenger and WhatsApp channels) are strictly for business inquiries. Please do not submit health data, medical records, patient information, or any other special category data under Article 9 GDPR through these channels.

11. Language and Changes to This Privacy Policy

  1. This Privacy Policy is published in Bulgarian (https://vivanheltprodjekts.com/bg/privacy/) and English (https://vivanheltprodjekts.com/privacy/) with identical meaning. In the event of any discrepancy in interpretation between the two language versions, the Bulgarian version prevails.
  2. Whenever our data processing practices, technologies, or legal requirements change, we update this page and display the new version number, effective date, and a summary of changes at the top of the document.