IndyKite.me

eIDAS - Bring Your Own Identity

“Every time an App or website asks us to create a new digital identity or to easily log on via a big platform, we have no idea what happens to our data in reality.” (EU Commission Sept 2020). Much like the concept of bring-your-own-device transformed the workplace over the last decade, the EU’s “bring-your-own-identity” requirements for Services Providers will transform the way in which businesses, public services, consumers and citizens interact online.

An Identity Wallet

IndyKite as a whitelabel

An eIDAS ready ID Wallet enables citizens and users with a way of leveraging their preferred eID towards any Service requiring identification, verification, and/or authentication credentials. It also offers an overview, as well as control over, their identity attributes, including how and where they are shared, accessed, and leveraged.

An Identity Broker

Safe, private access

The keys to providing secure, safe and private interoperability across multiple services providers in a diverse landscape means central governments, large corporates, and NGOs will need a way to ‘broker’ their services with potentially multiple different Electronic Identities (eIDs), across multiple different locational and regulatory contexts, for multiple different types of users.

Identity wallet workflow

Digital Twin

IndyKite as an Identity Broker

IndyKite’s Identity Relationship Graph (™) provides businesses and organisations alike with a means of managing this flow. Sitting ‘underneath’ the ID Wallet - or in fact used as a whitelabelled ID Wallet - IndyKite’s decentralized identity model allows for:

End users to 'broker' their eIDs across a multitude of different Trusted Services Providers (TSPs) and Qualified Trusted Services Providers (QTSPs), with the services they leverage everyday.

Creation of Digital Twins for deeper contextual understanding of their digital attributes and context. With rich contextual data linked to one or more Digital Twins, services providers can enrich their offerings, while solving for web3 use cases in ePrivacy & Consent.