By Incode

Incode On-device Age Estimation

Facial age-range and liveness estimation on the user’s device with a separate integrity check.

The offering

What Incode On-device Age Estimation does

On-device Age Estimation analyses a guided selfie to return an age range and liveness verdict locally. Incode states that raw facial images and biometric templates stay on the device, while a server-side integrity check uses non-PII metadata and session/device context. Optional privacy treatments change how the face appears during capture.

The output is an estimate, not proof of an exact birth date or a verified legal identity. An operator must set thresholds, supported devices and fallback checks appropriate to its approved market. Assess consent and data flows for the whole implementation, including metadata, rather than extending the device-side privacy claim to every system connected to it.

Who should explore it?

Age-assurance teams evaluating a separate estimation step with clearly defined thresholds and document fallback.

  • Estimate whether a player meets an age threshold before selecting further evidence
  • Escalate uncertain or failed age checks to an approved alternative method

Documented capabilities

  • Guided selfie capture
  • Local age-range estimation
  • Device-side liveness verdict
  • Server-side integrity metadata
  • Optional capture privacy treatments
  • Alternative-method rerouting

Reported in the linked public sources. We have not independently tested these capabilities.

Product details

Age-estimation job
Return an estimated age range and liveness verdict, distinct from legal-identity verification.Source
Local face analysis
Guided selfie with age and liveness models running on the user’s device.Source
Output and integrity
Local age/liveness output with a separate server-side check of non-PII session metadata.Source
Evidence boundary
Estimation does not supply an exact verified birth date; accepted methods and fallback are operator-defined.Source

Delivery & commercial details

Delivery & integration
Embed the supported device-side capture/models and configure the integrity and fallback flow. Validate device compatibility, thresholds and result handling.
Pricing
Request age-check usage, device support, metadata processing, implementation and alternative-method charges.

Confirm market availability, rights, service levels and contractual terms for your implementation. API availability alone does not establish a named integration.

Buyer questions, answered

Is the output an exact verified date of birth?

No. The product returns an estimated age range with a liveness verdict. An operator needs an accepted threshold policy and alternative evidence where estimation is insufficient.

Source
What information is processed on a server?

Incode describes a separate integrity check using non-PII metadata, device signals, behaviour and session context. Its stated local processing applies to the facial image and biometric model output path.

Source