Sub-processors

Every third party that processes data on our behalf to run Lawzer, what each one does, and where it does it.

Disclosurev1.4In force from 24 September 2026

Drafted against

  • Digital Personal Data Protection Act, 2023 — sections 8(2) and 16
  • Data Processing Addendum, clause 6

1.The register

Sub-processorWhat it doesData it can reachProcessing region
Vercel Inc.Application hosting, edge routing and the scheduled automation triggerCustomer content in transit; request logsServerless compute pinned to Mumbai (bom1). The company is US-incorporated; support access is governed by its own DPA.
Supabase (Supabase, Inc.)The production database — every record in the applicationAll Customer contentMumbai, India (ap-south-1). The application’s compute is in Mumbai too, so a query does not leave the country.
Vercel BlobThe evidence vault — uploaded acknowledgements, challans, resolutions, minutes and agreementsUploaded files and their metadataMumbai, India (bom1). Objects are stored private and are readable only through the authenticated route in the application.
Resend (Plus Five Five, Inc.)Delivery of statutory reminder emails and password-reset links. Not used where a deployment leaves the email variables unset, in which case reminders stay in the in-app inbox and no data reaches Resend at all.Recipient name and email address, and the content of the message — which names the obligation, the entity it belongs to and its due date. No uploaded files and no other Customer content.US infrastructure, under its own terms and DPA. Avoidable by not enabling email.
Google LLC — Firebase AuthenticationOptional Google and federated email sign-in. Not used where a deployment leaves the Firebase variables unset, in which case no data reaches Google at all.Email address, display name and Google account identifier of users who choose that door. No Customer content.Google's global infrastructure, under its own terms. Avoidable by not configuring it.
Each is engaged under written terms imposing obligations no less protective than our Data Processing Addendum. We remain liable to the Customer for their acts and omissions.

2.What we deliberately do not use

  • No analytics or product-analytics provider. There is no Google Analytics, no Mixpanel, no Amplitude, no PostHog.
  • No advertising or marketing-attribution network.
  • No session-recording or heatmap tool. Recording a company secretary working a statutory file would capture confidential client data by design.
  • No customer-support widget embedded in the application, which would run third-party script inside an authenticated workspace.
  • No third-party fonts loaded at runtime beyond the Google Fonts stylesheet, which serves the typeface and receives no Customer content.
  • No large-language-model API. The contract-vetting module is a structured checklist and a professional's own verdicts, not a generated opinion — so no Customer document is sent to a model provider.

This list is as much a part of the register as the first one. What a platform chooses not to embed tells a customer more about its data posture than what it has a contract with.

3.Changes to this register

  1. We give at least thirty days' notice before adding or replacing a sub-processor, by email to workspace administrators and by publishing a new version of this page.
  2. A Customer with a reasonable, data-protection-based objection may raise it within that period. We will try to resolve it; if we cannot, the Customer may terminate the affected subscription and take a pro-rated refund of the unused term.
  3. Where a change is forced on us at short notice — a provider withdrawing a service — we will notify as soon as we know and explain why the notice period could not be met.

To be told when this page changes, write to contact@lawzer.in and ask to be added to the notification list. Workspace administrators are on it automatically.

Read next