Jhana.ai vs LBOX: how they compare in 2026

J
Jhana.ai profile
L
LBOX profile
Last verifiedSeptember 27, 2026

Jhana.ai and LBOX are rarely compared because each serves one country: Jhana.ai builds legal AI for Indian law and LBOX for South Korean law. Set side by side, they show two answers to the same questions about who may use a legal AI and where client material goes. LBOX sits in the top two bands on ten of fifteen axes and Jhana.ai on four of fifteen, identical on five. LBOX limits its AI agent to verified legal professionals and staff working under their supervision, names the five providers that receive queries with a retention period for each, and deletes queries once answered. Jhana.ai's lead is in the courts. It reports more than 150 judges and registrars across five or more courts using its agents, which the courts own and host themselves. Its home page says it does not train on customer data and then that free users can opt out of training. Neither holds a security certification of its own, and neither publishes a vendor commitment on wrong output.

At a glance

Category
Jhana.aiLegal Research
LBOXLegal Research
Founded
Jhana.ai2022
LBOXNot published
Headquarters
Jhana.aiBengaluru, India
LBOXSeoul, South Korea
Last verified
Jhana.aiAug 29, 2026
LBOXSep 13, 2026

All 15 axes, side by side

The same grid applied to every vendor in the index, graded from public sources. Hover a grade to see what the letter means on that axis.

AI Centrality

How much of the product is actually AI. Whether the machine learning is the mechanism the buyer is paying for or a feature layered onto conventional software, and whether the vendor is specific about which is which.

Jhana.ai
AA on AI CentralityThe artificial intelligence is the product. Remove the models and there is nothing left to sell.

The models are the product and the corpus was built to feed them. The vendor describes itself as a frontier legal intelligence lab and names its proprietary work as verifier models, graph models for legal ontologies, a national legal archive of more than 16 million machine enhanced documents, and research and drafting agents. Machine enhanced is the operative phrase: the corpus was not licensed and wrapped, it was processed into a model asset, and the stated use of seed capital was to build proprietary datasets and models and to hire researchers in law and AI. Every product is an agent pipeline rather than a workflow tool with a model attached, including the public sector agents running extraction, synopsis and forensic scrutiny. Remove the models and there is no product left. Same shape as Reveal, reached from the opposite direction: Reveal acquired model capability into a platform, Jhana built the corpus and the models first and the interface after.

LBOX
BB on AI CentralityThe models are the engine of a core capability, layered on a product that would still function without them as a document or workflow system.

The models are the engine of a core capability on a product that would still function without them, which is the B band exactly, and the vendor's own history makes the boundary unusually easy to see. LBOX began as a judgment database. The AI arrived later as LBOX AI and was then rebuilt: the company's own product announcement describes the shift to an agent architecture as the most fundamental product change since LBOX AI launched, with every step from receiving the question to delivering the final answer now running on an agent, and it claims this as the first legal AI agent in Korea. The current positioning is AI-first, the platform being sold as the single AI working environment for lawyers covering case law and statute search, AI answers and document drafting. What keeps it off A is the A band's own test: remove the models and there is nothing left to sell. Remove them here and a Korean case law and statute database remains, with search, projects, folders and the instance linking that users single out, and it is that database the company treats as the durable asset, grounding its AI in its own legal data rather than in a general corpus. The AI is also not universally available within the product, being gated to occupationally verified legal professionals and to supervised staff, so some subscribers hold the platform without holding the agent. Recorded and not credited toward this axis: LCUBE, the Korean legal language model the company released with KAIST at NeurIPS 2022 on a 147,000-judgment corpus, is real and is the company's own, but it is a research artifact and is not what the seed's AI line implies is shipped. Verified 13 September 2026.

Citation Accuracy and Hallucination Disclosure

Whether the vendor publishes measured accuracy on citations and assertions, grounds output to primary sources, and says plainly what its system does when it does not know. Legal has a documented public record of fabricated citations reaching filed briefs, so an untested claim of accuracy is not evidence.

Jhana.ai
BB on Citation Accuracy and Hallucination DisclosureGrounding is real and documented, with linked primary sources and a described retrieval method, short of published accuracy figures an outsider can test.

Grounding is architectural and demonstrated, short of any published measurement. The vendor states plainly that its agents always cite their work, and names a verifier model as proprietary technology, which puts a checking mechanism in the architecture rather than in the marketing. Published product material shows source linked output where each conclusion sits one click from the underlying source page and each extracted figure is anchored to page and paragraph, which is a demonstrable behavior a reader can inspect rather than a claim about accuracy. Held at B because nothing measured is published: no accuracy figure, no precision or recall on retrieval or extraction, no hallucination rate, no test set, no independent benchmark participation, and no statement of what the verifier catches or how often. Searched the home page, the product pages, the published blog material, the privacy policy and the terms and conditions on 29 Aug 2026. For a vendor whose named innovation is a verifier, the absence of a measured verification result is the gap.

LBOX
BB on Citation Accuracy and Hallucination DisclosureGrounding is real and documented, with linked primary sources and a described retrieval method, short of published accuracy figures an outsider can test.

Grounding is real and documented with linked primary sources, and no measured accuracy is published, which is the B band. The grounding is described as the point of the product rather than as a footnote: answers are generated from the company's own legal data so that the question's intent is understood in context, and the vendor states in terms that this minimizes the hallucination that can occur with general-purpose AI. The index's rule governs rather than the D limb, because the claim sits alongside architecture rather than in place of it. The verification path is concrete. Cited precedents and statutes are linked and openable from the answer. Where a commentary or practice text from the company's own LBOX Scholar imprint supports an answer, the original text is reachable directly from the AI query so a reader can check the basis of the answer against the source, and authors are shown how often their material is cited by the AI. That is a closer coupling between answer and authority than most records in this corpus publish. What is absent is measurement. No accuracy figure, error rate, test set or evaluation is published on any first-party surface for the agent, for search or for drafting, and nothing states what proportion of answers carry support. Recorded and expressly not credited because it is not first-party: press coverage reports the company claiming its agentic AI outperformed human candidates on the bar examination and beats general-purpose AI on accuracy, which is a measurement claim made to a newspaper rather than published with a test set the reader can assess. The A band also asks whether the system states when it found no support, and nothing addresses that. Verified 13 September 2026.

Autonomy and Oversight Model

What the system decides on its own, what a lawyer must approve, and whether the vendor documents where the review point sits. A tool that drafts under review and a tool that files without one are different products and different risks.

Jhana.ai
CC on Autonomy and Oversight ModelAutonomy is claimed and oversight is asserted without a mechanism. Human in the loop appears as a phrase rather than a described control.

The positioning implies an oversight model and no document describes one. Calling the product a paralegal rather than a lawyer is a deliberate and meaningful choice: a paralegal works under supervision, and the naming carries that. But naming is not a published model. Nothing states where a human must review agent output before it is used, whether any step can complete without review, what the agents may do unattended in the Courtroom and PUBSEC pipelines running extraction, synopsis and forensic scrutiny for courts, or what happens when an agent is wrong inside a registry workflow. No confidence threshold, escalation path or human confirmation requirement was located. Checked the home page, the product pages, the public sector material, the terms and conditions and the blog on 29 Aug 2026. The gap matters more here than for a research tool sold only to private practice, because the deployed users include judges and registrars.

LBOX
BB on Autonomy and Oversight ModelA written commitment that the models work alongside a supervising lawyer, with real review surfaces, short of the full control structure: commonly the threshold at which the system stops or what happens after it is wrong.

A written commitment that the models work alongside a supervising lawyer, short of the full control structure, which is the B band, and the commitment here takes an unusual form worth setting out. Rather than describing a review step inside the product, the vendor controls who is permitted to operate the agent at all. Its published eligibility rules limit LBOX AI to members who have completed occupational verification as lawyers, judicial scriveners, labor attorneys, tax accountants, patent attorneys or accountants; to staff of courts, prosecution offices, police and legal research institutions the company recognizes as appropriate; to employees of other organizations only where a qualified legal professional has given prior approval and the work is performed under that professional's direction, supervision and review; and to public institutions using the IP-authenticated Public plan. Verification requires documentary proof by profession. So the supervising-lawyer requirement is not a sentence of marketing but an access control with an enrollment process behind it, and the vendor frames it as continuing work to keep use of legal AI lawful. Against that, the autonomy being supervised is real and broad: the agent plans and executes the entire sequence itself, from interpreting the question through searching and verifying to producing the answer and drafting documents. What the A band asks for is absent. No mode distinction is published, no confidence threshold, no statement of when the agent stops or escalates, no described review surface between generation and use, and nothing on what happens after the system is wrong. The verification affordance that exists, opening the cited authority, is the user's own diligence rather than a control the vendor operates. Verified 13 September 2026.

