A plain-language privacy posture built around minimal data.
CertMint keeps certificate issuance and verification working without turning recipient data into a marketing asset or a public directory by default.
Privacy summary
Organizations store the account and certificate records needed to issue, resend, verify, revoke, and re-issue community-recognition certificates. Search visibility can stay off by default.
Support path
Use one clear contact channel for billing, deletion, and verification help.
Liability posture
Community recognition only
CertMint does not issue licenses or regulated professional credentials.
Response posture
1
single support channel
Low
data collection by default
Monthly
self-serve billing posture
What we store
CertMint stores organization account details, issued certificate records, and the minimum recipient data needed to run the workflow: name and optional email address. If a paid organization enables public portfolios, recipient grouping can use those same records rather than collecting a second account by default.
What public pages show
Verification pages display the issuer, certificate details, and active or revoked status so recipients can share trusted proof. Public portfolio or verification search indexing can be disabled by the organization, and CertMint treats that low-liability posture as the default direction.
Sessions and requests
We use authenticated session cookies to keep workspace users signed in. We do not sell personal data. For account export or deletion requests, email [email protected] from the workspace email so the request can be verified safely.
Keep the trust path visible before the buyer needs support.
CertMint keeps privacy, refund, and support expectations on public pages so a coordinator can evaluate risk before opening the workspace.
Verification
Trust-ready public proof
Privacy
Minimal recipient exposure
Billing
Monthly self-serve controls