• Our sign-up and login pages have a new look and feel! 🎉
• Bug Fix: If you set your signals to the same weight, they should equally impact the risk score. But some signals check more data sources than others, impacting the risk score more than signals checking fewer data sources. We updated the scoring algorithm to account for this. 🐛
• Bug Fix: Previously if I tuned a policy and scored users again, the delta (aka change in score) remained zero. This is fixed so now you can determine if delta changed because users became more (or less) risky, or because of a policy change. 🐛

• Updated the policy tuner to automatically set all signals in a category to zero when you set that category to zero
• Added the ability to delete policies that you don’t need anymore
• Now when calculating scores, only data breaches that have occurred within the last 2 years will be considered
• app.verosint.com/sign-up will now take you directly to the sign up flow
• New policy results chart – now with a curve to better highlight where most of your scores are when comparing policies
• Added an empty state design when you don’t have any policies on your policies page
• Updated the descriptions of the starter policies (Strict, Moderate, and Permissive) based on customer feedback so you know what scores to expect when using them
• The delta value will no longer show up on the score response in Signal Playground
• Am I Risky? now shows better explanations of what caused each scenario to happen
• Am I Risky? now has prefilled emails and passwords for the example flows

Launched Am I Risky? to give examples of possible UI workflows that could be enabled by 443ID

Launched new signal processor infrastructure for fetching data from signal providers for risk scoring.

Launched Signal Playground to allow customers to explore our available signals and tuning while immediately seeing the impact to their score results

API Usage page now automatically updates to show your current remaining calls.

• Get fewer Unknowns when getting risk scores on a single user in Evaluator
• If customers get Unknown, they’ll see an improved message: “Still gathering enough information. Please try again.”
• Bug Fix: Disabled the policy selector in Evaluator after you hit “Get Results”, preventing half-baked info from showing up in Policy Results 🐛
• Bug Fix: Identifier headers in the csv template matches the parameters for the API request: email, ip, and phone-number, promoting consistency and cognitive recognition of our identifiers 🐛
• Bug Fix: The designed input validation errors show up in single user mode in Evaluator, minimizing the chances of a frustrated customer not knowing why their identifier is invalid 🐛
• Bug Fix: Some IP addresses were getting processed in Evaluator, but not showing up in the csv download of the results. Squashed! 🐛

• Added multiple users support to Evaluator
• Bug Fix: made improvements to the CSV uploader when it hits parsing errors
• Dropped support for GET calls on Risk Score API

• Added Evaluator for a single user to give customers an easy way to see a user's score without having to use another tool
• Added new starter policies for Permissive, Moderate, and Strict risk levels
• Removed Login and Registration starter policies

• Redesigned our login and sign up experience
• Added ability to sign up and login via Github and Google
• Added biometric support as a 2nd authentication factor