Operational and Outcome Evidence

Named, dated evidence that the product works in production at real firms or legal departments. Case studies with figures and identified customers count. Unattributed testimonials and launch announcements do not.

Jhana.ai
BB on Operational and Outcome EvidenceReal deployment evidence with substance, short of full attribution or measurement: a named customer without figures, or figures without the named customer.

Adoption is quantified and unusually institutional. Stated: more than 10,000 users, over 150 judges and registrars across five or more courts, more than 100,000 paralegal sessions and over 200,000 searches. Judicial adoption is the strongest element and the second instance on this index of a public authority using the product rather than merely appearing as a logo, after FinregE and the FCA Handbook. Also dated and attributable: a $1.6m seed led by Together Fund with named participants, a January 2026 partnership with CADRE ODR for online arbitration, and support from Jio GenNext, the AWS Public Sector Startup Hub, Microsoft Founders Hub and the Google Cloud Startups Program. Held at B on three gaps. Every usage figure is self reported with no methodology, period or definition, so a paralegal session is whatever the vendor counts. No court, institution or firm is named. No outcome measure of any kind is published: nothing on time saved, error reduction or research quality, only volume.

LBOX
CC on Operational and Outcome EvidenceCustomer logos and unattributed testimonials stand in for evidence, or results are quoted with no basis stated.

Unattributed testimonials and store metrics stand in for deployment evidence on first-party surfaces, which is the C band. What the vendor publishes itself is thin for a company of this standing. The pricing page carries user quotes attributed only by role, an in-house counsel and unnamed practitioners, with competitor names redacted; a testimonial is named customer evidence only where the customer is named, and none is. The Google Play listing gives 10,000-plus downloads and a 4.6 rating from 155 reviews, which measures an app rather than a platform. LBOX Scholar names authors, including senior academics and practitioners whose commentaries it publishes, but an author is a supplier rather than a customer and is not credited here. No named law firm, corporation, court or public institution was located on any first-party surface, no case study, and no outcome figure of any kind. Recorded and expressly not credited, because they are third-party and would breach the first-party floor: press coverage reports the company serving ten of the largest domestic law firms, corporations and major judicial institutions, and an aggregator profile reports some 23,000 lawyers using the service. Aggregator listings are excluded outright as evidence, and the press figures are neither published by the vendor nor attributable to a named customer. The gap is the interesting part of this record: a vendor with what its own market plainly treats as the leading position publishes almost nothing a buyer could verify about who uses it. Verified 13 September 2026.

Privilege and Confidentiality Posture

How client confidences are handled: attorney client privilege and work product treatment, segregation of one client matter from another, whether client data trains any model, and what the vendor commits to in writing rather than in marketing.

Jhana.ai
CC on Privilege and Confidentiality PostureConfidentiality is asserted in general terms, or the commitment lives only in a sales conversation and cannot be read in advance.

Real documentation exists and none of it is about privilege, and one disclosed practice cuts against the posture. The privacy policy is a genuine product document framed against the Digital Personal Data Protection Act 2023 and the Information Technology Act 2000, with erasure on request by email, retention carve outs for fraud prevention and for tax, legal reporting and audit obligations, and a security section. That is more than several better funded vendors on this index publish. What is absent: any treatment of legal professional privilege or work product, any statement about the confidentiality of case files uploaded to AI Paralegal or Document Intelligence, and any segregation model. Named as a concern rather than buried: the privacy policy states that personal information may be disclosed to data processors including marketing and advertising agencies and web analytics companies. For a platform holding client matter documents, disclosure to advertising and analytics categories is a real posture question, and the policy does not distinguish account level personal data from uploaded matter content.

LBOX
BB on Privilege and Confidentiality PostureSubstantive published commitments on confidentiality and training use, short of the full picture: commonly silence on segregation between users or matters, or on what the underlying model provider may retain.

Four of the five A limbs are met and the fifth is not addressed at all, which holds this at B under R33 and makes it the second record in this pull to sit one word short. What is published is strong and specific. On training, the vendor states that personal information in queries and uploaded files is not used to train AI models. On retention and deletion, query text and uploaded files are stated to be used only while the answer is being generated and deleted immediately once the purpose is met, with the privacy policy setting a further ceiling of 30 days at each overseas processor. On segregation, documents a user creates are visible only to that user and to Business plan colleagues expressly granted sharing rights, and all material is stated to be held encrypted in customer-dedicated storage. On third party model providers, the position is not merely explicit but enumerated: the privacy policy names OpenAI, Anthropic, Google, Amazon and Microsoft as recipients of user input to LBOX AI, with the purpose and the retention period for each. That last limb is answered more completely here than on any other record in this pull. The limb that fails is privilege and work product, and it fails by absence rather than by weakness. Neither privilege, professional secrecy nor work product is addressed anywhere located, on a platform whose users are verified lawyers uploading case documents for analysis, and nothing states what happens to that material if it is demanded. Two further limits belong on the record: the no-training sentence is written about personal information within queries and files rather than about the content itself, and the deletion commitment is what closes that gap in practice; and the customer agreement, which would be the natural home for all of this, is published and could not be read by this index. Verified 13 September 2026.

UPL and Professional Responsibility Posture

Whether the vendor is clear that it supplies a tool rather than legal advice, who its audience is, and how it addresses unauthorized practice of law, competence and supervision duties, and jurisdiction limits. ABA Formal Opinion 512 is the reference point. Where the advice line is not the duty a product raises, the axis is read through the nearest professional duty it does raise: judicial conduct rules and the reviewing duty for products sold only to courts, and the duty to bill for time actually spent for products that draft time entries.

Jhana.ai
DD on UPL and Professional Responsibility PostureNothing published on the advice line for a product that produces legal work, including where it is sold to people who are not lawyers.

Not addressed in any located material. The product generates propositions, advisories and memos from natural language input, which is output shaped like advice, and the user base explicitly extends beyond advocates to founders, tax professionals and compliance teams. That combination is precisely where the question bites: a non lawyer receiving an advisory generated from case law is the unauthorised practice scenario, and nothing published addresses it. No statement that output is not legal advice, no positioning on the supervising advocate's role, and no engagement with Bar Council of India rules on advocate conduct or advertising. Checked the home page, the product pages, the terms and conditions, the privacy policy and the blog on 29 Aug 2026. The paralegal naming is the closest thing to a position and it is a brand choice rather than a disclosure.

LBOX
BB on UPL and Professional Responsibility PostureA real position is published on advice versus tooling, short of full treatment: commonly a disclaimer without the supervision and competence dimension, or silence on jurisdiction limits.

A real published position, short of full treatment, which is the B band, and this record is the inverse of the usual shape. The B band anticipates a disclaimer without the supervision and competence dimension. Here the supervision dimension is the strongest thing on the axis and the disclaimer is what could not be found. Who may use the product is stated with more precision than any record in this corpus and is enforced rather than asserted. The AI agent is available only to members who have completed occupational verification against documentary proof as lawyers, judicial scriveners, labor attorneys, tax accountants, patent attorneys or accountants; to staff of courts, prosecution offices, police and legal research institutes the company recognizes; and to employees of other organizations only where a qualified legal professional has approved the use in advance and the work proceeds under that professional's direction, supervision and review. Public institutions reach it through an IP-authenticated plan. The vendor frames this as ongoing work so that those doing legal work can use legal AI lawfully, which engages the Korean regulation of legal services without naming it. That is the competence and supervision limb, answered operationally. What is missing is the rest of the A band. No statement was located of what the product is and is not, no advice disclaimer on any readable surface, and no jurisdiction limit stated, though the content is Korean law throughout. The customer agreement, where such a statement would ordinarily sit, is published and unreadable to this index. Recorded so the grade is read correctly: the consumer-facing lawyer directory the company also operates is a separate product and is not this record. Verified 13 September 2026.

