Legal
Last updated: 3 October 2026
This page describes how the platform is actually built, so your IT team can judge it rather than take our word. Where we have not done something, it says so.
Separation is enforced in one place rather than remembered at each query. Every database read and write for an institution passes through a scoping layer that attaches that institution’s identifier before the query reaches the database, and refuses any operation it does not recognise rather than letting it through unscoped. A new feature is therefore separated by default, and a developer who forgets gets an error rather than another institution’s records.
Stored files — certificate PDFs, artwork, signature images — are namespaced per institution and the namespace is checked when a file is read back, because a file path is not an authorisation boundary.
Each issuing institution has its own Ed25519 signing key. Private keys are derived on demand from a master secret and never stored — so no private key exists in the database or in any backup of it. The public half is published in the institution’s DID document so anyone can verify a credential without us.
A credential is signed once, at publication, and the signature is stored and served unchanged. Keys can be rotated, which keeps old signatures verifiable, or revoked, which withdraws them.
All traffic is HTTPS. The database is encrypted at rest by our hosting provider. Secrets we hold on your behalf — webhook signing secrets, SSO client secrets — are encrypted with a separate key before being stored, and the service refuses to start in production without that key configured.
Webhook deliveries and external document fetches resolve through a guard that refuses private and internal network addresses, checked at the point the connection is made rather than before, so a hostname cannot resolve to something different on a second look. Webhook payloads are signed, and a rotated secret signs with both the old and the new for 24 hours so a rotation does not break delivery.
The JSON-LD contexts needed to verify a credential are bundled with the server and never fetched at request time, so a signature never depends on a third party’s uptime or lets them change the meaning of a term we have already signed over.
Access tokens, API keys, session cookies and shared secrets are redacted before anything is written to our logs. Actions that change an institution’s data are recorded in an audit log, and everything that happens to a credential is recorded in an append-only timeline that the institution can read.
A promise worth stating as a security property: no account state invalidates an issued credential. Suspending an institution stops it signing in and issuing; the public check page for everything it has already published keeps working. The same is true of cancellation and non-payment.
Write to [email protected] with enough detail to reproduce it. We will acknowledge within 2 working days, tell you our assessment, and tell you when it is fixed. Please do not test against other institutions’ data or run load tests against the live service — ask us and we will arrange a way for you to test safely.
Dnyx Business Solutions Private Limited (CIN U62099TN2025PTC177624), incorporated 1 March 2025. Registered office: 6/13, Old Washermenpet, Mayor Basudev 2nd Street, Tondiarpet, Fort St George, Chennai, Tamil Nadu 600021, India. Contact: [email protected].