AreaFACE: 1:1 comparison
The person in front of the device is compared with one reference selected for that authentication workflow.
1:1 FACIAL AUTHENTICATION IN THE FIELD
The right identity, in front of the right device.
AreaFACE guides capture, analyzes local liveness signals and prepares individual 1:1 comparison in authorized workflows.
One person. One selected reference. No crowd search.
AREAFACE1:1
- 01Guided captureThe device helps the person position their face within the expected frame.
- 02Local analysisLiveness signals are assessed according to sensor and configuration.
- 03Selected referenceThe workflow provides one authorized reference for comparison.
- 04Workflow responseThe result follows the threshold, exceptions and review defined by the project.
A BOUNDARY THAT MUST REMAIN CLEAR
Comparing one person is not the same as searching a crowd.
The two problems require different architectures, purposes and controls. AreaFACE addresses the first.
1:N facial search: a separate flow
One reference is compared with multiple images. Within the Areatec ecosystem, this capability belongs to a separate solution and requires its own assessment.
This page does not attribute crowd facial search to AreaFACE.
THE FLOW
From capture guidance to the response defined by the project.
Comparison is meaningful only when capture, reference and decision rules belong to the same authorized process.
Guide capture
The interface provides positioning and framing guidance while the person is in front of the device.
Analyze liveness
Multiple signals are assessed locally according to sensor, environment and configuration.
Select the reference
The system receives the single reference linked to the expected identity in that flow.
Compare 1:1
Capture and reference are compared using the threshold defined for the use case.
Apply the rule
The response can authorize, request another capture, invoke another factor or go to review.
ON THE FIELD DEVICE
The interface needs to help before it compares.
Areatec has evaluated Android SDK integration and use on field devices. The design starts with capture quality and a safe path when the scenario is inconclusive.
Real time positioning
The person receives guidance on distance, framing and stability suitable for capture.
Local liveness signals
Analysis considers multiple signals available on the device within the tested coverage.
Android integration
The capability can be incorporated into a field application workflow without creating a separate journey.
Alternative path
Another capture, another factor or review prevents a poor image from becoming a final decision.
Production configuration depends on the hardware, sensor, workflow, thresholds and acceptance criteria defined for each project.
BIOMETRICS REQUIRE A PURPOSE
Technology comes after the project answers the difficult questions.
Facial biometrics is sensitive personal data. Deployment needs to explain why comparison is necessary, who may use it and what happens to each record.
Purpose and legal basis
Use must be delimited before capture and cannot expand merely for operational convenience.
Necessity and alternative
The project assesses whether biometrics is proportionate and when another factor needs to be available.
Access and security
People, devices, integrations and records receive permissions suited to their function.
Retention and disposal
Time limits and deletion routines need to match the stated purpose.
Human review
Ambiguous cases follow a documented rule without turning a technical threshold into an irreversible automated decision.
ACCEPTANCE IN THE REAL SETTING
One number cannot describe a biometric system.
Acceptance must measure the configuration that will actually be used, including equipment, environment, population, complete flow and exception handling.
- Capture
- Lighting, angle, distance, motion, occlusion and camera quality.
- Comparison
- False acceptance and false rejection rates at the selected threshold.
- Liveness
- Presentation types covered by the sensor and project tests.
- Latency
- End to end time without removing security steps to improve the result.
- Equity
- Representative samples and relevant differences between evaluated groups.
- Exceptions
- Another capture, an authentication alternative and review by an authorized person.
Areatec does not publish a universal accuracy percentage, fixed latency or claim that every fraud risk can be eliminated.
WITHIN THE AREATEC ECOSYSTEM
Identity, enforcement and privacy keep distinct roles.
Separation prevents one capability from being presented as the answer to every problem involving images of people.
Electronic ticketing
It can incorporate individual authentication at the start of an officer workflow, subject to configuration and acceptance.
Olho Vivo PatrolIt runs mobile operations and has a separate authorized facial search flow without turning that search into an AreaFACE function.
Blur InteligenteIt protects faces that do not need to remain identifiable in images intended for authorized use.
FREQUENTLY ASKED QUESTIONS
What needs to be clear before using 1:1 facial authentication.
The answers below separate technical capability, project configuration and controller responsibility.
What is 1:1 facial verification?
It compares the person in front of the device with one reference previously selected for that workflow. The result indicates whether the comparison meets the configured threshold and should not, by itself, be treated as a decision about identity.
Does AreaFACE perform 1:N facial search in public spaces?
That is not the purpose described on this page. AreaFACE covers individual 1:1 comparison against one selected reference. The 1:N search used in another Olho Vivo workflow has its own purpose, rules, controls and legal assessment.
How does liveness analysis take part in the flow?
Before comparison, the device can analyze multiple liveness signals to look for signs of an improper presentation. Coverage depends on the sensor, configuration, environment and attack types included in acceptance testing.
Is all AreaFACE processing local?
Liveness signals can be analyzed on the device. The complete flow, the data that leaves the device and any integrations depend on the architecture approved for each project. Areatec therefore makes no universal claim that all processing is local.
Does AreaFACE guarantee LGPD compliance?
No technology guarantees compliance on its own. AreaFACE provides resources for an LGPD compatible deployment, while the controller must define purpose, legal basis, necessity, transparency, access, security, retention, disposal and data subject rights for the specific case.
How should AreaFACE accuracy and latency be measured?
Acceptance testing should use the equipment, lighting, angles, population and workload planned for the operation. The report needs to state false acceptance and false rejection rates, end to end latency, sample, threshold and liveness scenarios. An isolated percentage does not describe actual performance.
Can AreaFACE be integrated with Android field devices?
Areatec has evaluated Android SDK integration and use on field devices. A production configuration still needs project acceptance using the hardware, sensor, authentication flow and decision criteria planned for the operation.
What happens when the comparison is inconclusive?
The project should define a safe path such as another capture, a different authentication factor or review by an authorized person. An inconclusive response should not automatically become a finding of fraud, a permanent denial or confirmation of identity.
TECHNICAL ASSESSMENT
Do you need a 1:1 flow suited to field work?
The Areatec team can assess purpose, device, sensor, authentication alternative, integrations and acceptance criteria before proposing a configuration.