Privacy Policy

1. Who operates this service

Matterlegal is an India-first pilot workspace for individuals, groups, partners, lawyers and law offices.

2. Information processed

• Sign-in: Google or Amazon Cognito provides a verified email address, account identifier and profile name. A profile name is not independent proof of identity or professional eligibility. Google sign-in requests only openid, email and profile; it does not authorize access to Gmail or Google Drive.
• Workspace and case information: membership, invitations, client instructions, summaries, party details, tasks, engagement records, procedural dates, evidence, legal sources and research selections supplied by users. These materials can contain sensitive information about clients and other people.
• Professional profiles: submitted enrollment references, council, location, languages, practice areas and review/publication status.
• Service records: recorded changes, actor identifiers, timestamps, security and operational logs, API usage and test billing references. This is not a promise that every read or action has a complete audit record.

3. Why and how information is used

Information supports authentication, permission checks, evidence storage and integrity checks, collaboration, source retrieval, procedural records, service operation and security. Roles are separate: organization membership does not automatically give access to every confidential case. Participants receive the access permitted by current grants, engagement, source permissions and recorded disclosure choices.

Partners and embedded applications can receive consented, application-scoped status or intake information. Granting an application access does not give it access to unrelated cases or authority to make legal decisions. Workspace administrators and participating organizations may separately determine how information they contribute is used. Authorized service operators and hosting providers may also handle information for operation, troubleshooting, security and lawful requests.

4. OCR and AI processing

Uploaded documents can be processed by Amazon Textract for English or the AWS-hosted Tesseract pipeline for Marathi/Hindi. Legal-library OCR output is unverified and requires review before publication. For case evidence, the client may separately enable automatic extraction for future uploads or request it for an existing original. A private processing copy and page text are retained with the original integrity hash. Candidate passages do not become drafting facts until the client compares the original and confirms a statement and the engaged lawyer accepts that exact version. OCR quotations, client corrections and lawyer reviews remain distinct; missing text pages and OCR confidence are displayed. Editing a fact clears its acceptance. Withdrawing extraction permission blocks subsequent processing and use of extracted facts, but does not erase retained originals, processing copies or audit records. The passage preparation agents process a bounded catalog of selected legal passages and the client goal. Case-specific drafting additionally requires the client’s recorded, revocable permission and the engaged lawyer’s selection of attributed, evidence-linked facts. That drafting flow sends the selected fact text, linked original file IDs, names and integrity hashes, selected legal passages and client objective to Bedrock in India. Raw attachment bytes and the full client account are not sent to these agents. A linked document does not prove a factual assertion or certify an extraction. Generated applications receive a separate automated grounding check and still require independent lawyer review and approval of the exact version by the client. Lawyer revisions preserve the original source register and reset document review and client authorization. After separate recorded, revocable client permission, the exact lawyer-written revision body and its attached attributed facts, original metadata and exact legal passages are processed by Bedrock in India in two automated source-check passes. Unsupported additions, unavailable checks and changed sources block document review and client approval until corrected and checked again. Source flags identify exact revised passages; they do not certify truth or legal correctness. Revoking revision-check permission blocks further reliance and resets current document approval without erasing retained text or audit records. Withdrawing permission blocks subsequent drafting and reliance on current AI draft support; it does not erase previously stored drafts, disclosures or audit history. Results require source checks and professional review. AI claim and element proposals require separate recorded client permission. Only selected client-confirmed, lawyer-accepted extracted factual statements and exact selected public legal passages, together with the lawyer’s question, are sent to Bedrock in India. Raw OCR, unconfirmed corrections, review notes and original file bytes are excluded from that proposal inference. Proposed elements, contradictions and opposing arguments receive a separate automated check against each field’s own cited sources, then require element-by-element engaged-lawyer review. Proposals are shared with the case client under the recorded permission; source or permission changes withhold earlier analysis and review without erasing retained audit history. These controls do not guarantee that selected passages are correct, current or legally sufficient.

5. Providers and processing locations