AI Governance and Bias Disclosure

Published governance over model behavior: who owns it inside the vendor, what is tested before release, and what is disclosed about disparate output across matter types, parties, or populations.

Jhana.ai
DD on AI Governance and Bias DisclosureNo governance position published for a system whose output affects legal outcomes.

Nothing published about how the models are governed, evaluated or monitored. No AI policy, no evaluation methodology, no bias or fairness assessment, no accuracy monitoring, no drift statement, no model card, no named governance body and no external standard such as ISO 42001. The absence is conspicuous against the vendor's own subject matter expertise, since its published blog material analyses the DPDP Act and DPDP Rules compliance obligations in structured detail for its customers, and none of that analytic rigour is turned on its own system. Also unaddressed: whether a corpus described as machine enhanced introduces systematic error into the archive itself, which for a research product built on a proprietary dataset is the governance question that matters most. Checked the home page, the company and funding material, the product pages, the blog and the terms and conditions on 29 Aug 2026.

LBOX
DD on AI Governance and Bias DisclosureNo governance position published for a system whose output affects legal outcomes.

Nothing published on AI governance was located, which is the D band, and the contrast with what this vendor does publish is the finding. On data protection the governance is documented in detail: a named protection officer who is the chief executive, a named handler, a named responsible department, an internal management plan with inspection, a dedicated organization, regular staff training, and a statutory grievance route. None of that reaches AI. No responsible AI or ethics statement, no AI policy, no acceptable use position, no accountable owner for model behavior, no description of what is tested before a model or agent change ships, and no disclosure of evaluation results of any kind was located on any readable surface. Bias is not addressed anywhere. That matters on this product for a specific reason worth naming rather than leaving general: the agent ranks and selects which precedents surface in answer to a legal question, and a systematic tilt in retrieval, toward particular courts, particular periods or particular outcomes, would be invisible to the user and would shape the authority a lawyer relies on. Nothing published would let a buyer test it. The vendor did publish a benchmark and model of its own with an academic partner in 2022, which shows the capability to evaluate exists internally, and no evaluation of the shipped agent has been published in the four years since. The absence is not explained by retrieval difficulty: the help center and policy estate are fully readable and carry nothing on this. Verified 13 September 2026.

AI Safety and Data Stewardship

Retention, deletion, access control, and what happens to prompts and documents after they are processed. Whether the vendor states its subprocessors and its incident practice, or leaves the buyer to assume.

Jhana.ai
CC on AI Safety and Data StewardshipA generic privacy policy covers the product without addressing what happens to documents and prompts after processing.

The vendor speaks to stewardship directly, which most of this roster does not, and what it says does not hold together. The home page states that customer data is not used for training, and in the next sentence that free users have the choice to opt out of sharing data for model training. Those two statements cannot both be complete. The privacy policy supports erasure on request, discloses processor categories, and states that appropriate security measures and generally accepted industry standards are applied. Held at C because the operative rule is unclear from public material: no retention period is stated for prompts or generated output, no distinction is drawn between account data and uploaded matter content, and the training position depends on which sentence a reader stops at. The signal row records the contradiction with the quote. Credited above D because a vendor that addresses training at all, and gives free users a control, is materially ahead of one that is silent.

LBOX
BB on AI Safety and Data StewardshipSubstantive published policy covering most of the ground, short of the full set: commonly no named subprocessor list or no stated incident practice.

Retention, deletion, access control and subprocessors are all published and specific, and no incident practice was located, which is the B band and precisely the second of the two gaps it names. The published material is detailed because Korean data protection law requires it to be, and the record benefits either way. Retention: query text and uploaded files used only during answer generation and deleted immediately afterwards, with a stated ceiling of 30 days at each overseas processor, behavioral logs held until withdrawal, and statutory periods set out instrument by instrument. Destruction: a stated procedure, electronic records rendered unrecoverable and paper shredded or incinerated, with credential documents destroyed immediately once verification is complete. Access control: access rights management, an access control system, encryption, security software, access logs retained and periodically inspected, plus physical control of server and archive rooms and locked storage, all under an internal management plan with a dedicated organization and regular training. Subprocessors: fully enumerated, domestic and overseas, including re-delegated parties, with the company committing to notify without delay through the privacy policy if a processor or the scope of its work changes and to consent to any re-delegation. What is absent is incident practice. No breach notification commitment to customers was located, no notification window, no description of incident response, and nothing states what a subscriber would be told or when. Verified 13 September 2026.

AI Liability and Recourse

What the vendor stands behind contractually when its output is wrong. Indemnities, caps, carve outs, insurance, and whether any of it is published or only reachable through a negotiated agreement.

Jhana.ai
DD on AI Liability and RecourseNothing published on who bears the loss when the system is wrong.

Terms exist, were read, and run one way. The terms and conditions contain an indemnity under which the user holds the company and its officers, agents and employees harmless against third party claims, demands, damages, penalties, losses and actions including reasonable attorneys' fees, together with an entire agreement clause incorporating the privacy policy. No corresponding vendor commitment was located: no warranty as to output, no accuracy undertaking, no service level, no liability position, and no remedy where a generated citation, advisory or memo is wrong. This is graded on published material rather than on absence, which is why the basis is Vendor Published: the document exists and allocates risk in one direction. Checked the terms and conditions and the privacy policy on 29 Aug 2026.

LBOX
DD on AI Liability and RecourseNothing published on who bears the loss when the system is wrong.

Nothing published on who bears the loss when the output is wrong could be located, and the note records the reason precisely so the grade is read as the state of the located record rather than as a finding about the vendor's contract. A customer agreement exists and is published. The integrated service terms, the paid service terms and the operating policy are all linked from the vendor's own footer and help center. The paid service terms and operating policy are hosted on Notion and return the JavaScript shell rather than a body, and the terms page on the main domain sits behind the same bot detection that blocks the rest of the site to this index. The index's rule governs: a document that is published and machine-unreadable is a limit on the reader, not an absence by the vendor, and it is never graded as a finding against them. The R8 ladder was run in full, including recovery through the vendor's own Korean document vocabulary, which opened the whole help center and policy estate but did not surface the operative liability clauses. So what is recorded is that no warranty position, no liability cap, no indemnity and no insurance statement was located on any readable surface. What was located is commercial rather than liability material and is not credited here: refunds where a paid plan is unused within seven days of payment, or within thirty days on a switch from Standard to Business or Public, no fee reduction where a Business plan's active user count falls mid-term, and a notice-and-objection process for fee changes. The grade would move on a reading of the agreement, and the note says so. Verified 13 September 2026.

Practice Systems Integration Depth

How deeply the product reaches into the systems legal work already lives in: document management such as iManage and NetDocuments, Word and Outlook, contract lifecycle management, matter management, e-billing, and court filing systems.

Jhana.ai
CC on Practice Systems Integration DepthIntegrations are listed as logos or marked as coming, with no documentation an implementer could use.

Interoperability is claimed at the right level for the public sector product and documented nowhere. The vendor states that Courtroom and PUBSEC are interoperable with existing and new systems and are transacted with over API, which is the correct shape for selling into court registries, and the January 2026 CADRE ODR partnership is a named integration into an online arbitration workflow. What does not exist: any API documentation, any authentication or scope detail, any statement of what moves in which direction, and any named integration for private practice. No document management system, no practice management platform, and nothing addressing how a firm gets its own matter files in and its work product out. Checked the home page, the public sector material, the product pages and the blog on 29 Aug 2026.

LBOX
DD on Practice Systems Integration DepthNo integration into practice systems located, or the product stands alone and requires work to move to it.

No integration into the systems legal work already lives in was located, which is the D band, and the product's own shape is part of the explanation. LBOX is built to be the place the work happens rather than a layer over something else: the vendor's own framing is a single AI working environment for lawyers, running search, AI answers and drafting inside its own interface, with projects and folders for organizing matters and sharing within a Business plan. Nothing published describes moving that work anywhere else. No practice management system, document management system, billing system or CRM used by Korean firms is named as supported. No public API reference, developer documentation, connector catalog or authentication model was located, and there is no integrations page anywhere in the navigation or the help center, which is a page-inventory finding rather than an unreachable page. The only external touchpoints located are a mobile application on iOS and Android, which is the same product on another device rather than an integration, and third-party services in the vendor's own processing chain, being optical character recognition and payments, which are supplier arrangements and are not capabilities offered to a customer. Recorded so the D is read correctly: a firm adopting this platform is adopting a destination, and nothing published tells it how the work leaves. Verified 13 September 2026.

