Terms and Conditions

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.

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.

As a general policy, payment is split into two equal parts: a 50% deposit upon accepting the proposal, which starts development, and the remaining 50% at the pre-delivery session, before going live (see section 10 for cancellation terms). The payment method and any case-by-case variation 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.

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 no later than the pre-delivery session. If the technical nature of a specific transfer prevents this at that moment — for example, lock periods imposed by the registrar after registering a domain or changing its owner —, we let you know and give an estimated timeframe for completing it, without this affecting delivery of the rest of the project.

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, except for any occasional or ongoing access the client grants us to provide contracted maintenance (see section 6), which is governed by the terms of that service.

Access credentials are shared through a reasonably secure channel, avoiding, as far as reasonably possible, sending them in plain text over unencrypted channels.

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. This includes, for example, the proprietary panel we use in Self-Managed Sites (Konssor), whose core we continue to use and maintain for other clients, and which is not part of the project's code assignment.

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

Once development is complete, we invite the client to a pre-delivery session where we present the site as agreed in the proposal. From that session, the client has up to one week of margin to request specific adjustments regarding deviations from what was agreed; requests beyond that scope are quoted separately, as an extension (see section 2).

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.

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.

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.

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.

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.

In any case, our total liability to the client for causes arising from this contract does not exceed the amount actually paid for the project, except where applicable law does not allow it to be limited (for example, willful misconduct, gross negligence, or damages that cannot be limited under consumer protection law).

Upon accepting the proposal, the client pays 50% of the total project value to begin work, as a deposit; the remaining 50% is paid at the pre-delivery session, before going live. If the client decides to withdraw from the project at any point after paying the deposit — including during the adjustment margin following pre-delivery —, that 50% is non-refundable, and in exchange the client receives the setup built up to that point (code, database, and infrastructure, as applicable to the project's stage). This handover is a material delivery only and does not transfer intellectual property rights beyond a license for the client to use and modify that code; it is delivered as-is, with no guarantee of functionality or completeness.

If the client decides not to continue with the project at any point before the pre-delivery session, or stops responding for more than 30 days, they have 48 hours from that decision (or from the end of that inactivity period) to claim, in writing, the code produced up to that point. After that period, if no claim is made, that code is not considered a deliverable, and Bicho de Luz may keep or delete it at its discretion, as it constitutes internal development work.

Cancellation by the client is valid and takes immediate effect regardless of the means used to communicate it — message, phone call, or verbally —, with no need to sign an additional cancellation document. As a safeguard, we may confirm the cancellation in writing; if the client does not object within 48 hours, it is deemed accepted.

If no cancellation occurs, and final delivery has already happened or the delay is attributable to the client (see "What we need from you"), the project is automatically considered closed and completed twenty (20) business days after the proposal is accepted, unless that period is extended due to client delays or a different delivery timeframe expressly agreed in the proposal. If the delay at that point is attributable to Bicho de Luz, automatic closure does not apply and the project remains open until effective delivery.

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.