Compliance
Designed to align with PIPEDA. Not a substitute for your own legal advice.
"Compliant" gets printed on a lot of trust pages with nothing behind it. Here is specifically what ShieldID does that supports your organization's own privacy obligations, and what it doesn't do.
PIPEDA
Built around minimum collection and purpose limitation, not bolted on after.
PIPEDA's principles show up as product decisions, not a policy document nobody reads.
- We collect what a verification decision needs — the ID, a selfie, the fields on the document — and nothing beyond it.
- ID images are purged automatically on a short timer, seven days by default, rather than retained indefinitely by default.
- Sign-ins, document views, verification outcomes and API-driven actions are recorded in an append-only Activity Ledger. Per-view access to a raw ID image is not yet a logged event — that's on the way.
- Compliance with PIPEDA is an obligation of the organization using ShieldID, not something we can certify on your behalf. What we provide is the controls and the record; how they fit your organization's obligations is a question for your own privacy officer or counsel.
Provincial privacy law
We've considered Quebec's Law 25. We haven't been assessed against it.
Provincial regimes layer on top of PIPEDA, and Quebec's Law 25 is the one most likely to apply to a Canadian identity-verification workflow. We've factored its direction — minimum collection, a clear basis for processing, a documented record of access — into how ShieldID is built. We have not undergone a formal assessment against Law 25 or any other provincial regime, and we won't claim one until it exists. If your organization operates in Quebec, confirm your own obligations with counsel rather than relying on this page alone.
Consent
Captured in the flow, not assumed.
An applicant sees what's being collected and why before their document and face are captured.
- Consent is presented to the applicant, on their own device, as part of the verification flow itself — not buried in a separate terms page they never open.
- Acceptance of the e-signature terms is recorded as an EULA_ACCEPTED event at the moment it happens. A separate, biometric-scan-specific consent event does not exist yet.
- The images described by that consent are the ones purged automatically on the retention timer described on the retention page.
Operational controls
The parts of compliance that live in the software, not the policy binder.
Two-factor authentication
Coming soon for self-serve enrollment. Once a TOTP code is set on an account, the portal enforces it at sign-in.
Append-only audit
Every sign-in, document view, verification outcome and export is entered in a record the database itself refuses to let anyone edit or delete.
Prove it, don't just claim it
The Activity Ledger is how compliance stays checkable.
A policy that says access is controlled is a promise. A ledger that shows every access, enforced by the database, is evidence. That's the difference we're building toward, and it's already live for sign-ins, document access and verification outcomes.
Certifications
None held yet. We won't print a badge we haven't earned.
No SOC 2, ISO 27001 or similar certification exists for ShieldID today, and none is implied anywhere on this site. If and when we hold one, it will appear here with the date it was issued and exactly what it covers — never as an unlabelled logo in a row of badges.
One more thing
This page is not legal advice.
It describes what the ShieldID platform does. Whether that satisfies your organization's specific obligations under PIPEDA, provincial privacy law or any other regime is a question for your own counsel or privacy officer, not for a marketing page.
Questions
Straight answers about compliance.
Talk to us
Have a specific compliance question?
Ask us directly — for a security questionnaire, a specific control, or something this page didn't cover.