Identity Protection

Whalebone Aura — More ways
to stay safe.

Aura already protects subscribers browsing on and off your network; but data breaches can happen anywhere in their digital lives. Now, Aura helps them stay safe when using their payment cards, social media accounts, interacting with government agencies/using personal ID numbers, and when using online accounts.

The Identity Protection feature is an integral part of Whalebone Aura’s product architecture and works perfectly together with other layers to provide best business results for telcos.

Not just for subscribers

Aura’s ID Protection feature adds more ways to increase customer adoption; showing value by identifying breaches that happen away from your network, at social media providers, government agencies, and online services where account data can be stolen.

Adoption and stickiness

Customer data breaches often happen — for example at their favorite retailer — without the customer even knowing and can have damaging long-term consequences if not mitigated. Aura increases customer stickiness by identifying not just recent breaches, but historical ones, meaning they can start to see the value of the service early in the trial, giving them more reasons to subscribe and stay subscribed.

65 assets

We take care of 65 assets such as birth dates, personal health data, bank account numbers, credit card numbers, IP addresses, and more — with emails and phone numbers being the most commonly leaked assets.

How it works for your customers

In their customer portal, users can add both their email address and phone number to instantly see any leaks connected to them.

They can look into the details of any given leak and see what data was leaked, what it actually means for them, what kind of real-life threats it poses, and information about the given breach.

Whalebone provides the most detailed information about the threats and mitigation tactics to the telco customers.

If a new leak occurs later, the user is notified via email or SMS and asked to look for instructions in the user portal — so they never need to actively check for leaks; the system does it for them.