Your inventory. Your customers. Your data.
A jewelry shop's catalogue, client list, and sales history are among its most valuable assets. Lapis collects only what it needs to run the store, keeps it encrypted, and never sells it.
Built to be trusted with the shop's crown jewels.
Your data stays yours
Inventory, clients, sales, and repairs belong to your business. We never sell it, never use it to train models, and never share it with other shops.
Encrypted in transit & at rest
TLS everywhere, hashed passwords, signed session tokens. Daily encrypted backups to redundant storage so a disk failure never costs you the catalogue.
Scoped staff access
Every login is a named, revocable session. Roles limit who can void a sale, adjust inventory, or see cost — and every sensitive action is recorded with the actor.
An audit trail you can't quietly erase.
Inventory shrinkage and after-the-fact edits are real risks in a jewelry business. Lapis is built on an append-only event ledger: every movement of every piece — received, transferred, reserved, sold, scrapped — is an immutable record. Status is a projection of that history, not a field a staffer can simply overwrite.
That means the question "what happened to this piece, and who touched it?" always has an answer. The trail is part of the data model, not a logging afterthought that can drift.
Only what's needed to run the store.
We collect the data you put in (inventory, clients, sales, repairs) and the minimum operational metadata needed to run your business securely.
We do not run third-party advertising, behavioral tracking, or session-replay tools on the application. Card data is handled by your payment processor — Lapis never sees or stores full card numbers. The full detail lives in the Privacy Policy.
Found a security issue?
We take security reports seriously. If you've found a vulnerability, email [email protected] with details and a way to reproduce. We'll acknowledge within two business days and work with you on a fix and disclosure timeline.