Deployment Model and Data Residency

Where the software runs and where the data sits. Multi tenant cloud, single tenant, private deployment, on premises, and whether region of residence is a published option or an enterprise conversation.

Jhana.ai
CC on Deployment Model and Data ResidencyCloud delivery is implied and neither the tenancy model nor the region is stated.

One genuinely strong deployment disclosure sits beside a complete absence for everyone else. For the public sector products the vendor states that the agents are owned and hosted by the courts themselves, which is customer hosted deployment stated plainly and is the strongest such position located in this pull. It is also the correct answer for a judiciary that cannot put case data on a startup's infrastructure. For the commercial product nothing equivalent exists: no hosting provider is named, no region or data residency commitment is published, and no private or single tenant option is described for firms. Cloud vendor program memberships with AWS, Microsoft and Google are startup support programs and are not a hosting disclosure, and are not credited as one. Data residency is a live question in India under the DPDP framework the vendor itself writes about. Checked the home page, the public sector material, the privacy policy and the terms and conditions on 29 Aug 2026.

LBOX
BB on Deployment Model and Data ResidencyDeployment model is stated clearly with partial residency detail, or residency is offered without the processing location being addressed, or the tenancy model is stated on its own with no residency detail published.

Cloud delivery with a genuinely detailed answer on where data goes and a partial one on tenancy, which is B on either limb and is comfortably clear of C on both. Residency is answered with more precision than almost any record in this corpus, because the privacy policy carries a statutory cross-border transfer table naming each recipient, the destination country, the transfer method, what is transferred, the purpose and the retention period. A buyer can therefore establish that text and files entered into LBOX AI are transmitted to the United States to OpenAI, Anthropic, Google, Amazon and Microsoft, that transfers to Amazon and Microsoft are described as traveling over an encrypted network, and that retention at each is capped at 30 days after the purpose is met except Google at 180 days. The policy also states plainly that refusing the overseas transfer means the service cannot be used, and that the only remedy is to close the account, which is an unusually candid statement of the trade-off. Tenancy is claimed rather than described: all material is stated to be held encrypted in customer-dedicated storage, and document visibility is limited to the creator and to Business plan colleagues given sharing rights. What is absent is the domestic half of the picture. No data center, region, cloud provider or hosting arrangement is named for the primary platform, nothing distinguishes storage from processing for Korean-resident data, no residency option or on-premises deployment is offered or refused, and the dedicated-storage claim carries no description of how the separation is implemented. Verified 13 September 2026.

Security Certifications and Trust Center

Independent attestation a buyer can pull without a sales call: SOC 2, ISO 27001, penetration test summaries, a trust center with current reports and named scope rather than a badge image.

Jhana.ai
DD on Security Certifications and Trust CenterNo independent security attestation located.

No certification of any kind was located, and the security language is the unfalsifiable shape this index does not credit. The privacy policy states that appropriate security measures are taken against unauthorised access, alteration, modification, disclosure or destruction, and that generally accepted industry standards are followed. Neither statement names a standard, an auditor, a scope or a date, and generally accepted industry standards is a phrase that cannot be checked or falsified by any reader. Located nothing on SOC 2 of either type, ISO 27001, ISO 42001, CERT-In empanelment or any Indian assurance framework, and no trust center, security page or documentation request route exists. Checked the privacy policy, the terms and conditions, the home page, the product pages and the site footer on 29 Aug 2026. Under the three tier test the artifact is absent rather than gated. Weighed against the deployment position: a vendor whose court customers host the software themselves has offloaded the hardest part of this question for those customers, and published nothing for the rest.

LBOX
DD on Security Certifications and Trust CenterNo independent security attestation located.

No certification held by this vendor and no trust center were located, which is the D band, and the reason the grade is not higher needs stating because the site invites the opposite reading. The home page tells a buyer that all data is processed on verified infrastructure that has obtained global security certification. Read carefully, that is a statement about the infrastructure provider, not about LBOX. The ground rules and R16 both bite here: a cloud provider's certification is infrastructure rather than the vendor's own attestation, and credit follows scope that a buyer can establish. No certificate, attestation or audit report of LBOX itself was located under any standard, whether ISO 27001, ISO 27701, SOC 2 or Korea's own ISMS-P, which is the certification a Korean information service provider of this size would ordinarily hold and publish. No auditor is named, no report period or certificate number appears, no penetration test summary exists, and there is no trust center, security page or compliance page anywhere in the navigation or the help center. What is published instead is a description of controls without third-party validation, and it is substantive: administrative, technical and physical measures set out by category, an internal management plan with inspection, a dedicated organization, regular training, access rights management, an access control system, encryption, security software, access log retention and periodic inspection, and controlled physical access to server and archive rooms. Statutory compliance with the Personal Information Protection Act is asserted and a protection officer is named, and neither is an independent attestation. Verified 13 September 2026.

Model Supply Chain Disclosure

Which models sit underneath, whose they are, where they run, and whether the vendor commits to telling customers when that changes. A legal buyer inherits every dependency it cannot see.

Jhana.ai
CC on Model Supply Chain DisclosureThe vendor refers to advanced or proprietary models without identifying what sits underneath.

Processor categories are disclosed, a list is promised, and no entity is named. The privacy policy states that personal information may be disclosed to entities that may qualify as data processors under the DPDP Act, listing categories including hosting service providers, cloud computing entities, IT service firms, marketing and advertising agencies and web analytics companies, and states that the vendor will make efforts to disclose an updated list of key processors. A promise to publish is not a publication, and no such list was located. On the model layer specifically: the vendor claims proprietary verifier and graph models, which is a supply chain statement of a kind, and never says whether any third party foundation model sits underneath the agents, which is the question a buyer needs answered. Compare Onspring at B, the only record on this index that names its model provider outright.

LBOX
BB on Model Supply Chain DisclosureThe supply chain is partly disclosed: providers named without change notification, or architecture described without the providers.

The supply chain is partly disclosed, which is the B band by design, and the part that is disclosed is the most complete provider naming located in this pull. The privacy policy's cross-border transfer table identifies, by legal entity and contact address, every party that receives what a user types into LBOX AI: OpenAI LLC, Anthropic PBC, Google, Amazon and Microsoft, each with the purpose stated as generating the answer to the user's question, and Microsoft additionally for optical character recognition of uploaded files. Upstage is named as the domestic processor performing the same OCR conversion. Each entry carries a retention period, 30 days after the purpose is met for all but Google, which is 180. Change notification, which R34 counts as a distinct limb and which most records lack entirely, is committed: the vendor undertakes to disclose without delay through the privacy policy any change of processor or of the scope of the work, and states that re-delegation requires its consent and is published. What holds this off A is the limb the index's rule makes decisive: providers are identified and the models themselves are not. No model or version is named for any of the five providers, nothing states which provider serves which function or how requests are routed between them, and nothing distinguishes the vendor's own retrieval layer from the frontier models it calls. The company's own LCUBE model, released with an academic partner in 2022, is not described as part of the current stack and is not credited as one. So a buyer learns exactly whose infrastructure sees its content, and not what is running on it. Verified 13 September 2026.

Commercial Transparency

Whether a buyer can learn what this costs without entering a sales process: published rates, the unit being charged, what sits behind an enterprise tier, and what implementation adds.

Jhana.ai
CC on Commercial TransparencyPricing is gated behind a demo request while tier names and feature splits are published, so the shape is visible and the number is not.

A free tier is quantified and the paid ladder is behind a login. Published free tier limits are specific: ten paralegal sessions, fifteen searches and thirty file document intelligence per month, which tells a buyer both the unit of consumption and the shape of the meter, and is more structural disclosure than most of this roster offers. Beyond that, plan details require signing in, and no price, currency or range for any paid tier was located. Held at C rather than higher because the headline is visible and the actual cost is not, and a buyer cannot compare against an incumbent subscription without creating an account. Source basis recorded as Third Party Estimated: the free tier limits come from an independent review platform's product assessment dated July 2026 rather than from a vendor pricing page read directly, and that assessment itself notes pricing is not fully public and may be out of date.

