Most identity checks happen at the entrance to a digital process. A user enters credentials, completes a biometric check or verifies an identity document, and access is granted. Continuous Facial Recognition becomes relevant when an organisation also needs assurance after that opening check. <\/p>\n\n\n\n
Imagine a customer joining a confidential remote consultation and verifying their identity at the start. Halfway through, the customer steps away while the session remains open and another person takes over. The opening check has already done its job, but Continuous Facial Recognition can provide a signal that the verified person is no longer present. <\/p>\n\n\n\n
This is the practical difference between point-in-time verification and ongoing identity assurance. One establishes confidence at the beginning, while Continuous Facial Recognition seeks to maintain confidence as the session continues. <\/p>\n\n\n\n
How the technology works<\/strong>\u00a0<\/h2>\n\n\n\nThe process starts with a trusted facial reference linked to the verified user. Continuous Facial Recognition captures further facial samples during the session and compares them with that reference. <\/p>\n\n\n\n
If the comparison remains consistent, the session can continue according to the organisation\u2019s rules. If the face disappears or a comparison fails, Continuous Facial Recognition can trigger a predefined response, such as pausing an action, requesting another check or directing the user to a different verification route. <\/p>\n\n\n\n
Biometric comparison does not produce perfect certainty. Continuous Facial Recognition uses similarity scores and thresholds, and the Information Commissioner\u2019s Office explains<\/a> that biometric comparison results are statistically informed estimates that can produce errors. <\/p>\n\n\n\n\n.image-swap {\n display: inline-block;\n width: 100%;\n}\n\n.image-swap a {\n position: relative;\n display: block;\n}\n\n.image-swap img {\n display: block;\n width: 100%;\n height: auto;\n}\n\n.image-swap img.hover {\n position: absolute;\n top: 0;\n left: 0;\n width: 100%;\n height: 100%;\n object-fit: contain;\n opacity: 0;\n transition: opacity 0.3s ease-in-out;\n z-index: 2;\n}\n\n.image-swap:hover img.hover {\n opacity: 1;\n}\n\n\n\n \n ![\"Primary](\"\/media\/media\/media\/wp-content\/uploads\/sites\/2\/2025\/04\/CTA-Blog-Mpho-light-primary1.png\")
\n ![\"Secondary](\"\/media\/media\/media\/wp-content\/uploads\/sites\/2\/2025\/04\/CTA-Blog-Mpho-light-secondary-1.png\")
\n <\/a>\n<\/div>\n\n\n\nWhat liveness detection adds<\/strong>\u00a0<\/h2>\n\n\n\nFacial comparison answers whether the face at the camera resembles the verified reference. Continuous Facial Recognition also needs a way to assess whether the camera is seeing a real person rather than a photograph, replayed video, mask or other imitation. <\/p>\n\n\n\n
Liveness detection supports that assessment within Continuous Facial Recognition. It forms part of what NIST calls presentation attack detection<\/a>: methods intended to identify attempts to interfere with a biometric capture system. <\/p>\n\n\n\nLiveness should be treated as an additional safeguard rather than a guarantee. NIST\u2019s testing of passive, software-based presentation attack detection<\/a> has shown that performance differs between algorithms, which means organisations should examine the evidence supporting any Continuous Facial Recognition product. <\/p>\n\n\n\nWhen does ongoing identity assurance make sense?<\/strong>\u00a0<\/h2>\n\n\n\nNot every online action requires Continuous Facial Recognition. Repeatedly checking someone who is completing a low-risk task could add biometric processing and inconvenience without addressing a meaningful problem. <\/p>\n\n\n\n
Continuous Facial Recognition becomes more relevant when losing control of a session could have serious consequences. Examples might include access to sensitive information, participation in a confidential interaction or the remote completion of a consequential action. <\/p>\n\n\n\n
The decision can begin with one practical question: what could happen if the person who passed the opening check is no longer the person completing the interaction? Continuous Facial Recognition may be worth considering when the answer carries material risk; otherwise, a simpler control may be more appropriate. <\/p>\n\n\n\n
What should an organisation assess?<\/strong>\u00a0<\/h2>\n\n\n\nTechnology is only one part of the decision. Before adopting Continuous Facial Recognition, an organisation should understand: <\/p>\n\n\n\n
\n- The risk that requires checks throughout the session\u00a0<\/li>\n<\/ul>\n\n\n\n
\n- The testing evidence for facial matching and spoof detection\u00a0<\/li>\n<\/ul>\n\n\n\n
\n- How false matches, false rejections and interrupted camera access are handled\u00a0<\/li>\n<\/ul>\n\n\n\n
\n- Where biometric data is processed and stored\u00a0<\/li>\n<\/ul>\n\n\n\n
\n- What notice, choice or alternative route is provided to users\u00a0<\/li>\n<\/ul>\n\n\n\n
\n- How accessibility, device quality and connectivity affect the experience\u00a0<\/li>\n<\/ul>\n\n\n\n
\n- What action follows an unsuccessful or uncertain check\u00a0<\/li>\n<\/ul>\n\n\n\n
The right design is not necessarily the one that checks most often. A responsible Continuous Facial Recognition deployment uses biometric checks for a defined purpose, treats uncertain results sensibly and gives people a clear route forward when the technology cannot reach a reliable result. <\/p>\n\n\n\n
How YEO Messaging applies the technology<\/strong>\u00a0<\/h2>\n\n\n\nYEO Messaging describes its Continuous Facial Recognition technology as checking for the verified person\u2019s presence throughout an active session rather than only at login. According to YEO Messaging\u2019s product information<\/a>, its approach includes anti-spoofing measures, liveness detection and depth verification. <\/p>\n\n\n\nYEO Messaging also states that biometric information is stored on the user\u2019s device rather than in a central biometric database. Organisations considering YEO Messaging\u2019s Continuous Facial Recognition technology should assess this product-specific claim and the supporting technical evidence against their own requirements. <\/p>\n\n\n\n
Accessing YEO Messaging through SigniFlow<\/strong>\u00a0<\/h2>\n\n\n\nSigniFlow partners with and resells YEO Messaging\u2019s Continuous Facial Recognition with Liveness product as supplied by YEO Messaging. YEO Messaging remains a separate third-party solution and is not built into or integrated with the SigniFlow application or workflows. <\/p>\n\n\n\n
Organisations interested in Continuous Facial Recognition can enquire about YEO Messaging through SigniFlow without assuming that the technology forms part of another SigniFlow product. <\/p>\n\n\n\n
Maintaining confidence throughout a digital session<\/strong>\u00a0<\/h2>\n\n\n\nAn identity check at login provides a starting point. For some higher-risk interactions, Continuous Facial Recognition can provide an additional signal that the verified person remains present while the session continues. <\/p>\n\n\n\n
The value of Continuous Facial Recognition depends on applying it to a genuine risk, understanding its limitations and designing an appropriate response when a check is unsuccessful or uncertain. <\/p>\n\n\n\n
\n \n <\/a>\n<\/div>\n\n\n\nWhat liveness detection adds<\/strong>\u00a0<\/h2>\n\n\n\nFacial comparison answers whether the face at the camera resembles the verified reference. Continuous Facial Recognition also needs a way to assess whether the camera is seeing a real person rather than a photograph, replayed video, mask or other imitation. <\/p>\n\n\n\n
Liveness detection supports that assessment within Continuous Facial Recognition. It forms part of what NIST calls presentation attack detection<\/a>: methods intended to identify attempts to interfere with a biometric capture system. <\/p>\n\n\n\nLiveness should be treated as an additional safeguard rather than a guarantee. NIST\u2019s testing of passive, software-based presentation attack detection<\/a> has shown that performance differs between algorithms, which means organisations should examine the evidence supporting any Continuous Facial Recognition product. <\/p>\n\n\n\nWhen does ongoing identity assurance make sense?<\/strong>\u00a0<\/h2>\n\n\n\nNot every online action requires Continuous Facial Recognition. Repeatedly checking someone who is completing a low-risk task could add biometric processing and inconvenience without addressing a meaningful problem. <\/p>\n\n\n\n
Continuous Facial Recognition becomes more relevant when losing control of a session could have serious consequences. Examples might include access to sensitive information, participation in a confidential interaction or the remote completion of a consequential action. <\/p>\n\n\n\n
The decision can begin with one practical question: what could happen if the person who passed the opening check is no longer the person completing the interaction? Continuous Facial Recognition may be worth considering when the answer carries material risk; otherwise, a simpler control may be more appropriate. <\/p>\n\n\n\n
What should an organisation assess?<\/strong>\u00a0<\/h2>\n\n\n\nTechnology is only one part of the decision. Before adopting Continuous Facial Recognition, an organisation should understand: <\/p>\n\n\n\n
\n- The risk that requires checks throughout the session\u00a0<\/li>\n<\/ul>\n\n\n\n
\n- The testing evidence for facial matching and spoof detection\u00a0<\/li>\n<\/ul>\n\n\n\n
\n- How false matches, false rejections and interrupted camera access are handled\u00a0<\/li>\n<\/ul>\n\n\n\n
\n- Where biometric data is processed and stored\u00a0<\/li>\n<\/ul>\n\n\n\n
\n- What notice, choice or alternative route is provided to users\u00a0<\/li>\n<\/ul>\n\n\n\n
\n- How accessibility, device quality and connectivity affect the experience\u00a0<\/li>\n<\/ul>\n\n\n\n
\n- What action follows an unsuccessful or uncertain check\u00a0<\/li>\n<\/ul>\n\n\n\n
The right design is not necessarily the one that checks most often. A responsible Continuous Facial Recognition deployment uses biometric checks for a defined purpose, treats uncertain results sensibly and gives people a clear route forward when the technology cannot reach a reliable result. <\/p>\n\n\n\n
How YEO Messaging applies the technology<\/strong>\u00a0<\/h2>\n\n\n\nYEO Messaging describes its Continuous Facial Recognition technology as checking for the verified person\u2019s presence throughout an active session rather than only at login. According to YEO Messaging\u2019s product information<\/a>, its approach includes anti-spoofing measures, liveness detection and depth verification. <\/p>\n\n\n\nYEO Messaging also states that biometric information is stored on the user\u2019s device rather than in a central biometric database. Organisations considering YEO Messaging\u2019s Continuous Facial Recognition technology should assess this product-specific claim and the supporting technical evidence against their own requirements. <\/p>\n\n\n\n
Accessing YEO Messaging through SigniFlow<\/strong>\u00a0<\/h2>\n\n\n\nSigniFlow partners with and resells YEO Messaging\u2019s Continuous Facial Recognition with Liveness product as supplied by YEO Messaging. YEO Messaging remains a separate third-party solution and is not built into or integrated with the SigniFlow application or workflows. <\/p>\n\n\n\n
Organisations interested in Continuous Facial Recognition can enquire about YEO Messaging through SigniFlow without assuming that the technology forms part of another SigniFlow product. <\/p>\n\n\n\n
Maintaining confidence throughout a digital session<\/strong>\u00a0<\/h2>\n\n\n\nAn identity check at login provides a starting point. For some higher-risk interactions, Continuous Facial Recognition can provide an additional signal that the verified person remains present while the session continues. <\/p>\n\n\n\n
The value of Continuous Facial Recognition depends on applying it to a genuine risk, understanding its limitations and designing an appropriate response when a check is unsuccessful or uncertain. <\/p>\n\n\n\n
Liveness should be treated as an additional safeguard rather than a guarantee. NIST\u2019s testing of passive, software-based presentation attack detection<\/a> has shown that performance differs between algorithms, which means organisations should examine the evidence supporting any Continuous Facial Recognition product. <\/p>\n\n\n\n Not every online action requires Continuous Facial Recognition. Repeatedly checking someone who is completing a low-risk task could add biometric processing and inconvenience without addressing a meaningful problem. <\/p>\n\n\n\n Continuous Facial Recognition becomes more relevant when losing control of a session could have serious consequences. Examples might include access to sensitive information, participation in a confidential interaction or the remote completion of a consequential action. <\/p>\n\n\n\n The decision can begin with one practical question: what could happen if the person who passed the opening check is no longer the person completing the interaction? Continuous Facial Recognition may be worth considering when the answer carries material risk; otherwise, a simpler control may be more appropriate. <\/p>\n\n\n\n Technology is only one part of the decision. Before adopting Continuous Facial Recognition, an organisation should understand: <\/p>\n\n\n\n The right design is not necessarily the one that checks most often. A responsible Continuous Facial Recognition deployment uses biometric checks for a defined purpose, treats uncertain results sensibly and gives people a clear route forward when the technology cannot reach a reliable result. <\/p>\n\n\n\n YEO Messaging describes its Continuous Facial Recognition technology as checking for the verified person\u2019s presence throughout an active session rather than only at login. According to YEO Messaging\u2019s product information<\/a>, its approach includes anti-spoofing measures, liveness detection and depth verification. <\/p>\n\n\n\n YEO Messaging also states that biometric information is stored on the user\u2019s device rather than in a central biometric database. Organisations considering YEO Messaging\u2019s Continuous Facial Recognition technology should assess this product-specific claim and the supporting technical evidence against their own requirements. <\/p>\n\n\n\n SigniFlow partners with and resells YEO Messaging\u2019s Continuous Facial Recognition with Liveness product as supplied by YEO Messaging. YEO Messaging remains a separate third-party solution and is not built into or integrated with the SigniFlow application or workflows. <\/p>\n\n\n\n Organisations interested in Continuous Facial Recognition can enquire about YEO Messaging through SigniFlow without assuming that the technology forms part of another SigniFlow product. <\/p>\n\n\n\n An identity check at login provides a starting point. For some higher-risk interactions, Continuous Facial Recognition can provide an additional signal that the verified person remains present while the session continues. <\/p>\n\n\n\n The value of Continuous Facial Recognition depends on applying it to a genuine risk, understanding its limitations and designing an appropriate response when a check is unsuccessful or uncertain. <\/p>\n\n\n\nWhen does ongoing identity assurance make sense?<\/strong>\u00a0<\/h2>\n\n\n\n
What should an organisation assess?<\/strong>\u00a0<\/h2>\n\n\n\n
\n
\n
\n
\n
\n
\n
\n
How YEO Messaging applies the technology<\/strong>\u00a0<\/h2>\n\n\n\n
Accessing YEO Messaging through SigniFlow<\/strong>\u00a0<\/h2>\n\n\n\n
Maintaining confidence throughout a digital session<\/strong>\u00a0<\/h2>\n\n\n\n