Open web appDownload for macOSDownload

Privacy Policy

1. Scope and operator

This policy applies to Luthor's website, web application, desktop application, support channels, and connected services (together, the "Service"). It does not govern a third-party site or service merely because Luthor links to it.

Luthor is in early access. The legal person operating the Service and responsible for your account must be named in your invitation, pilot agreement, order form, or invoice. If you have not received a document identifying that operator, do not submit real client or matter data; contact support@luthor.in first.

Privacy questions and requests may be sent to support@luthor.in. This is also the published business contact for questions about processing and grievances unless your agreement identifies a separate privacy or grievance officer.

2. Our role and your role

Luthor determines how it uses account, security, billing, support, and service-operation data. For those activities, Luthor acts as the data fiduciary or equivalent responsible party under applicable law.

For personal data in client files, evidence, correspondence, prompts, and other matter material, the advocate or organisation using Luthor normally decides why the data is processed. Luthor processes that material on the user's instructions to provide the Service. Users remain responsible for professional confidentiality, client notices and permissions, lawful collection, data accuracy, and deciding what may be uploaded or connected. This allocation does not override responsibilities imposed by law.

3. Information we process

  • Account and profile data: email address, name, authentication identifiers, profile image, account status, language and practice settings.
  • Matter data: party and counsel details, case numbers, court and judge information, hearing dates, facts, instructions, files, extracted text, evidence, correspondence, notes, strategies, tasks, drafts, and other work product.
  • AI and research data: prompts, scoped matter context, model inputs and outputs, research queries, public legal sources, citation checks, tool results, feedback, and records of approvals or refusals.
  • Connected-service data: the Google account email, granted scopes, encrypted OAuth tokens, selected Gmail or Drive content, imported attachments or files, and identifiers and hashes needed to register approved writes.
  • Technical and security data: session and device information, request times, coarse sign-in and feature events, error type, rate-limit events, access and security records, and limited network metadata processed by our hosts. Production application logs are designed not to contain matter text, prompts, party names, document titles, tokens, or raw query strings.
  • Communications: access requests, support emails, incident reports, survey responses, and product feedback you choose to provide.

Legal files may contain sensitive personal data about clients, opponents, witnesses, children, medical conditions, finances, alleged offences, or other third parties. Do not upload information that is not reasonably necessary for the matter and authorised for this form of processing.

4. Where information comes from

We receive information from you and authorised users, from files and services you connect, from authentication providers, and from the Service itself. If enabled for a matter, we may also retrieve public or licensed legal information from sources such as court-record providers, Indian Kanoon, official legal sources, and public web pages. Public availability does not make all information non-personal or remove your duty to use it lawfully.

5. Why we process information

We process information only for the following purposes:

  • create, authenticate, and administer accounts and early-access eligibility;
  • store and organise matters, extract documents, research, draft, compare, and re-plan;
  • perform user-requested Gmail, Drive, Google Docs, export, and communication actions;
  • show the source, verification, approval, and activity history of work performed;
  • secure the Service, prevent abuse, investigate incidents, and recover from failures;
  • provide support, send service notices, and administer pilots or paid subscriptions;
  • comply with law, enforce the Terms, and establish or defend legal claims; and
  • improve reliability and usability using feedback and operational data that is not matter content.

We do not sell or rent personal data, use matter content for advertising, build advertising profiles, or permit matter files, prompts, outputs, or Google Workspace data to be used to train general-purpose AI models.

6. AI processing

To perform a request, Luthor sends the minimum scoped instructions, document content, and matter context required for that request to its configured business AI inference provider. Document extraction, summaries, embeddings, outputs, and cached or derived representations inherit the confidentiality of their source; they are not treated as anonymous merely because they are transformed.

Production deployments are configured to use a reviewed business inference path and must not use a consumer AI account or an unreviewed developer-key path for privileged material. Luthor does not promise that an AI output is accurate, complete, current, or free from personal data contained in the supplied record. Users must review outputs before relying on, sharing, or filing them.

7. Legal research and external queries

Depending on deployment settings and the tools you enable, Luthor may send an abstract legal query, citation, public judgment identifier, CNR, or similar lookup value to a legal-research, court-record, or public-web provider. External web search uses Google Search grounding through the configured AI provider and may be disabled in Settings or disabled for the deployment.

The Service applies controls intended to block matter text and redact known private identifiers from public research queries. These controls reduce risk but are not a substitute for user review. Do not instruct Luthor to search the public web using a client name, confidential fact pattern, or non-public document text. Public research results should be treated as leads until verified against an authoritative source.

8. Google sign-in

If you choose "Continue with Google," Google authenticates you. We receive your Google account email address, name, profile image if available, and a stable account identifier to create or recognise your Luthor account. Google sign-in by itself does not give Luthor access to Gmail or Drive.

9. Optional Google Workspace connection

Connecting Google Workspace is optional and separate from sign-in. Luthor requests Gmail read and compose access and Drive read and per-file write access. The current connection grants these scopes together, while Gmail and Drive tools remain inactive until you activate the corresponding source for a turn.

  • Gmail: narrow search, bounded thread reading, selected attachment import, and user-approved draft creation or update. Sending requires a separate approval.
  • Drive and Google Docs: narrow search, selected file import, Google Doc reading, creation from a Luthor draft, and user-approved, revision-bound edits.