LBOX
BB on Commercial TransparencyReal pricing is published for part of the range, with enterprise tiers withheld, or the unit and structure are stated without the figure.

Real pricing is published for part of the range with the enterprise tiers withheld, which is the B band in its own words. The structure is fully published and ungated: an individual Standard plan, Business and Enterprise plans for firms and legal departments, a Law School plan for students, and a Public plan offered to government and public institutions on IP authentication, with discounts published for members of bar associations and of the labor attorney and loss adjuster bodies under partnership arrangements. The unit of charge is clear, being per user per month for Standard, per seat with volume discounting for Business and Enterprise, and institution-wide by IP for Public. The commercial mechanics are published in the operating policy rather than hidden: refund where a paid plan is unused within seven days of payment, or within thirty days on a switch from Standard to Business or Public, expressly no fee reduction or refund where a Business plan's active user count falls during a term, and fee changes announced in advance with an objection window and an opt-in for preferential rates. Figures exist and are the vendor's own, published in its fee-change notices: a Standard monthly rate moving from 29,900 won to a six-month preferential 39,900 won and then to 69,900 won. Two limits keep it off A and are stated rather than implied. Those figures come from a fee-change notice rather than from a current rate card, so their age goes in the note under the standing rule that age never enters the grade; and the live pricing page, which exists and is ungated, sits behind the bot detection that blocks the whole main domain to this index, so what a buyer sees there today could not be read. Business and Enterprise pricing is quoted rather than published in any event. Verified 13 September 2026.

Firm and Practice Coverage

Who the product is actually built for. AmLaw, midlaw, small firm and solo, in house departments, government and courts, and which practice areas are supported rather than merely claimed.

Jhana.ai
BB on Firm and Practice CoverageSegment and practice coverage is described with substance, short of the boundaries: what is supported is clear, what is not is left open.

Corpus scale and jurisdiction are stated precisely and the vendor is candid that the scope is one country. More than 16 million judgments and statutes in a corpus described as India's National Legal Archive, with the explicit positioning that this is purpose built for the Indian legal context rather than a general model with a legal skin. Named user populations span private practice lawyers, law firms, in house teams, judges and registrars across five or more courts, founders, tax professionals and compliance teams, and published subject matter reaches SEBI regulations, AML and CFT, the DPDP Act and Rules, the IT Act and Supreme Court authority on Section 65B evidence certification. Single jurisdiction scope is a limitation for a buyer outside India and is not a disclosure failure. Held at B rather than A because the corpus is not broken down: no list of which courts, tribunals and forums are included, no statement of historical depth, and no update lag or refresh frequency, so a practitioner cannot confirm their own forum is covered or how current it is.

LBOX
BB on Firm and Practice CoverageSegment and practice coverage is described with substance, short of the boundaries: what is supported is clear, what is not is left open.

Segment coverage is described with real substance and the practice boundaries are left open, which is the B band. Who this is for is set out more precisely than most records manage, and it is set out as an enforced eligibility rule rather than as marketing. Named professional segments are lawyers, judicial scriveners, labor attorneys, tax accountants, patent attorneys and accountants, each with its own verification route. Institutional segments are named too: courts, prosecution offices, police and legal research institutions, reached through recognition by the vendor, and government and public bodies through an IP-authenticated Public plan the company describes as a social contribution. Law firms and in-house legal departments are addressed through Business and Enterprise plans with an administrator and user distinction, students through a Law School plan with defined eligibility including repeat bar candidates and doctoral students, and non-lawyer staff only under a qualified professional's supervision. Content coverage is Korean, spanning court precedents, statutes and administrative rules, with the company's own commentary and practice texts layered over it through its Scholar imprint. What is left open is the practice dimension. No practice area is named as supported or unsupported, nothing states which courts or which years the judgment database reaches, and nothing says whether the AI agent covers the whole corpus or only parts of it. Jurisdiction is Korea throughout and is never stated as a limit, which matters for a buyer with cross-border work. Verified 13 September 2026.

The 12 legal signals, side by side

Recorded rather than graded. These are the questions a practitioner has to answer before a tool touches a client matter, and the answers are taken from public material only.

Client Data in Training

Can material a lawyer puts into this product be used to train a model?

Jhana.ai
Opt out

Recorded at opt-out, which is the weakest position the vendor's own text establishes, because the two statements it makes cannot both be complete. The quoted sentence appears on the home page, and the sentence immediately following it states that free users have the choice to opt out of sharing data for model training. A choice to opt out only exists where the default is participation, so free tier data is used for training unless the user acts, which contradicts the blanket claim.

Reading the stronger sentence alone would credit a never commitment the vendor has qualified in the next breath. Both statements sit on a marketing page rather than in the terms and conditions or the privacy policy, neither of which was found to address model training at all, so even the stronger reading is policy rather than contract. Checked the home page, the terms and conditions and the privacy policy on 29 Aug 2026. This is the clearest instance in the pull of why the value set separates contract from policy.

LBOX
Never, in policy only

Public material states that customer content is not used to train, with no matching term located in a published agreement, which is this value. The statement sits on the product surface and is direct: personal information in queries and uploaded files is not used for AI model training. Around it the vendor publishes a purpose limitation that does most of the practical work, stating that text entered as a query and files uploaded are used only during the process of generating the answer and are deleted immediately once the collection and use purpose is met, and the privacy policy caps retention at each overseas model provider at 30 days after that purpose is achieved.

Two qualifications belong on the record rather than in the value. The training sentence is written about personal information within queries and files rather than about the content of those files as such, so read strictly it is narrower than a general no-training commitment; what closes that gap is the immediate-deletion commitment, since material deleted on completion is not available as training data. And the value is policy rather than contractual because R43(1) was run and could not be discharged: the integrated terms, the paid service terms and the operating policy are all published and linked from the vendor's own footer, and all three are machine-unreadable to this index, the first behind the site's bot detection and the others as JavaScript shells.

The three-way choice therefore remains live for a later pass in the manner recorded on Anytime AI, and a reading of the agreement could move this row in either direction.

Prompt and Output Retention

How long does the product keep what a lawyer typed, and can that be set to zero?

Jhana.ai
Disclosed without a period

Disclosed vaguely. The privacy policy gives users a route to request erasure of personal information and account closure by email, which is a real control, and then states that some information may be retained for legitimate business interests such as fraud detection and prevention and safety, and to meet tax, legal reporting and audit obligations. That describes the exceptions without ever stating the rule. No retention period is given for anything, no distinction is drawn between account data and uploaded matter documents or paralegal session content, and nothing indicates whether retention is configurable or can be set to zero.

A user knows they can ask for deletion and not what is kept, for how long, or which of their case files fall inside the carve outs. Checked the privacy policy, the terms and conditions and the home page on 29 Aug 2026.

LBOX
Disclosed fixed window

A fixed period is published, and it is published twice at two different levels, which is this value. At the product level the vendor states that query text and uploaded files are used only while the answer is being generated and deleted immediately once the collection and use purpose is achieved. At the processor level the privacy policy's cross-border transfer table sets an explicit ceiling for each recipient of that same content: a maximum of 30 days after the purpose is met for OpenAI, Anthropic, Amazon and Microsoft.

The discrepancy inside that table is named rather than averaged away, because a reader who finds it unaided and does not find it here would trust the record less: Google's entry is not 30 days but 180, stated as until the collection purpose is achieved or the retention period of 180 days expires. Nothing explains why one provider holds the same material six times longer than the others. Behavioral and usage data is treated separately and held until the member withdraws, covering search terms entered, search result clicks, AI query submission history, and document creation, saving and download history, collected through named third-party software development kits.

Statutory retention is set out instrument by instrument, including three months for communication confirmation data and five years for contract and payment records. The customer agreement, which would ordinarily carry a return or deletion obligation on termination, is published and unreadable to this index.

Ethical Walls and Matter Segregation

Does retrieval respect the firm’s ethical walls, or can the model read across them?

