Skip to content
IAC Trust Registry
Verify

/en/legal/trust-registry · v1.0 · 2026-05-27 · Current

Public Trust Registry policy

This policy defines what Trust Registry information is public, what is reserved in non-public documentation, what consents apply and how the holder may exercise their rights over their data.

1 · Governing principle

IAC operates a public registry with verifiable holders. Publication is governed by the holder’s explicit consent, the declared modality (standard or protected) and public data-minimization rules.

2 · What is published for each registry

Unique IAC code; registry type (Professional · Organization · Program); current status (Active · Expired · Suspended · Revoked · Under review); reference standard or program; declared technical scope; issue and validity dates; status reason, where applicable (without exposing individual evaluations); country associated with the scope; associated documentary evidence (public URL); public history of status transitions.

3 · What is never published

Identity document (DNI, CUIT, CURP, NIE, RFC, etc.); postal address; telephone; the holder’s personal email; individual evaluation notes or grades; private documents provided during the process; any sensitive data under the applicable legislation.

4 · Publication modalities

Standard: the public ficha shows the holder’s full name; applies to professionals, organizations and programs (default). Protected: the public ficha shows the holder’s initials or “Protected holder”; applies to professionals upon express request.

5 · Public minimization rule

The Trust Registry publishes only the data needed to verify a ficha: code, type, status, scope, validity and associated public evidence. The holder’s identity is shown only where permitted by the declared modality, consent and current policy.

6 · Holder consent

Nominative publication requires explicit consent on the application form, renewed at least every 3 years or upon a substantive change of policy. Consent is kept as evidence (date, IP-country, version accepted).

7 · Holder rights

At any time, and without stating a reason, the holder may: switch modality from “standard” to “protected” or vice versa; access the published and reserved data in their file; rectify published data; request full removal of the registry (revocation on request); receive a portable copy of their file. Channel: privacy@accreditationcenter.org.

8 · Post-revocation

When a registry is revoked: the public ficha keeps the code and the “Revoked” status with a public categorical reason where applicable; this persistence prevents covert reactivations and complies with the principle of public traceability; the holder may request additional redaction of the reason if it exposes sensitive information; reserved data is kept in a closed file for the term applicable to institutional documents.

9 · QR verification

Each valid ficha can emit a QR code for public verification. The public page confirms whether the code corresponds to a valid ficha within the declared scope. Verification activity is handled in aggregate form and is not published individually.

10 · Proportional retention of verification activity

Verifications are handled in aggregate form and proportionally to security, audit and compliance purposes. They are not cross-referenced with the holder’s personal data nor published individually. Operational retention details are not part of the public surface.

11 · Limitation of use by third parties

An affirmative verification confirms status, validity, modality and declared scope. It does not constitute IAC endorsement of uses of the registry outside the declared scope. Nor does it replace the reasonable diligence of the party consulting it when making hiring, third-party certification, public procurement or regulatory compliance decisions.

12 · Contact

Privacy and Registry data: privacy@accreditationcenter.org. Institutional matters: contact@accreditationcenter.org.

13 · Versioning

This policy is versioned. Substantive changes are notified to holders at least 30 days in advance and require renewal of consent where they affect the scope of publication.

privacy@accreditationcenter.org

← Back to legal