Last updated: August 2, 2026

Terms and Conditions

These Terms and Conditions govern the relationship between Bicho de Luz (“we,” “us,” or “the provider”) and the client who commissions the development of a website and, optionally, its ongoing maintenance.

1. Purpose and scope

These Terms and Conditions apply to the three types of projects we offer: High-Impact Sites (static), Self-Managed Sites (with an admin panel and database), and Advanced Management Sites (complex, multi-role systems). The type of project is defined in the proposal accepted by the client.

These three project types are also marketed under their own brand names — Relik (High-Impact), Konssor (Self-Managed), and Rama (Advanced Management) — without this implying a different service or category from those defined here: they are simply the commercial name for the same category.

2. Budget, payment terms and closed scope

The budget is provided in writing before work begins, based on the scope described in the proposal. Once accepted, the price is not reopened unless the client requests new functionality not included in the original scope — in that case, the additional work is quoted separately, as an extension, before it is carried out.

Payment terms (deposit, installments, payment method) are detailed in each individual proposal. Development of the project, and in particular the final handover of access and code (see section 5), is subject to payments being up to date.

3. Infrastructure and access

As a general rule, we create all the infrastructure the project needs (domain, hosting, database, code repository) under an email account dedicated to the client's project, and transfer it to the client once the work is complete.

At the client's explicit request, and only in specific cases agreed before the project starts, the client may create their own accounts from the outset.

In both cases, ownership of the domain, hosting, database, repository and their access credentials belongs to the client. We retain no control over any of these once delivery is complete.

4. Ownership of code and content

Source code developed specifically for the client's project becomes the client's property once the agreed payment has been paid in full. General-purpose tools, libraries or components that we developed independently of the project — and that are not exclusive to it — may continue to be reused by us in other projects.

Content uploaded by the client (text, images, video, business information) is and remains the client's exclusive property at all times.

5. Delivery, acceptance and claim period

Once development is complete, we hand over full access documentation to the client (usernames, passwords, the location of each piece of infrastructure). The client is asked to change those credentials, if desired, within 48 hours of delivery.

The client has 30 calendar days from the delivery date to raise claims or observations about the code repository and the access delivered. After that period, delivery is considered accepted and closed, and claims about access or handovers already completed will not be processed. It is the client's responsibility to verify the material received within that period.

Within that same 30-day period, any functional error relative to what was specified in the requirements document of the accepted proposal is fixed at no charge. After that period, or if the error originates from content changes, third-party integrations, or uses not contemplated in that document, the fix is quoted separately under section 6.

6. Maintenance and post-delivery support

Maintenance is not included by default in the initial development, unless expressly contracted. For High-Impact and Self-Managed Sites, support is billed hourly, with an optional quarterly review; for Advanced Management Sites we offer fixed-fee plans, or hourly support if the client doesn't contract one of them.

7. Confidentiality

We commit to not disclosing confidential business information of the client that we access during the project (customer data, business information, credentials), except where legally required. This obligation remains in effect after the project ends.

As a specific exception, expressly authorized by each client, we may display on this site and in our presentation materials the name, industry, and general results of their project as a reference case. Any client may request at any time that their case be removed from display.

8. Content responsibility and data protection clause

All content the client publishes on their site (text, images, video, catalogs, their own customers' or users' data, business information) is and has always been their exclusive property and responsibility, as set out in section 4. Once the site is handed over to the client, we do not control, moderate, or take responsibility for that content.

When the contracted project requires it, we create a Terms and Conditions page and a Privacy Policy page for the client's site as a starting point. It is the client's sole responsibility to complete them, adapt them to their actual business activity and the data they actually collect or publish, and keep them up to date while using the site.

We are not responsible for inaccuracies, omissions, or regulatory non-compliance arising from the specific content the client uploads to those pages, nor for how the client processes their own users' or customers' data through their site (for example, contact forms or their own user databases).

If the project involves processing third parties' personal data, both parties commit to complying with the data protection regulations applicable in the client's jurisdiction. At the time of delivery (section 5), we expressly record that all information published on the site — including the protection of data of those who visit or use it — is the client's responsibility, as the owner of the site and the business.

9. Limitation of liability

We are responsible for correctly executing the work commissioned, but we do not guarantee business results that depend on factors outside our control (for example: exact search engine rankings, sales volume, or leads generated). We are also not responsible for service interruptions caused by third-party infrastructure providers (hosting, domain, database) outside our direct control, although we are responsible for configuring that infrastructure correctly and for assisting the client in resolving incidents within the contracted maintenance plan.

10. Early project cancellation

Upon accepting the proposal, the client pays 10% of the total project value to begin work, as a deposit. If the client decides to withdraw from the project at any point after that payment, that 10% is non-refundable — in exchange, the client receives the setup built up to that point (code, database, and infrastructure, as applicable to the project's stage).

Beyond the initial deposit, if the client decides to cancel the project before completion, the work actually performed up to that point is billed, as agreed in the proposal. The material produced up to the cancellation (code, designs) is delivered to the client once that partial invoice is settled.

11. Governing law, jurisdiction and term

These Terms and Conditions are governed by Spanish law. In the event of any dispute arising from the business relationship, both parties will first attempt an amicable resolution; failing that, they submit to the Spanish Courts and Tribunals with competent jurisdiction under applicable law. If the client is a consumer residing in the European Union, this clause does not deprive them of the protection granted by the mandatory provisions of the law of their country of residence.

These Terms and Conditions may be updated. The version in effect at the time a proposal is accepted governs that business relationship, unless otherwise explicitly agreed in writing.

Questions about this document? Get in touch.

Message us on WhatsApp