YumiPass Credential Gard for Microsoft Entra

RCDevs YumiPass Privacy Policy
This policy explains how personal data is processed when organizations use YumiPass Credential Guard to protect Microsoft Entra credential recovery workflows with YumiPass Passport NFC verification.

01

Purpose of the service

YumiPass Credential Guard allows an authorized Microsoft Entra administrator to create a one-time credential reveal link for a selected user.

Before a Temporary Access Pass, password reset credential, or similar recovery credential is revealed, the user must complete YumiPass Passport NFC verification and pass the identity matching policy configured by the administrator.

02

Data minimization

YumiPass Credential Guard is designed as a data-minimizing verification relay.

The claimant does not create a YumiPass account, does not create a YumiPass wallet, and does not store an identity document with YumiPass.

The YumiPass mobile app is used as a transient NFC passport reader for a single verification transaction. The YumiPass backend verifies the authenticity of the passport chip, including passive authentication and chip authentication where supported, and relays only the minimum passport-derived claims required to evaluate the administrator-defined matching policy.

03

Passport and identity document data

For YumiPass Credential Guard for Microsoft Entra, YumiPass does not store passport NFC chip contents, passport images, document images, OCR-extracted document data, selfie images, biometric templates, liveness data, or proof packages after the verification transaction.

Passport-derived claims are processed transiently only to complete the verification transaction and decide whether the one-time credential reveal may proceed.

04

Data processed by the service

The service processes only the data needed to provide, secure, and audit the credential reveal workflow. This may include:

  • Microsoft Entra tenant identifiers and Marketplace subscription status;
  • administrator sign-in information and administrator actions;
  • selected Microsoft Entra user information required for the recovery request;
  • one-time request state, expiry timestamps, and status;
  • the administrator-configured matching policy;
  • a temporary encrypted credential until it is revealed, locked, or expired;
  • YumiPass verification status and the minimum passport-derived claims required to evaluate the matching policy;
  • operational logs, security events, support records, and billing or metering records.

05

Temporary credential storage

Credentials are stored only temporarily, in encrypted form.

A credential is deleted after successful reveal, lockout, or expiry. Opening a link, starting verification, or completing passport verification does not by itself disclose the credential.

06

Customer role

The customer organization decides when the service is used, which user is selected, which matching policy is required, and how the result is used in its Microsoft Entra recovery workflow.

Customer administrators are responsible for configuring appropriate matching policies and ensuring that use of the service complies with their internal policies and applicable laws.

07

Retention

Passport-derived claims used for the verification transaction are processed transiently and are not retained after the transaction.

Temporary encrypted credentials are deleted after successful reveal, lockout, or expiry.

Operational records needed for service security, troubleshooting, auditability, billing, abuse prevention, and legal or contractual obligations may be retained for a limited period.

08

Sharing of data

YumiPass does not sell end-user personal data.

Data may be processed by service providers needed to operate the service, including cloud hosting, Microsoft Azure services, Microsoft Marketplace billing and subscription services, monitoring and security providers, and YumiPass verification infrastructure.

09

Security

The service uses technical and organizational measures designed to protect the credential reveal workflow, including encryption in transit, encrypted temporary credential storage, one-time reveal links, expiry controls, match-attempt lockout, access controls, tenant separation, and audit-oriented logging.

10

Contact

Privacy contact: privacy@yumipass.com

Operator:
RCDevs Identity SA
1 Boulevard du Jazz
4370 Esch-sur-Alzette
Luxembourg

 

11

Changes

RCDevs Identity SA may update this policy from time to time. The current version will be published with its effective date.