Legal

Terms of Service

Last updated: July 29, 2026

These terms cover two separate things: your use of this website, and the basis on which UloveAI INC takes on client work. The second one matters more, so it is stated plainly rather than buried.

1. The website

This website is published by UloveAI INC, a General Stock Corporation registered in the State of California, at 17800 Castleton St, Suite 409, City of Industry, CA 91748.

Everything on it is provided for general information. Descriptions of our services, timelines and approach are a good-faith summary of how we work, not an offer capable of acceptance and not a warranty of any particular result. Nothing here is legal, financial or tax advice.

The text, layout, photography and code of this site belong to UloveAI INC. You are welcome to read it, print it, quote it with attribution and send it to a colleague. You may not republish it as your own.

2. Nothing on this page is the contract

We do not take on work through this website. Every engagement is governed by a separate written agreement signed by both parties, and that agreement — not this page and not any email exchange — sets out the scope, the price, the schedule and the obligations on each side.

If those two documents ever disagree, the signed agreement wins.

3. How we engage

Discovery first

Most engagements begin with a paid discovery: a fixed fee for a fixed number of days, ending in a written scope document. That document is the client's property on payment, whether or not they go on to hire us to build anything, and whether or not they take it to another firm for a competing quote.

Fixed scope, fixed price

Build work is quoted as a fixed price against a written scope, not as an open-ended hourly arrangement. Where a client asks for something outside that scope, we price it as a written change order and wait for approval before starting. We do not add work and invoice for it afterwards.

Ownership

On final payment, ownership of the software written specifically for a client — source code, configuration and documentation — transfers to that client. Deployment runs on infrastructure and accounts the client owns.

Two carve-outs, stated so they are not a surprise later: general-purpose tools, libraries and internal components that predate the engagement or are reused across clients remain ours and are licensed to the client perpetually for use in the delivered software; and third-party open-source and commercial components stay under their own licenses, which we identify in the handover documentation.

Acceptance

Scope documents name the specific outcome the software has to meet. Where a signed agreement contains that acceptance standard and the delivered software does not meet it, our obligation is to continue working until it does or to refund the final milestone, at the client's election. The precise wording that applies is the wording in the signed agreement.

4. What the client is responsible for

• Timely access to the systems, data and people the project needs
• The accuracy and lawfulness of data supplied to us, including having the right to share it
• Naming one person who can make decisions and give approvals
• Reviewing deliverables within the agreed review window
• Their own accounts, licenses and ongoing running costs after handover

Where a project stalls because access or approvals do not arrive, timelines move accordingly. We will say so at the time rather than absorb it silently and miss a date.

5. Confidentiality

Each side keeps the other's non-public information confidential and uses it only for the engagement. We do not name a client or describe their project publicly without their written permission. Handling of personal information is described in our Privacy Policy.

6. Artificial intelligence — the honest version

Our work commonly incorporates machine learning models, including third-party models from providers such as OpenAI, Anthropic and Google. Two things follow from that, and we would rather say them here than have a client discover them later:

• These systems are probabilistic. They can produce output that is wrong, incomplete or unsuitable, including on inputs they previously handled correctly. Where the consequences of a wrong output are material, we design human review into the process and we will say so during scoping.
• They depend on third parties. Model providers change pricing, deprecate models and alter behavior on their own schedule. We build so that a provider can be replaced, but we cannot guarantee a third-party service will remain available or unchanged.

The client remains responsible for decisions taken on the basis of software output, and for the legal and regulatory requirements that apply to their own industry.

7. Warranties and liability

Except for the commitments written into a signed agreement, the website and any information on it are provided "as is", without warranties of any kind, express or implied, including implied warranties of merchantability, fitness for a particular purpose and non-infringement.

To the fullest extent permitted by law, UloveAI INC is not liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, revenue, data or business opportunity, arising out of use of this website. Liability arising from an engagement is governed by the limitation of liability set out in the signed agreement for that engagement.

Nothing in these terms excludes liability that cannot lawfully be excluded.

8. Governing law

These terms are governed by the laws of the State of California, without regard to its conflict-of-law rules. The state and federal courts located in Los Angeles County, California have exclusive jurisdiction, and both parties consent to venue there.

9. Changes

We may update these terms. The version in force is the one published here on the date you use the site; the date at the top reflects the most recent change. Signed agreements are not altered by changes to this page.