The rules we publish in advance.

This website and the studio's engagements are for businesses and organisations. We do not sell to consumers, so these terms are written for a business relationship rather than a consumer one. They govern your use of this website, and they state the substance of an engagement with us; the agreement you sign governs your own engagement in detail.

The content on this website, its text, design, and code, is ours. You may read it and link to it. You may not copy, republish, or reuse it as your own without asking first. Use the site for what it is: do not try to break into it, do not scrape it at a volume that degrades it for other people, and do not send anything through its forms that is unlawful, deliberately misleading, or not yours to send.

We keep this website running with reasonable effort, but we do not warrant that it is always available or free of errors. Where it links to annxa.com, ui.ilinxa.com, GitHub, or any other third party, the link is a reference and not an endorsement of that site's own content or terms. If something here is broken or wrong, write to us at studio@ilinxa.com.

Every engagement is defined by a written scope: deliverables, sequence, and what is explicitly excluded. Changes to scope are agreed before they are built.

By default you receive a use license: we build, own, host and keep evolving the application, and you operate it under your own brand with full admin access. On request you can instead purchase the source code outright, at a significantly higher price. Which model applies is stated in writing before work begins.

Every engagement is priced in writing before any work starts, and the figures live in the agreement rather than on this page. Invoices follow the schedule that agreement sets, work begins once the first payment has been received, and if an invoice goes unpaid we may pause the work until it is settled. Taxes and transfer charges, where they apply, are stated in the agreement too.

Every build includes six to twelve months of support. Extension afterward is available and is priced before it starts, not after.

Support and the terms of the engagement hold only while Ilinxa is the sole party with developer-level access to what we built. The moment another developer writes into the system, we can no longer stand behind its behaviour, and the terms of the engagement no longer apply to it.

Deployment and DevOps work carry a separate fee unless the engagement states in writing that they are included.

Your material is confidential without expiry. We never showcase client projects, never share one client's project with another, and never sell an idea brought to us.

Ownership of what is built follows the licensing model chosen. Our own tooling, libraries, and pre-existing components remain ours in every case, and nothing in an engagement transfers them.

For any engagement, our total liability to you is capped at the fees you have paid us for that engagement. We are not liable for indirect or consequential loss, for lost profit, or for lost data beyond what the agreement provides for. Nothing here excludes or limits liability that the law does not allow us to exclude, including liability for death or personal injury caused by negligence, and for fraud.

Either side can end an engagement in writing. Work already delivered and paid for stays delivered; work in progress is invoiced up to the point it stops. Confidentiality, intellectual property, and the limits above survive the end of an engagement.

All agreements are digital and take effect on signature. Work on a project begins only after its agreement is signed. The signed agreement governs where it differs from this page.

Use of this website is governed by the laws of the Republic of Türkiye. Each engagement with the studio is governed by the law, and decided by the courts, that its own signed agreement names. Before either side goes to court, we will try to settle the disagreement by talking.