1. Who we are
These terms govern your use of steinnlabs.ae and any engagement you agree to with Steinn AI Labs Limited ("Steinn Labs", "we", "us", "our").
Steinn AI Labs Limited is a private company incorporated in the Dubai International Financial Centre (DIFC), United Arab Emirates, under registration number SR-808691, holding commercial license CL13762. Our registered office is IH-00-01-03-OF-05, Level 3, Innovation One, Dubai International Financial Centre, Dubai, United Arab Emirates.
We design and build software, data and artificial intelligence systems, and we provide technology consultancy. We are not a bank, an insurance company, a regulated financial institution, a law firm, or a medical device or clinical services provider.
2. Using our website
You may use this website to read about our work, make an enquiry, and find contact details. You agree to use it lawfully and not to:
- attempt to gain unauthorised access to the site, its servers, or any connected system;
- scrape, harvest, or systematically extract content, including by automated means, without our written permission;
- upload malicious code, or interfere with the availability or integrity of the site;
- reproduce our name, logo, or substantial parts of the content except to consider or act on an engagement with us.
The website and its content are provided for general information. Nothing on it is legal, regulatory, investment, tax, or medical advice, and nothing on it is a binding offer.
The site, its design, text, graphics, and original illustrations are our property or are used with permission. You keep the rights to what you send us.
3. Enquiries, bookings and no obligation
Submitting an enquiry, booking a call, or requesting a two-week sprint brief creates no obligation on either side until a written agreement is signed. It tells us you would like to talk.
We aim to reply to enquiries within one business day where possible. We may decline an enquiry, and we may ask for information about your problem, your data, and your access requirements before agreeing to work together.
Information you send in an enquiry is treated under our Privacy Policy. Please do not send confidential or sensitive data until we have agreed how it will be handled.
4. Written agreements take priority
Where we work together, the operative document is the agreement we sign with you: a master services agreement, an order form, a statement of work, or a written confirmation of a paid two-week sprint.
If anything in these terms conflicts with a signed agreement, the signed agreement prevails for that engagement. These terms fill the gaps: they cover the website, pre-contract communications, and any work where no signed document exists.
Only a person with authority to bind the company may agree an engagement, a price, or a change to one. We will not treat an approval from an individual team member as a contractual acceptance unless that person is named in the agreement.
5. Scope, estimates and changes
For fixed-scope work, the order form states what is included, what is excluded, the price, the schedule, and the acceptance criteria. Work outside that description is additional.
Estimates and dates are our good-faith planning figures. They assume access, decisions, and data arrive when agreed. Where a delay is caused by something outside our reasonable control, including waiting on access or approvals, we will adjust the schedule with you rather than treat it as our breach.
Changes are normal in software and AI work. Where a change affects price or dates, we will set out the effect in writing before proceeding, so you can approve it knowingly.
Where work is time-based, we record hours and share them with you on request, so the billed position can be checked against the work.
6. What we need from you
To deliver, we typically need the following from you, and you agree to arrange them or tell us early when you cannot:
- access to the systems, repositories, environments, and data the work requires, limited to what is necessary;
- a named person who can answer questions and approve decisions within the agreed time;
- confirmation that you have the rights and lawful basis to share the data and materials you give us;
- a working environment that matches what the order form describes, including test data where testing is in scope;
- timely review of work in progress, so problems surface while they are still cheap to fix.
7. Fees, invoicing and payment
Fees, currency, and payment terms are set out in the order form. Where no term is stated, payment is due within 14 days of the invoice date.
We invoice in advance for a paid sprint, and in instalments or on milestones for longer work, as the order form states. Where the engagement is ongoing and monthly, either side may end it on the notice stated in the agreement.
If payment is late, we will tell you in writing and may pause work until the position is cleared. Pausing work for non-payment is not a termination, and we will restart when payment is received.
We do not charge for the time our wider team spends on review and support behind an engineer unless the order form says so. If a cost is not written down, it is not payable.
8. Taxes
Our prices are quoted in the currency stated in the order form. Unless we say otherwise in writing, they exclude any sales tax, value added tax, withholding tax, or similar duty that applies.
You are responsible for determining and paying any tax you owe on your side of the transaction, including withholding tax where it applies in your country. Where we are required to withhold or charge something by law, we will show it separately on the invoice.
9. Intellectual property
What you bring stays yours. What we build for you under an order form transfers to you once the related invoice is paid, as the agreement states.
We keep our own pre-existing tools, libraries, frameworks, and know-how, including internal utilities we have built over previous engagements. Where those form part of the delivery, you get a perpetual, royalty-free licence to use them as part of the delivered system, and we can hand over their source where it is ours to give.
Open-source components stay under their own licences. We list them and their licences in the handover documentation so your team can check obligations before distribution.
We do not take ownership of your data, your models trained on your data, or your business records, at any point.
10. Confidentiality and data
Each side keeps the other's confidential information private, uses it only for the engagement, and shares it only with people who need it and are bound to the same terms.
Personal data is handled under our Privacy Policy and, where we process data on your behalf, under a data processing agreement that names the purpose, the data, the sub-processors, and the security measures.
Our day-to-day handling rules, including least-privilege access, secrets in a vault, and access revocation at the end of work, are published at /how-we-engage/security-data-handling.
Confidentiality obligations continue after the engagement ends and do not apply to information that is already public, lawfully obtained from elsewhere, independently developed, or required to be disclosed by law.
11. AI use, human review and decisions
We use AI assistants and automated tooling in our own work, including for drafting, code review support, testing, and documentation. A named engineer remains accountable for what we deliver and reviews it before it reaches you.
Systems we build are designed so that consequential decisions stay with a person unless your written approval says otherwise. Where a system informs a decision about an individual, we design in review, evidence, and an override path.
AI output can be wrong, incomplete, or out of date. Model behaviour, accuracy, and cost change over time. We test and monitor, but we cannot guarantee that any model, including a third-party model, will produce a particular result.
You remain responsible for how the systems you operate are used, including approvals, customer communications, and any decision taken with their help.
12. Regulatory responsibility
You decide which licences, approvals, notifications, and filings your business and your products need, and you tell us the constraints that apply. We build inside the boundaries you set.
We can help you prepare evidence, documentation, audit trails, and controls that support your own compliance work. We do not give legal or regulatory advice, we do not act as your regulatory representative, and we do not obtain approvals on your behalf.
Where an engagement touches regulated activity, including health, financial services, or personal data, the order form records who owns each obligation, so accountability is written down rather than assumed.
13. Warranties and disclaimers
We warrant that we will carry out the work with reasonable skill and care, in line with the standards published at /how-we-engage/quality-delivery-standards.
Beyond that, the website and its materials are provided "as is" and "as available", without warranty of any kind, to the fullest extent the law allows. We do not warrant that the site will be uninterrupted or error free, or that its content is current.
We do not claim certification against the standards we work to. Where we say we follow ISO/IEC 25010, OWASP ASVS, NIST AI RMF, WCAG 2.2, or similar, we mean our practice is aligned to them, not that an accredited body has audited us.
You are responsible for your own testing, user acceptance, and the decision to release anything to your users.
14. Limitation of liability
Nothing in these terms limits liability that cannot be limited by law, including death or personal injury caused by negligence, fraud, and wilful misconduct.
Subject to that, and to any liability cap stated in a signed agreement, our total liability to you arising from an engagement is limited to the fees you have paid or are payable to us for the part of the work that the claim relates to, in the twelve months before the event giving rise to the claim.
We are not liable for loss of profit, loss of revenue, loss of goodwill, loss of business opportunity, loss or corruption of data, or any indirect or consequential loss, in each case whether or not we were told such a loss could happen.
You must notify us of a claim in writing within six months of the event giving rise to it, so that we have a fair chance to investigate while the evidence still exists.
15. Suspension, termination and handover
Either side may end an engagement on the notice stated in the agreement. Where no notice is stated, either side may end it on 30 days' written notice.
Either side may end an engagement immediately in writing if the other commits a material breach and fails to put it right within 14 days of being told in writing, or becomes insolvent.
On end of work, you pay for work done and commitments already made, and we hand over the source, documentation, credentials, and deployment steps your team needs, and revoke our own access. Our handback process is described at /how-we-engage/security-data-handling.
Sections on confidentiality, intellectual property, liability, governing law, and dispute resolution continue after termination.
16. Third-party services and links
We use third-party models, cloud platforms, and tools in the systems we build and in our own operations. Their terms apply to their services, and we will tell you which ones are in play before work starts.
We may list or link to products and sites we do not control, including our own products hosted elsewhere. A link is not a recommendation, and we are not responsible for those services.
If a third-party model or platform changes, is deprecated, or fails, we will tell you and agree how to respond. Where a change is outside our control, we will not treat it as our breach, but we will help you plan the move.
17. Changes to these terms
We may update these terms to reflect changes to our services, our legal obligations, or the way the website works. The date at the top of this page shows when it last changed.
Changes apply from the date they are published, except that for an engagement already agreed, the terms in force at the time of that engagement continue to apply to it unless the agreement says otherwise.
18. Governing law and disputes
These terms and any dispute or claim arising from them are governed by the laws of the Dubai International Financial Centre, and the parties submit to the exclusive jurisdiction of the DIFC Courts.
Before formal proceedings, both sides will try to resolve the issue in good faith: first between the working leads, then between a director of each side, within 15 business days of a written notice of dispute.
Where a signed agreement chooses arbitration or another forum instead, that choice applies to that engagement.
19. Contact
Questions about these terms, or a request for the version that applied to your engagement, can go to abhishek@steinnlabs.com or jeet@steinnlabs.com.
Steinn AI Labs Limited, DIFC Registration SR-808691, Commercial License CL13762, IH-00-01-03-OF-05, Level 3, Innovation One, Dubai International Financial Centre, Dubai, United Arab Emirates.