Trust
Digital credentials can be better for privacy than emailing scans of documents around. They are not automatically better. Here is what actually happens to information.
DiligenceID does not hold a copy of an issued credential, and cannot read one.
These records exist so issuers and checkers can see what happened. They are how withdrawal works.
Issuing and checking credentials creates records, and those records are what make withdrawal work and give both sides an audit trail. What stays out of them is the credential itself and the keys that bind it to a person.
The design point is that an organisation asks for what it needs, rather than taking a copy of everything.
Hosting region is set per deployment and stated in writing in the agreement. If data residency is a firm requirement, raise it early and we will confirm what is achievable.
Retention for issuance and checking records is set per deployment to match your own retention policy, and written into the agreement.
Issuing or checking credentials means handling personal information, so the Privacy Act applies to your organisation as it does today. We will work through what that means for your design.
Credential design decides what information travels. We work through that with you so a credential carries what the decision needs and no more.
This website
This is a static website. It sets no cookies, includes no third-party analytics or advertising, and does not track you between visits.
If you send an enquiry through the contact form, we receive what you typed and use it to answer you. Please do not put identity documents, credential contents or anything else sensitive into it.
Privacy questions: privacy@maits.co.nz. The MAITS privacy statement covers how MAITS handles enquiries.
Tell us the deployment you have in mind and we will work through what information travels, who holds it, and the options for carrying less.
