Lucern

Draft: pending founder review. This page describes how Lucern handles information today. It has not been reviewed by a lawyer and is not yet a binding notice or agreement, and the legal entity and grievance officer below are placeholders until the founder names them.

Privacy

What Lucern collects, why, where it is kept, who sees it and how long it is kept, as the product works today.

1. Who we are

Lucern is operated by [FOUNDER TO FILL: legal entity name]. It runs a supplier qualification platform for Indian defence and aerospace procurement: buyers publish their qualification process, and suppliers answer it from a profile they keep with us.

Questions about this page go to support@lucern.com. Concerns about your personal data go to the grievance officer named below.

2. What we collect

Early-access requests. Your email, name, company (optional) and role. To limit abuse, each request is logged with the network address it came from.

Accounts. Your name and email, the organisation you belong to and your role in it, and a 90-day history of sign-ins (a shortened browser description; no IP address).

Supplier profiles. Statutory identifiers (PAN, GSTIN, CIN, Udyam), bank details for a one-time account check, financial statements, certificates and other documents you upload, and the names, DINs, mobile numbers and email addresses of directors and signatories.

Use of the site. Product interaction events (PostHog) and error reports (Sentry). An error report can incidentally contain an identifier that was on screen.

3. How we use it, and what you agree to

We ask for consent per purpose, not once for everything:

  • Identity verification (required): storing your identifiers and checking them against each other.
  • Showing your profile to a buyer (required): only when you respond to that buyer's listing.
  • Registry lookups (optional): sending identifiers to a verification provider that queries MCA, GST and Udyam. Without it, identifiers are checked for format only, and say so.
  • Reading documents automatically (optional): extracting details from certificates and financial statements with an AI model.

You can withdraw an optional purpose from your settings at any time.

4. Where it is kept and processed

Supplier and qualification data is stored in India. The database and file store are Supabase, in its Mumbai (ap-south-1) region. That covers your profile, identifiers, documents, submissions and the buyer's decisions on them.

Our application servers run in Singapore (Railway, which has no India region). They process requests in transit and store nothing of yours themselves.

Analytics and error reports leave India. Product usage events go to PostHog and error reports to Sentry, both hosted in the United States. Neither receives your documents or your profile; an error report can carry an identifier that was on screen when it happened.

Document reading sends the contents of a document you upload to Google (Gemini) to read it, only under the optional consent above. The rendered page images are not stored.

5. Who sees it

Your profile reaches a buyer only when you act on one of their listings, such as by responding to it.

These service providers process information for us:

  • Supabase: database and file storage, in its Mumbai (ap-south-1) region.
  • Railway: the application servers, in Singapore.
  • Google (Gemini): the contents of documents you upload, to read them.
  • Surepass and Sandbox.co.in: statutory identifiers and bank details, for registry lookups and the bank account check, under the optional consent above.
  • MSG91: a signatory's mobile number, to send a one-time code.
  • Certificate registries: a certificate's number and holder name, to check it against the body that issued it. Today that is the NABL and ASME public directories; IAF CertSearch is connected the same way once access is in place.
  • Resend: your email address and name, to send email.
  • Sentry and PostHog: error reports and product usage events, in the United States.

To be decided by the founder: confirmation that each provider has a data-processing agreement in place.

6. How long we keep it

  • Bank account numbers are deleted 7 days after the account check finishes. We keep the last four digits, the account holder's name and the result. Lucern never sends or receives payments.
  • Registry answers we cache are deleted once they are too old to use. Dates of birth, mobile numbers, emails and other sensitive fields are removed before one is stored.
  • Sign-in history is kept for 90 days.
  • Identifiers, profile data and documents are kept for the life of the account. A certificate you remove has its file deleted.
  • The audit log (a record of who did what) is kept indefinitely.

To be decided by the founder: whether deleting an account removes names and email addresses from the audit log, and how long onboarding analytics are kept.

7. Your choices

  • Withdraw any optional consent from your settings.
  • See your whole profile in the product, and ask for a correction to a verified identity field from your account page, with a supporting document.

To be decided by the founder: the deletion process and its timeline, and a downloadable copy of your data.

8. Grievance officer

The Digital Personal Data Protection Act requires a named person you can write to about how your personal data is handled. Ours is [FOUNDER TO FILL: grievance officer name], at [FOUNDER TO FILL: grievance officer email].

To be decided by the founder: how quickly a grievance is acknowledged and resolved.