01Who we are and what this covers
This Privacy Policy explains how Kimevik (“we”, “us”) handles personal information in the KimeGem mobile app, the KimeGem website, and the KimeGem API (together, the “Service”).
It does not cover other Kimevik products, which publish their own policies, or third-party websites we link to such as the grading laboratories.
We handle personal information in accordance with the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs). We are the entity responsible for the personal information described here, and you can reach us at support-kimegem@kimevik.com.
We do not collect sensitive information as the Privacy Act defines it — no health, biometric, racial, political, religious, or sexual-orientation data — and we have no government-identifier collection of any kind.
02What we collect
Account identity. When you sign in with Google or Apple we receive a stable account identifier, your email address, and where you allow it, your display name. We never receive or store your password for either provider.
Certificate entries. The grading laboratory and report number you register, the type of entry (lookup, ownership, or buying check), and its verification status and trust tier.
Evidence you choose to upload. Camera photographs of a grading card, a purchase invoice, and up to three images of the jewellery. Uploading evidence is optional; you can use the Service without it and still receive duplicate-claim alerts.
Settings and device data. Your notification preferences, and a push notification token for the device you install the app on.
Technical and security data. IP address, coarse location derived from it (country, region, city, time zone), request timestamps, and error logs. This is used to operate the Service, apply rate limits, and investigate abuse.
Audit records. An append-only log of actions taken on your entries — who verified what, when, and what the outcome was.
03What we deliberately do not collect
We do not ask for your home address, phone number, government identity documents, bank details, or payment card. We do not run advertising, we do not embed advertising or social media trackers, and we do not build advertising profiles.
We do not sell personal information, and we do not share it with data brokers.
04How we use it
To operate the registry: verifying a report number against the grading laboratory, matching entries against each other, and alerting the parties when the same certificate identity is claimed more than once.
To review evidence you submit, so a trust tier means something.
To send the notifications you asked for, at the tier threshold you selected.
To keep the Service secure and available: rate limiting, abuse investigation, fraud prevention, and debugging.
To meet legal obligations and to respond to lawful requests.
Where our processing rests on legitimate interests, that interest is operating a fraud-detection registry that its users have asked to be part of. Where you have given consent — push notifications, optional evidence uploads — you can withdraw it at any time in the app.
05How report numbers and evidence are protected
Report numbers are not stored in the clear. Each number is encrypted with AES-GCM. Matching is done against a keyed HMAC-SHA256 blind index rather than the number itself, so the database can tell that two entries are the same number without holding a searchable list of diamonds.
Evidence lives in a private store. Photographs are never public, never indexed, and never served without an authenticated request from you or an authorised reviewer. Responses are marked no-store so they are not cached along the way.
Evidence is never shown to the other party. A conflict alert reveals the other claim’s trust tier and the approximate week it appeared. It does not reveal a name, email address, postal address, photograph, or exact timestamp.
Sessions are revocable. Sign-in tokens are stored only as a one-way hash, expire automatically, and are destroyed on the server when you sign out.
No system is perfectly secure, and we do not claim otherwise. We do commit to designing for the assumption that a copy of the database will one day end up somewhere it should not.
06There is no public register
KimeGem has no public directory, no public search, and no browsable listing of registered stones or owners. A searchable index of who owns which diamond would be a gift to precisely the people this Service exists to frustrate.
Matching happens internally. Results are shown only to the people party to the match.
07Who we share it with
Infrastructure providers. The Service runs on Cloudflare (compute, database, object storage, and network security). Push notifications are delivered through Apple and Google. These providers process data on our instructions.
Grading laboratories. When we verify a report number, that number is sent to the relevant laboratory’s public lookup service. Your identity is not sent with it.
Authorised reviewers. Named individuals on an explicit allow list, whose every action is written to the audit log.
Legal and safety. We may disclose information where we are legally required to, or where it is necessary to investigate fraud, protect someone from harm, or establish or defend a legal claim.
If the business is ever sold or reorganised, information may transfer as part of that transaction; the terms of this policy would continue to apply to it.
08Overseas disclosure
The Service runs on Cloudflare’s global edge network, so your data is processed in whichever region is closest to the request. That means personal information is likely to be handled in the United States, the European Union, and other countries where Cloudflare operates, as well as in Australia.
This is an overseas disclosure for the purposes of APP 8. We take reasonable steps to ensure our providers handle personal information consistently with the Australian Privacy Principles, relying on their contractual commitments and standard contractual clauses. Push notifications are delivered through Apple and Google, which operate on the same basis.
09Data breaches
If we suffer a data breach that is likely to result in serious harm to you, we will notify you and the Office of the Australian Information Commissioner as required by the Notifiable Data Breaches scheme under Part IIIC of the Privacy Act 1988 (Cth).
The design decisions in the section above exist to keep that bar high: an attacker with a copy of the database gets encrypted report numbers, blind-index digests, and hashed session tokens rather than a usable list of diamonds and live logins.
10How long we keep it
Certificate entries are kept while they are active in your vault. Deleting an entry removes it from community matching immediately.
Evidence photographs are deleted from the object store when you delete the evidence or the entry.
Your account can be marked for deletion in Settings. Deletion completes after a seven-day grace period, which exists so an accidental or coerced deletion can be reversed.
Audit and security records are retained longer than the data they describe, because their purpose is to show what happened after the fact. They hold identifiers and actions, not evidence images.
11Your rights
You can access and correct your profile and entries in the app, delete individual entries at any time, change or switch off notifications, and request deletion of the whole account.
Under APP 12 and APP 13 you may request access to the personal information we hold about you, and ask us to correct it if it is wrong. Write to support-kimegem@kimevik.com. We will respond within 30 days. There is no charge for making a request, and we will not charge for a correction.
If you are unhappy with how we handled your personal information or your request, tell us first so we can try to fix it. If you are still unsatisfied, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.
If you live outside Australia, you may have further rights under your local law — including data portability and the right to object to or restrict processing — and we will honour them where they apply.
12Anonymity
APP 2 gives you the option of dealing with us anonymously or under a pseudonym where that is lawful and practicable. It is not practicable here: the Service exists to tell two specific people that they have claimed the same certificate identity, and it cannot alert an account it cannot identify. Sign-in through Google or Apple is therefore required.
What you can do is use the Service without ever uploading a document. Registering a report number and receiving duplicate-claim alerts needs nothing beyond your sign-in identity.
13Children
The Service is not directed at children and is not intended for anyone under 18. We do not knowingly collect information from children. If you believe a child has registered, contact us and we will remove the account.
14Changes to this policy
We will update this page when our practices change and move the “last updated” date. Where a change materially affects how your information is used, we will tell you in the app before it takes effect.