The fine print
Terms.
Plain language. Read section 03 and 05 carefully — they describe the line where our responsibility ends and yours begins.
01 · Engagement
These terms govern any engagement with our productized engineering service.
We work async, one ticket at a time, against acceptance criteria you submit.
Either party may pause or cancel at any time. Unused days within a billing cycle bank for a reasonable window.
02 · Deliverables and ownership
On payment, the code we write for you is yours.
We may retain non-confidential techniques, snippets, and patterns for use in other engagements. We will not reuse anything that identifies you, your customers, or your data.
03 · Use of deliverables — your responsibility
You are solely responsible for what you do with the code we deliver.
That includes: how you deploy it, where you host it, who you give access to, what data you connect to it, what features you build on top of it, what regulatory regimes it operates under, and what end users do with the resulting software.
If our code becomes part of a product used for unlawful, harmful, deceptive, or otherwise malicious purposes, that use is yours, not ours. We do not monitor or police downstream use, and we accept no responsibility for it.
If the code is incorporated into a system that processes personal data, payments, health information, financial data, or anything subject to specific regulation, it is your obligation to ensure the surrounding system meets those requirements.
04 · No warranty
Deliverables are provided AS IS, without warranty of any kind, express or implied — including warranties of merchantability, fitness for a particular purpose, security, or non-infringement.
We do not warrant that the code is free of defects, suitable for production at any specific scale, or compatible with any system not explicitly named in the ticket scope.
05 · Limitation of liability
To the maximum extent allowed by law, we are not liable for indirect, incidental, special, consequential, exemplary, or punitive damages — including lost profits, lost data, business interruption, or reputational harm — arising out of or related to the deliverables, even if advised of the possibility of such damages.
Our total cumulative liability for any direct damages will not exceed the fees you paid us in the three (3) months preceding the event giving rise to the claim.
06 · Indemnity
You will defend and indemnify us against any claim, demand, proceeding, or loss arising from your use, deployment, distribution, or operation of the deliverables, including any claim brought by your customers, your end users, or any regulator.
07 · Confidentiality
Each party will treat the other's non-public information with reasonable care and use it only for the engagement.
We may describe the engagement in general, non-identifying terms ("a SaaS company in X industry") for our portfolio unless you ask in writing not to.
08 · Out of scope
We do not provide legal, tax, security audit, regulatory compliance, or accessibility certification advice.
We do not take on legacy migrations, mobile native work, or stacks outside our published list. If a ticket strays outside scope, we will refine it back or decline it.
09 · Billing and auto-renewal
Payments are processed by Stripe. We are the merchant — Stripe is our payment service provider, not the merchant of record. Stripe handles card processing and fraud screening; we never see card details.
Subscriptions auto-renew every 30 days at the price displayed at checkout, charged to the payment method on file, until cancelled. By completing checkout you authorise these recurring charges.
You may cancel at any time by emailing us. Cancellation stops the next renewal; the current cycle remains active until its end date.
Price changes are communicated at least 30 days in advance and apply only to subsequent renewals.
10 · Refunds
Refund eligibility and procedure are described in our refund policy. See /refund-policy for the current terms.
11 · Changes
We may update these terms from time to time. The version in effect for any engagement is the version published when the engagement started.
Questions? Email contact@ondemandly.dev.