The core platform uses AWS in Mumbai and Hyderabad for regional continuity, including replicated database and evidence storage and regional processing services. A separate Singapore control-plane witness holds routing/recovery state and opaque operation identifiers; the application does not place case content, names, email addresses or passwords in that witness. Google supports sign-in; Amazon Cognito manages authentication. Stripe processes sandbox billing for platform statements. Provider account, security, support and operational processing may take place outside India; this notice does not promise that every provider operation occurs in India.

Provider terms and privacy notices also apply to their services: Google, AWS and Stripe. Do not enter real card details into test billing. Matterlegal does not collect client settlement funds through this release.

6. Cookies and browser storage

Secure, HttpOnly session/flow cookies support sign-in and consent. Embedded sign-in uses sessionStorage for its short-lived flow and holds the embedded session token in memory. The demo also remembers the selected application in sessionStorage. The optional offline drafting page caches only its static editing shell. Drafts are saved on this device only after your explicit choice, encrypted with your passphrase; their title, matter reference and text are not stored in plaintext. A device copy cannot be remotely revoked, a forgotten passphrase cannot be recovered, and browser storage can be removed. Reconnecting verifies current identity and case access; it never automatically uploads or authorizes work. Explicit plaintext exports and clipboard copies leave the encrypted vault. These pages add no advertising or analytics trackers. Google, AWS and Stripe may use their own storage when you visit their services.

7. Retention and deletion

Case records, originals, source versions, consent and audit records persist for the service. Closing a case, withdrawing a source or revoking access does not by itself guarantee erasure of stored records, historical versions or backups. Fixed retention periods and a complete automated deletion schedule for case records have not yet been approved for this pilot.

Deletion and correction requests require verified manual review, including the rights of other case participants, legal holds and applicable retention duties. A workspace administrator cannot promise immediate permanent deletion through the current interface. Security/application access logs are configured for 180 days from this release; infrastructure audit logs for 365 days and Aurora backups for 14 days. A longer configured period does not recover logs already expired under earlier settings. Matter retention review dates and legal holds are recorded separately; no automatic case/evidence/backups erasure is performed. Independent legal/security review is deferred, and these operational settings are not a certification of statutory compliance.

8. Requests, choices and security

You may contact the operator to request a review of access, correction, export, deletion or withdrawal of consent, as applicable. Availability and scope depend on applicable law, identity/authority verification, other participants' rights and necessary retained records. Signed-in users can record a request in Privacy & account and read the operator’s response there. Requests are reviewed manually; the request queue does not perform automatic erasure or guarantee a portability format. Requests about a participating organization may also need that organization's involvement.

Controls include HTTPS, encrypted storage, private evidence objects, server-enforced permissions, file integrity checks and version/conflict checks. They reduce risk but cannot guarantee confidentiality, availability or legal privilege. Keep your own important records and protect your accounts.

Support linked to lawyer revisions

With client revision-check permission, engaged counsel may link existing client-attributed shared facts and exact legal-library passages to a flagged paragraph. Only these selected statements, original-file metadata, exact legal excerpts and revised text are processed by Bedrock in India. The linking explanation is retained for audit and excluded from inference. Links create a new document version, a supplemental source register and fresh checks; they do not automatically approve the work. The client can inspect the supplemental support before authorizing the exact reviewed version. Source or access changes can invalidate reliance on earlier checks.

New evidence for flagged revisions

A lawyer may turn an unsupported revised passage into a client evidence request. The exact flagged text and earlier work version are retained in case history. New uploads follow the existing sharing and extraction permissions. Resuming that text requires client-confirmed, lawyer-accepted extracted facts from the request originals, current acceptance of the request answer and a fresh record review. Original drafting facts, including opposing accounts, remain selected; earlier AI claim reviews are not transferred to changed evidence. A fresh source register, automated revision checks, lawyer exact-text review and client exact-version approval are required. Resuming does not certify the evidence or legal correctness.

9. Contact and changes

Operator: lawyer.diy
Postal address: Landmark Building, Sector 67, Gurgaon 122102
Privacy and complaints: privacy@lawyer.diy · Support: support@lawyer.diy

Material changes will be described with an updated version/date. Any notice or fresh consent required by applicable law must still be provided; continued use is not a substitute for it. Nothing here limits mandatory statutory rights.