Hi HN,<p>We are the core developers behind FACEIO (<a href="https://faceio.net" rel="nofollow">https://faceio.net</a>), a product developed from scratch here at PixLab (<a href="https://pixlab.io" rel="nofollow">https://pixlab.io</a>) in the past few years.<p>FACEIO is a cross-browser, Cloud & On-Premise deployable, facial authentication framework, with a client-side JavaScript library (fio.js) that integrates seamlessly with any website or web application desiring to offer secure facial recognition experience to their users.<p>Put it simply, FACEIO is the easiest way to add passwordless authentication to web based applications. Simply implement fio.js on your website, and you will be able to instantly authenticate your existing users, and enroll new ones via Face Recognition using their computer Webcam or smartphone frontal camera on their favorite browser.<p>FACEIO works with regular Webcams or smartphones frontal camera on all modern browsers, does not require biometric sensors to be available on the client side, and works seemingly with all websites and web applications regardless of the underlying front-end JavaScript framework or server-side language or technology.<p>Implementing FACEIO is straightforward. Before so, you need to create a new application first on the FACEIO Console (<a href="https://console.faceio.net" rel="nofollow">https://console.faceio.net</a>), and link this resource to your website or web application. The checklist below highlights the steps to follow for a smooth integration of fio.js on your site:<p>1. Create a new FACEIO application first: Follow the Application Wizard on the FACEIO Console to create your first application and link it to your website or web application.<p>2. Select a Facial Recognition Engine: Review Security & Privacy settings, Cloud or On-Premise deployment and customize the Widget look & feel, all done via the Application Wizard (<a href="https://console.faceio.net" rel="nofollow">https://console.faceio.net</a>).<p>3. Add the fio.js library to your Website: Implement fio.js (<a href="https://faceio.net/getting-started" rel="nofollow">https://faceio.net/getting-started</a>), our facial recognition library on your website before rolling facial authentication to your audience...<p>4. Enroll & Authenticate your first used via the enroll() & authenticate() methods respectively, the only two exported methods from the fio.js library.<p>The details:<p>Each enrolled user on your website represented by its feature vector (biometrics hashes, mapped by the selected facial recognition engine), alongside with his Unique Facial ID (<a href="https://faceio.net/facialid" rel="nofollow">https://faceio.net/facialid</a>), as well as, any metadata you have already linked to a particular user, is stored in a sand-boxed binary index called Application in the FACEIO jargon. Think of FACEIO Application as an isolated container of your users' data. Only your application with its encryption key can gain access to this index (features vectors & metadata). You can retrieve your encryption key via the Application Manager on the FACEIO Console.<p>You can create a new application via the FACEIO Console in a matter of minutes. This is easily done thanks to the Application Wizard. The wizard should automate the creation process for you. Usually, this involve inputting an application name, selecting a facial Recognition engine, reviewing security options, customizing the Widget layout, and so forth.<p>We have baked privacy and security directly into our infrastructure. We collect and store the minimum amount of personal information needed to authenticate users, and we back that up with intelligence-backed security monitoring. The underlying Facial Recognition Engines that FACEIO rely on such as PixLab Insight or AWS Rekognition only stores hash signatures of your facial features, a stream of meaningless floating point numbers anonymously, after your full explicit consent, and/or until you submits a removal request.<p>FACEIO itself (the service) including this Website, the fio.js facial authentication library, the Embedded Widget, the Rest API, the Console) does not store or handle biometrics nor even know anything about them. It is the responsibility of the selected facial recognition engine by the application owner (eg website or web application you use) to choose a cloud storage region or opt for on-premises deployment for storing biometrics hash.<p>Finally, The following tutorials, and guides should help you get started with FACEIO:<p>1.Getting Started Tutorial: Learn the fundamentals. Your first steps with FACEIO - <a href="https://faceio.net/getting-started" rel="nofollow">https://faceio.net/getting-started</a>.<p>2.Integration Guide: Learn how to implement fio.js, our facial recognition library on your website before rolling facial authentication to your audience - <a href="https://faceio.net/integration-guide" rel="nofollow">https://faceio.net/integration-guide</a><p>3.Developer Center: Code samples, documentation, support channels, and all the resources you need to implement FACEIO on your website - <a href="https://faceio.net/dev-guides" rel="nofollow">https://faceio.net/dev-guides</a><p>4. Trust Center: Learn how we handle your data securely and in compliance with privacy and legal requirements. - <a href="https://faceio.net/trust-center" rel="nofollow">https://faceio.net/trust-center</a> | <a href="https://faceio.net/apps-best-practice" rel="nofollow">https://faceio.net/apps-best-practice</a>