Detailed legal provisions
The numbered provisions below set out the relevant policy and contractual framework. Details that depend on a particular transaction or processing operation should be confirmed directly with the company before relying on them.
1. Identity, scope and transparency
1.1. This notice explains how personal data may be processed in connection with ENERGOBUILD.eu, including browsing, enquiries, prospective professional engagements, and future transactions if enabled.
1.2. Proposed controller: ENERGO BUILD LTD. / „ЕНЕРГО БИЛД“ ООД, EIK 207451381, Bulgaria. The corporate identity derives from dated project evidence and requires current official-register verification. Registered office: Burgas 8000, 10 Apostol Karamitev Street, floor 5, office 13, Bulgaria. Direct privacy contact: energobuild.contact@gmail.com. General business contact: energobuild.contact@gmail.com.
1.3. For questions about the processing of your personal data, use the privacy contact above.
1.4. The controller decides the purposes and means of its own processing. A hosting or software provider may act as processor for specified functions and as an independent controller for its own separately determined purposes. This distinction must be checked against actual contracts and configuration.
2. Scope of data subjects and services
2.1. This notice concerns website visitors, people who send enquiries, corporate representatives, prospective customers, suppliers and — only if functionality becomes active — registered account holders, purchasers and newsletter recipients.
2.2. The website's published Wix context confirms an Editorless site, Velo enabled and installed Wix Forms, Wix Hotels and Wix Invoices V2. Installation is not evidence that an app is used, enabled for visitors, or currently collecting their data. The precise front-end components, back-end calls, forms, tracking tags and integrations remain to be audited.
2.3. Links to third-party sites or payment platforms may be governed by separate privacy notices. A prospective payment integration is not treated as operational merely because it appears in planning documentation.
3. Categories and sources of personal data
3.1. Website technical data — conditional on actual collection: IP address, approximate location derived from IP, request date/time, user-agent, device and browser attributes, requested URLs, network or error logs, cookie identifiers and security signals.
3.2. Enquiry data — if forms or email are active: name, company, job title, business email, telephone voluntarily supplied, subject, message, requested service and correspondence history. Do not submit payment-card secrets, identity documents or special-category data through a general contact form.
3.3. Contract and transaction data — future conditional category: contracting entity, representative, order identifier, purchased edition or service, billing address, applicable tax information, currency, payment status, delivery confirmation, complaint and refund records. Payment providers may process payment credentials directly; the controller's actual access must be documented and must not be exaggerated.
3.4. Marketing preferences — only if implemented: independently evidenced opt-in, timestamp, channel, notice version and withdrawal or objection status. A contact enquiry is not itself consent to unrelated marketing.
3.5. Research, recruitment, supplier or professional correspondence — if actually processed: contact details, professional role, documents and relevant communications, limited to a specified lawful purpose.
3.6. Indirect sources: corporate websites, publicly available professional registers or referrals may supply professional contact information, subject to Article 14 GDPR transparency and applicable exceptions. No bulk scraping or purchased database is presumed.
3.7. Special categories under Article 9 GDPR and criminal-conviction data are not intended for general site collection. If inadvertently received, access and retention must be minimized and lawful handling evaluated.
4. Purposes and legal bases — processing register
4.1. Site transmission, availability and security: technical delivery, service integrity, prevention of abuse and incident investigation; possible bases Article 6(1)(f) legitimate interests or Article 6(1)(c) legal obligation, as appropriate. The specific interest, necessity and balancing test must be documented.
4.2. Replying to a business enquiry: Article 6(1)(f) legitimate interest in responding to professional contacts or Article 6(1)(b) pre-contractual steps requested by a natural-person prospective customer, depending on circumstances. Do not apply Article 6(1)(b) indiscriminately to every employee of a corporate client.
4.3. Providing contracted products/services: Article 6(1)(b) for processing necessary to a contract with an individual data subject; Article 6(1)(f) for appropriately assessed corporate-representative administration; Article 6(1)(c) for tax and accounting duties.
4.4. Payments, invoicing and statutory records: Article 6(1)(b) and/or (c) where applicable, with Article 6(1)(f) for proportionate fraud prevention where justified. No actual payment processing is verified.
4.5. Non-essential analytics, advertising and similar terminal-equipment access: prior consent where required by ePrivacy rules, with a separately valid GDPR basis for subsequent personal-data processing. Consent must be freely given, specific, informed, unambiguous, demonstrable and withdrawable.
4.6. Direct electronic marketing: applicable Bulgarian electronic communications and marketing rules, including consent where required; any legally permitted existing-customer exception must be verified rather than assumed. Record opt-outs and honor objections.
4.7. Disputes and legal claims: Article 6(1)(f) for establishing, exercising or defending lawful claims, or Article 6(1)(c) for mandatory legal process, with appropriate proportionality and retention.
4.8. A legal basis is determined for each real processing operation before activation. Listing a possible legal basis does not mean the corresponding processing takes place.
5. Wix platform and processing roles
5.1. The site is hosted and managed using Wix technology. Wix documentation describes the site owner as controller of visitor data processed for its purposes and Wix as processor for relevant site-owner processing. Wix may separately act as controller for its own services; the exact role must be checked against the current agreement and operation.
5.2. Wix's published subprocessor list includes Wix entities and external suppliers in multiple jurisdictions. Wix's own privacy notice is not a substitute for ENERGOBUILD's controller notice.
5.3. Installed Wix Forms warrants an audit of field names, recipient addresses, submission storage, automations, spam filtering, retention and data-subject deletion mechanisms. No public submission has been performed in this audit.
5.4. Installed Wix Hotels warrants a determination of whether accommodation or booking functions are exposed or simply dormant. Do not mention hotel reservations as an actual ENERGOBUILD activity without verification.
5.5. Installed Wix Invoices V2 warrants an audit of whether invoice records, contacts or payment links are used. Do not claim invoicing or checkout is active without evidence.
5.6. Velo scripts and any headless front end require review of network requests, external APIs, cookies, embedded assets, access permissions, server-side logs and secrets handling. The observed legal-page 404s do not establish what personal data are collected.
6. Cookies, local storage and tracking
6.1. You can review or change available categories using Cookie settings. Previously saved preferences may still apply.
6.2. According to Wix's Headless Site Script documentation, the script stores an anonymous visitor token in browser localStorage under a key beginning with wixSiteScript: followed by the public Headless client ID. Wix describes the token as supporting visitor recognition, analytics and scripts that it loads; the token is not an administrator credential or a client secret, and that token itself is not set as a first-party cookie. This is documented provider behavior, not a measured list of this site's live browser storage. The real key, retention, identifiers, origins, third-party integrations and network activity still require an EN/BG clean-session audit before release.
6.3. The bilingual on-page cookie settings interface uses Wix's consent policy manager when available and submits a visitor's selection only on an explicit action. A choice must not be represented as stored unless the manager confirms it; if the manager is unavailable or errors, the control must explain that persistence is unconfirmed. As Wix's consent-runtime documentation describes, current visitor settings may differ from the site default, and a change may require a refresh. A real hosted verification is required before claiming that scripts are blocked before consent or that withdrawal functions end to end. Declining optional categories must not block core information pages.
6.4. The separate Cookies Policy and the cookie-settings control must identify actual vendors and storage technologies; a generic “we use cookies” statement is insufficient.
7. Recipients and disclosures
7.1. Potential recipient categories, subject to verification, include hosting and cloud providers, form delivery and email providers, customer-support tools, IT security vendors, accounting advisers, professional legal advisers and — if approved — payment processors.
7.2. Disclose only information necessary for the purpose, under an appropriate processor agreement where GDPR Article 28 applies. Evaluate each provider's controller/processor role, subprocessor authorizations and confidentiality obligations.
7.3. Data may be disclosed to authorities when required by a valid legal obligation or lawful request, subject to applicable safeguards and transparency restrictions.
7.4. Personal data are not sold as a commercial product merely by operating the Website; any definitive statement that data are never sold or shared must first be checked against actual analytics and advertising integrations.
8. International transfers and safeguards
8.1. Wix publicly states that visitor data may be processed in Israel and in other jurisdictions through affiliates and subprocessors. It describes potential storage locations including the United States, Ireland, South Korea, Taiwan and Israel. These are vendor-level possibilities, not verified actual ENERGOBUILD data flows.
8.2. Transfers to a destination covered by an applicable European Commission adequacy decision may rely on Article 45 GDPR within its precise scope. The Commission lists Israel as adequate; the US adequacy decision applies only to participating certified organizations under the EU–US Data Privacy Framework, not all US recipients.
8.3. For transfers without applicable adequacy, appropriate Article 46 safeguards may include the European Commission's Standard Contractual Clauses, supplemented by a transfer impact assessment and additional measures when necessary. Article 49 derogations are exceptional and not a routine substitute for a transfer mechanism.
8.4. For information on safeguards applicable to a specific transfer or to request a copy of those safeguards, use the privacy contact in this notice. This notice does not state that data are stored only in the EU.
9. Retention, deletion and record integrity
9.1. Personal data must be retained no longer than necessary for the documented purpose, subject to applicable statutory accounting, tax, limitation, consumer and security obligations.
9.2. Actual retention periods remain unverified. The controller must approve a schedule by data category: security logs period not yet confirmed; enquiries period not yet confirmed; customer contracts period not yet confirmed; invoices period not yet confirmed against applicable law; consent records period not yet confirmed; support cases period not yet confirmed.
9.3. The final notice must publish the actual period or objective criteria for each significant category. Backup retention and processor deletion timelines must be reconciled with Wix and other vendors.
9.4. Deletion requests are assessed against lawful retention obligations; deletion from a visible form entry does not automatically mean erasure from all backups and processors.
10. Security and breach response
10.1. The controller must implement risk-appropriate technical and organizational measures under GDPR Article 32, including access controls, least privilege, secure transmission, appropriate logging, backup recovery and vendor oversight, to the extent required by the actual risks.
10.2. This notice does not claim ISO 27001, SOC 2, PCI DSS or encryption certification for ENERGOBUILD. Vendor compliance statements do not automatically certify the site's entire implementation.
10.3. Suspected personal-data breaches must be investigated and documented. Where Article 33 applies, notification to the competent supervisory authority is generally due without undue delay and, where feasible, within 72 hours after awareness unless the legal risk threshold is not met. Article 34 communications to affected people are assessed separately.
10.4. Incident contact: energobuild.contact@gmail.com.
11. Individual rights and requests
11.1. Subject to legal conditions, people may request access, rectification, erasure, restriction, portability and object to processing; consent may be withdrawn at any time without affecting earlier lawful processing.
11.2. Where processing relies on legitimate interests, a person may object on grounds relating to their particular situation. Objection to processing for direct marketing must be honored in accordance with Article 21 GDPR.
11.3. Requests may be sent to energobuild.contact@gmail.com. The controller may verify identity proportionately without routinely demanding excessive documents. Requests must be assessed without undue delay and generally answered within one month, with lawful extensions where justified.
11.4. A request may be refused or limited only where GDPR permits, with reasons and information on available complaint or judicial remedies. Data portability applies only where its statutory conditions are met.
11.5. The controller must provide accessible procedures and, where relevant, coordinate with Wix or other processors to retrieve, correct or delete data.
12. Automated decisions, profiling and AI
12.1. No solely automated decision producing legal or similarly significant effects is verified for this Website. No individual profiling or personalized advertising system is assumed to be active.
12.2. If such processing is later introduced, the controller must separately assess GDPR Article 22, transparency, lawful basis, meaningful information about the logic and effects where required, and applicable human intervention and contestation rights.
12.3. Any use of AI assistants to process customer enquiries or professional documents requires an approved data-flow inventory, confidentiality controls, appropriate provider agreements and purpose-specific transparency before activation.
13. Children and special-category data
13.1. The Website is intended for corporate and professional information and is not designed to solicit personal data from children. This is not a claim that all visitors are adults.
13.2. If an information-society service is directly offered to children based on consent, the applicable Bulgarian age and parental-authorization rules must be verified before deployment.
13.3. Users should avoid including health information, government identifiers, biometric data or other sensitive content in general enquiries. Unsolicited sensitive information should be handled under a documented minimization and deletion procedure.
14. Supervisory authority and complaints
14.1. Individuals may lodge a complaint with the competent supervisory authority, including the Bulgarian Commission for Personal Data Protection (CPDP/KZLD) where appropriate, and may seek judicial remedies under GDPR.
14.2. The controller should provide the verified official CPDP contact details and website in the approved public edition: official CPDP contact page (kzld@cpdp.bg). Complaints to the controller are welcome but do not prevent regulatory complaints.
14.3. A person may also contact a supervisory authority in the Member State of habitual residence, place of work or alleged infringement as provided by GDPR Article 77.
15. Changes, languages and accessibility
15.1. This notice is available in English and Bulgarian.
15.2. If you have questions about which information applies to your enquiry or transaction, use the privacy contact in this notice.
15.3. If you cannot read or access this notice, you can ask for a copy in an accessible format.
15.4. Nothing here restricts rights under GDPR, Bulgarian law or applicable electronic communications rules.