Jhana.ai
Not addressed

Not addressed. No permission model, access control statement or segregation description was located for either the private practice product or the public sector agents. Nothing indicates whether one user's uploaded case files are reachable by another user in the same firm, whether matter level restriction is possible, or how retrieval behaves across a shared workspace. The vendor describes a collaborative interface, which raises the question rather than answering it.

There is no document management system integration to inherit permissions from. Checked the home page, the product pages, the privacy policy and the terms and conditions on 29 Aug 2026.

LBOX
Own model, documented

A permission model is described rather than merely claimed, which is this value. The rule is stated at document level and in the vendor's own words: material a user creates is viewable by that user alone, and beyond them only by Business plan members who have been granted sharing rights. That is a default-closed model with an explicit grant, which is the substance of a wall between colleagues inside the same subscribing organization, and it is the form of segregation a firm actually needs.

Around it sit two supporting statements: all material is held encrypted in customer-dedicated storage, which is a tenant-level separation claim, and work is organized into projects and folders that carry the sharing boundary. The Business and Enterprise plans distinguish administrators from users, and the help center addresses what happens to a departing employee's projects when a corporate account is closed, which indicates the model is administered rather than notional.

What is not published keeps this off the top of the range. Nothing describes the roles or permission levels available, how a grant is made or revoked, whether an administrator can read a user's projects, or whether any audit record of access exists. Nothing addresses conflicts or matter-level walls as a legal concept rather than as a sharing setting, which is the framing a Korean firm managing a conflict would look for.

And on the vendor's own side, no statement was located limiting which staff may view customer material or requiring that such access be logged.

Third Party Request and Subpoena Notice

If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?

Jhana.ai
Not addressed

Not addressed. The privacy policy states that personal data may be processed for certain legitimate uses where required in compliance with the Digital Personal Data Protection Act 2023, the Information Technology Act 2000 and other laws. That discloses that lawful processing may occur; it is not a commitment to notify the customer before producing their data to an authority. No notice commitment, no stated process, no window and no transparency report were located.

Checked the privacy policy, the terms and conditions and the site footer on 29 Aug 2026. Worth flagging for a later reader that this vendor's public sector agents are deployed inside courts and registries, which makes the relationship between vendor, customer and state less arm's length than usual.

LBOX
Disclosure addressed, notice absent

Compelled disclosure is addressed and customer notice is absent, which is this value. The privacy policy states that where a state agency requests provision under the procedure and method prescribed by law, the company may provide personal data to a third party. The trigger is narrower than most in this corpus, being tied to a statutory procedure rather than to any legal request or to protecting the vendor's own interests, and the surrounding third-party provision regime is consent-based and enumerated, listing only the lawyer receiving a consultation request and the payment provider, each with the items provided and the recipient's retention period.

One unusual feature is recorded because it is a real mitigation and is rare: the same clause commits the company, where such a disclosure occurs, to state the fact in the privacy policy itself. That is a published-transparency undertaking rather than a transparency report, and it is more than most vendors offer, but it is a disclosure to the world after the event and not notice to the affected customer. What is absent is the thing this signal names.

Nothing states that the subscriber would be told a demand had been received, given an opportunity to object or to seek relief before production, or informed afterwards, and no transparency report or law enforcement guidelines page exists. The customer agreement, which might carry a notice term, is published and unreadable to this index, so the row records the policy position.

Primary Law Corpus Provenance

Where does the law in this product come from, and does the vendor have the right to use it?

Jhana.ai
Jurisdictions only

Jurisdiction stated, sources not. India is named unambiguously and the corpus is quantified at more than 16 million judgments and statutes described as India's National Legal Archive, machine enhanced and proprietary. That is a clear jurisdictional boundary and a real scale claim. What is absent is everything a researcher would check: no list of which courts, tribunals or forums are included, no historical coverage range, no statement of the license or public domain basis on which Indian judgments and statutes were obtained, and no update lag or refresh frequency.

The machine enhanced description also leaves open what was altered in processing, which is a provenance question about the archive itself rather than about its sources. Checked the home page, the product pages and the blog material on 29 Aug 2026.

LBOX
Sources named, basis unstated

The sources are identifiable and the licensing basis for the main corpus is not stated, which is this value. What the corpus consists of is clear enough from the vendor's own surfaces: South Korean court judgments across instances, statutes and administrative rules, with the linking between lower and appellate decisions singled out by its own users as the distinguishing feature. The published research the company did with an academic partner describes the same underlying material at scale, a corpus of 147,000 Korean precedents amounting to 259 million tokens.

What is not published is the basis on which the judgment database is held. Nothing states how judgments are obtained, under what statutory access route or agreement, whether any court or government body licenses them, or what the vendor may do with them, which is a live question in Korea where access to written judgments has been a contested policy matter rather than a settled open-data position. One part of the corpus is licensed and is licensed transparently, and it is recorded as the exception rather than allowed to carry the row: LBOX Scholar commissions commentaries, practice texts and articles from named academics and practitioners, publishes them as citation support inside AI answers, and settles royalties with the author on the basis of actual usage, with the author shown how often the AI cited their work.

That is an express licensing arrangement with a named counterparty class and a consideration, and it covers the secondary material rather than the precedents. Verified against the surfaces read on the date shown.

Good Law Verification

Does the product tell you when the authority it just cited has been overruled?

Jhana.ai
Not addressed

Not addressed, and this one was nearly recorded higher on material that does not qualify. A third party company profile states that the platform automatically detects contradictions and flags outdated citations, which if it appeared in vendor material would support an own treatment signal value. It does not appear in vendor material. Under the standing rule that a credential must appear in the vendor's own material, because directories and review sites routinely attribute capabilities a vendor never claimed, it is not credited and is recorded here so the next reader knows it was seen and rejected rather than missed.

What the vendor itself publishes is that its agents always cite their work and that verifier models are proprietary technology. Citing an authority is not checking whether that authority is still good law, and no citator, treatment signal or overruled and superseded flag is described anywhere in vendor material. Checked the home page, the product pages, the blog and the public sector material on 29 Aug 2026.

LBOX
Not addressed

No located public material addresses whether authority is checked for subsequent history, and the note distinguishes what is genuinely absent from what is adjacent. The adjacent capability is real and is what users praise: the platform links a case across instances, connecting first instance to appellate to Supreme Court, and that linkage is repeatedly named as the reason practitioners prefer it. Cited precedents and statutes are also linked and openable from an AI answer.

But instance linking is case history, not treatment. It tells a reader what happened to this case on appeal; it does not tell them whether the proposition the case stands for has since been overruled, distinguished, doubted or superseded, and no flag, indicator, status or treatment vocabulary of any kind was located. Nothing states whether a judgment surfaced by AI Search or cited in an answer is still good law, and nothing describes any editorial or algorithmic process that would establish it.

The gap is worth naming plainly because of what the product is: an agent that selects and presents precedent to verified lawyers, in a jurisdiction whose courts have begun demanding explanations for citations that turn out not to hold. The surfaces read on the date shown were the product home page, the AI landing page, the Scholar pages, the help center in full including the release and policy notices, and the mobile listing.

Refusal and Uncertainty Behavior

What does the product do when the answer is not in the corpus?

Jhana.ai
Not addressed

Not addressed. No explicit no answer path, abstention behavior or confidence signal is documented. The named verifier model implies a checking step and nothing states what happens when the check fails: whether the agent declines, flags the output, retries, or returns it anyway with a citation. For a research product whose central claim is that its agents always cite their work, the behavior when nothing supportable is found is the load bearing case, and it is undocumented. Checked the home page, the product pages, the blog and the terms and conditions on 29 Aug 2026.

LBOX
Not addressed

No located public material describes what the system does when it cannot produce a reliable answer. What the vendor publishes is a claim about the rate of the problem rather than a description of the behavior: answers are generated from its own legal data so as to minimize the hallucination that can arise with general-purpose AI. That is an architectural argument for fewer bad answers, not a statement of what happens when one is about to be produced.

Nothing states that the agent declines a question outside its corpus, reports that it found no supporting authority, attaches a confidence signal to an answer, marks a low-confidence passage for checking, or escalates rather than answering. The question has particular force on this product because of the architecture the vendor itself describes: the agent plans and executes the whole sequence, deciding what to search, judging what it has found and composing the answer, and the vendor states that it verifies information as part of that loop.

