Last updated: November 2026. This page explains what data CertLaurel
collects, why, and what you can do about it — in plain language. Questions:
support@certlaurel.com.
Who has data here
Two kinds of people appear in our records:
Issuers — the people and organizations with accounts, who create certificates.
Recipients — the people certificates are issued to. Recipients don't have accounts; their issuer gives us their name and email so we can deliver the certificate.
What we collect
Account data (issuers): email address, business/issuer name, and a hashed password (we never store your password in readable form). Email verification status.
Billing data: payments are handled by our payment processor. We receive and store a customer reference, your plan, and subscription status — we never see or store your full card number.
Recipient data (provided by issuers): recipient name, recipient email, program title, issue date, and any custom line on the certificate. We store this only to issue, deliver, and verify the certificate.
Issuance records: for every certificate — who issued it, to whom, which template, when, delivery status (sent / delivered / bounced), and whether it has been revoked. This record is what makes verification possible.
Technical data: server logs, and the IP address of signup attempts (used only for abuse prevention — the free tier has a per-IP signup quota). API keys are stored only as hashes.
How we use it
To run the service: render and email certificates, show verification pages, meter credits, and bill plans.
To keep it trustworthy: prevent fraud and abuse, enforce plan limits, and keep an audit trail of issuance.
To communicate: verification and password-reset emails, billing notices (such as the 80%-of-allowance warning), and replies to support requests.
We do not use recipient data for marketing, and issuers may not either through our delivery email (§5 of the Terms).
Verification pages are public
This is the product working as intended, and it's worth stating plainly: anyone who has a
certificate's link or QR code can open its verification page and see the recipient's name,
the program, the issuer, the issue date, and whether the certificate is still valid.
No account is needed to view it — that's what lets an employer check a certificate in seconds.
Issuers should tell recipients this before issuing. A recipient's email address is
not shown on the verification page.
Who else processes data
We use a small number of service providers, each only for its job:
A hosting provider runs our servers and stores the database and certificate files.
A payment processor handles subscriptions and card payments.
An email delivery provider sends certificate and account emails and tells us whether they were delivered or bounced.
We do not sell personal data — not issuer data, not recipient data, not to
anyone. We don't run advertising trackers. Data is shared with authorities only when the law
requires it.
Cookies
One essential cookie: a session cookie that keeps issuers logged in to the dashboard. It's
HttpOnly (scripts can't read it) and it's the only cookie we set. There are no analytics or
advertising cookies.
Site visits
We count visits to our public pages on our own server — just which page was viewed and
the name of the site that referred the visit. We set no cookie for this, store no IP
address, and cannot identify individual visitors.
How long we keep data
Issuance records and verification pages persist — that permanence is the product's promise (§4 of the Terms). A certificate issued today must still verify years from now.
Account data is kept while the account is active.
Backups are kept for up to 30 days and then rotated out.
Signup-attempt records (IP addresses) are kept only as long as they're useful for abuse prevention.
Your choices and deletion
Email support@certlaurel.com to ask what data we hold about you, to correct it, or to delete it. We'll confirm who you are before acting, and we aim to answer within 30 days.
Issuers: deleting your account deletes your account data and the recipient data and issuance records under it. Be aware: a certificate whose issuance record is deleted can no longer be verified — its verification page stops working. Export anything you need first.
Recipients: if a certificate was issued to you and you want your data removed, contact us at the address above (or ask your issuer to contact us). The same note applies: removal means the certificate stops verifying.
Some records may be kept where the law requires it or to prevent fraud — for example, billing records held by our payment processor under its own policies.
Security
Passwords and API keys are stored only as hashes. Certificate downloads use signed, expiring
links. Dashboard sessions use HttpOnly cookies, sent over HTTPS in production. No system is
perfectly secure, but we build so that a single leak doesn't expose credentials.
Changes and contact
If we change this policy in a way that matters, we'll update this page and email account
holders before the change takes effect. Questions or requests:
support@certlaurel.com.