Department staff portals
Offer a convenient face-assisted sign-in for authorised personnel accessing routine internal services. Department applications retain their own roles and permissions.
FACELOCK CLOUD · GOVERNMENT BODIESA simpler sign-in.
A simpler sign-in.
A carefully scoped rollout.
Explore face-assisted access for staff portals and everyday administrative tools, with named users, a reviewed integration and clear verification boundaries.
Pilot onboarding subject to your organisation's security and procurement review. No government certification, national identity integration, data-residency guarantee or high-assurance biometric claim is implied.
Practical starting points
Support the staff doing everyday public-service work.
Administrative desks
Use browser privacy locking when staff step away from an individual workstation. Combine it with managed browser policies and operating-system screen locking.
Municipal operations
Pilot the login flow in approved work-order or routine service-management tools. Start with a defined staff group and a documented support and recovery process.
Training & knowledge portals
Give enrolled employees a simpler way back into learning or reference systems where local convenience verification meets the organisation's risk assessment.
Public-sector software teams
Add FaceLock to an application through an explicit integration. Keep account provisioning, authorisation and sensitive action approvals in your own system.
Controlled evaluation groups
Evaluate usability, recovery, device management and operational fit before considering wider deployment. Record acceptance criteria and review results with the responsible team.
Scope matters. This offering is for explicitly enrolled users. It is not public-space face recognition, citizen identification, an attendance-verification guarantee or a replacement for mandated authentication controls.
Sign in with FaceLock
A familiar face. A deliberate sign-in.
- Connect your productRegister the exact callback and add the FaceLock sign-in button to your application.
- Let the user reviewThe extension shows which organisation is requesting access and what identity details will be shared.
- Verify on the deviceThe user completes a fresh face check. Their registered device signs the specific login request.
- Create your sessionYour backend verifies the code and identity token, then applies your own account permissions.
Link an existing account through an authenticated account-linking step. FaceLock does not collect or submit your application's passwords.
Before activation
Bring procurement, security and operations into the same plan.
- Authorised sponsorship: record the body, department, official sponsor and procurement, technical and support contacts.
- Data and assurance review: identify the portal's data sensitivity, deployment requirements, recovery process and actions needing stronger authentication.
- Commercial scope: agree named seats, annual billing and invoice details through your approved process.
- Technical acceptance: register exact callbacks, protect client credentials and verify account linking, removal and failure behaviour.
- Controlled activation: complete the ownership and security review, record payment and assign approved users before enabling access.
Requirements for hosting location, retention, certifications, procurement and service levels must be evaluated and agreed separately. The current pilot does not advertise these as already fulfilled.
Simple annual pricing
One price for every named user.
$5 / user / year
Minimum 100 seats. Minimum annual billing: $500 USD.
An assigned company seat covers FaceLock company sign-in. Users do not need a separate personal Browser subscription for that access. Taxes, where applicable, are specified in the quote.
| Seats | Annual total |
|---|---|
| 100 | $500 |
| 150 | $750 |
| 500 | $2,500 |
| 1,000 | $5,000 |
Named seats are assigned by email. This is not unlimited customer authentication. Seat changes and annual renewal are agreed explicitly; there is no silent overage billing.
Clear boundaries
Know what the verification means.
Webcam face matching with blink and head movement is a convenience check. The cloud verifies a registered device signature; it does not independently inspect a face or attest to hardware-backed biometrics. Use additional controls for privileged actions, financial approvals and high-assurance workflows.
Your face stays local. Face images and templates stay in the extension. FaceLock Cloud stores account, registered device, organisation membership, subscription and short-lived login records. Your product receives a verified email and an ID unique to its integration.
Browser privacy locking covers ordinary web tabs. It cannot protect Chrome settings, prevent extension removal, cover other profiles or replace the operating system's screen lock. Read the cloud privacy details.
Define the pilot before you widen access.
Share your department, intended staff workflow and technical contact. We will discuss the integration, review requirements and named-user scope.