Verification is asserted as a step in the pipeline, and nothing published says what the step does when it fails. The user-side mitigation that exists is real and is recorded without being credited as this signal: cited precedents, statutes and Scholar passages are linked so a lawyer can open the source and check the answer against it, which is the reader's diligence rather than the system's behavior. The surfaces read on the date shown were the product home page, the AI landing and agent announcement pages, the help center in full, and the mobile listing.

Fabricated Citation Record

Does a public court record exist addressing fabricated or hallucinated legal citations in output from this product?

Jhana.ai
None located

None located, with the instrument named so the finding is worth what the search is worth. General web searches combining the vendor and product names with court, judgment, order, hallucination, fabricated citation and disciplinary terms returned nothing on 29 Aug 2026. No Indian court record database was searched, and none of the Indian judgment reporting services was queried directly, so the instrument here is weaker than the subject deserves: this is a research product deployed with judges and registrars in Indian courts, and an Indian docket search would be the correct instrument.

Recorded as a statement about what this search found and not as a clearance, and flagged as worth revisiting with a proper Indian court record search.

LBOX
None located

Searched on 13 September 2026 against the company name in Korean and English and against the product name, across Korean legal press reporting on AI-generated fabricated citations and the international trackers. None located. No decision, order or disciplinary finding names LBOX or LBOX AI. Context is recorded because the jurisdiction is now live on this question and a reader should be able to see that the absence was tested against a real body of cases rather than an empty field.

Korean legal press reported in 2026 the first domestic instance of fabricated citations reaching a court, a criminal division finding that five judgments cited in an advocate's written opinion did not exist on the court network, the advocate withdrawing them and then acknowledging under questioning that AI had been used; separate reporting describes a court ordering a party to file an explanation of how a fabricated judgment came to be cited and to produce the originals of every Supreme Court decision relied on, and describes courts and bar bodies weighing what sanctions should follow.

No product is named in any of that reporting, and general-purpose assistants rather than legal platforms are what the accounts describe. This signal records fabricated legal citations in filings and nothing else, so no other proceeding involving this vendor would appear here.

Bar Guidance Alignment

Has the vendor engaged in public with the ethics opinions its buyers are bound by?

Jhana.ai
Not addressed

Not addressed. No engagement with Bar Council of India rules, no reference to advocate conduct or advertising restrictions, and no named professional guidance of any jurisdiction was located. The vendor publishes substantial regulatory analysis for its customers, covering SEBI regulations, AML and CFT, the DPDP Act and Rules and Section 65B evidence certification, so the capacity to engage with a professional rules framework plainly exists and has not been turned toward the duties of the advocates using the tool. Checked the home page, the product pages, the blog index and the terms and conditions on 29 Aug 2026.

LBOX
Generic reference

Professional responsibility is engaged in general terms without any authority being named, which is this value, and the engagement here is more operational than most records at this level. The vendor restricts who may use the AI agent by professional qualification, verifying lawyers, judicial scriveners, labor attorneys, tax accountants, patent attorneys and accountants against documentary proof, admitting staff of courts, prosecution offices, police and legal research institutions it recognizes, and permitting other employees only under the prior approval and the direction, supervision and review of a qualified legal professional.

It frames that regime as continuing review so that those working in law can use legal AI lawfully, which is an explicit if unnamed reference to the Korean statutory framework governing who may perform legal work. The Korean Bar Association appears on the estate, but only as an identity source: bar membership card registration and issue numbers are collected to verify that a member is a lawyer, and bar association partnership discounts are offered.

That is credential plumbing, not alignment. What is absent is any named authority or guidance. No provision of the Attorney-at-Law Act is cited, no Korean Bar Association opinion, ethics rule or AI guidance is referenced, and no court guidance is mapped to the product, at a moment when Korean courts have begun demanding explanations for citations that do not exist and bar bodies are publicly weighing what sanctions should follow. Nothing connects the agent's output to the verification duty falling on the lawyer who files it.

Billing and Fee Posture

Does the vendor address what happens to the bill when the work takes an hour instead of six?

Jhana.ai
Not addressed

Not addressed. Nothing published addresses billing for AI assisted time, and no record is described that an advocate could produce to a client showing what was machine generated. Published metering describes what the customer is charged by the vendor, in paralegal sessions, searches and files per month, which is the vendor's own pricing unit rather than a fee posture toward the end client. Checked the home page, the pricing material and the terms and conditions on 29 Aug 2026.

LBOX
Not addressed

Nothing published addresses what happens to the bill when AI-assisted work takes an hour instead of six, which is the floor, and none of the higher values is true of this record. The product sits inside a lawyer-to-client fee relationship: its buyers are verified practicing lawyers and law firms on Business and Enterprise seats, and legal research time in Korea is conventionally either billed or absorbed into a fee. Nothing states which.

No per-matter record of AI-assisted work is described, nothing marks output as machine-generated for the purpose of a bill or a fee note, no guidance on fee or disclosure treatment is published, and no saving is claimed in billable terms. The vendor's efficiency claims are framed as productivity for the practitioner rather than as time removed from a client's invoice, and the one quantified claim located anywhere is a bar-examination accuracy comparison in press coverage, which is about quality rather than cost.

Recorded and expressly not credited, because subscription cost is a different object from AI-assisted work: the platform publishes per-seat pricing, volume discounts for Business and Enterprise, bar association partnership discounts, and refund mechanics, all of which would let a firm attribute software cost to a matter and none of which addresses the client's bill. All four higher values being false, this is a gap rather than a grading error and the summary carries it.

Outside Counsel Guideline Readiness

Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?

Jhana.ai
Not addressed

Not addressed, with a promise on the record that has not been kept. The privacy policy states that the vendor will make efforts to disclose an updated list of key entities engaged as data processors, and no such list was located. Categories are given, including hosting providers, cloud computing entities, IT service firms, marketing and advertising agencies and web analytics companies, but no entity is named. No model provider disclosure, no trust center, no security documentation and no request route exist, so a firm has nothing it could forward to its own client.

The undertaking to publish is noted here because it is checkable later and gives a reader a specific thing to look for on the next verification pass. Checked the privacy policy, the terms and conditions, the home page and the site footer on 29 Aug 2026.

LBOX
Subprocessors listed

A current processor list and a model provider statement are both published and no forwardable client-facing pack sits around them, which is this value under R29's IPRally condition. Two of the three artifacts are present and are the most complete in this pull. The privacy policy enumerates every processor, domestic and overseas, including re-delegated parties: payment and identity providers with their own re-delegates named, Upstage for optical character recognition of uploaded files, and messaging and mailing suppliers.

Separately, and this is what answers a client's AI clause, the cross-border transfer table names by legal entity every recipient of what a user types into LBOX AI, being OpenAI LLC, Anthropic PBC, Google, Amazon and Microsoft, with the destination country, the transfer method, the purpose stated as generating the answer, a contact address for each, and a retention period of 30 days after purpose except Google at 180.

That satisfies the model provider limb outright rather than partially, and infrastructure is not doing the work: three of the five are model providers named as such. The vendor also commits to publish any change of processor without delay. The third limb fails. There is no data processing addendum, no consent or notification pack drafted to be forwarded, and no client-facing disclosure artifact of any kind; the disclosure lives in a privacy policy written for the data subject under Korean statute.

R29's condition is explicit that where the list sits outside a DPA and no other forwardable artifact exists, the value drops rather than the top two values collapsing into each other. A firm can nonetheless forward the policy and answer its client precisely, which is more than most records at this value permit.

Court Disclosure Support

If a judge’s standing order requires an AI disclosure, can the product produce one?

Jhana.ai
Partial record

Partial record, and the source linking is the strongest element of it. Published product material shows output where each conclusion sits one click from the underlying source page and extracted figures are anchored to page and paragraph, and the vendor states its agents always cite their work, so a user can produce what the system relied on and where it came from. That is the sources retrieved limb, evidenced rather than asserted.

The other two limbs are missing: nothing indicates that output records which model produced it, and nothing describes a human verification record or an export a court could be handed. The gap is sharpest in the public sector products, where Courtroom runs extraction, synopsis and forensic scrutiny inside judicial and registry workflows and no disclosure artifact is described for work a court itself would need to stand behind.

