Security & data handling
The short version
- Images are analysed to produce a result and then discarded. We do not store face images and we do not build face databases.
- Processing happens in AWS's Sydney region, with one disclosed exception for liveness (below).
- Every request travels over TLS, to the API and on the website.
- Each client runs in a dedicated environment with its own credentials.
- We operate under the Australian Privacy Act and do not sell personal information.
What happens to an image you send
A check is a single round trip. Your request arrives over TLS, the image is analysed by the relevant AWS Rekognition operation, the result goes back to you, and the image is discarded. What we keep is a transaction record about the check, not the image: the request type and status, a timestamp, the calling IP address, and result metadata such as a confidence score. Those records exist for billing, support and abuse prevention.
Where processing happens
The platform runs in AWS's Sydney region (ap-southeast-2). The one exception is the Face Liveness check, which AWS does not offer in Sydney: liveness sessions are processed in an overseas AWS region (Japan). This is disclosed in the Privacy Policy, and liveness video is treated the same way as everything else: processed for the result, not retained by us.
Isolation and access
- Dedicated per-client environments. Each client gets their own API endpoint, their own credentials and their own transaction records. There is no shared multi-tenant data store for client traffic.
- Authentication. Your API is provisioned with an API key or OAuth2 client-credentials, chosen at setup. Credentials can be rotated.
- Least privilege. The platform is serverless; each function runs with only the permissions it needs, secrets are kept in encrypted parameter storage, and stored records are encrypted at rest with AWS-managed encryption.
- Admin access. Operational dashboards sit behind their own authentication, separate from customer credentials.
The website and demo
The website is a static site served over HTTPS. It has no user accounts and sets no tracking cookies; analytics use Cloudflare's cookieless Web Analytics. The contact form is protected by reCAPTCHA. Demo images follow the same rule as the API: analysed, then discarded.
Retention and breaches
Face images and video: not retained, full stop. Operational records (enquiries, billing, server logs) are kept for the periods set out in the Privacy Policy and then destroyed or de-identified; server logs age out automatically. If a data breach involving personal information is likely to result in serious harm, we notify affected people and the OAIC under the Notifiable Data Breaches scheme.
What we don't claim
Honesty cuts both ways, so to be explicit: eaglecheck is not an accredited digital identity provider, does not verify the authenticity of identity documents, and does not hold formal certifications such as ISO 27001. If your procurement process needs specifics beyond this page, ask us directly.
Questions
Security or privacy questions: legal@eaglecheck.com.au. We typically reply within one business day.