Verification Process

How we review every listing on Go-LX

Last updated: 01 June 2026

Every cow listing, every gaushala registration and every vet profile on Go-LX is reviewed by a human before it goes public. There is no auto-approval flow. This page explains exactly what we check, what gets rejected, and how the platform's safeguards (phone-number gating, reporting, audit logs) work in practice.

Cow listing review

1. Step 1

   Seller submits with structured fields

   Sellers fill a structured form: breed, gender, age, weight, milk yield, vaccinations, district, state, price and at least one photograph. Free-text health notes and a description are optional. The form rejects submissions that omit any mandatory field.

2. Step 2

   Admin review against the welfare ruleset

   Every submission lands in the admin moderation queue with status "pending". A human reviewer checks photos for authenticity, cross-references the claimed breed against visible markers (coat, horn shape, dewlap, build), and runs the price against the regional band for that breed. Listings with red flags are rejected with a written reason that the seller can read.

3. Step 3

   Approved or rejected — never silently published

   Only listings with status "approved" appear publicly. Rejected listings stay private with the rejection reason visible to the seller. There is no auto-approval flow: every cow on the public marketplace passed a human review.

4. Step 4

   Buyer-seller contact is gated

   Seller phone numbers are NEVER shown on a public listing. A buyer must be signed in, submit a contact request, and wait for the seller to approve. The seller sees the buyer's context first and can accept, decline (with a reason), or ignore. This protects sellers from spam and gives both parties a logged trail.

Gaushala verification

1. Step 1

   Registration with verifiable identity

   Gaushalas register with their organisation name, registration/trust number, contact person, address, district and state. The registration number is the primary verification anchor — we cross-check against the issuing authority where one is published online.

2. Step 2

   Admin verification before public listing

   A pending gaushala registration is reviewed manually. We look at the registration documents, the photos of the facility, and (when possible) confirm contact details by phone before flipping the verified flag to true.

3. Step 3

   Public profile with the verified badge

   Verified gaushalas display a "Verified Gaushala" badge and show their full contact details, capacity, current population and services. Donors and adopters can reach them directly. Gaushalas can be unverified again if a credible welfare concern is raised.

Vet directory verification

1. Step 1

   Qualification + registration number required

   Vets submit their qualification (BVSc, MVSc, etc.), Veterinary Council registration number, clinic name and location. Registration numbers tied to the State Veterinary Council are the primary verification anchor.

2. Step 2

   Admin review before public profile

   Vet profiles are pending until reviewed. We check the registration number against the relevant council's public roster when one is available, and flag profiles where the claimed qualification doesn't match.

Platform safeguards

1. Step 1

   Phone numbers are RLS-locked

   Buyer and seller mobile numbers are protected by database row-level security. They are only retrieved server-side after a contact request is approved (for sellers) or after an adoption intent is approved (for adoption listings). Public profile views never include the mobile field.

2. Step 2

   Reporting goes to the moderation queue

   Every listing and every user profile has a "Report" option. Reports surface in an admin queue with the reason, the reporter's context, and a one-click action to remove the listing or restrict the user. Welfare-flagged reports are the highest-priority bucket.

3. Step 3

   Rate-limited public submissions

   Every public POST endpoint (newsletter signup, adopter form, contact request, visit tracking) is rate-limited per IP. We hash IPs with a server-side salt so we can deduplicate without storing the raw address.

4. Step 4

   Activity log survives deletes

   Critical actions — listing approval, contact request, adoption intent, handover confirmation — are recorded in a durable activity log that survives the deletion of the underlying row. The log is the audit trail when a dispute arises.