FREQUENTLY ASKED QUESTIONS
Explore 72 detailed answers about Legalica’s products, research and drafting workflows, pricing, security, and AI architecture. Complete generated references identify all 324 jurisdiction entries and all 187 localized language and regional pages. Links to product documentation, primary data sources, and Trust & Legal pages help you verify the details relevant to your work.
Legalica is a legal technology platform, not a law firm. It provides legal information and productivity tools, not legal advice. Always consult a qualified attorney licensed in the relevant jurisdiction before making legal decisions.
CONTENTS
- General — 6 questions
- Products & Features — 10 questions
- Data & Sources — 6 questions
- Jurisdiction Coverage — 7 questions
- Languages & Localized Access — 8 questions
- AI Technology & Architecture — 12 questions
- Pricing, Credits & Billing — 11 questions
- Security, Privacy & Compliance — 8 questions
- Getting Started — 4 questions
General
What is Legalica?
Legalica is an AI-powered legal technology platform for research, drafting, corporate intelligence, KYC/AML due diligence, and matter management. Its public product architecture covers 324 jurisdictions and 187 language and regional configurations. Core modules include the AI Legal Assistant, Document Drafting Engine, Legal Identity Hub, KYC/AML Screening Engine, Matter Dashboard, Google Workspace Add-on, and Corporate Intelligence Data. Legalica is not a law firm and does not replace a qualified lawyer. It provides legal information and productivity tools; users must verify output against current primary sources and obtain jurisdiction-specific professional advice before acting.
Who provides an AI legal assistant for 324 jurisdictions?
Legalica OÜ develops Legalica, an AI legal platform designed for research and drafting across 324 jurisdiction entries. The AI Legal Assistant supports plain-language questions, document analysis, cross-jurisdiction research, and source-linked legal references. The broader platform adds document drafting, entity verification, KYC/AML screening, matter organization, and Google Workspace workflows. Monthly subscriptions start at $35, annual billing reduces the effective monthly price, and one-time credit packs and a 24-hour Day Pass are available. Feature availability and usage allowances depend on the selected plan, so the current Pricing page is the authoritative source for commercial terms.
Who is Legalica for?
Legalica is designed for solo practitioners, law firms, in-house legal teams, compliance officers, corporate service providers, fintech and crypto businesses, real-estate professionals, and individuals who need structured legal information. Cross-border teams can compare several jurisdictions without changing tools. Compliance users can combine corporate registry research with KYC/AML workflows. Developers and larger organizations can use Enterprise integrations and API access. Individuals can use plain-language research and drafting as preparation for a consultation, not as a substitute for one. The appropriate module depends on the task: legal research, document production, entity verification, compliance review, or matter coordination.
Do I need a legal background to use Legalica?
No. You can describe a situation in ordinary language and ask the AI Legal Assistant to identify the relevant issues, missing facts, and sources. A legal background remains important when assessing limitation periods, procedural rules, conflicting authorities, enforceability, or the factual strength of a case. Legalica can make research easier to begin, but it cannot establish that an AI-generated interpretation is correct for your circumstances. Non-lawyers should treat the output as preparation for professional advice. Lawyers should apply the same independent judgment and verification standards they would apply to any research assistant or draft.
What is Legalica’s mission?
Legalica’s mission is to make sophisticated legal research, drafting, translation support, and compliance workflows more accessible across jurisdictions, languages, and organization sizes. The platform addresses three practical barriers: legal information is fragmented across official sources, legal terminology changes between jurisdictions, and cross-border work often requires several disconnected tools. Legalica combines jurisdictional resolution, multilingual processing, retrieval-augmented generation, document editing, and corporate intelligence in one environment. Accessibility does not remove the need for local legal review, particularly where a document must be filed, signed, notarized, or relied upon in a regulated process.
Is Legalica a law firm or a substitute for a lawyer?
No. Legalica is a legal technology platform operated by Legalica OÜ, not a law firm. Using it does not create an attorney-client relationship, and communications with Legalica are not protected by attorney-client privilege merely because the subject is legal. AI output may be incomplete, outdated, or inapplicable to the facts supplied. A qualified lawyer licensed in the relevant jurisdiction should review consequential research and documents. This is especially important for litigation, regulatory filings, notarized instruments, tax positions, immigration, criminal matters, and transactions with material financial or personal consequences.
Products & Features
What products and modules does Legalica include?
The platform brings together seven practical capability groups: AI Legal Assistant for legal research and analysis; Document Drafting Engine for jurisdiction-aware documents; Legal Identity Hub for entity searches and ownership research; KYC/AML Screening Engine for sanctions, PEP, adverse-media, and risk workflows; Matter Dashboard for matters, deadlines, documents, and alerts; Google Workspace Add-on for Calendar, Tasks, Drive, and Meet; and Corporate Intelligence Data for registry-based company research and reports. These modules share matter context rather than operating as isolated tools. Some capabilities—such as document uploads, team features, and API access—depend on the plan.
What can the AI Legal Assistant do?
The AI Legal Assistant helps users investigate legal questions conversationally. Typical tasks include issue spotting, statute and case-law research, contract review, document Q&A, comparison of legal approaches across jurisdictions, identification of missing facts, and preparation of follow-up questions or drafting steps. It uses jurisdictional resolution and retrieval-augmented generation rather than relying only on a model’s stored knowledge. Responses are designed to expose legal references and source links where available. Usage is credit-based, not unlimited. The relevance and completeness of an answer still depend on the question, accessible sources, jurisdiction, and facts provided.
What can the Document Drafting Engine create and edit?
The Document Drafting Engine supports contracts, NDAs, pleadings, motions, corporate resolutions, employment and lease agreements, website terms, privacy documents, notices, and other structured legal texts. It combines jurisdiction and document-type selection with interactive placeholders, incremental AI editing, risk and clarification prompts, OCR-supported import, and version history. Users can work with DOCX, PDF, TXT, ODT, and Google Docs workflows and export editable output. A generated document is a draft for review, not a guarantee of enforceability, filing readiness, or compliance with every local formality.
Does Legalica provide legal translation?
Legalica provides AI-assisted legal language workflows through the Mirror Language Protocol. The protocol is designed to preserve defined terms, numbering, cross-references, placeholders, and document structure while separating the user’s working language from the language required for the target jurisdiction. Source and output can be reviewed together so that terminology choices remain visible. This is a drafting and comprehension aid, not a sworn or certified translation. Where a court, registry, notary, or authority requires a certified translation, use a qualified professional translator and verify the receiving authority’s formal requirements.
What is the difference between Legal Identity Hub and the KYC/AML Screening Engine?
Legal Identity Hub is the entity-research layer: it searches legal entities, validates LEI records, examines corporate profiles, traces ownership structures, and supports registry monitoring and private searches. The KYC/AML Screening Engine turns that entity context into a compliance workflow by screening names against sanctions and other watchlists, assessing PEP and adverse-media indicators, reviewing ownership risk, and structuring due-diligence reports. Identity research and compliance screening are related but not interchangeable. A registry record does not by itself prove good standing, beneficial ownership, or the absence of sanctions risk; each result requires appropriate verification.
What is the difference between Corporate Intelligence Data and a KYC report?
Corporate Intelligence Data concerns the retrieval and organization of company information from sources such as the GLEIF Global LEI Index and relevant registry records. It can include identifiers, registration details, entity status, relationships, and source attribution, depending on availability. A KYC report is a compliance-oriented work product that places entity data beside ownership research, screening results, risk indicators, and reviewer notes. Registry coverage is a separate dimension from Legalica’s 324 legal-research jurisdiction entries and varies by source and entity type. Users should not assume that every registry field is available for every company.
What does the Matter Dashboard organize?
The Matter Dashboard centralizes matters, tasks, deadlines, documents, client and entity research, KYC status, notifications, and AI-assisted work. Configurable widgets allow users to arrange operational views for litigation, corporate matters, compliance reviews, or daily priorities. Matter-linked context helps users move between a research conversation, a draft, an entity search, and a deadline without reconstructing the file each time. Calendar and task information can also participate in Google Workspace synchronization. Dashboard organization supports professional judgment; it does not determine legal deadlines automatically without user verification.
How does the Google Workspace Add-on fit into legal workflows?
The Google Workspace Add-on connects selected Legalica workflows with Google Calendar, Tasks, Drive, and Meet through OAuth 2.0 authorization. Depending on the connected workflow, users can synchronize matter-related events and tasks, organize documents, import or export work, and retain matter context around meetings and deadlines. Access is permission-based and limited to the authorized scope. Connecting an account does not give Legalica unrestricted access to email, contacts, or unrelated Drive files. Users should review the requested permissions and their organization’s confidentiality and records-management policies before connecting a workspace.
Can I upload my own documents?
Document upload is available for supported chat and drafting workflows on Professional and Enterprise plans. Supported workflows include analysis, summarisation, Q&A, OCR-assisted extraction, and AI-assisted editing for formats such as PDF, DOCX, and TXT. Uploaded content is protected with TLS 1.3 in transit and AES-256 at rest, and provider agreements prohibit training on Customer Data. Usage is charged by actual token consumption, so a large attachment can consume substantially more credits than a short question. Remove unnecessary personal or highly sensitive information before upload and check whether your matter requires EU-only routing.
Is API access available?
Enterprise includes API access for integrations, alongside custom AI model configuration, advanced user management, audit logs, and a dedicated account manager. API use should be scoped around a defined workflow—for example, initiating research, supporting document production, or connecting corporate intelligence to an internal system—rather than treated as an unrestricted entitlement. Rate limits, technical credentials, data flows, retention settings, and service commitments must be reviewed for the specific implementation. Enterprise customers requiring direct invoicing, custom integration work, or EU-only routing should agree those requirements with Legalica before deployment.
Data & Sources
Where does Legalica’s legal information come from?
Legalica is designed to ground legal work in primary and authoritative materials, including legislation, official gazettes, legislative portals, court materials, regulators, and other public legal sources relevant to the selected jurisdiction. Corporate identity research uses the GLEIF Global LEI Index and applicable registry sources. KYC/AML workflows also rely on sanctions, watchlist, PEP, and adverse-media sources described in the product documentation. Source availability differs by jurisdiction and task. Users should follow the supplied reference to the originating publisher and confirm that the document is the current, complete, and legally relevant version.
How current is the legal information?
Retrieval-augmented generation allows Legalica to retrieve material at query time instead of relying solely on the model’s training data. That improves access to published sources, but it does not guarantee that every answer reflects the latest amendment, judgment, commencement rule, transitional provision, or official consolidation. Publishers update at different times and some changes take effect after publication. Check the source’s publication date, effective date, amendment history, and territorial scope before relying on an answer. For time-sensitive work, verify the position directly with the issuing authority or a qualified local lawyer.
Does Legalica cite its sources?
Legalica is designed to provide jurisdiction-relevant legal references and links to originating sources where available. Citation panels and statutory references help users inspect the basis of an answer rather than accepting generated prose on trust. A citation is not proof that every surrounding inference is correct: the cited passage may be incomplete, superseded, factually distinguishable, or wrongly associated with the question. Users should open the source, read the relevant provision in context, and verify its current status. If an answer lacks an adequate reference, treat it as unverified and research the point independently.
Can Legalica compare laws across multiple jurisdictions?
Yes. You can frame one issue across two or more of the 324 jurisdiction entries—for example, comparing formation requirements, consumer cancellation rights, employment clauses, or disclosure duties. A useful comparison should keep the facts, date, entity type, and legal question constant while changing only the jurisdiction. Legalica’s jurisdictional resolution and terminology mapping help structure that analysis. The result should distinguish national law, subdivision law, regional instruments, and any conflict-of-laws issue. Cross-border output is a research map, not a determination of which law ultimately applies to a particular dispute or transaction.
How does GLEIF data relate to Legalica’s 324 jurisdictions?
The 324-entry jurisdiction directory is based on the GLEIF Accepted Legal Jurisdictions Code List and supplies standardized country and subdivision identifiers for Legalica’s jurisdictional architecture. The GLEIF Global LEI Index is a separate corporate-identity resource used for LEI validation and entity research. Neither dataset means that every statute, judgment, registry field, or beneficial-ownership record is available for every jurisdiction. Legal-research coverage, localized landing pages, and corporate-registry coverage are different coverage dimensions and should be evaluated separately for the task at hand.
What source limitations should users check?
Check whether the source is official, current, complete, applicable to the territory, and available in a legally authoritative language. Also check whether a rule comes from legislation, delegated regulation, soft-law guidance, a court, or commentary; these do not carry the same weight. For companies, distinguish an LEI record from a full national registry extract and from verified beneficial ownership. For screening, distinguish a potential name match from a confirmed match. Legalica can accelerate source discovery and comparison, but it cannot remove publication gaps, access restrictions, transcription errors, or the need for professional source evaluation.
Jurisdiction Coverage
What does coverage of 324 jurisdictions actually mean?
Legalica uses 324 standardized jurisdiction entries drawn from the GLEIF Accepted Legal Jurisdictions Code List v1.5. The directory combines ISO 3166-1 alpha-2 country codes with ISO 3166-2 subdivision codes where legal entity forms or legal frameworks may be defined below national level. It therefore does not mean 324 sovereign states. The entries give users a consistent way to select the legal context for research, drafting, entity classification, and cross-border comparison. Each entry is an identifier for legal work, not a promise that every official source or registry field is equally accessible in that jurisdiction.
How does Legalica resolve a selected jurisdiction?
The Prismatic Resolution Chain first looks for an exact country or subdivision profile. For a subdivision, it can also load the parent-country context and local warning guards. Where an exact profile is incomplete, the architecture can use regional frameworks and then broader international principles as fallback context. This hierarchy helps prevent a query about Dubai, Alberta, or New York from being treated as an undifferentiated national question. Resolution is a routing and terminology safeguard, not proof that a fallback rule is the governing law. Users should verify the exact source and legal hierarchy shown in the answer.
Why are countries and subdivisions both included?
Some legal questions are governed mainly at national level, while others depend on a state, province, territory, emirate, or special administrative area. A country-only model would miss important differences in places such as the United States, Canada, Australia, and the United Arab Emirates. Conversely, a subdivision-only query can miss federal legislation, constitutional rules, international obligations, and nationwide regulators. Legalica’s directory preserves both levels and their parent relationships so that users can research the local rule without losing the national framework. The table identifies these relationships explicitly for all 324 entries.
How should I choose the right jurisdiction for a query?
Start with the jurisdiction whose law you expect to govern the issue, then add any connected jurisdictions that affect parties, assets, performance, registration, enforcement, or procedure. For a subdivision-specific issue, select the subdivision and review the parent-country context as well. Do not choose a jurisdiction solely because it matches your language or physical location: a contract’s governing-law clause, a company’s place of incorporation, the location of property, and the forum can point in different directions. If the applicable jurisdiction itself is uncertain, ask Legalica to map the connecting factors and then obtain conflict-of-laws advice.
What is the best way to conduct cross-jurisdiction research?
Define one precise legal question, fix the relevant date, identify the parties and transaction, and list each jurisdiction separately. Ask for the governing sources, territorial scope, effective dates, exceptions, and official terminology in each jurisdiction before requesting a comparison. Then compare like with like: legislation with legislation, regulator guidance with regulator guidance, and binding case law with binding case law. Legalica can organize this workflow and expose terminology differences, but users should independently verify the primary sources. For a real transaction, also review governing law, jurisdiction clauses, recognition, and enforcement with local counsel.
Does jurisdiction coverage guarantee a complete local legal answer?
No. Jurisdiction coverage identifies the legal contexts Legalica is designed to support; it does not guarantee comprehensive source coverage, official-language perfection, or a definitive legal outcome. Some jurisdictions publish consolidated legislation and extensive case law online, while others provide fragmented or limited digital sources. Local practice, unreported decisions, administrative procedure, and formalities may require direct verification. Treat the jurisdiction profile as the starting point for structured research and always inspect the underlying sources. For consequential matters, use a lawyer or other qualified professional in the selected jurisdiction.
Where can I verify all 324 jurisdiction entries?
The complete reference below lists every jurisdiction name, standardized code, entry level, and parent relationship from Legalica’s canonical GLEIF-based dataset. “Country / territory” identifies a top-level entry; “Subdivision” identifies a subnational entry linked to a parent. This is the authoritative directory for understanding the 324 count and for avoiding confusion between a country and its subdivisions. The searchable Supported Jurisdictions page uses the same dataset. The reference describes coverage identifiers, not the content or current state of each jurisdiction’s laws, which must be checked against primary sources.
| Jurisdiction | Code | Entry level | Parent jurisdiction |
|---|---|---|---|
| Andorra | AD | Country / territory | None — top-level entry |
| United Arab Emirates | AE | Country / territory | None — top-level entry |
| ‘Ajmān (United Arab Emirates) | AE-AJ | Subdivision | United Arab Emirates (AE) |
| Abu Dhabi (United Arab Emirates) | AE-AZ | Subdivision | United Arab Emirates (AE) |
| Dubai (United Arab Emirates) | AE-DU | Subdivision | United Arab Emirates (AE) |
| Fujairah (United Arab Emirates) | AE-FU | Subdivision | United Arab Emirates (AE) |
| Ras Al Khaimah (United Arab Emirates) | AE-RK | Subdivision | United Arab Emirates (AE) |
| Sharjah (United Arab Emirates) | AE-SH | Subdivision | United Arab Emirates (AE) |
| Umm Al Quwain (United Arab Emirates) | AE-UQ | Subdivision | United Arab Emirates (AE) |
| Afghanistan | AF | Country / territory | None — top-level entry |
| Antigua and Barbuda | AG | Country / territory | None — top-level entry |
| Anguilla | AI | Country / territory | None — top-level entry |
| Albania | AL | Country / territory | None — top-level entry |
| Armenia | AM | Country / territory | None — top-level entry |
| Angola | AO | Country / territory | None — top-level entry |
| Antarctica | AQ | Country / territory | None — top-level entry |
| Argentina | AR | Country / territory | None — top-level entry |
| American Samoa | AS | Country / territory | None — top-level entry |
| Austria | AT | Country / territory | None — top-level entry |
| Australia | AU | Country / territory | None — top-level entry |
| Aruba | AW | Country / territory | None — top-level entry |
| Åland Islands | AX | Country / territory | None — top-level entry |
| Azerbaijan | AZ | Country / territory | None — top-level entry |
| Bosnia and Herzegovina | BA | Country / territory | None — top-level entry |
| Barbados | BB | Country / territory | None — top-level entry |
| Bangladesh | BD | Country / territory | None — top-level entry |
| Belgium | BE | Country / territory | None — top-level entry |
| Flemish Region (Belgium) | BE-VLG | Subdivision | Belgium (BE) |
| Burkina Faso | BF | Country / territory | None — top-level entry |
| Bulgaria | BG | Country / territory | None — top-level entry |
| Bahrain | BH | Country / territory | None — top-level entry |
| Burundi | BI | Country / territory | None — top-level entry |
| Benin | BJ | Country / territory | None — top-level entry |
| Bermuda | BM | Country / territory | None — top-level entry |
| Brunei Darussalam | BN | Country / territory | None — top-level entry |
| Bolivia (Plurinational State of) | BO | Country / territory | None — top-level entry |
| Bonaire, Sint Eustatius and Saba | BQ | Country / territory | None — top-level entry |
| Brazil | BR | Country / territory | None — top-level entry |
| Bahamas | BS | Country / territory | None — top-level entry |
| Bhutan | BT | Country / territory | None — top-level entry |
| Bouvet Island | BV | Country / territory | None — top-level entry |
| Botswana | BW | Country / territory | None — top-level entry |
| Belarus | BY | Country / territory | None — top-level entry |
| Belize | BZ | Country / territory | None — top-level entry |
| Canada | CA | Country / territory | None — top-level entry |
| Alberta (Canada) | CA-AB | Subdivision | Canada (CA) |
| British Columbia (Canada) | CA-BC | Subdivision | Canada (CA) |
| Manitoba (Canada) | CA-MB | Subdivision | Canada (CA) |
| New Brunswick (Canada) | CA-NB | Subdivision | Canada (CA) |
| Newfoundland and Labrador (Canada) | CA-NL | Subdivision | Canada (CA) |
| Nova Scotia (Canada) | CA-NS | Subdivision | Canada (CA) |
| Northwest Territories (Canada) | CA-NT | Subdivision | Canada (CA) |
| Nunavut (Canada) | CA-NU | Subdivision | Canada (CA) |
| Ontario (Canada) | CA-ON | Subdivision | Canada (CA) |
| Prince Edward Island (Canada) | CA-PE | Subdivision | Canada (CA) |
| Quebec (Canada) | CA-QC | Subdivision | Canada (CA) |
| Saskatchewan (Canada) | CA-SK | Subdivision | Canada (CA) |
| Yukon (Canada) | CA-YT | Subdivision | Canada (CA) |
| Cocos (Keeling) Islands | CC | Country / territory | None — top-level entry |
| Congo (the Democratic Republic of the) | CD | Country / territory | None — top-level entry |
| Central African Republic | CF | Country / territory | None — top-level entry |
| Congo | CG | Country / territory | None — top-level entry |
| Switzerland | CH | Country / territory | None — top-level entry |
| Côte d'Ivoire | CI | Country / territory | None — top-level entry |
| Cook Islands | CK | Country / territory | None — top-level entry |
| Chile | CL | Country / territory | None — top-level entry |
| Cameroon | CM | Country / territory | None — top-level entry |
| China | CN | Country / territory | None — top-level entry |
| Colombia | CO | Country / territory | None — top-level entry |
| Costa Rica | CR | Country / territory | None — top-level entry |
| Cuba | CU | Country / territory | None — top-level entry |
| Cabo Verde | CV | Country / territory | None — top-level entry |
| Curaçao | CW | Country / territory | None — top-level entry |
| Christmas Island | CX | Country / territory | None — top-level entry |
| Cyprus | CY | Country / territory | None — top-level entry |
| Czechia | CZ | Country / territory | None — top-level entry |
| Germany | DE | Country / territory | None — top-level entry |
| Djibouti | DJ | Country / territory | None — top-level entry |
| Denmark | DK | Country / territory | None — top-level entry |
| Dominica | DM | Country / territory | None — top-level entry |
| Dominican Republic | DO | Country / territory | None — top-level entry |
| Algeria | DZ | Country / territory | None — top-level entry |
| Ecuador | EC | Country / territory | None — top-level entry |
| Estonia | EE | Country / territory | None — top-level entry |
| Egypt | EG | Country / territory | None — top-level entry |
| Western Sahara* (*Provisional name) | EH | Country / territory | None — top-level entry |
| Eritrea | ER | Country / territory | None — top-level entry |
| Spain | ES | Country / territory | None — top-level entry |
| Ethiopia | ET | Country / territory | None — top-level entry |
| European Union | EU | Country / territory | None — top-level entry |
| Finland | FI | Country / territory | None — top-level entry |
| Fiji | FJ | Country / territory | None — top-level entry |
| Falkland Islands [Malvinas] | FK | Country / territory | None — top-level entry |
| Micronesia (Federated States of) | FM | Country / territory | None — top-level entry |
| Faroe Islands | FO | Country / territory | None — top-level entry |
| France | FR | Country / territory | None — top-level entry |
| Gabon | GA | Country / territory | None — top-level entry |
| United Kingdom of Great Britain and Northern Ireland | GB | Country / territory | None — top-level entry |
| Northern Ireland (United Kingdom of Great Britain and Northern Ireland) | GB-NIR | Subdivision | United Kingdom of Great Britain and Northern Ireland (GB) |
| Scotland (United Kingdom of Great Britain and Northern Ireland) | GB-SCT | Subdivision | United Kingdom of Great Britain and Northern Ireland (GB) |
| Grenada | GD | Country / territory | None — top-level entry |
| Georgia | GE | Country / territory | None — top-level entry |
| Guernsey | GG | Country / territory | None — top-level entry |
| Ghana | GH | Country / territory | None — top-level entry |
| Gibraltar | GI | Country / territory | None — top-level entry |
| Greenland | GL | Country / territory | None — top-level entry |
| Gambia | GM | Country / territory | None — top-level entry |
| Guinea | GN | Country / territory | None — top-level entry |
| Equatorial Guinea | GQ | Country / territory | None — top-level entry |
| Greece | GR | Country / territory | None — top-level entry |
| South Georgia and the South Sandwich Islands | GS | Country / territory | None — top-level entry |
| Guatemala | GT | Country / territory | None — top-level entry |
| Guam | GU | Country / territory | None — top-level entry |
| Guinea-Bissau | GW | Country / territory | None — top-level entry |
| Guyana | GY | Country / territory | None — top-level entry |
| Hong Kong | HK | Country / territory | None — top-level entry |
| Heard Island and McDonald Islands | HM | Country / territory | None — top-level entry |
| Honduras | HN | Country / territory | None — top-level entry |
| Croatia | HR | Country / territory | None — top-level entry |
| Haiti | HT | Country / territory | None — top-level entry |
| Hungary | HU | Country / territory | None — top-level entry |
| Indonesia | ID | Country / territory | None — top-level entry |
| Ireland | IE | Country / territory | None — top-level entry |
| Israel | IL | Country / territory | None — top-level entry |
| Isle of Man | IM | Country / territory | None — top-level entry |
| India | IN | Country / territory | None — top-level entry |
| British Indian Ocean Territory | IO | Country / territory | None — top-level entry |
| Iraq | IQ | Country / territory | None — top-level entry |
| Iran (Islamic Republic of) | IR | Country / territory | None — top-level entry |
| Iceland | IS | Country / territory | None — top-level entry |
| Italy | IT | Country / territory | None — top-level entry |
| Jersey | JE | Country / territory | None — top-level entry |
| Jamaica | JM | Country / territory | None — top-level entry |
| Jordan | JO | Country / territory | None — top-level entry |
| Japan | JP | Country / territory | None — top-level entry |
| Kenya | KE | Country / territory | None — top-level entry |
| Kyrgyzstan | KG | Country / territory | None — top-level entry |
| Cambodia | KH | Country / territory | None — top-level entry |
| Kiribati | KI | Country / territory | None — top-level entry |
| Comoros | KM | Country / territory | None — top-level entry |
| Saint Kitts and Nevis | KN | Country / territory | None — top-level entry |
| Nevis (Saint Kitts and Nevis) | KN-N | Subdivision | Saint Kitts and Nevis (KN) |
| Korea (the Democratic People's Republic of) | KP | Country / territory | None — top-level entry |
| Korea (Republic of) | KR | Country / territory | None — top-level entry |
| Kuwait | KW | Country / territory | None — top-level entry |
| Cayman Islands | KY | Country / territory | None — top-level entry |
| Kazakhstan | KZ | Country / territory | None — top-level entry |
| Lao People's Democratic Republic | LA | Country / territory | None — top-level entry |
| Lebanon | LB | Country / territory | None — top-level entry |
| Saint Lucia | LC | Country / territory | None — top-level entry |
| Liechtenstein | LI | Country / territory | None — top-level entry |
| Sri Lanka | LK | Country / territory | None — top-level entry |
| Liberia | LR | Country / territory | None — top-level entry |
| Lesotho | LS | Country / territory | None — top-level entry |
| Lithuania | LT | Country / territory | None — top-level entry |
| Luxembourg | LU | Country / territory | None — top-level entry |
| Latvia | LV | Country / territory | None — top-level entry |
| Libya | LY | Country / territory | None — top-level entry |
| Morocco | MA | Country / territory | None — top-level entry |
| Monaco | MC | Country / territory | None — top-level entry |
| Moldova (the Republic of) | MD | Country / territory | None — top-level entry |
| Montenegro | ME | Country / territory | None — top-level entry |
| Madagascar | MG | Country / territory | None — top-level entry |
| Marshall Islands | MH | Country / territory | None — top-level entry |
| North Macedonia | MK | Country / territory | None — top-level entry |
| Mali | ML | Country / territory | None — top-level entry |
| Myanmar | MM | Country / territory | None — top-level entry |
| Mongolia | MN | Country / territory | None — top-level entry |
| Macao | MO | Country / territory | None — top-level entry |
| Northern Mariana Islands | MP | Country / territory | None — top-level entry |
| Mauritania | MR | Country / territory | None — top-level entry |
| Montserrat | MS | Country / territory | None — top-level entry |
| Malta | MT | Country / territory | None — top-level entry |
| Mauritius | MU | Country / territory | None — top-level entry |
| Maldives | MV | Country / territory | None — top-level entry |
| Malawi | MW | Country / territory | None — top-level entry |
| Mexico | MX | Country / territory | None — top-level entry |
| Malaysia | MY | Country / territory | None — top-level entry |
| Labuan (Malaysia) | MY-15 | Subdivision | Malaysia (MY) |
| Mozambique | MZ | Country / territory | None — top-level entry |
| Namibia | NA | Country / territory | None — top-level entry |
| New Caledonia | NC | Country / territory | None — top-level entry |
| Niger | NE | Country / territory | None — top-level entry |
| Norfolk Island | NF | Country / territory | None — top-level entry |
| Nigeria | NG | Country / territory | None — top-level entry |
| Nicaragua | NI | Country / territory | None — top-level entry |
| Netherlands | NL | Country / territory | None — top-level entry |
| Norway | NO | Country / territory | None — top-level entry |
| Nepal | NP | Country / territory | None — top-level entry |
| Nauru | NR | Country / territory | None — top-level entry |
| Niue | NU | Country / territory | None — top-level entry |
| New Zealand | NZ | Country / territory | None — top-level entry |
| Oman | OM | Country / territory | None — top-level entry |
| Panama | PA | Country / territory | None — top-level entry |
| Peru | PE | Country / territory | None — top-level entry |
| French Polynesia | PF | Country / territory | None — top-level entry |
| Papua New Guinea | PG | Country / territory | None — top-level entry |
| Philippines | PH | Country / territory | None — top-level entry |
| Pakistan | PK | Country / territory | None — top-level entry |
| Poland | PL | Country / territory | None — top-level entry |
| Saint Pierre and Miquelon | PM | Country / territory | None — top-level entry |
| Pitcairn | PN | Country / territory | None — top-level entry |
| Puerto Rico | PR | Country / territory | None — top-level entry |
| Palestine, State of | PS | Country / territory | None — top-level entry |
| Portugal | PT | Country / territory | None — top-level entry |
| Região Autónoma dos Açores (Portugal) | PT-20 | Subdivision | Portugal (PT) |
| Madeira (Portugal) | PT-30 | Subdivision | Portugal (PT) |
| Palau | PW | Country / territory | None — top-level entry |
| Paraguay | PY | Country / territory | None — top-level entry |
| Qatar | QA | Country / territory | None — top-level entry |
| Romania | RO | Country / territory | None — top-level entry |
| Serbia | RS | Country / territory | None — top-level entry |
| Russian Federation | RU | Country / territory | None — top-level entry |
| Rwanda | RW | Country / territory | None — top-level entry |
| Saudi Arabia | SA | Country / territory | None — top-level entry |
| Solomon Islands | SB | Country / territory | None — top-level entry |
| Seychelles | SC | Country / territory | None — top-level entry |
| Sudan | SD | Country / territory | None — top-level entry |
| Sweden | SE | Country / territory | None — top-level entry |
| Singapore | SG | Country / territory | None — top-level entry |
| Saint Helena, Ascension and Tristan da Cunha | SH | Country / territory | None — top-level entry |
| Slovenia | SI | Country / territory | None — top-level entry |
| Svalbard and Jan Mayen | SJ | Country / territory | None — top-level entry |
| Slovakia | SK | Country / territory | None — top-level entry |
| Sierra Leone | SL | Country / territory | None — top-level entry |
| San Marino | SM | Country / territory | None — top-level entry |
| Senegal | SN | Country / territory | None — top-level entry |
| Somalia | SO | Country / territory | None — top-level entry |
| Suriname | SR | Country / territory | None — top-level entry |
| South Sudan | SS | Country / territory | None — top-level entry |
| Sao Tome and Principe | ST | Country / territory | None — top-level entry |
| El Salvador | SV | Country / territory | None — top-level entry |
| Sint Maarten | SX | Country / territory | None — top-level entry |
| Syrian Arab Republic | SY | Country / territory | None — top-level entry |
| Eswatini | SZ | Country / territory | None — top-level entry |
| Turks and Caicos Islands | TC | Country / territory | None — top-level entry |
| Chad | TD | Country / territory | None — top-level entry |
| French Southern Territories | TF | Country / territory | None — top-level entry |
| Togo | TG | Country / territory | None — top-level entry |
| Thailand | TH | Country / territory | None — top-level entry |
| Tajikistan | TJ | Country / territory | None — top-level entry |
| Tokelau | TK | Country / territory | None — top-level entry |
| Timor-Leste | TL | Country / territory | None — top-level entry |
| Turkmenistan | TM | Country / territory | None — top-level entry |
| Tunisia | TN | Country / territory | None — top-level entry |
| Tonga | TO | Country / territory | None — top-level entry |
| Türkiye | TR | Country / territory | None — top-level entry |
| Trinidad and Tobago | TT | Country / territory | None — top-level entry |
| Tuvalu | TV | Country / territory | None — top-level entry |
| Taiwan (Province of China) | TW | Country / territory | None — top-level entry |
| Tanzania, the United Republic of | TZ | Country / territory | None — top-level entry |
| Ukraine | UA | Country / territory | None — top-level entry |
| Uganda | UG | Country / territory | None — top-level entry |
| United States Minor Outlying Islands | UM | Country / territory | None — top-level entry |
| United Nations | UN | Country / territory | None — top-level entry |
| United States of America | US | Country / territory | None — top-level entry |
| Alaska (United States of America) | US-AK | Subdivision | United States of America (US) |
| Alabama (United States of America) | US-AL | Subdivision | United States of America (US) |
| Arkansas (United States of America) | US-AR | Subdivision | United States of America (US) |
| Arizona (United States of America) | US-AZ | Subdivision | United States of America (US) |
| California (United States of America) | US-CA | Subdivision | United States of America (US) |
| Colorado (United States of America) | US-CO | Subdivision | United States of America (US) |
| Connecticut (United States of America) | US-CT | Subdivision | United States of America (US) |
| District of Columbia (United States of America) | US-DC | Subdivision | United States of America (US) |
| Delaware (United States of America) | US-DE | Subdivision | United States of America (US) |
| Florida (United States of America) | US-FL | Subdivision | United States of America (US) |
| Georgia (United States of America) | US-GA | Subdivision | United States of America (US) |
| Hawaii (United States of America) | US-HI | Subdivision | United States of America (US) |
| Iowa (United States of America) | US-IA | Subdivision | United States of America (US) |
| Idaho (United States of America) | US-ID | Subdivision | United States of America (US) |
| Illinois (United States of America) | US-IL | Subdivision | United States of America (US) |
| Indiana (United States of America) | US-IN | Subdivision | United States of America (US) |
| Kansas (United States of America) | US-KS | Subdivision | United States of America (US) |
| Kentucky (United States of America) | US-KY | Subdivision | United States of America (US) |
| Louisiana (United States of America) | US-LA | Subdivision | United States of America (US) |
| Massachusetts (United States of America) | US-MA | Subdivision | United States of America (US) |
| Maryland (United States of America) | US-MD | Subdivision | United States of America (US) |
| Maine (United States of America) | US-ME | Subdivision | United States of America (US) |
| Michigan (United States of America) | US-MI | Subdivision | United States of America (US) |
| Minnesota (United States of America) | US-MN | Subdivision | United States of America (US) |
| Missouri (United States of America) | US-MO | Subdivision | United States of America (US) |
| Mississippi (United States of America) | US-MS | Subdivision | United States of America (US) |
| Montana (United States of America) | US-MT | Subdivision | United States of America (US) |
| North Carolina (United States of America) | US-NC | Subdivision | United States of America (US) |
| North Dakota (United States of America) | US-ND | Subdivision | United States of America (US) |
| Nebraska (United States of America) | US-NE | Subdivision | United States of America (US) |
| New Hampshire (United States of America) | US-NH | Subdivision | United States of America (US) |
| New Jersey (United States of America) | US-NJ | Subdivision | United States of America (US) |
| New Mexico (United States of America) | US-NM | Subdivision | United States of America (US) |
| Nevada (United States of America) | US-NV | Subdivision | United States of America (US) |
| New York (United States of America) | US-NY | Subdivision | United States of America (US) |
| Ohio (United States of America) | US-OH | Subdivision | United States of America (US) |
| Oklahoma (United States of America) | US-OK | Subdivision | United States of America (US) |
| Oregon (United States of America) | US-OR | Subdivision | United States of America (US) |
| Pennsylvania (United States of America) | US-PA | Subdivision | United States of America (US) |
| Rhode Island (United States of America) | US-RI | Subdivision | United States of America (US) |
| South Carolina (United States of America) | US-SC | Subdivision | United States of America (US) |
| South Dakota (United States of America) | US-SD | Subdivision | United States of America (US) |
| Tennessee (United States of America) | US-TN | Subdivision | United States of America (US) |
| Texas (United States of America) | US-TX | Subdivision | United States of America (US) |
| Utah (United States of America) | US-UT | Subdivision | United States of America (US) |
| Virginia (United States of America) | US-VA | Subdivision | United States of America (US) |
| Vermont (United States of America) | US-VT | Subdivision | United States of America (US) |
| Washington (United States of America) | US-WA | Subdivision | United States of America (US) |
| Wisconsin (United States of America) | US-WI | Subdivision | United States of America (US) |
| West Virginia (United States of America) | US-WV | Subdivision | United States of America (US) |
| Wyoming (United States of America) | US-WY | Subdivision | United States of America (US) |
| Uruguay | UY | Country / territory | None — top-level entry |
| Uzbekistan | UZ | Country / territory | None — top-level entry |
| Holy See | VA | Country / territory | None — top-level entry |
| Saint Vincent and the Grenadines | VC | Country / territory | None — top-level entry |
| Venezuela (Bolivarian Republic of) | VE | Country / territory | None — top-level entry |
| Virgin Islands (British) | VG | Country / territory | None — top-level entry |
| Virgin Islands (U.S.) | VI | Country / territory | None — top-level entry |
| Viet Nam | VN | Country / territory | None — top-level entry |
| Vanuatu | VU | Country / territory | None — top-level entry |
| Wallis and Futuna | WF | Country / territory | None — top-level entry |
| Samoa | WS | Country / territory | None — top-level entry |
| Kosovo | XK | Country / territory | None — top-level entry |
| Unknown states | XX | Country / territory | None — top-level entry |
| Yemen | YE | Country / territory | None — top-level entry |
| South Africa | ZA | Country / territory | None — top-level entry |
| Zambia | ZM | Country / territory | None — top-level entry |
| Zimbabwe | ZW | Country / territory | None — top-level entry |
Languages & Localized Access
What do the 187 language and regional configurations include?
Legalica’s public experience includes 187 localized landing configurations, and the platform is designed for multilingual legal research and drafting across the same global language-and-region footprint. A configuration can be language-wide, such as English or French, or regional, such as English (United States), English (United Kingdom), French (Canada), or Spanish (Mexico). Regional variants share a base language but adapt jurisdiction-focused copy, sources, and terminology. They should not be mistaken for unrelated languages. The full table below lists every published configuration, its BCP 47 tag, its regional context, and its localized page.
How does Legalica detect the language of a legal question?
The language detector combines trigram analysis from franc-min with an ISO 639-3 to internal language-code mapping, Unicode and script fallbacks, keyword overrides, confidence checks, and post-processing for known confusions. This layered approach is intended to distinguish related languages and to handle text for which a statistical detector is uncertain. Very short prompts, mixed-language text, names, quotations, and legal formulas can still be ambiguous. For important work, state the desired answer language explicitly and keep the source language identifiable. Detection is a routing aid, not a guarantee of correct legal terminology.
Can I ask in one language and research another jurisdiction?
Yes. Your working language and the jurisdiction being researched are separate choices. You can ask in Bulgarian about German law, in Russian about English law, or in Japanese about a cross-border transaction involving several jurisdictions. The AI Legal Assistant is designed to answer in the user’s language while preserving the relevant jurisdiction’s legal terms and references. Official source passages may remain in their original language. Where an authority publishes an official translation, prefer it for formal use; otherwise, verify important translated terms with a qualified professional.
How does the Mirror Language Protocol handle legal meaning?
The Mirror Language Protocol separates interface language from legal output language and carries document structure between versions. It is designed to retain defined terms, clause numbering, cross-references, placeholders, and jurisdiction-specific terminology rather than substituting fluent but legally imprecise wording. In drafting workflows, the document can target the official language of the selected jurisdiction while completion labels remain understandable to the user. The protocol reduces terminology drift; it does not certify that every translation is authoritative or accepted by a court. Review names, amounts, negations, deadlines, and operative clauses line by line.
What is the difference between a localized landing page and product language support?
A localized landing page is public, prerendered content written for a specific language and jurisdiction context. It explains Legalica, its modules, typical workflows, and relevant primary-source starting points without requiring JavaScript. Product language support concerns language detection, AI responses, document generation, and legal-language workflows inside the application. The two are related but not identical: a localized landing page does not prove that every public resource or every generated document has a professionally certified translation. The directory below distinguishes the 187 public localized routes and links directly to each one.
Are Legalica translations certified for courts or registries?
No. AI-generated translations and multilingual drafts are processing and drafting aids, not sworn, notarized, or certified translations. Courts, registries, immigration authorities, notaries, and counterparties may require a particular translator qualification, certification statement, seal, apostille, or original-language document. Those requirements vary by jurisdiction and procedure. Use Legalica to understand and prepare text, then confirm the receiving authority’s rules and instruct a qualified translator where certification is required. Even for unofficial use, a reviewer who understands both languages should check legally operative terms before signature or submission.
What happens if my browser language has no exact localized landing page?
Legalica first evaluates an explicit saved language choice, then browser language preferences. It looks for an exact language-and-region match, a matching regional variant, a generic language page, and finally a supported sibling in the same language. If no supported language matches, the visitor is directed to the neutral English page at /en rather than to a jurisdiction-specific page chosen only from location. This prevents an unsupported language from producing an arbitrary country landing. Users can follow any localized route in the reference directly and save their preferred choice where the language selector offers that option.
Where can I find all 187 localized language and regional pages?
The complete reference below is generated from Legalica’s canonical landing-locale registry. It lists the base language, BCP 47 tag, regional context, and live route for every enabled localized landing page. “Language-wide / neutral” means the configuration is not tied to a regional tag; it does not describe the legal coverage of the whole language. Each route opens real localized content, so users can read the platform overview and jurisdiction-relevant source guidance in the selected language. Product output remains AI-assisted and should be verified as described in the preceding answers.
| Language | BCP 47 tag | Regional context | Localized page |
|---|---|---|---|
| English | en | Language-wide / neutral | /en |
| Chinese | zh-CN | China | /cn |
| Spanish | es | Language-wide / neutral | /es |
| Portuguese | pt-BR | Brazil | /br |
| German | de | Language-wide / neutral | /de |
| French | fr | Language-wide / neutral | /fr |
| Japanese | ja | Language-wide / neutral | /jp |
| Italian | it | Language-wide / neutral | /it |
| Dutch | nl | Language-wide / neutral | /nl |
| Polish | pl | Language-wide / neutral | /pl |
| Korean | ko | Language-wide / neutral | /kr |
| Swedish | sv | Language-wide / neutral | /se |
| Turkish | tr | Language-wide / neutral | /tr |
| Portuguese | pt-PT | Portugal | /pt |
| Czech | cs | Language-wide / neutral | /cz |
| Greek | el | Language-wide / neutral | /gr |
| Ukrainian | uk | Language-wide / neutral | /ua |
| Arabic | ar | Language-wide / neutral | /ae |
| Danish | da | Language-wide / neutral | /dk |
| Norwegian Bokmål | nb | Language-wide / neutral | /no |
| Finnish | fi | Language-wide / neutral | /fi |
| Romanian | ro | Language-wide / neutral | /ro |
| Hungarian | hu | Language-wide / neutral | /hu |
| Spanish | es-MX | Mexico | /mx |
| Bulgarian | bg-BG | Bulgaria | /bg |
| Hindi | hi-IN | India | /in |
| Indonesian | id-ID | Indonesia | /id |
| Vietnamese | vi-VN | Vietnam | /vn |
| Thai | th-TH | Thailand | /th |
| Hebrew | he-IL | Israel | /il |
| Malay | ms-MY | Malaysia | /my |
| Croatian | hr-HR | Croatia | /hr |
| Slovak | sk-SK | Slovakia | /sk |
| Slovenian | sl-SI | Slovenia | /si |
| Estonian | et-EE | Estonia | /ee |
| Latvian | lv-LV | Latvia | /lv |
| Lithuanian | lt-LT | Lithuania | /lt |
| Spanish | es-AR | Argentina | /ar |
| Spanish | es-CO | Colombia | /co |
| French | fr-CA | Canada | /ca |
| German | de-CH | Switzerland | /ch |
| German | de-AT | Austria | /at |
| English | en-ZA | South Africa | /za |
| English | en-SG | Singapore | /sg |
| Chinese | zh-TW | Taiwan | /tw |
| Chinese | zh-HK | Hong Kong | /hk |
| Arabic | ar-SA | Saudi Arabia | /sa |
| Spanish | es-CL | Chile | /cl |
| Spanish | es-PE | Peru | /pe |
| English | en-IE | Ireland | /ie |
| English | en-NG | Nigeria | /ng |
| English | en-KE | Kenya | /ke |
| English | en-GB | United Kingdom | /uk |
| Russian | ru-RU | Russia | /ru |
| Persian | fa-IR | Iran | /ir |
| Urdu | ur-PK | Pakistan | /pk |
| Bangla | bn-BD | Bangladesh | /bd |
| Filipino | fil-PH | Philippines | /ph |
| Arabic | ar-EG | Egypt | /eg |
| English | en-AU | Australia | /au |
| Swahili | sw-TZ | Tanzania | /tz |
| Serbian | sr-RS | Serbia | /rs |
| Kazakh | kk-KZ | Kazakhstan | /kz |
| Uzbek | uz-UZ | Uzbekistan | /uz |
| Azerbaijani | az-AZ | Azerbaijan | /az |
| Georgian | ka-GE | Georgia | /ge |
| Armenian | hy-AM | Armenia | /am |
| Albanian | sq-AL | Albania | /al |
| Macedonian | mk-MK | North Macedonia | /mk |
| Bosnian | bs-BA | Bosnia & Herzegovina | /ba |
| Belarusian | be-BY | Belarus | /by |
| Icelandic | is-IS | Iceland | /is |
| Khmer | km-KH | Cambodia | /kh |
| Burmese | my-MM | Myanmar (Burma) | /mm |
| Nepali | ne-NP | Nepal | /np |
| Sinhala | si-LK | Sri Lanka | /lk |
| Mongolian | mn-MN | Mongolia | /mn |
| Dutch | nl-BE | Belgium | /be |
| Greek | el-CY | Cyprus | /cy |
| Luxembourgish | lb | Language-wide / neutral | /lu |
| Montenegrin | cnr | Language-wide / neutral | /me |
| Romanian | ro-MD | Moldova | /md |
| Albanian | sq-XK | Kosovo | /xk |
| Catalan | ca-AD | Andorra | /ad |
| French | fr-MC | Monaco | /mc |
| German | de-LI | Liechtenstein | /li |
| Italian | it-SM | San Marino | /sm |
| Kyrgyz | ky | Language-wide / neutral | /kg |
| Tajik | tg | Language-wide / neutral | /tj |
| Turkmen | tk | Language-wide / neutral | /tm |
| Lao | lo | Language-wide / neutral | /la |
| Pashto | ps-AF | Afghanistan | /af |
| Amharic | am-ET | Ethiopia | /et |
| Somali | so-SO | Somalia | /so |
| Kinyarwanda | rw-RW | Rwanda | /rw |
| Shona | sn-ZW | Zimbabwe | /zw |
| English | en-GH | Ghana | /gh |
| English | en-ZM | Zambia | /zm |
| French | fr-CM | Cameroon | /cm |
| French | fr-CI | Côte d’Ivoire | /ci |
| French | fr-SN | Senegal | /sn |
| Swahili | sw-UG | Uganda | /ug |
| Tamil | ta-IN | India | /in-ta |
| Telugu | te-IN | India | /in-te |
| Marathi | mr-IN | India | /in-mr |
| Gujarati | gu-IN | India | /in-gu |
| Kannada | kn-IN | India | /in-kn |
| Malayalam | ml-IN | India | /in-ml |
| Punjabi | pa-IN | India | /in-pa |
| Punjabi | pa-PK | Pakistan | /pk-pa |
| Odia | or-IN | India | /in-or |
| Assamese | as-IN | India | /in-as |
| Spanish | es-UY | Uruguay | /uy |
| Spanish | es-PY | Paraguay | /py |
| Spanish | es-BO | Bolivia | /bo |
| Spanish | es-EC | Ecuador | /ec |
| Spanish | es-VE | Venezuela | /ve |
| Spanish | es-GT | Guatemala | /gt |
| Spanish | es-CR | Costa Rica | /cr |
| Spanish | es-PA | Panama | /pa |
| Spanish | es-DO | Dominican Republic | /do |
| Spanish | es-CU | Cuba | /cu |
| Spanish | es-HN | Honduras | /hn |
| Spanish | es-NI | Nicaragua | /ni |
| Spanish | es-SV | El Salvador | /sv |
| Spanish | es-PR | Puerto Rico | /pr |
| English | en-JM | Jamaica | /jm |
| English | en-TT | Trinidad & Tobago | /tt |
| English | en-BB | Barbados | /bb |
| English | en-BS | Bahamas | /bs |
| English | en-BZ | Belize | /bz |
| English | en-GY | Guyana | /gy |
| French | fr-HT | Haiti | /ht |
| French | fr-MA | Morocco | /ma |
| French | fr-DZ | Algeria | /dz |
| French | fr-TN | Tunisia | /tn |
| French | fr-ML | Mali | /ml |
| French | fr-BF | Burkina Faso | /bf |
| French | fr-NE | Niger | /ne |
| French | fr-TD | Chad | /td |
| French | fr-CD | Congo - Kinshasa | /cd |
| French | fr-CG | Congo - Brazzaville | /cg |
| French | fr-GA | Gabon | /ga |
| French | fr-GN | Guinea | /gn |
| French | fr-BJ | Benin | /bj |
| French | fr-TG | Togo | /tg |
| French | fr-MG | Madagascar | /mg |
| Portuguese | pt-AO | Angola | /ao |
| Portuguese | pt-MZ | Mozambique | /mz |
| Spanish | es-GQ | Equatorial Guinea | /gq |
| English | en-BW | Botswana | /bw |
| English | en-NA | Namibia | /na |
| English | en-MW | Malawi | /mw |
| English | en-SL | Sierra Leone | /sl |
| English | en-LR | Liberia | /lr |
| English | en-GM | Gambia | /gm |
| English | en-MU | Mauritius | /mu |
| Arabic | ar-QA | Qatar | /qa |
| Arabic | ar-KW | Kuwait | /kw |
| Arabic | ar-BH | Bahrain | /bh |
| Arabic | ar-OM | Oman | /om |
| Arabic | ar-JO | Jordan | /jo |
| Arabic | ar-LB | Lebanon | /lb |
| Arabic | ar-IQ | Iraq | /iq |
| Arabic | ar-YE | Yemen | /ye |
| Arabic | ar-PS | Palestine | /ps |
| Arabic | ar-SY | Syria | /sy |
| English | en-GI | Gibraltar | /gi |
| English | en-GG | Guernsey | /gg |
| English | en-JE | Jersey | /je |
| English | en-IM | Isle of Man | /im |
| English | en-US | United States | /us |
| Italian | it-VA | Vatican City | /va |
| Italian | it-CH | Switzerland | /ch-it |
| French | fr-BE | Belgium | /be-fr |
| French | fr-CH | Switzerland | /ch-fr |
| Swedish | sv-FI | Finland | /fi-sv |
| Catalan | ca-ES | Spain | /es-ca |
| Galician | gl-ES | Spain | /es-gl |
| Basque | eu-ES | Spain | /es-eu |
| Welsh | cy-GB | United Kingdom | /gb-cy |
| Spanish | es-US | United States | /us-es |
| Swedish | sv-AX | Åland Islands | /ax |
| Faroese | fo-FO | Faroe Islands | /fo |
| Romansh | rm-CH | Switzerland | /ch-rm |
| Scottish Gaelic | gd-GB | United Kingdom | /gb-gd |
| Irish | ga-IE | Ireland | /ie-ga |
AI Technology & Architecture
What is Amicus v.3.1?
Amicus v.3.1 is the public name of Legalica’s current legal AI configuration. It combines multi-jurisdictional retrieval-augmented generation, cross-lingual semantic search, and a published 128k-token context-window capacity with Legalica’s jurisdiction, drafting, and provider-routing architecture. Amicus is not presented as a single standalone foundation model or as a claim about proprietary model weights. The Sovereign Eight AI Cascade supplies the underlying provider routes, while Legalica’s retrieval and jurisdictional layers shape the legal workflow. The Current Model page is the authoritative public source for the version and its published technical specifications.
How does retrieval-augmented generation work in Legalica?
Retrieval-augmented generation, or RAG, adds a source-retrieval stage before the AI forms an answer. Legalica’s published architecture uses dense-sparse hybrid vector retrieval with semantic reranking: semantic retrieval helps find conceptually related material, sparse retrieval helps preserve exact legal terms and identifiers, and reranking prioritizes candidates for the query. The selected jurisdictional context further narrows the research task. This process is designed to make answers more inspectable through references to retrieved material. It does not prove that every proposition is supported, so users should open the cited source and verify its text, status, and relevance.
How does the Sovereign Eight AI Cascade route requests?
The Sovereign Eight AI Cascade is Legalica’s four-tier provider architecture. Google Vertex AI running Gemini Pro series models is the primary EU route; Moonshot AI’s Kimi models provide a deep-analysis fallback; Groq Cloud running Llama 3 series models provides a speed fallback; and locally executed Qwen models through Ollama form the local fallback. Automatic failover is designed to keep a workflow available when a provider cannot serve a request. Routing can change the processing location and technical characteristics of a response. Fallback processing may involve the United States or China, so users with strict residency requirements should review the Subprocessors page and arrange an appropriate Enterprise configuration before use.
What does the Prismatic Resolution Chain contribute to legal research?
The Prismatic Resolution Chain turns a selected jurisdiction into structured context for retrieval, terminology, and drafting. It checks an exact country or subdivision profile, adds the subdivision’s parent-country framework where relevant, and can then use regional frameworks or broader international principles as fallback context. A terminology matrix maps generic concepts to local legal vocabulary. This helps distinguish, for example, a provincial rule from a federal rule and a regional instrument from national implementing legislation. A fallback supplies research context only; it must not be treated as the governing law without a source that establishes its applicability.
How does the Mirror Language Protocol work technically?
The Mirror Language Protocol maintains separate channels for the user’s working language and the legal output language. Language detection routes the query; the jurisdiction layer supplies target terminology; and the drafting layer preserves clause numbering, defined terms, placeholders, and cross-references between versions. A user can therefore work in one language while preparing a document in the language required for the selected jurisdiction, with completion labels kept understandable. The protocol is designed to reduce structural and terminology drift. It does not make an AI translation official, certified, or immune to error, so operative language still needs bilingual review for consequential use.
What does the Dual Trigger System add to an AI conversation?
The Dual Trigger System evaluates whether a legal conversation contains enough information for a useful next step. The first trigger identifies missing material facts that could change the analysis, such as dates, party roles, location, governing law, or procedural posture. The second proposes an actionable workflow when the matter is sufficiently developed—for example, preparing a notice, creating a checklist, or moving into drafting. This makes the assistant more useful than a single-answer chatbot while keeping the user in control. A suggested next step is not a legal recommendation to act, and the absence of a warning does not mean that all relevant facts are known.
What can the Lexical Legal Editor do?
The Document Drafting Workspace adapts Meta’s Lexical editor framework for structured legal documents. It supports justified paragraphs, centered uppercase headings, structured subsections and lists, interactive placeholders for variable fields, and incremental AI editing. Visual diff highlighting helps users inspect proposed changes instead of accepting a replacement blindly. The editor also maintains a 20-version history with side-by-side comparison, allowing users to inspect earlier language before accepting further edits. These controls support deliberate document review; they do not independently establish legal validity or replace a final check of the complete document.
What is the Cognitive Jurisdictional Drafting Protocol?
The Cognitive Jurisdictional Drafting Protocol, or CJDP, coordinates document generation. It detects the requested document type, loads the selected jurisdiction profile, chooses the associated formatting style, generates structured semantic HTML for the editor, and adds a strategic review block with risks and clarifying questions. In practical terms, CJDP connects jurisdiction selection to the structure of the draft rather than producing the same generic form for every country. Its output remains a starting draft. Local execution clauses, mandatory forms, filing rules, notarization, language requirements, and current legislation must still be checked before use.
Which infrastructure and integrations support the platform?
Cloud Firestore stores user, matter, task, chat, and document-metadata records; Google Cloud Storage holds drafts, attachments, and exports; Firebase Authentication supports account access; and Cloud Functions coordinate server-side operations, API orchestration, and webhooks. GLEIF supplies corporate-identity data for LEI-related workflows, while Google Workspace APIs support authorized Calendar, Tasks, Drive, and Meet integrations. Creem acts as Merchant of Record for billing. These components have different roles in the data flow, so storage location, transient compute, AI inference, payment processing, and third-party integration should not be treated as one identical processing operation.
How does Legalica approach long and multi-document contexts?
The published Amicus v.3.1 configuration lists a 128k-token context-window capacity for multi-document analysis. Retrieval and reranking select material relevant to the query instead of treating every stored document as equally important. In practice, the usable context depends on the provider route, input length, attachments, retrieved passages, and the space required for the answer. Token-based billing also means that large attachments can cost more than ordinary questions. For a substantial matter, organize documents by issue, ask for a source-indexed synthesis first, and then test individual propositions against the original documents rather than assuming that every detail was retained.
Does Legalica’s technology eliminate hallucinations or guarantee accuracy?
No. RAG, source references, jurisdictional routing, semantic reranking, and drafting controls are designed to reduce unsupported output and make verification easier, but no generative AI system can guarantee error-free legal analysis. A model can misread a source, omit an exception, combine incompatible rules, or generate a plausible inference that the source does not support. Provider failover can also change response characteristics. Legalica’s safeguards are reasons to inspect the work more effectively, not reasons to skip review. Verify consequential statements, citations, dates, amounts, names, and operative clauses against current primary sources and qualified professional judgment.
Why is Legalica’s architecture useful for cross-border legal work?
The architecture connects capabilities that are often separated: jurisdiction identifiers and parent relationships, multilingual detection, hybrid source retrieval, provider failover, legal terminology mapping, structured drafting, and versioned editing. A user can define one issue, research it in several jurisdictional contexts, preserve official terminology, and carry the result into a document without rebuilding the workflow in disconnected tools. The practical value is better-organized research and review across borders. It is not a claim that one answer can resolve every national difference or replace local advice; each jurisdiction’s sources and formal requirements still need separate verification.
Pricing, Credits & Billing
What subscription plans and prices does Legalica offer?
Starter costs $35 per month, or $348 per year with an effective monthly price of $29, and includes 50 credits. Professional costs $119 per month, or $1,164 per year with an effective monthly price of $97, and includes 220 credits. Enterprise costs $499 per month, or $4,668 per year with an effective monthly price of $389, and includes 1,100 credits. Annual plans grant the full year’s credit volume up front. Professional adds team collaboration and document upload; Enterprise adds capabilities including API access, custom AI configuration, advanced user management, audit logs, and a dedicated account manager. The live Pricing page controls if commercial terms change.
How does the credit and token system work?
One credit covers up to 8,200 tokens, counting both your input and the AI’s answer. Tokens are units of text processing, not words or pages, so the same document can produce different token counts depending on language and formatting. Credits are charged for actual usage rather than as a fixed fee for every feature. You can inspect the exact charge for each message in Billing Profile. Background activity such as automatic chat titles is not billed. Because credit consumption depends on input, retrieved context, attachments, and output length, a credit allowance should not be interpreted as a guaranteed number of pages or answers.
How many credits does a question or document upload use?
A simple question typically uses 1 credit. Complex research can use up to 4 credits per message. Messages with attached documents, available on Professional and Enterprise, are charged by exact token consumption; a large attachment can use 10–20 credits. These are practical usage ranges, not a universal cap for every future workflow. The exact charge appears in Billing Profile, which is the best place to assess your own pattern of use. To control consumption, remove irrelevant pages, narrow the question, and split a broad multi-issue request into clearly defined research steps when that improves the workflow.
How many documents or full research queries can a plan support?
The Pricing page estimates approximately 20 drafted documents per month on Starter and approximately 90 on Professional, depending on actual token use. At the simple-query end of the range, 50, 220, and 1,100 credits can support up to 50, 220, and 1,100 one-credit research interactions respectively on Starter, Professional, and Enterprise. Complex research and large attachments reduce those totals. Enterprise’s document allowance is therefore not “unlimited everything”: work remains subject to the plan’s credit pool and applicable technical limits. For a predictable estimate, measure several representative tasks in Billing Profile before choosing a higher volume plan.
What one-time credit packs are available?
The Mini Pack costs $6 and adds 5 credits; the Standard Pack costs $12 and adds 14 credits; and the Power Pack costs $24 and adds 30 credits. One-time packs apply immediately, do not change your subscription or billing cycle, and expire 90 days after purchase. They are useful when you need additional volume without moving to another subscription. Their validity remains governed by their own expiry terms even if a subscription changes or is cancelled. Check the pack size, expiry, and current balance before purchasing so that the additional credits match the work you expect to complete.
Is there a free trial or a short-term access option?
The published short-term option is a paid Day Pass, not a five-day free trial. It costs $35 and provides a fixed pool of 50 credits for 24 hours, making it suitable for an urgent, clearly scoped task. You can hold one active Day Pass at a time; another can be purchased after the current pass expires. Unused Day Pass value is not a monthly subscription allowance. If you want to evaluate the platform, define a representative research or drafting task in advance and monitor actual credit use during the pass. The Pricing page and Terms of Service contain the current purchase and expiry conditions.
When do subscription and one-time credits expire?
Monthly subscription credits refresh with each monthly billing period. Annual plans grant the full year’s credit volume up front rather than adding it one month at a time. One-Time Credit Packs remain valid for 90 days from purchase, while a Day Pass is valid for 24 hours from activation. These different clocks should be considered separately when planning usage. A plan change preserves remaining credits under the published plan-change rules, and top-up packs and Day Passes retain their own expiry despite a subscription change or cancellation. Billing Profile and the applicable checkout terms are the authoritative record for your balance and validity.
What happens when I upgrade or downgrade?
A plan change is a fresh full-price purchase of the new plan through Creem checkout. The new billing period starts on the day of the change, and the old subscription is cancelled immediately so it does not renew or create double billing. Remaining credits carry over and are added to the new plan’s full allowance. There is no proration calculation and no automatic refund for the old purchase. Downgrades follow the same process. Review the checkout amount and new renewal date before confirming, particularly if you change plans near the end of a paid period or hold time-limited top-up credits.
How do cancellation and refunds work?
You can cancel a subscription so that it does not renew, with access continuing until the end of the current paid period. Purchases are generally non-refundable. The published goodwill exception allows a mistaken purchase to be fully refunded within 24 hours if none of its credits were used; contact support@legalica.app so the purchase can be cancelled and the credits voided. One-time packs and Day Passes retain their own expiry terms. This summary does not replace Terms of Service §7 or any mandatory consumer right that applies to you. For a billing dispute, include the purchase date, product, and account details in your support request.
Who processes payments and how are taxes handled?
Creem acts as Merchant of Record for Legalica’s published checkout. It processes the payment using a card or another method offered at checkout and handles the transaction within its merchant-of-record billing flow. Applicable taxes are displayed at checkout, so the final amount can depend on the customer’s billing details and tax treatment. Legalica’s plan prices and credit allowances should be read together with that checkout total. Keep the Creem receipt for your records. Enterprise customers who need direct invoicing or another procurement arrangement should agree it with Legalica before starting an implementation rather than assuming the standard self-service checkout applies.
Are discounts available, and which plan should I choose?
Verified nonprofit organizations, legal aid clinics, and educational institutions can apply for discounted pricing by emailing support@legalica.app with their organization details. For standard plans, choose according to features and measured volume: Starter suits lighter individual use, Professional adds upload and team workflows with 220 credits, and Enterprise supports larger volumes and integration requirements with 1,100 credits. Do not choose solely from the estimated document count; actual token use is decisive. A short representative workflow and the exact charges in Billing Profile provide a better basis for selection than a generic estimate.
Security, Privacy & Compliance
How does Legalica encrypt data?
Connections between your browser and the platform, and between the platform and third-party AI or API endpoints, use HTTPS with TLS 1.3. Data stored in Cloud Firestore and Cloud Storage is encrypted at rest by Google Cloud using AES-256, with encryption keys managed through Google Cloud Key Management Service. Encryption protects data in transit and at rest; it does not make Legalica a zero-knowledge system and does not prevent an authorized service from processing content needed to answer a request. Users should still minimize unnecessary sensitive information and apply their own confidentiality, access-control, and records-management policies.
Where is data stored and can processing occur outside the EU?
Legalica’s primary persistent data-at-rest region is Google Cloud europe-west3 in Frankfurt, Germany. That statement does not mean every processing operation stays in the EU. Serverless compute can involve transient processing in the United States, and fallback AI inference can involve providers in the United States or China. The primary AI route uses EU-based processing, while locally executed models form the final fallback without an external AI transfer. Current provider locations, transfer safeguards, and any unfinished safeguard work are disclosed on the Subprocessors page. Users requiring EU-only processing should agree an appropriate Enterprise configuration before uploading restricted material.
Is my content used to train AI models?
Legalica prohibits the use of Customer Data to train its own proprietary AI models. Its third-party LLM providers are engaged under API terms requiring transient processing, no retention of prompts or outputs after response generation, and no use of that content for foundation-model training or fine-tuning. Only the context needed for the request is intended to be sent to the selected provider, not the entire workspace. These are architectural controls and contractual provider commitments, not a claim that Legalica can independently verify every provider’s internal conduct. Review the Privacy Policy, Terms, and current Subprocessors register when assessing a sensitive workflow.
What application and access security controls are used?
Cloud Firestore and Cloud Storage security rules enforce per-user isolation so one authenticated user cannot read another user’s workspace, documents, or matter data. Sensitive operations such as payments, AI orchestration, and registry queries run in server-side Cloud Functions rather than exposing secrets in browser code. Service accounts and API credentials follow least-privilege scoping, and the development workflow includes dependency tracking and known-vulnerability scanning. These controls reduce specific technical risks but do not replace safe account practices, organization-level access reviews, or careful management of exports and shared documents.
Does Legalica hold SOC 2 or ISO 27001 certification?
No. Legalica itself does not currently hold SOC 2, ISO 27001, or similar independent certifications. Google Cloud holds certifications and assurance reports for its infrastructure, but those documents cover Google’s services and are not certifications of Legalica’s application or organization. An independent penetration test of Legalica is planned and has not yet been performed. Enterprise customers can request the compliance and security documentation currently available under an NDA. This distinction matters when completing a vendor assessment: infrastructure assurance and application-level assurance should be evaluated separately.
How does Legalica approach GDPR and EU AI Act compliance?
Legalica maintains an active GDPR compliance program covering controller and processor roles, data-subject rights, retention, subprocessors, and international transfer mechanisms. It does not describe itself as holding a blanket GDPR certification. EU AI Act readiness work is also active: users are informed when they interact with an AI system, and exported AI-generated documents carry an AI-content notice as part of the published transparency approach. Regulatory obligations can still depend on how a customer configures and uses the platform. Organizations should assess their own role, lawful basis, instructions, and downstream use rather than treating a vendor statement as complete compliance for their workflow.
What happens when I delete content or close my account?
Individual documents and conversations are deleted from active systems immediately when the user deletes them. For account closure, Legalica’s published process provides for verification within 7 days, deletion of active account data within 30 days, and purging from backups within 90 days. A legal hold or another lawful retention requirement can extend those periods for the affected records. Deleting content from Legalica does not recall exports, emails, or copies already stored by a recipient or another integrated service. Before closing an account, export anything you must retain and review connected workspaces separately.
Are communications with Legalica protected by legal privilege?
No. Terms of Service §15.2 states that communications with Legalica are not protected by attorney-client privilege, legal professional privilege, or work-product doctrine. Encryption, access controls, and no-training commitments address security and data use; they do not create privilege. Do not assume that uploading a client document produces the same legal protection as communicating with your lawyer. Consider whether the information is necessary, remove irrelevant confidential material, and follow your professional and organizational obligations. If privilege or confidentiality is central to the matter, obtain advice on the permissible workflow before uploading the content.
Getting Started
How do I start using Legalica?
Create an account, choose the subscription, one-time pack, or 24-hour Day Pass that fits your task, and open the module you need. For research, select the jurisdiction and describe the legal question in the AI Legal Assistant. For drafting, choose the document type and jurisdiction, complete the placeholders, and review the strategic questions and proposed edits. For company work, begin with an entity search in Legal Identity Hub and add screening only where your compliance process requires it. Check the exact plan capabilities before starting, especially for uploads, team workflows, or API access.
How should I write an effective legal research prompt?
State the jurisdiction, relevant date, parties, facts, legal issue, and desired output. Ask for governing primary sources, effective dates, exceptions, and conflicting authority, not only a conclusion. For a comparison, keep the facts constant and address each jurisdiction separately before requesting a synthesis. For a document question, identify the clause or page and explain your role and objective. A useful closing instruction is: “List the material facts still missing and distinguish sourced propositions from inferences.” Then open the sources and test the answer against them. Precise input improves the research path but does not guarantee a correct legal outcome.
How should I prepare documents for upload or drafting?
Use a supported Professional or Enterprise workflow and check that the file is readable, complete, and relevant to the question. Remove unnecessary personal data, credentials, unrelated client material, and duplicate pages. Identify the document type, jurisdiction, language, and specific clauses or issues you want reviewed. Large attachments can consume 10–20 credits, so narrowing the file can also control cost. Keep the original, review OCR extraction where the file is scanned, and compare every proposed change through the editor’s diff and version-history controls. Do not upload privileged or restricted material without first assessing the applicable confidentiality and data-transfer requirements.
Where can I get help or verify a product claim?
For account, billing, or product support, email support@legalica.app with the relevant plan, workflow, date, and a description of the issue; do not include unnecessary confidential documents. Use the live Pricing page for prices and allowances, Supported Jurisdictions for the 324-entry directory, this FAQ’s generated table for the 187 localized routes, and the Current Model page for Amicus v.3.1. Security, transfers, retention, and subprocessors should be checked against the Trust & Legal pages, which provide the authoritative detailed statements. Product behavior and commercial terms can change, so rely on the current pages rather than an archived answer or third-party summary.