Acceptable Use
Effective 1 May 2026
This page is the Acceptable Use Policy (Policy) for the Law1 legal-research service at https://law1.in (the Service). It is an electronic record under the Information Technology Act, 2000. It does not need a physical or digital signature.
LAWONE SOLUTIONS PRIVATE LIMITED (we, us, Law1, or Lawone Solutions Pvt Ltd) operates the Service.
Registered office: 2nd Floor, A417, Lane 4, Road no 28, Ramnagar, Wagle Estate, MH, 400604, India. CIN: U58122MR2026PTC481366.
The Terms of Service are the contract. This Policy is incorporated into those Terms. It binds every User and every Org. Breaking this Policy is a breach of the Terms.
This page does not replace the Terms. It does not set a second money policy, liability cap, or dispute clause.
If you do not agree to this Policy, do not use the Service.
1. Who this Policy binds
A User is an individual. An Org is the organisation that is the billing and data boundary for research on Law1. There is no “personal org”.
When you create an Org, you confirm you are authorised to bind that Org. Members who join an Org accept this Policy for themselves. Joining as a Member does not, by itself, let that Member bind the Org.
The Service is for people who are 18 or older. An Org category labelled student means an adult professional student (for example law, CA, or CS). It does not mean a minor.
2. Lawful professional use
Use Law1 for lawful legal research and professional work for the Org.
You may search, display, and read material we host. Where the product allows and entitlements remain, you may download it for that work.
You may share an insubstantial extract with another Member of the same Org, or with a client, when that sharing is incidental to advice or research for that client. You may not republish, resell, or systematically redistribute Law1 content. The licence and what you may do with court text and our editorial are in the Terms of Service (section 9).
The Service is a professional research aid. It is not legal advice. Using Law1 does not create an advocate–client or other professional relationship with us. Read the Disclaimer.
3. Named seats and sessions
Access is by named seat. Each Member occupies one seat.
You must not share sign-in credentials, share a seat, or let anyone who is not that named User use that seat.
The product enforces concurrent-session limits. Those limits are set in the product and may change. We do not publish the numbers on this page. You must not exceed the session limits the product applies to you.
The Owner must not invite more Members than the Org’s seat cap.
You must keep your sign-in details and mailbox under your control. You are responsible for activity under your User account, unless you have told us of unauthorised use and we have had a reasonable chance to act.
Do not create extra User accounts to evade seats, session limits, metering, a suspension, or this Policy.
4. Scrape, harvest, and bypass
You must not scrape, harvest, bulk-extract, or bypass access, metering, or rate limits.
Without limiting that rule, you must not:
- use a bot, spider, crawler, script, or other automated tool to access, query, download, or index the Service, except through Law1’s official MCP surface as section 5 allows;
- harvest HTML, APIs, search results, judgment bodies, PDFs, or our editorial in bulk;
- run a resumable crawler, download accelerator, or similar tool against the Service;
- bypass, defeat, or probe proof-of-work, rate limits, session caps, entitlements, watermarks, or other access controls;
- copy or extract at a volume or pattern that is not ordinary interactive research for the Org, including by hand if the effect is the same as a scrape.
Rate limits and other technical controls exist in the product. They may change. We do not publish the numbers on this page.
Using the official MCP surface does not allow scrape, harvest, or bulk extraction. That surface is still subject to this section and to section 5.
Unauthorised access to a computer resource, unauthorised downloading, or interference with a computer resource may also attract consequences under the Information Technology Act, 2000, including sections 43 and 66.
This section does not stop you obtaining judgments from the courts themselves.
5. MCP and agents
You may connect an external agent (for example a desktop or cloud assistant that speaks the Model Context Protocol) only through Law1’s official MCP surface, after the human User has signed in and consented in the product.
That agent acts as that User for the active Org. It uses the same entitlements, credit pools, and rate limits as the browser. There is no extra bulk or privileged path for agents.
Using an agent, script, or other automation to evade metering, rate limits, or this Policy is a breach.
Do not connect an unofficial or undocumented machine-readable path to Law1.
6. Training and bulk corpus
Training and bulk corpus use are forbidden by default.
You must not use Law1 — including the site, the official MCP surface, exports, or our editorial — to train, develop, test, or improve a model, or to build a competing collection.
We may permit training only under a separately executed one-to-one agreement. That path is not self-serve and is not an in-app purchase in this version of the Service.
That exception, if we grant it, does not licence or forbid court text you obtain from the courts themselves. It only addresses what you may do with Law1 and with our editorial.
We do not claim copyright in the raw judgment as delivered by the court. Copyright may subsist in our original editorial and compilation. See the Terms of Service (section 9).
7. Other prohibited conduct
You and the Org must not:
- use the Service for any illegal purpose, or store, submit, or transmit unlawful content;
- introduce malware, viruses, or other harmful code, or attempt intrusion into our systems or another User’s account;
- impersonate any person or entity, or misrepresent your affiliation or authority;
- interfere with another User’s or Org’s access to the Service;
- attempt to break, probe, or circumvent security, authentication, or access controls.
8. User content
User content is material you or the Org submit to the Service — including project names and notes, comments, stars, and, when we offer them, uploads.
Comments and similar notes are visible to Members of the Org. They are not a public forum.
You confirm that you have the rights needed to submit the User content and that it is lawful. You must not submit material that infringes someone else’s rights or that this Policy forbids.
We may remove or restrict User content as described in Case and content removal and this Policy. Removing User content does not take a judgment page down.
Requests to unpublish or redact a judgment follow Case and content removal, not this page.
9. Enforcement
We may monitor usage patterns to enforce this Policy and to protect the Service.
If you or the Org break this Policy, we may suspend or limit access, or end the Terms as to a User or an Org, as the Terms of Service (section 11) provide. Where reasonable we will give notice. We may act without prior notice for abuse, scrape, unpaid charges, or legal risk.
There is no uptime, support, or plan-tier service-level agreement. We do not promise a percentage of availability. We do not offer service credits.
Questions about this Policy: [email protected] or Contact. A grievance under applicable IT or data-protection rules: Grievance officer.