Search returns bounded results and Luthor opens selected items rather than scanning an account merely because it is connected. A write receipt may retain the action, target identifier, content hash, approval outcome, and provider result identifier without retaining a second copy of the written content in that receipt.

Luthor's use and transfer of information received from Google Workspace APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google Workspace data is used only to provide or improve the user-facing feature you request, for permitted security purposes, or as required by law. It is not used for advertising or to train or improve a general-purpose AI or machine-learning model.

10. Cookies and local storage

Luthor uses essential authentication and security cookies, a language-preference cookie, and a short-lived desktop handoff cookie when you choose that flow. The Service does not currently use third-party advertising cookies or behavioural advertising trackers. If non-essential analytics are introduced, this policy and any consent controls will be updated before they are enabled where consent is required.

11. When information is disclosed

Information may be disclosed only:

  • to service providers supporting hosting, database and storage, authentication, AI inference, monitoring, and email;
  • to Google or another connected service when you connect or direct that feature;
  • to legal, court-record, or public-web providers for a lookup that you enable;
  • to your organisation's authorised users or administrators, where an organisation account is provided;
  • when you direct, approve, or reasonably expect the disclosure to complete your request;
  • to investigate abuse, protect the Service or another person, or comply with a valid legal requirement; or
  • as part of a financing, reorganisation, merger, acquisition, or asset transfer, subject to confidentiality and applicable notice or consent requirements.

Service providers are permitted to access information only for the contracted function and are subject to appropriate confidentiality, data-protection, and security terms. A current subprocessor and processing-location list is available from support@luthor.in.

12. Processing locations

Luthor and its providers may process information in India and in other countries where approved infrastructure and personnel operate. Those countries may have different data protection laws. Luthor will apply contractual and technical safeguards and observe any transfer or localisation restriction that applies to the data or deployment. Ask support@luthor.in for the currently approved regions before using real client material.

13. Retention and deletion

  • Active matters: retained while the matter remains active or until you archive it or validly request deletion.
  • Archived matters: recoverable in the archive for 30 days, then deleted from the active database and primary object storage, unless a legal hold or documented retention requirement applies.
  • Google connection data:retained until you disconnect Google or close the account. Disconnect attempts to revoke the provider tokens and deletes Luthor's local tokens and authorisation metadata. Imported matter copies remain under the matter's retention rule.
  • Account, support, security, and transaction records: retained for as long as needed to operate the account, resolve the request, secure the Service, meet tax or legal obligations, or establish and defend claims.

Deletion from active systems may not immediately remove an item from encrypted disaster- recovery backups. Backup copies are isolated from ordinary use and expire on the applicable backup cycle unless preservation is legally required. We may retain a minimal record of a deletion request and its completion. We do not retain personal data merely because storage is inexpensive.

14. Your choices and rights

You may choose email sign-in, keep Workspace disconnected, disable available research tools, decline a proposed external write, disconnect Google, archive a matter, or stop using the Service. Subject to applicable law and verification, you may also request:

  • a summary of personal data and processing activities relating to you;
  • the identities or categories of other parties with whom that data was shared;
  • correction, completion, or updating of inaccurate or incomplete personal data;
  • erasure of personal data that is no longer needed or lawfully required;
  • withdrawal of consent for optional processing, without affecting earlier lawful processing;
  • redress of a privacy grievance; and
  • nomination of another individual to exercise applicable rights in the event of death or incapacity, when that right becomes applicable.

Send requests to support@luthor.infrom the account email and describe the account, matter, and right involved. We may ask for proportionate information to verify identity and authority, especially where a request could disclose client files or another person's data. We ordinarily aim to respond within 30 days and will meet any shorter or mandatory period that applies. If Luthor processes the relevant matter data only for an advocate or organisation, we may refer the request to that responsible user.

15. Security and human access

Luthor uses measures intended to protect matter data, including private storage, authenticated server-side access, row- and matter-level authorisation, encryption in transit and at rest, encrypted connected-account tokens, scoped provider access, and approval controls for external writes. Available controls and implementation limits are described on the Security page.

Authorised personnel may access customer data only when needed for support the user requests, a security or abuse investigation, legal compliance, or critical recovery. Google Workspace content is not read by a person except with specific user permission, for permitted security purposes, or as required by law. Access is limited and subject to confidentiality obligations. No security measure is absolute.

16. Personal data breaches

If we confirm a personal data breach, we will contain and investigate it, preserve appropriate evidence, and notify affected individuals and authorities when and in the form required by applicable law. Report suspected unauthorised access promptly to support@luthor.in.

17. Children

Accounts are for adults with legal capacity and the Service is not directed to children. Matter files may necessarily concern children. The responsible advocate must have a lawful professional basis for that processing, minimise the data, and avoid using a child's information for public research queries. Contact us if a child created an account or supplied account data without proper authorisation.

18. Grievances and complaints

Send a privacy grievance to support@luthor.inwith the subject "Privacy grievance". Include enough detail to investigate, but do not email unnecessary client documents. We will acknowledge, investigate, and provide an outcome or status within the period required by applicable law. Where the Digital Personal Data Protection Act, 2023 right of grievance redressal applies, the internal process must be used before approaching the Data Protection Board of India.

19. Changes to this policy

We may update this policy as the Service, providers, or law changes. We will post the revised policy with a new date and give account users reasonable advance notice of a material change where practicable or legally required. A change will not retroactively reduce rights or expand use of previously collected matter data without an appropriate lawful basis and notice or consent where required.