Compliance is code, never a setting.
Every rule below is enforced by the platform’s database and pipelines — not by staff remembering a policy. Changing any of them requires a signed-off compliance note in the engineering record.
BIS hallmarking & HUID
Every inventory piece can carry its HUID; the admin includes BIS lookup so the hallmark a customer sees matches the national registry. The marketplace “BIS verified” badge appears only for houses whose registration is recorded at onboarding — the badge cannot be self-declared.
Savings schemes — the 365-day rule
Gold savings schemes are hard-capped at 365 days and instalments at ₹15,000 by database constraints. A misconfigured scheme cannot be created, by anyone, on any plan. Every instalment is rate-stamped to the published snapshot it was booked against, in an append-only double-entry ledger where corrections are reversals — never edits.
Digital gold — SEBI disclosure
Every digital-gold flow renders the mandated disclosure copy before purchase: digital gold is not a SEBI-regulated product, no investor-protection mechanisms apply, and the customer is buying from the jeweller, not from JewelHouse. The screen is part of the flow’s code — it cannot be disabled per store.
Privacy & DPDP
Customer consent is captured with a versioned notice before any KYC or marketing use; KYC documents live in a private bucket readable only by reviewers with sign-off. Marketplace enquiries reach a jeweller only with the shopper’s explicit, versioned DPDP consent attached. Data lives in India (ap-south-1).
GST, HSN & e-invoicing
POS invoices compute CGST/SGST/IGST from the store’s place of supply, carry HSN summaries, and support government IRN e-invoicing for B2B sales. Totals are re-derived server-side on every invoice — a client cannot submit its own arithmetic.
Marketplace neutrality
The JewelHouse marketplace is a discovery directory: listings are strictly opt-in, ordering is by relevance, distance and the shopper’s filters ONLY — never an editorial or paid ranking of jewellers — and every purchase happens on the jeweller’s own storefront. JewelHouse is never the merchant of record.
Grievance officer
Per the IT Rules, grievances about the platform or marketplace listings: grievance@jewel-house.com. We acknowledge within 24 hours and resolve within 15 days. For a specific jeweller’s products or orders, the jeweller named on the invoice remains the seller of record.
Bank-grade controls, built in — not bolted on
Your storefront handles gold, money and customer data. Every privileged surface is guarded by configurable multi-factor sign-in, an append-only audit trail, and secrets that are encrypted and never leave the server — all switched on from your own console.
Admin two-factor sign-in
Turn on 2FA for your team from settings — an authenticator app (TOTP) with an email one-time-code fallback for a lost device. Configurable per store and for the platform team, with a self-service reset path. Off by default; one switch to enforce for everyone.
Session idle-timeout
Set an inactivity window after which admin sessions sign out automatically — so an unattended counter tablet can never be walked up to and used. Configurable per store and platform-wide.
Append-only audit trail
Every privileged action — and every sign-in and failed sign-in attempt — is recorded forever in an append-only log. Owners get an Activity page gated by a dedicated capability; the record can be read but never altered or deleted.
Your keys, encrypted & write-only
Bring your own Razorpay, WhatsApp, MSG91 or Resend credentials. They are stored encrypted, are write-only — never rendered back to any browser, not even a super-admin’s — and you can test the connection without the secret ever leaving the server.
Rate-freshness guard
A stale metal rate can never quietly misprice a scheme instalment or gold accrual — the platform rejects rate snapshots past their freshness window, and buyback pins the exact rate it quoted so a quote is never silently repriced.
16-capability staff roles
Every staff member sees only what their role grants, across a 16-capability permission model enforced at the database with row-level security — not merely hidden in the interface. One jeweller’s data is never reachable from another’s.