Privacy policy

Introduction

This privacy policy describes how Prado Consulting Limited ("we", "us", "our") collects, uses, stores and shares personal data when you use:

• the ID Wallet mobile application for iOS and Android ("the app");

• our public website at verisia.id;

• web portals (wallet, issuer, admin and verifier) on verisia.id subdomains; and

• related authentication and API services.

We are the data controller for processing described here. Questions: jorge@pradoconsulting.co.uk.

Data we collect

The data we process depends on how you use the service.

Account and identity data

When you sign in, an identity provider authenticates you. Depending on the method you choose and what that provider releases, we may receive:

• email address;

• display name;

• a stable subject identifier from the provider;

• session tokens needed to keep you signed in.

Sign-in methods include email/password via Keycloak, Sign in with Google, Sign in with Apple, Sign in with Microsoft, or an organisation's federated directory. We never receive your Google, Apple or Microsoft password. Apple may send your name only on the first authorisation.

Google user data

If you choose Sign in with Google, Google shares with us, with your permission, only the basic profile information that the "openid", "email" and "profile" permissions allow:

• your email address, and whether Google has verified it;

• your first and last name;

• an identifier for your Google account.

We do not ask Google for access to your contacts, files, calendar, Gmail or any other Google service, and we never receive your Google password.

We use this information only to create your account, to sign you in, to show your name in your account and to contact you about the service. We keep it for as long as your account exists, and you can ask us to delete your account and this information at any time by writing to jorge@pradoconsulting.co.uk.

We do not sell Google user data, we do not use it for advertising, and we do not use it to train artificial intelligence or machine learning models. We do not transfer it to anyone else, except to the providers that host and run our service for us, under contract, or where the law requires it.

Our use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.

You can remove our access at any time in your Google Account, under Security, "Your connections to third-party apps & services".

Apple user data

If you choose Sign in with Apple, Apple shares with us the name and email address you agree to share, which may be a private relay address that Apple creates for you, and an identifier for your Apple account. Apple sends your name only the first time you sign in.

We use this information only to create your account, to sign you in and to contact you about the service, and we keep it for as long as your account exists. We do not sell it or use it for advertising.

You can stop using Sign in with Apple with us at any time in your Apple Account settings, under Sign in with Apple.

Microsoft user data

If you choose Sign in with Microsoft, with a personal Microsoft account or a work or school account, we ask Microsoft for one permission only, "User.Read" ("Sign in and read user profile"), which you or your organisation grant. We do not ask Microsoft for access to your email, files, calendar, contacts or any other Microsoft service, and we never receive your Microsoft password.

When you sign in with Microsoft we read your basic profile, and Microsoft returns: an identifier for your Microsoft account, your display name, first and last name, email address and user principal name (the name you sign in with) and, where your account has them, your job title, business and mobile phone numbers, office location and preferred language. Of these we keep only:

• the identifier for your Microsoft account;

• your email address or, when Microsoft holds none for you, your sign-in name if it is an email address. We record it as not verified, because a work or school organisation can set it to any address;

• your first and last name.

The rest of that profile is used only while that sign-in completes and is not stored. The access token Microsoft issues for reading it is kept with your sign-in session in our sign-in service, is used for nothing else, and is deleted when that session ends. For a work or school account, that token also carries your name, sign-in name, your organisation's identifier and the IP address you signed in from. In our wallet apps a session ends once the app has not used it for 30 days, so it ends within 30 days of your signing out of the app.

We use this information only to create your account, to sign you in, to show your name in your account and to contact you about the service. We keep it for as long as your account exists, and you can ask us to delete your account and this information at any time by writing to jorge@pradoconsulting.co.uk.

We do not sell Microsoft user data, we do not use it for advertising, and we do not use it to train artificial intelligence or machine learning models. We do not transfer it to anyone else, except to the providers that host and run our service for us, under contract, or where the law requires it.

You can remove our access at any time. With a personal Microsoft account, open the list of apps and services that can access your data (https://account.live.com/consent/Manage) and remove our app's permissions. With a work or school account, open My Apps (https://myapplications.microsoft.com), choose "Manage your application" for our app, then "Revoke permissions"; permissions your organisation's administrator granted can be removed only by that administrator.

Wallet and credential data (stored on your device)

The app stores verifiable credentials, cryptographic holder keys, and wallet preferences on your device using the platform secure storage (iOS Keychain / Secure Enclave, Android Keystore where available).

Holder private keys do not leave your device. We do not upload the contents of your credentials to our servers for ordinary wallet use.

If you use the web wallet, credential data is held in browser storage for that session and origin.

Credential offers and issuance

When you accept a credential offer, the app contacts issuer and platform endpoints to complete OpenID4VCI. Those requests may include:

• the offer identifier and pre-authorized code;

• a proof of possession of your holder key (public key material, not the private key);

• network metadata (IP address, user agent) in server logs.

Receiving a credential through a pre-authorized offer does not require an account.

Presentation and verification

When you present a credential to a verifier, you choose which attributes to disclose. Presentation data is sent to the verifier you select; we do not automatically notify issuers when you present privacy-preserving credentials.

Claims, evidence and organisation portals

If you submit a claim or evidence through a portal, that data is processed within the issuing organisation's ecosystem. Retention and access are governed by that organisation's policies as well as this one.

Technical and diagnostic data

Our servers and apps may process:

• IP address, request timestamps, HTTP headers and user agent;

• authentication and API error logs;

• container and infrastructure metrics for reliability and security.

We do not sell personal data. We do not use your data for third-party advertising.

How we use data

We use personal data to:

• provide sign-in and session management;

• deliver, store locally, and help you manage credentials;

• operate, secure and improve the platform;

• comply with law and respond to lawful requests;

• communicate with you about the service when necessary.

Legal bases (EEA / UK)

Where the GDPR or UK GDPR applies, we rely on: performance of a contract (providing the service you request); legitimate interests (security, fraud prevention, improving reliability); and consent where required (for example optional features). You may withdraw consent without affecting the lawfulness of processing before withdrawal.

Sharing and processors

We share data only as needed to run the service:

• Identity providers (Google, Apple, Microsoft, Keycloak, organisation IdPs) when you choose to sign in with them;

• Cloud and hosting providers that operate our infrastructure;

• Issuers and verifiers you interact with when you receive or present credentials;

• Professional advisers or authorities when required by law.

Contracts with processors require appropriate safeguards.

International transfers

Data may be processed in the European Economic Area and in other countries where our providers operate. Where required, we use appropriate safeguards such as Standard Contractual Clauses.

Retention

Session and authentication logs are kept for a limited period for security, then deleted or aggregated.

Credentials remain on your device until you delete them or uninstall the app.

Account data at the identity provider follows that provider's retention settings.

Organisation-held claim and evidence data follows the relevant ecosystem retention rules.

Security

We use TLS in transit, access controls, and industry practices appropriate to the sensitivity of the data. Holder keys are designed to stay on your device. No method of transmission or storage is completely secure.

Your rights

Depending on your location, you may have the right to access, rectify, erase, restrict or object to processing, and to data portability. Contact jorge@pradoconsulting.co.uk. You may lodge a complaint with your supervisory authority.

Uninstalling the app removes locally stored wallet data from your device. Account deletion at the identity provider is handled through that provider or by contacting us.

Children

The service is not directed at children under 16. We do not knowingly collect personal data from children. Contact us if you believe a child has provided data.

Changes

We may update this policy. The "Last updated" date at the top will change. Material changes may be communicated through the app or website.