LBOX
Not addressed

No located public material addresses disclosure of AI involvement in legal work, which is the floor, and on this record the absence is more pointed than on most because the jurisdiction has begun asking the question directly. Nothing identifies output as machine-generated once it leaves the platform. No audit trail of AI use is described, no per-query or per-matter record a firm could produce, no export designed to evidence what the agent did, no certification template, and no guidance on when or how AI assistance should be disclosed to a court or a client.

The platform records AI query submission history as behavioral telemetry for its own analytics, held until the member withdraws, and nothing indicates that record is available to the subscriber as evidence of its own use. Two adjacent features are recorded and not credited. Cited precedents, statutes and Scholar passages are linked and openable from an answer, which supports verification before filing rather than disclosure after it.

And documents generated in the platform sit in projects with sharing controls, which is storage rather than provenance. The concrete consequence is worth naming: Korean courts have begun ordering parties to explain how a fabricated citation came to be filed and to produce the originals of the authorities relied on, and a lawyer using this agent has nothing published that would let them show afterwards which passages the model produced and which authority it drew on at the time.

What neither one publishes

The questions both sides leave open

Derived from the records above rather than written, so it cannot favor either vendor. Take these into both conversations and ask each side the same question.

Axes where neither earns credit
  • AI Governance and Bias Disclosure
  • AI Liability and Recourse
  • Security Certifications and Trust Center
Signals neither addresses in public material
  • Good Law Verification
  • Refusal and Uncertainty Behavior
  • Billing and Fee Posture

Which one fits

Choose Jhana.ai if

  • Your problem is Indian law. Jhana.ai researches and drafts over a corpus of more than 16 million Indian judgments and statutes, with each conclusion linked to its source page and extracted figures anchored to page and paragraph.
  • You run a court registry or public body. Jhana.ai's Courtroom and PUBSEC agents handle extraction, synopsis, research and drafting, are owned and hosted by the courts themselves, and are used by more than 150 judges and registrars.
  • You want to try it without paying. Jhana.ai offers a free tier with ten paralegal sessions, fifteen searches and thirty document intelligence files a month, with paid plans behind a login.

Choose LBOX if

  • Your problem is South Korean law. LBOX searches Korean judgments, statutes and administrative rules, links a case across first instance, appeal and Supreme Court, and its AI agent plans, searches, verifies and drafts in one sequence.
  • You need the AI kept to qualified professionals. LBOX verifies lawyers, judicial scriveners, labor attorneys, tax accountants, patent attorneys and accountants against documents, and lets other staff use the agent only under a qualified professional's supervision.
  • You must tell clients where their queries go. LBOX's privacy policy names OpenAI, Anthropic, Google, Amazon and Microsoft as recipients of AI queries, with a retention ceiling for each, and states queries and uploads are deleted once the answer is generated.

In summary

Jhana.ai

Jhana.ai, founded in 2022 and based in Bengaluru, is an AI legal research and drafting platform built for Indian law, marketed as India's first AI paralegal, over a corpus of more than 16 million judgments and statutes. AI Paralegal produces propositions, citations, advisories and memos, Document Intelligence reviews documents, and Courtroom and PUBSEC agents serve courts and public bodies. The AI Legal Index grades it in the top two bands on four of fifteen capability axes, with an A on AI centrality. It reports more than 10,000 users and over 150 judges and registrars. As of 29 August 2026 the index located no security certification, named model or paid price.

Source: AI Legal Index, 2026

LBOX

LBOX, from LBOX Co., Ltd. of Seoul, is a Korean legal research and AI platform built on South Korean judgments, statutes and administrative rules, with LBOX AI, an agent that plans, searches, verifies and drafts, and a publishing arm, LBOX Scholar. The AI Legal Index grades it in the top two bands on ten of fifteen capability axes. It limits the agent to verified legal professionals and supervised staff, names OpenAI, Anthropic, Google, Amazon and Microsoft as recipients of AI queries, deletes queries once answered, and publishes a Standard rate of ₩69,900 a month. As of 13 September 2026 the index located no security certification of its own or readable customer agreement.

Source: AI Legal Index, 2026

Questions buyers ask

Are Jhana.ai and LBOX alternatives to each other?

Only in the sense that each is a national legal AI platform: Jhana.ai covers Indian law and LBOX covers South Korean law, so a buyer chooses by jurisdiction. On the AI Legal Index LBOX sits in the top two bands on ten of fifteen capability axes and Jhana.ai on four of fifteen. LBOX publishes more on eligibility, data flows and providers; Jhana.ai reports deployment inside courts.

Does Jhana.ai train on customer data?

Its home page says it does not train on any customer data, and the next sentence says free users can opt out of sharing data for model training, which implies free tier data is used unless the user acts. Neither statement appears in its terms or privacy policy. LBOX states that personal information in queries and uploads is not used to train AI models. Graded by AI Legal Index against 15 capability axes and 12 legal signals, including privilege handling and citation accuracy, from each vendor's own published materials, verified September 27, 2026. No vendor pays for placement.

Who can use LBOX's AI agent?

Members verified against documents as lawyers, judicial scriveners, labor attorneys, tax accountants, patent attorneys or accountants; staff of courts, prosecution offices, police and legal research institutions it recognizes; and employees of other organizations only with a qualified professional's prior approval and under that professional's supervision. Public institutions use an IP authenticated plan. Graded by AI Legal Index against 15 capability axes and 12 legal signals, including privilege handling and citation accuracy, from each vendor's own published materials, verified September 27, 2026. No vendor pays for placement.

How much do Jhana.ai and LBOX cost?

LBOX's fee notice sets its Standard individual plan at ₩69,900 a month, with Business and Enterprise quoted per seat and discounts for bar association members. Jhana.ai offers a free tier of ten paralegal sessions, fifteen searches and thirty document files a month, according to an independent review; its paid plans require a login. Graded by AI Legal Index against 15 capability axes and 12 legal signals, including privilege handling and citation accuracy, from each vendor's own published materials, verified September 27, 2026. No vendor pays for placement.

What do Jhana.ai and LBOX both leave unpublished?

A security certification, an AI governance position and a good law check. Neither holds a certification of its own, neither describes how its models are tested or who is accountable for them, and neither checks whether a cited judgment has since been overruled. Neither publishes a vendor commitment on wrong output. Graded by AI Legal Index against 15 capability axes and 12 legal signals, including privilege handling and citation accuracy, from each vendor's own published materials, verified September 27, 2026. No vendor pays for placement.

Disclosure

Three readings to weigh. Jhana.ai's privacy policy allows disclosure to marketing, advertising and analytics processors without separating account data from uploaded case files. LBOX's customer agreement is published but could not be read by this index, and its privacy policy lets Google retain AI queries for up to 180 days against 30 for its other providers. LBOX's published monthly rate comes from a fee change notice rather than a current rate card. Jhana.ai was verified on 29 August 2026 and LBOX on 13 September 2026. Neither vendor reviewed this page.

Neither vendor paid for inclusion, placement or a grade, and neither reviewed this page before it published. Everything above comes from public material on the dates shown. How the index grades.

Contact

Correct a record, or ask how something was graded

Every grade and every signal on this index is drawn from public sources and dated. If a record is wrong, out of date, or missing an artifact the index did not locate, send the source and it will be reviewed and the record redated. Vendors are welcome to submit documentation. Nothing on this index is for sale, including a listing, a placement, or a grade.

AI Legal Index

The AI Legal Index is an independent index that tracks changes to AI vendors in legal. It holds 303 vendors across 9 categories, each graded on the same 15 capability axes and recorded against 12 legal signals, from public sources. No vendor pays for inclusion, placement, or rating.

Index Status
Last index update
September 26, 2026
The AI Legal Index is an editorial reference. It is not a regulatory body, not a law firm, and nothing published here is legal advice or a recommendation to retain or avoid a vendor. Records are verified against published sources, bar guidance and public court records. Where a record reads not addressed, the material was not located in public sources on the date shown. See the Methodology page for evaluation standards and limitations.
© 2026 AI Legal Index
3801 N Capital of Texas Hwy, Ste E240 · Austin, TX 78746