Privacy policy
Under legal review. This document describes the system's real architecture and is published for transparency while counsel finalizes the wording. Questions: privacy@glemo.io.
Who we are
Glemo is a credential verification network. For credentials issued by our customers, Glemo acts as a processor; the issuer is the data controller.
What data we process and why
| Data | Basis | For what |
|---|---|---|
| Holder email | Service delivery (issuer's instruction) | Deliver the credential and its verification link |
| Credential claims (name, achievement) | Same | The verifiable content |
| Account email (users) | Contract | Authentication and account management |
| Verification events (verdicts, latencies, no claims) | Legitimate interest | Metering, anti-fraud, and aggregate analytics |
What we don't do
- We publish no personal data on any public ledger. Credential data lives in ordinary, erasable storage. Where an integrity anchor is used, it is a keyed hash (commitment) that cannot be reversed or linked without the key.
- We don't sell data. We don't use claims for advertising.
Your rights
Access, rectification, erasure, portability. Erasure follows the pattern the CNIL endorses: we destroy the cryptographic key (the public anchor becomes unlinkable) and delete the internal copies. Target time: 72 h from a validated request; backups rotate out fully within the stated retention window. Contact: privacy@glemo.io.
Retention
Credential data: while the credential is active, or until an erasure request. Verification events: aggregated without claims, retained for billing and audit.