Terms of Service

CodeBliss is operated by Texxet Company S.r.l., registered at [TO CONFIRM: registered address], VAT number [TO CONFIRM: VAT number]. You can reach us at [TO CONFIRM: legal email].

Payments are processed by Creem, which acts as merchant of record for the sale. Creem issues the invoice and handles tax; the work itself is delivered by us, and these terms govern that work.

You subscribe to a plan and send us requests about a product you already have. We work on one request at a time and deliver it asynchronously. We are not an emergency service, we are not on-call support, and we do not take phone calls as part of a subscription.

Lite includes 2 requests per billing cycle. Keep includes up to 8 requests per billing cycle, with 1 of them in progress at any moment. Project is not a subscription: it is a separate, one-time engagement, quoted after an evaluation.

Your billing cycle starts on the day you subscribe, not on the first of the month. Requests do not accumulate: whatever you have not used when the cycle ends expires, and does not move to the next cycle. We price a plan on the capacity we hold open for you during that month, which is why unused capacity cannot be banked.

Capacity is measured in slots. One slot is approximately three hours of work. A request that is bigger costs more than one slot: roughly two slots for half a day, three for a full day, five to six for two days.

We tell you how many slots a request costs before we start it, and you decide whether to go ahead. If a request turns out to be larger than it looked once work has begun, we stop and tell you, and you choose whether to spend the extra slots, reduce the scope, or move it to a Project.

Every request includes two rounds of revision. We send you a preview, you tell us what is wrong, and we correct it — twice.

A revision means correcting what you asked for. If what comes back is a new idea rather than a correction, it is a new request and costs its own slots. This boundary is what allows us to keep delivery times for everyone else in the queue.

Work that takes more than two or three days does not belong in a subscription. That includes a site or app built from zero, a large rebuild or structural redesign, and a full product with its own accounts, payments and administration. We will tell you when a request falls into that category and offer a Project evaluation instead.

Most requests are completed within two to three working days. This is what we aim for and what we normally achieve; it is not a guaranteed deadline, and we do not offer service credits for a late delivery. A request that costs several slots takes proportionally longer, and we say so when we price it.

If you use up your cycle and cannot wait, you can ask us for extra slots. We will confirm whether we have the capacity that month, quote a price, and send you a payment link. You pay only if you accept. Extra slots are not sold automatically, because we will not sell capacity we do not have.

You can pause or cancel your subscription at any time from your account. Pausing stops the billing and keeps your queue and your history; when you resume, you are not asked to buy a new plan.

Cancelling ends the subscription at the end of the cycle you have already paid for. Work that is in progress at that moment is completed; work still waiting in the queue is not started.

Once a request is paid for, the deliverable for that request is yours. You own the code, the content and the assets we produce for you, and you may use, modify and redistribute them without restriction.

We keep the right to reuse general techniques, patterns and non-confidential know-how, and to reuse our own pre-existing components, which are licensed to you for use within your product rather than transferred. Nothing here gives us a claim over your product.

To do the work we often need access to your systems. You grant that access, and you can withdraw it at any time. We treat anything we see in your systems as confidential, we do not use it for anything other than your requests, and we do not name you as a client publicly without your permission.

You remain responsible for keeping your own backups. We are not a backup service.

We take care with the work we deliver, and a senior developer reviews and tests every piece of it before it ships. We cannot, however, accept liability for indirect or consequential losses, lost profits, or loss of data beyond what you are protected by under the law that applies to you.

Our total liability in connection with the service is limited to the amount you paid us in the three months before the event giving rise to the claim.

These terms are governed by the law of [TO CONFIRM: jurisdiction]. If you are a consumer, nothing here removes the protections you have under the mandatory law of the country where you live.

If we change these terms, the change applies from your next billing cycle, not retroactively, and we tell you before it takes effect. If you do not accept a change, you can cancel before it applies.