Rilin FAQ: Contractual Liability Control, Answered Plainly

No. Rilin is a technology company built by Suvarna Nyayanidhi Private Limited. Not a law firm. Not a legal services provider. The platform surfaces obligations and risk from contract text and can load empanelled specialist counsel with full context when a matter needs a lawyer, and the advice in that engagement comes from the counsel, not from Rilin.

It reads executed contracts and converts each material agreement into a Transaction. A Transaction holds the document, the parties and the value, and underneath it the set of business actions the agreement requires, each carrying a due date, a named owner and a reference back to the clause that produced it.

The contract expressed as work. Instead of a file with metadata, you get a live object with obligations, owners, dates, evidence and status, so someone who has never opened the PDF can operate the agreement.

Risk Surfacing reads the executed document and flags terms that create asymmetric exposure. Obligation Tracking runs the dated actions to completion. Draft and Review handle the pre-signature side for teams that want it. Specialist Counsel loads empanelled external counsel with the full Transaction context when a matter needs one.

Companies with material negotiated contracts, performance distributed across several functions, and a legal team too small to re-read the portfolio every quarter. Buyers are usually a mix of enterprise leadership, finance and legal, because the exposure lands on all three.

A company with fifteen contracts and one counterparty. A company whose agreements are all click-through terms with no negotiated obligations. In both cases a spreadsheet is the right answer and we will say so.

Suvarna Nyayanidhi Private Limited, incorporated in Bengaluru in 2024, with a $2 million seed round led by 3one4 Capital. Corporate filings are public at the [LINK https://www.mca.gov.in/mcafoportal/viewCompanyMasterData.do]Ministry of Corporate Affairs[/LINK].

CLM optimises the route to signature, covering intake, templates, redlining, approvals and execution. Rilin begins where that ends. A CLM measures cycle time. Rilin measures whether the thirty to eighty obligations inside the signed agreement were performed on time by the people who owe them.

A negotiated master services agreement commonly yields between thirty and eighty distinct obligations once payment terms, reporting, insurance, data protection, audit rights, notice requirements and termination mechanics are separated out. Short purchase orders yield a handful.

A window opens and closes, unlike a deadline that simply arrives. A non-renewal right exercisable between day 120 and day 90 before the anniversary is worthless if it is recorded as a single due date, because the alert fires on the last day and the clause requires registered post.

Yes, and those are often the more valuable rows. Rights you hold against a supplier go unexercised because nobody internally argued for the clause, so unclaimed service credits and unenforced audit rights accumulate quietly.

Terms where exposure is asymmetric. Uncapped indemnities, liability caps carved out by exception, automatic renewal with a short non-renewal window, unilateral termination rights, price escalation without a ceiling, and obligations conditional on evidence you are not collecting.

Yes, and that is where it earns most. Obligations drafted by the other side are the ones your team is least likely to remember, because nobody internally negotiated for them and nobody feels ownership of them afterwards.

An amendment is a change event on the Transaction. Affected obligations are re-derived against the amended clauses, superseded rows are closed with a pointer to the amending document, and new obligations are routed to owners for acceptance.

Hosting region is confirmed during evaluation and documented in the agreement rather than assumed. Ask for it in the technical call along with the data processing agreement, before commercials.

Not generally. Section 16 of the Act permits transfer of personal data outside India except to territories the Central Government restricts by notification. Sectoral regulators can impose stricter rules, and entities regulated by the Reserve Bank of India should check the outsourcing and storage directions that apply to them.

In a normal deployment the customer is the data fiduciary and Rilin processes personal data on the customer's instructions. The customer remains answerable for processing carried out on its behalf, which is why the data processing agreement is the control that matters. The Act is published at [LINK https://www.meity.gov.in/data-protection-framework]meity.gov.in[/LINK].

Under the Schedule to the Digital Personal Data Protection Act 2023, failure to take reasonable security safeguards to prevent a personal data breach attracts a penalty of up to Rs 250 crore. That figure is the reason vendor diligence on contract systems has stopped being a formality.

Yes. Access is scoped by Transaction and by role, which matters because an obligation owner in delivery needs the clause and the date without needing the commercial terms of the whole agreement.

Yes. Status changes on an obligation carry the actor, the timestamp and the evidence attached, which is the difference between a register and a to-do list.

Export is contractual. Agree the export format and the retention and deletion timelines in the agreement rather than discovering them at renewal.

No. The platform surfaces what the document says and what it requires, and it flags terms that create exposure. Interpretation of those terms for a specific dispute or transaction is legal advice, and that comes from counsel.

A routing capability. When a matter needs a lawyer, the platform loads empanelled external counsel with the full Transaction context, so the engagement starts with the obligations, the clause references and the correspondence rather than with a folder of PDFs. The counsel is engaged by you and advises you.

If a supplier is registered as a micro or small enterprise, Section 15 of the Micro, Small and Medium Enterprises Development Act 2006 caps the agreed payment period at forty-five days, and Section 16 imposes compound interest at three times the Reserve Bank of India bank rate on delay. Your contract cannot override the statutory ceiling. The Act is at [LINK https://www.indiacode.nic.in/handle/123456789/2050]India Code[/LINK].

Yes, both sit inside the flow that produces the obligation record, so the executed instrument and its stamp certificate live with the Transaction. Signature validity and stamp duty are separate legal requirements, and a validly e-signed agreement that is insufficiently stamped still runs into Section 35 of the Indian Stamp Act 1899.

For the period the survival clause states. Where duration is unstated, a suit for compensation for breach of contract is subject to Article 55 of the Schedule to the Limitation Act 1963, which runs three years from the date the contract is broken.

No, and the platform is designed on the opposite assumption. Counsel does the legal work. The platform makes sure counsel receives a complete picture instead of reconstructing one at a billable rate.

No. The only route in is a demo, because the platform is configured against your contract set, your entity structure and your obligation owners before it produces anything useful.

Twenty real executed agreements, including the ugliest counterparty paper you have. A demo run on clean templates from the vendor's own library is a demo of the vendor's templates.

Extraction is fast and ownership assignment is slow. Machine extraction of clause-level obligations from a standard MSA takes seconds per document. Getting a named person in the business to accept accountability for a specific row takes weeks, and that ratio surprises buyers who expect an extraction problem.

With the top fifty agreements by value or by counterparty criticality. A register covering everything at low quality is worse than one covering the material set at high quality, because the first teaches people to ignore alerts.

Two ratios. Coverage is the proportion of material contracts with a populated obligation register. Acceptance is the proportion of obligation rows with an owner who has actively confirmed accountability, and acceptance is the number that predicts whether the register is real.

No. Rilin sits after signature and coexists with a CLM. Companies with a working pre-signature workflow keep it and connect the executed output.

Legal operations or finance usually owns the register as a system. Individual obligation rows must sit with the function that performs them, because a register owned entirely by legal becomes a legal to-do list that legal cannot execute.

In rupees, against portfolio scope rather than seat count, and confirmed in the commercial conversation after the demo.