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. Scope, operator and binding offer
This policy describes delivery and access for ENERGOBUILD digital research reports, datasets, software-related deliverables and other expressly described electronic products if and when sales are activated. Proposed seller: ENERGO BUILD LTD. / „ЕНЕРГО БИЛД“ ООД, EIK 207451381, subject to current registry and merchant verification. The actual product page, order confirmation and negotiated statement of work control the precise deliverable and delivery date, without reducing mandatory rights. Online payments are not currently available through this website.
2. Digital content, digital service and bespoke work
A downloadable report may constitute digital content not supplied on a tangible medium. A continuously accessible database may be a digital service. Individually researched engineering or consulting work may instead be a service even when its output is a PDF. Mixed orders require component-by-component classification; rights under Directive (EU) 2019/770 must not be applied mechanically to every bespoke service. A physical device with digital elements can be governed by different sales rules. The product-specific legal classification must be completed before checkout.
3. Pre-contract technical disclosures
Before payment, the offer must clearly identify title, edition, scope, format (for example PDF, CSV or XLSX only if actually offered), file size or limits where material, language, required reader/software, operating-system or browser dependencies, accessibility features, licence, update entitlement, delivery channel and timing. Any watermark, DRM, usage cap, expiry, geographical limitation or device restriction must be disclosed before the consumer is bound. Do not advertise machine-readable datasets, source code, guaranteed updates or lifetime access unless contracted and deliverable.
4. When supply legally occurs
For applicable consumer digital-content contracts, Article 5 of Directive 2019/770 treats supply as completed when content or a suitable means of access or download is made available or accessible to the consumer, or to a chosen facility. The default is supply without undue delay unless otherwise agreed. This legal test is not identical to email sent, payment authorized, invoice issued, URL generated or file actually opened. The merchant bears the statutory burden of proving supply; retain evidence of genuine accessibility, not merely a server-side event.
5. Payment-to-fulfilment authorization
Automated paid delivery, if implemented, should follow verified payment status from an authorized PSP and a trusted server-side transaction reference. A client-side redirect, screenshot, unpaid invoice, pending authorization or forged callback must not independently grant a paid entitlement. The system should distinguish authorized, captured/settled where applicable, failed, reversed, refunded and disputed states. Duplicate webhook delivery and network retries require idempotent processing; no live PSP connection or checkout is confirmed.
6. Permitted secure delivery channels
The chosen channel may be a secure customer portal, authenticated download page or verified email carrying a time-limited link, as explicitly described in the offer. Sensitive paid files should not be published at guessable permanent public URLs. Access controls should bind entitlements to the correct order or verified customer, use HTTPS, avoid exposing tokens in analytics/referrers, limit token scope, and permit revocation where justified. The particular mechanism, TTL and hosting vendor are pending technical selection and must not be asserted as deployed.
7. Delivery times and delays
For instantly supplied catalogue content, the offer should state when access will become available, subject to payment verification and lawful withdrawal-consent controls. For custom research, an agreed timetable, dependencies, acceptance milestones and change procedure must be provided; no fictitious “instant delivery” promise. The merchant must notify the buyer of material delays through a verified channel, state the reason and revised estimate, and preserve applicable rights to demand supply, terminate or seek remedies. A technical queue does not extinguish legal deadlines.
8. Download limits, expiry and re-access
Any expiry of a link, download-count cap, account suspension rule, re-download availability, replacement entitlement or retention period must be specified in the product offer. Expiry of a security token is not necessarily expiry of a contractual licence or statutory remedy. Where a valid buyer cannot access a purchased file due to a token expiry, the merchant should provide a secure reissue path without imposing unlawful additional fees. No fixed 24-hour or seven-day lifetime is promised without verified infrastructure.
9. File integrity, authenticity and versioning
The seller should maintain a release register identifying SKU, edition, language, release date, filename, format, size and cryptographic SHA-256 checksum for each approved artifact. Before distribution, scan for malware and verify that the download corresponds to the advertised version; a checksum alone does not prove malware freedom or scientific accuracy. Material corrections require documented versioning and a notice to affected customers where contractually or legally necessary. A draft must never be silently substituted for a purchased approved edition.
10. Compatibility, interoperability and accessibility
Relevant minimum hardware/software requirements, supported readers, encryption, assistive-technology compatibility and known material limitations should be disclosed. Digital content must meet applicable contractual and statutory subjective/objective conformity requirements, including necessary updates where legally required. Provide accessible document structure and usable alternatives where required by applicable accessibility law; WCAG 2.2 AA may be used as an engineering target but does not by itself establish legal compliance. No untested certification or universal device support is claimed.
11. Non-delivery and troubleshooting
If access fails, the customer should contact energobuild.contact@gmail.com with order reference, approximate time, error description and device/browser information as needed, without sending full card data or passwords. The seller should verify the order, entitlement, link state, file integrity and delivery endpoint, then provide lawful resupply or another remedy. Under Directive 2019/770 Article 13, consumers may call upon the trader to supply; continued failure may permit termination, with exceptions allowing immediate termination. Do not require excessive troubleshooting before honoring statutory remedies.
12. Conformity and statutory remedies
An unreadable, incomplete, corrupted, wrong-language or materially misdescribed deliverable may lack conformity. The trader must assess free correction within a reasonable time and without significant inconvenience, proportionate price reduction or termination under applicable conditions. A successful HTTP 200, email dispatch or single download click does not conclusively establish contractual conformity. The burden-of-proof rules of Directive 2019/770 and Bulgarian implementing law must be respected, including the distinction between supply proof and conformity proof.
13. Withdrawal consent versus delivery
The immediate delivery of non-tangible digital content may affect the 14-day withdrawal right only where all conditions of the relevant exception are satisfied, including prior express consent, acknowledgement of loss of withdrawal and required durable-medium confirmation. These controls must be separate from general Terms acceptance and not pre-ticked. An individually performed professional service follows different early-performance rules. Even lawful loss of withdrawal does not remove statutory non-supply or conformity remedies; the Refunds and Withdrawal policy controls refunds and withdrawal.
14. Durable-medium order and delivery confirmation
Where legally required, the customer must receive durable-medium contract confirmation containing the required pre-contract information, order identity, seller details, total price and currency, purchased edition, delivery conditions and any express digital withdrawal consent/acknowledgement. A transient web toast or modifiable account screen alone may not qualify. Separate operational notifications should identify order received, payment status, access ready and fulfillment exceptions without falsely claiming completed delivery. The exact email/SMS/portal implementation is not verified.
15. Delivery evidence and dispute audit trail
A proportionate fulfillment record should link order ID, contracted SKU/version, verified payment event, entitlement creation, delivery channel, token issue/expiry, server access response, failed attempts, customer notices and correction/reissue events. Record timestamps with timezone, immutable event identifiers and appropriate access restrictions. Evidence should demonstrate availability to the correct buyer without assuming that a click equals comprehension or satisfaction. Log integrity, retention and the legal burden of proof must be reviewed before production.
16. Personal data, GDPR and processor roles
Order, billing, account, IP, download-event and support records may contain personal data. Processing requires a documented purpose and GDPR Article 6 basis, data minimization, proportionate retention, access controls, vendor Article 28 agreements where applicable and lawful international-transfer safeguards. Avoid placing email addresses or sensitive identifiers in public download URLs and analytics events. Actual Wix storage, Velo scripts, email providers, logging and subprocessors must be mapped; Wix vendor documentation does not establish the site's specific data flows. See Privacy Notice and Cookie Policy.
17. Security, incidents and recovery
The delivery system should apply least-privilege access, secret management, HTTPS, validated authorization, abuse rate limits, integrity checks, secure backups and incident procedures proportionate to risk. An expired link should not reveal whether another person purchased a report. Security incidents affecting personal data must be handled under GDPR breach-assessment and notification rules where applicable. Service recovery should avoid duplicate fulfillment, unintended free entitlements or deletion of lawful customer records. No ISO, SOC, PCI or end-to-end security certification is asserted.
18. B2B acceptance, revisions and bespoke deliverables
A genuine B2B statement of work may define secure exchange, acceptance tests, milestone dates, review windows, permitted revisions, confidentiality, export formats and sign-off authority. A professional report's transmission is not automatically acceptance if the agreement requires review. The contract should distinguish a deliverable defect from a request for expanded scope, and define documented change orders. B2B arrangements cannot waive mandatory consumer rights where the buyer is legally a consumer. Any engineering estimate remains subject to the agreed limitations and professional standards.
19. Third-party material, licences and updates
Reports may include licensed datasets, charts or excerpts subject to rights and permitted use. Delivery transfers only the licence expressly described in the offer and the Research Licence and Intellectual Property policy; it does not assign all intellectual property by default. Source attribution, redistribution limits and export restrictions must be disclosed when applicable. Whether post-sale updates, corrected editions or continued access are included must be stated; mandatory conformity/security updates cannot be excluded by a generic “no updates” disclaimer where the law requires them.
20. Customer support, escalation and languages
Delivery assistance must be reachable through energobuild.contact@gmail.com and any other verified channel specified before purchase. The seller should acknowledge and track incidents, prioritize inability to access paid content, and provide a written resolution or statutory remedy without unjustified delay. English and Bulgarian descriptions, file versions and support paths must be consistent; no unverified telephone number should appear. Public legal links must be functional on mobile, tablet and desktop. Any applicable consumer authority or judicial remedies remain available.
21. Refund, chargeback and revocation boundaries
A refund, chargeback or contract termination may justify revocation of future licensed access under applicable law and agreement, but must not destroy evidence, personal-data rights or access to content the customer is legally entitled to retrieve. Duplicate PSP notifications must not cause duplicate refunds or irreversible loss of unrelated purchases. The Purchases, Pricing and Taxes policy governs prices and currency; the Refunds and Withdrawal policy governs withdrawal and refunds. A card payment dispute does not replace statutory remedies.
22. Delivery information and existing rights
For a digital product sold online, check the offer and order confirmation for delivery details. Where required, the applicable information is provided on a durable medium. Later changes to delivery arrangements do not remove existing contractual entitlements or rights guaranteed by applicable EU or Bulgarian law.