Public Offer Agreement for SaaS and Online Services in Uzbekistan: How to Get It Right

Public Offer Agreement for SaaS and Online Services in Uzbekistan: How to Get It Right

A public offer agreement (terms of service) for SaaS is a contract that forms automatically the moment a user registers or starts using your service. Without it, you have no protection against abuse, no grounds to restrict access, and no framework for resolving disputes. Put simply: a product without a proper agreement is a business running on good faith alone.

Key takeaways:

• A public offer replaces individual contracts with each user — this is legally valid and essential for scaling.
• Acceptance (assent to terms) must be captured through a clear user action — a checkbox, a button, an explicit step.
• An offer agreement without a privacy policy is an incomplete document: Uzbekistan has personal data protection requirements, and they are enforced.
• Generic templates from the internet don't account for Uzbek law — they create the illusion of protection, not actual protection.

---

What Is a Public Offer Agreement and Why Does It Matter for an Online Service

Under Uzbekistan's civil law framework, a public offer is a proposal to enter into a contract addressed to an unlimited number of persons. A user accepts the terms (assents to the offer) through a specific action: clicking "Sign Up," paying for a subscription tier, or beginning to use the service. From that moment, the contract is considered concluded — no wet signatures or stamps required.

For SaaS, this is the ideal model: you define the rules once, and they apply to every user automatically. But "ideal" doesn't mean "problem-free." A poorly drafted agreement has gaps — and sooner or later, users or regulators will find them.

---

What a SaaS Offer Agreement Must Include

When we were building Pactum, I went through several iterations of our own terms of service before I realized: structure matters more than length. Here are the essential sections:

1. Parties and subject matter. Who you are, what you provide, and on what terms. Include a description of the service and its core functionality.

2. Acceptance mechanism. Explicitly state which user action constitutes acceptance of the terms. Without this, the agreement never legally "activates."

3. Pricing, billing, and refunds. How pricing is calculated, when charges occur, and what happens in case of non-payment. Refund conditions must also be stated — even if you limit them.

4. Rights and obligations of both parties. What you guarantee (uptime, support, updates) and what the user is prohibited from doing (reverse engineering, reselling, automated scraping).

5. Intellectual property. Who owns user-generated content? Who owns your product, API, and algorithms? For AI-powered services, this section is especially critical.

6. Limitation of liability. You are not liable for indirect damages, third-party actions, or force majeure events — all of this must be stated explicitly.

7. Modification of terms. How you notify users of changes and when those changes take effect.

8. Termination and account suspension. Under what conditions you have the right to restrict access or delete an account.

9. Governing law and disputes. Uzbekistan law, courts at the company's registered location — or alternative dispute resolution mechanisms.

---

Format Comparison: What to Choose for Your Service

My advice: start with a public offer agreement — and add individual contracts only when a client explicitly requires it (and the deal size justifies it).

---

Common Mistakes We See in Real Products

Copy-pasting a foreign template. A US or EU terms of service doesn't account for Uzbekistan's requirements — especially around personal data and e-commerce. This isn't just "slightly inaccurate" — it's potential regulatory action.

No privacy policy, or it isn't linked to the offer agreement. Both documents must work together. If you collect user data (and you do), a privacy policy is not optional.

Acceptance isn't captured technically. "By using the service, you agree to..." is a weak construction. You need an explicit checkbox or a button labeled "I accept the terms" — and ideally, that moment should be logged.

No clause covering AI-generated content. If your service uses artificial intelligence to generate content — who owns it? Who is liable for its accuracy? This is a new risk area that most agreements still ignore.

---

What to Do This Week

• [ ] Check whether your service and app have a public offer agreement and a privacy policy
• [ ] Confirm that acceptance is captured through an explicit user action
• [ ] Verify that AI feature terms are addressed if your product uses them
• [ ] Ensure the agreement was drafted under Uzbek law — not adapted from a foreign template
• [ ] Schedule a document review annually or whenever the product changes significantly

---

FAQ: Public Offer Agreements for Online Services

Do I need an agreement if my product is small with only a few clients?

Yes. Even with ten users — when the first dispute arises, you'll be glad it exists. Drafting one costs far less than resolving a conflict without one.

Can I use an agreement written in English?

Technically yes, if your audience is international. But for users based in Uzbekistan, a Russian or Uzbek version is strongly recommended: courts and regulators operate in those languages.

How often should the agreement be updated?

Whenever your product, pricing, business model, or applicable law changes. At minimum, review it once a year. For your specific situation — including notice periods and update procedures — consult a qualified lawyer.

What can I do if a user violates the terms?

A properly drafted agreement gives you the right to restrict or terminate access and seek compensation for damages — but only if the violation and its consequences were explicitly addressed in the document. That's why the details matter.

Do B2B clients need a separate contract?

For smaller B2B clients, a public offer works fine. For large enterprise clients, you'll typically need a bespoke contract covering SLA, NDA, and specific commercial terms. The two models can be combined.

---

*This article is general informational content and does not constitute individual legal advice. Specific decisions depend on your situation and the law as it stands at the time of application. Always verify current requirements before relying on any information here.*

---

If you'd like a public offer agreement drafted specifically for your product and compliant with Uzbek law — book a consultation. At Pactum, we work exclusively with tech companies and startups, so you won't need to explain what SaaS or an API is.