This policy explains how FaceGate handles information in two different contexts: this website, and the FaceGate mobile app. The website is a landing page used to explain the product and receive enquiries. The mobile app is an on-device tool used by authorised organisations to screen photos against locally stored person profiles and publication consent categories.
Who we are
FaceGate is operated by Matthew Haskins, ABN 86 371 005 483, based in Western Australia. For privacy enquiries about this website or FaceGate as a product, email matthew.haskins.mh@gmail.com.
Who this policy is written for
FaceGate is designed for business, school, institutional, and organisational use. It is not intended to be a consumer social app, public surveillance system, or public facial identification service. In the app context, the operating organisation controls the device, the people profiles, the enrolment images, the consent category assigned to each person, the scanned photos, and the publication decision.
If your image or biometric template is held inside a FaceGate app operated by a school, business, or other organisation, that organisation is the first point of contact for access, correction, deletion, consent withdrawal, and publication questions, because FaceGate does not receive a copy of that local app data.
What this website collects
- Contact form submissions. If you submit an enquiry, the form may ask for details such as your name, email address, organisation, role, sector, organisation size, region, message, and how you heard about FaceGate. The submission is sent to Matthew by email and is used to respond to your enquiry.
- Technical request information. Like most websites, the hosting provider and website infrastructure may process basic request metadata such as IP address, timestamp, requested path, browser information, and error logs for delivery, security, troubleshooting, and abuse prevention.
- Local preferences. The site may store a functional preference in your browser, such as light or dark theme selection. This is not used for advertising or profiling.
What this website does not do
- It does not create user accounts.
- It does not process payments.
- It does not add contact-form submissions to a mailing list.
- It does not sell enquiry information.
- It does not use contact-form information for behavioural advertising.
How website enquiries are used
Contact-form information is used to read, assess, and respond to your enquiry. If your enquiry leads to a meeting, pilot, or commercial discussion, the information may also be used in that direct correspondence. It is not shared with marketing partners and is not transferred to a mailing list.
How long website enquiry information is kept
Enquiry emails may be retained in Matthew’s email records indefinitely unless they are deleted in the ordinary course of mailbox management or you ask for deletion. If you want a website enquiry deleted, email matthew.haskins.mh@gmail.com with enough detail to identify the enquiry.
What the FaceGate mobile app stores locally
The FaceGate mobile app may store person profiles, names, include/exclude consent categories, enrolment images, face crops, biometric templates, scanned images, detected face records, matching scores, classification results, manual review feedback, emoji overlays, app settings, export files, and audit logs. These records are created and controlled by the operating organisation on its own device.
FaceGate treats biometric templates and related facial information as sensitive information. The app is designed so that face detection, face matching, classification, review, audit logging, deletion, and export functions run locally on the device. FaceGate does not upload enrolment images, face crops, biometric templates, scanned photos, classification results, or audit logs to a FaceGate server.
Mobile app consent and lawful authority
The operating organisation is responsible for ensuring it has the required consent or other lawful authority to collect, store, and use any image, biometric template, person profile, consent category, or scanned photo entered into the app. The organisation is also responsible for ensuring that FaceGate is appropriate for its own publication workflow, privacy obligations, child-safety obligations, device-management rules, and recordkeeping requirements.
For schools and similar institutions, FaceGate is intended to support publication governance. For example, a school may already be permitted to hold student images internally on secure school-owned devices, while some students are excluded from external promotional or publicity materials. FaceGate helps the school apply those internal publication settings when screening later photos. If an organisation is not permitted to retain the relevant images or biometric templates on its own device, it should not use FaceGate for those people or images.
On-device processing and third-party components
FaceGate uses on-device mobile technology to perform face detection and face matching. Some platform or software components, including Google ML Kit, may perform non-sensitive diagnostics, service, or update-related communications. FaceGate is not designed to send sensitive app data such as enrolment images, biometric templates, scanned photos, classification results, or audit logs through those communications.
For more detail about the product architecture, see the Privacy & Trust page.
Deletion, export, and local controls
The FaceGate mobile app includes local controls for deleting biometric data, deleting individual people, deleting images, deleting audit logs, and exporting app data for backup or migration. Because the app data is stored locally on the operating organisation’s device, those controls are operated by the organisation, not by a FaceGate server.
Publication decisions
FaceGate classifications are decision-support outputs. The operating organisation remains responsible for reviewing results and deciding whether a photo may be published, withheld, edited, obscured, or escalated for further review. A Safe, Unsafe, or Review Required label should not be treated as a complete legal or compliance determination.
Data breaches and lost devices
Because FaceGate does not receive a copy of the local app database, the operating organisation is responsible for managing its own devices, backups, exports, access controls, staff permissions, incident response, and any notification obligations that may apply if a device, export, image, or local database is lost, accessed without authority, or disclosed without authority.
Cookies and tracking
This website does not set tracking cookies for advertising. Functional browser storage may be used for basic site preferences, such as remembering a theme preference.
Access, correction, and deletion requests
For website enquiry information held by Matthew, email matthew.haskins.mh@gmail.com to request access, correction, or deletion. For information stored inside a FaceGate app operated by a school, business, or other organisation, contact that organisation directly because it controls the local device and local app database.
Complaints
If you have a privacy concern about FaceGate or this website, email matthew.haskins.mh@gmail.com. If you are not satisfied with the response and the matter falls within Australian privacy law, you may contact the Office of the Australian Information Commissioner at oaic.gov.au.
Changes to this policy
This policy may be updated from time to time. Material changes will be reflected in the “Last updated” date at the top of this page.