Matched by keyed blind index
Report numbers are matched through a keyed HMAC, never a plain hash and never in the clear. The stored number itself is encrypted with AES-GCM.
HMAC-SHA256 + AES-GCMTrust & privacy
Built to expose duplicate claims without becoming a public register.
A searchable directory of who owns which diamond would be a gift to the wrong people. Every design decision here exists to detect conflicts while keeping identity and evidence private.
Evidence is never public
Card photos, invoices, and jewellery images live in a private bucket. They are served only to you and to an authorised reviewer, always with no-store caching.
Private bucket, authenticated readsAlerts reveal a score, not a person
A conflict signal shows the other claim's trust score and the week it appeared. No name, no email, no address, no exact timestamp.
Score plus week onlyCamera-only evidence
Evidence must be taken with the camera rather than uploaded as a file, which makes a forwarded screenshot of somebody else's document far harder to pass off.
No file or PDF uploadsReviewed by a named admin
Reviewers sign in with an explicitly allow-listed Google account. Every login, queue action, and decision is written to an append-only audit log.
Full audit trailDeletion you control
Remove a single entry at any time, or mark the whole account for deletion. Account deletion completes after a seven-day window in case it was a mistake.
Seven-day grace periodLIMITS
What we deliberately cannot tell you.
KimeGem cannot confirm that a physical stone matches its report, cannot value a diamond, and cannot decide who legally owns one. It tells you that a certificate identity is being claimed more than once, which is the signal to investigate with the seller, marketplace, insurer, or grading laboratory.
Free to join
Private by default, useful from the first number.
You can register and receive duplicate alerts without ever uploading a single document.
Get the app