Security & control
Your data, safe and in the right hands
Each lab runs its own installation with its own data. Inside it, every person sees only what their job needs — and every change to a certificate is on record.

Security pillars
Enterprise-grade control, built in.
Each lab gets its own installation on its own web address, with its own data, logo and branding.
Once issued, only a lab owner or manager can change a certificate.
Staff sign in with Google — only for accounts you have approved.
The whole database every night, photos weekly, optionally emailed off the server.
Protection in layers
Six layers between a certificate and anyone who shouldn't touch it.
- Your own installationL1
Your lab's own web address and database — never shared with another lab.
- Approved sign-inL2
Staff sign in with a password or approved Google account only.
- Role-based accessL3
Lab managers, gemologists and reception each see only their part.
- Locked certificatesL4
Once issued, only a lab owner or manager can change a certificate.
- Change historyL5
Every create, edit, print, transfer and withdrawal is on record.
- Public verificationL6
Buyers see the findings — never customer names or prices.
Roles
Who can do what
The lab owner, lab managers, gemologists and reception each see only what their job needs.
| Area | Lab OwnerThe business | Lab ManagerOversight | GemologistThe bench | ReceptionFront desk |
|---|---|---|---|---|
| Daily work | ||||
| Dashboard | Yes | Yes | Yes | Yes |
| Stone intake | Yes | Yes | Yes | Yes |
| Lab queue | Yes | Yes | Yes | Yes |
| Printing & PDFs | Yes | Yes | Yes | Yes |
| Certificates | Yes | Yes | Yes | No |
| Customers | Yes | Yes | No | Yes |
| Collection & invoicing | Yes | Yes | No | Yes |
| Business & administration | ||||
| Gem categories | Yes | Yes | No | No |
| Reports | Yes | Yes | No | No |
| Staff, payroll & user accounts | Yes | Yes | No | No |
| Lab profile & branding | Yes | Yes | No | No |
| Customer portal | Yes | Yes | No | No |
| Lab settings & backups | Yes | No | No | No |
Has access No access
Accountability
Every change is on record
The change history shows who created, edited, printed, transferred or withdrew each certificate, and when. When a stone is sold, the certificate moves to the new owner and the ownership history keeps every change.
- Withdraw with a reason; reinstate any time
- A withdrawn certificate can no longer be printed
- Public pages never show customer names or prices
What if…
Ready for the bad days, too.
Five situations every gem lab worries about, and exactly what happens in GemcertX™ when they do.
What if…
A forged copy circulates
A copy of one of your certificates turns up in the market with altered findings.
How GemcertX™ responds
- 01A lab owner or manager withdraws the certificate and records the reason.
- 02The certificate can no longer be printed or transferred to a new owner.
- 03The withdrawal, and who made it, is kept in the change history.
What if…
A staff member leaves
Someone who had access to customers, certificates or invoices no longer works at the lab.
How GemcertX™ responds
- 01Switch their account off in one click.
- 02They can no longer sign in, by password or by Google.
- 03Everything they created or changed stays on record under their name.
What if…
Someone guesses certificate numbers
A person tries certificate numbers one after another on your Verify page, hoping to collect data.
How GemcertX™ responds
- 01Checking by hand needs both the certificate number and the stone's weight.
- 02A QR code carries a secure link, so it cannot be worked out from the number.
- 03The public page never shows customer names or prices.
What if…
An issued certificate needs a correction
A finding has to change after the certificate has already gone to the customer.
How GemcertX™ responds
- 01Issued certificates are locked for gemologists and reception.
- 02Only a lab owner or manager can make the change.
- 03The edit is recorded: what changed, who changed it and when.
What if…
The server has a bad day
Hardware fails or a mistake deletes records you need back.
How GemcertX™ responds
- 01The whole database is backed up every night.
- 02Stone photos, logos and stamps are backed up every week.
- 03Copies can be emailed off the server, and the dashboard warns you if a backup is missed.
Under the hood
The security spec sheet.
The technical detail your IT person will ask about, in one place.
Sign-in
- Passwords
- Stored hashed, never in plain text
- Failed sign-ins
- Rate-limited, so passwords can't be guessed at speed
- Customer portal
- Locked for 15 minutes after 5 failed attempts
- Leavers
- A switched-off account can't sign in, by password or Google
Verification
- QR links
- Carry a key signed with HMAC-SHA256 and your lab's secret
- Manual checks
- Need the certificate number and the stone's weight
- Before proof
- Nothing is revealed, not even whether the number exists
- Drafts
- Never public until the lab has issued the certificate
Website API
- API key
- Accepted only in a request header, never in the address
- Rate limit
- 120 requests a minute per key
- Data
- Gemological details only, no customer names or prices
- Off switch
- The lab can turn the API off at any time
Data & sessions
- Installation
- Your own database, never pooled with another lab
- Backups
- Database nightly, photos weekly, optional off-server copies
- Sessions
- HTTP-only cookies with same-site protection
- Audit
- Every create, edit, print, transfer and withdrawal recorded
Data ownership
Your data stays yours.
Your lab's own web address and database — never pooled with another lab's records.
Reports export to a spreadsheet, so your figures are always in your hands.
Copies of your backups can be emailed off the server to an address you choose.
Who can see customer names and prices?
Only signed-in staff whose role needs them. The public Verify page and the Website API never show customer names or prices.
Can an issued certificate be changed?
Only by a lab manager. Issued certificates are locked for everyone else, and every change is kept in the change history.
What if a forged copy of a certificate circulates?
A lab owner or manager withdraws the certificate with a reason. Anyone who checks it then sees "Withdrawn — not valid", and it can no longer be printed.
What happens when a staff member leaves?
Switch their account off. A switched-off account can no longer sign in — by password or by Google.
Is the Verify page safe from people guessing numbers?
Yes. Checking by hand needs both the certificate number and the stone's weight; the QR code carries a secure link instead.
Book a demo
Give every certificate the proof it deserves.
See GemcertX™ running with your own lab's name and logo. We set it up, bring your existing records across, and train your team.
TM