Know exactly who's on site. And prove it.

Face matching runs entirely on the iPad or iPhone at the door. Only a numeric template (not a photo) is stored and only on devices assigned to the sites a person can access. Templates are removed from a device as soon as a person is unassigned or disabled.

Enrolment templates are held in our Australian-region database so they can be synced to the terminals at your sites, encrypted at rest and in transit. Images are never uploaded or stored. Recognition happens on-device.

Every enrolment starts with a consent screen the person must accept before the camera opens. The consent version and timestamp are recorded against their profile and administrators can export or revoke it at any time.

Yes. Anyone can request deletion from the app or dashboard; administrators can also remove a person, which deletes their templates from every device on the next sync. Visitor records auto-purge on the retention schedule each site sets.

Yes and since 3 November 2025 it is specifically regulated. The Privacy Commissioner's Biometric Processing Privacy Code 2025 applies to any organisation processing biometric information through a technological system. Organisations already using biometrics before the Code had until 3 August 2026 to comply and that transition period has now ended. The Code requires a documented proportionality assessment and detailed notification, including whether non-biometric alternatives are available. iENTR is built to support that: on-device matching, configurable retention and a genuine non-biometric alternative on every site. Compliance rests with your organisation and iENTR ships the assessment and notification templates to help you evidence it.

In practice, yes and it has to be real consent. In February 2024 the UK Information Commissioner ordered Serco Leisure to stop using facial recognition for staff attendance across 38 sites, partly because enrolment was presented as a requirement in order to get paid, so employees had no genuine choice. iENTR is designed the other way round. Every site can run card, PIN or QR entry with identical functionality, so an employee who declines to enrol a face is never disadvantaged.

They use a card, a PIN or a QR code and everything else works exactly the same. This is deliberate. A biometric system with no real alternative is a system a regulator can order you to switch off.

A code of practice issued by New Zealand's Privacy Commissioner on 6 August 2025, in force from 3 November 2025, which replaces the ordinary information privacy principles for biometric processing. Its central requirement is a proportionality assessment: a documented case that the benefit of using biometrics clearly outweighs the privacy risk, supported by objective evidence, with express consideration of cultural impacts and effects on Māori. It also restricts using biometrics to infer health, emotion or protected characteristics. iENTR does none of those things by design.

Any iPad or iPhone that runs a current iOS. Mount it at the entrance, optionally connect a door relay for unlocking and you are done. For doorways where a tablet cannot be mounted, a terminal can use an external network camera instead.

Most sites are live in under 30 minutes: create the site, pair the terminal with a one-time code, invite your team and enrol. No installers, no cabling.

Yes. Each terminal holds its site roster and templates locally, so recognition and sign-in continue without a network. Events queue on the device and sync automatically when connectivity returns.

Yes. Each terminal is configured independently as entry only, exit only or both, with its own sign-in mode, visitor module, relay and questionnaire settings.

Enrolment captures multiple angles in a guided ring capture and matching uses a strict acceptance threshold with a second-best margin, so look-alikes are rejected rather than guessed. Anyone not recognised can always fall back to name lookup, so recognition is never a dead end.

Yes. Visitors sign in at the terminal with their details and consent. Depending on the terminal setting, they are approved automatically or the host is notified and the kiosk waits for approval. Visitor records purge on your retention schedule.

Yes, for people already enrolled at your site, through Restricted access. An administrator can mark an enrolled person as Blocked, so they are refused at the terminal and an incident is raised, or as Flagged, so they are admitted but staff are alerted immediately. This is an access decision about a known, enrolled person, like cancelling a keycard. iENTR never scans strangers or passers-by against any list.

Yes. The Who Is Here view shows everyone currently signed in, with their company, phone, the terminal they used and how long they have been on site. It is filterable and sortable and essential for emergency roll-calls.

Yes. Entries and exits become daily timesheets per person and per company, with date presets (today, this week, last week) or custom ranges plus reports for average entry/exit times and peak hours.

Seven days of the full product with your own data. Choose a plan and add a card to activate it. You won't be charged until the 8th day and you can cancel at any time during the trial without being charged.

A monthly subscription covers your first terminal; additional terminals are a flat monthly fee each and scans are charged per recorded entry or exit. You only pay for the traffic you actually have.

Yes. Add or remove terminals and sites whenever you like; billing adjusts on the next cycle.

iENTR is multi-site by design: one dashboard, per-site managers and realtime sync across every entrance. Contact us for volume pricing and a dedicated onboarding plan.

Role-based access (business admin, site manager, standard, visitor registry) and two-factor authentication are included today. SSO and directory sync are available on enterprise plans. Talk to us.

Yes. Events, people, sites and visitors are all available through our API and door relays integrate over a simple authenticated HTTP pulse. Ask us for the integration guide.