EccLogger Privacy Policy
Last updated: 14 October 2026
1. Introduction and scope
This Privacy Policy explains how Michael Shannon, a sole trader ("we," "us") collects, uses, discloses, and protects personal information in connection with EccLogger (our product): the web operations console, the EccLogger mobile application, and the underlying API.
EccLogger is an event incident logging tool for small to mid-sized events. It is not designed for large-scale emergency management. It is used by event coordinators, security supervisors, and field operatives (security, medics, stewards) across Australia and New Zealand. This Policy applies to personal information we collect from event organisers, the organisations they belong to, their staff and field personnel, and, where applicable, members of the public referenced in incident records.
We are bound by the Australian Privacy Principles (APPs) under the Privacy Act 1988 (Cth), as amended, and, for New Zealand operations and users, the Information Privacy Principles (IPPs) under the Privacy Act 2020 (NZ). Where this Policy refers to "applicable privacy law," it means whichever of these regimes applies to the relevant collection, use, or disclosure of personal information.
This Policy does not currently address the requirements of any jurisdiction outside Australia and New Zealand.
2. Who we are
Michael Shannon, a sole trader (ABN 68 770 735 262), is the person responsible for EccLogger and for handling personal information collected through it.
For privacy questions, access and correction requests, or complaints, contact our Privacy Officer:
- Email: webmaster@doteukali.net
3. Information we collect
We collect the following categories of personal information across the web console, mobile app, and API:
| Category | Examples | Collected from |
|---|---|---|
| Account and identity data | Name, email, phone, employer/organisation, role, login credentials | User directly, organisation admin |
| Location data | GPS location of field operatives who have enabled tracking during an active event; only pings inside the configured site boundary are stored (see section 3.1) | Mobile app, device sensors |
| Incident and interaction data | Incident logs, event notes, timestamps, status updates, attachments | Field operatives, ops console users |
| Device and technical data | Device identifiers, app version, OS version, crash/diagnostic logs, IP address | Automatically, via web console and mobile app |
| Organisation and usage data | Org structure, user roles/permissions, report generation activity, audit logs | Ops console, API |
We do not intentionally collect sensitive information (as defined under applicable privacy law, e.g. health or biometric information) beyond what field personnel or medics voluntarily record in incident notes as part of a safety response. Where such information is captured, it is collected only for the purpose of the safety response being documented and is handled with the additional care sensitive information requires under applicable privacy law.
3.1 Location data
Location is the most sensitive data the service handles, so we describe how it works in detail.
- Operative-controlled and event-scoped: Location tracking runs only while an event is active, and only after the field operative enables tracking in the mobile app. The operative can disable tracking at any time. No location data is collected when tracking is disabled or when no event is active.
- Background collection: While tracking is enabled, the app reads the device's location in the background, including when the app is not on screen, in order to check it against the site boundary. Readings inside the boundary are sent to our servers with their timestamp.
- Site-boundary filtering: The site boundary is the area covered by the event's calibrated site maps, plus a margin of 50 metres to allow for GPS error. If an event has no calibrated site map, no location is shared or stored. The check is applied twice. First, the app compares each reading with those coordinates on the device and sends only readings inside the boundary; readings outside the boundary are not sent to us. Second, as a safeguard, our servers repeat the check on every ping received and discard any ping that falls outside the boundary (for example, after a configuration change) without storing it. Only pings inside the boundary are stored.
- What we store: For each ping inside the boundary, we store the operative's identity, the event, the coordinates, and the timestamp.
- Retention: Stored location pings are retained for as long as the organisation's data is held on the service, and are deleted when that data is deleted (see section 8).
- Access: Access to location data in the ops console is controlled by user-specific permissions configured by the organisation. Location data is never shared with other organisations.
- Purpose: We use location data to show authorised users where field operatives are during an event, for safety coordination and resource tracking. We do not use it for advertising and we do not sell it.
- Organisation responsibilities: Organisations are responsible for meeting the obligations that apply to them as employers or principals, including workplace surveillance notice requirements in the jurisdictions where they operate.
4. How we use your information
We use personal information to:
- Provide the core service: incident logging, location tracking of field operatives who have enabled it during an active event, event workspace management, and multi-organisation user administration
- Maintain audit trails required for regulatory compliance and incident accountability
- Communicate with organisations about their account, service updates, and support requests
- Detect, investigate, and prevent misuse of the service and maintain system security
- Comply with our legal obligations, including responding to lawful requests from regulators or law enforcement
We do not use personal information for advertising, and we do not sell personal information.
5. Legal basis and collection notices
We collect personal information only by lawful and fair means, and only where reasonably necessary for the safety and operational purposes described in this Policy, consistent with APP 3 (AU) and IPPs 1–4 (NZ).
Field operatives and other individuals are given a collection notice at the point of onboarding to an organisation's EccLogger instance, or within the mobile app's terms of use, covering: what is collected (including background location), why, who it may be disclosed to, and how to exercise access and correction rights. Organisations are responsible for ensuring their own staff and field personnel receive this notice before use of the service begins.
Where personal information about a third party (for example, a member of the public named in an incident record) is collected other than directly from that individual, we rely on the applicable exceptions under APP 3 and IPP 2 relating to law enforcement, safety, and safety-response contexts, consistent with the service's purpose.
6. Disclosure of information
We disclose personal information to the following categories of recipients, each acting as our service provider under contractual confidentiality and security obligations:
| Recipient | Purpose | Location |
|---|---|---|
| Amazon Web Services (AWS) | Hosting, storage, and infrastructure | ap-southeast-2 (Sydney, Australia) |
| Expo (Expo Application Services) | Delivering push notifications to the mobile app (device push token and notification text) | United States |
| Resend (email delivery) | Sending account and notification emails (recipient address and message content) | Japan (Tokyo) |
| Sumo Logic | Server logging and diagnostics (technical identifiers such as IP addresses and record IDs; logs do not contain names or contact details) | Australia |
| MapTiler | Satellite basemap imagery in the web console's map calibration tool (IP address and map area viewed; no user identifiers are sent) | France |
| New Relic | Application performance monitoring and telemetry (metrics, traces and logs containing technical identifiers such as IP addresses and record IDs; no names or contact details) | United States |
We do not sell personal information to third parties, and we do not disclose it for the recipient's own marketing purposes.
We may also disclose personal information where required or authorised by law, including to police, emergency services, or regulators in connection with an actual or suspected safety incident, or in response to a valid legal process.
Within an organisation, personal information is visible to the users that organisation has authorised, according to the roles and permissions it configures.
7. Data storage, security, and location
Our database and uploaded files are stored and processed in AWS's ap-southeast-2 (Sydney) region. Some service providers listed in section 6 (push notifications, email delivery, application monitoring, and map imagery) process limited personal information outside Australia, in the locations shown there. We take reasonable steps to ensure these providers handle personal information in line with the Australian Privacy Principles and NZ Information Privacy Principles.
We apply technical and organisational measures appropriate to the sensitivity of the data we hold, including:
- Encryption of data in transit and at rest
- Role-based access controls and strict per-organisation data isolation, so one organisation cannot access another's data
- Secure CI/CD practices for deploying changes to the service
No method of transmission or storage is completely secure. If we become aware of a data breach that is likely to result in serious harm, we will notify affected individuals and the relevant regulator (OAIC and/or the NZ Privacy Commissioner, as applicable) in accordance with our notifiable data breach obligations.
8. Data retention
We retain personal information only for as long as necessary for the purposes it was collected, or as required by law. Indicative retention periods, to be finalised per data category:
| Data category | Indicative retention | Basis |
|---|---|---|
| Account/identity data | Life of the account; login and contact details are removed when you delete your account (see section 8.1) | Ongoing service provision |
| GPS location data | For the life of the organisation's data (see section 3.1) | Retained as part of the organisation's event records |
| Incident/interaction logs | End of the event + 7 years | Audit and regulatory record-keeping |
| Device/technical logs | 12 months | Security and diagnostics |
When personal information is no longer required for any purpose for which it may be used or disclosed, we take reasonable steps to destroy it or ensure it is de-identified.
8.1 Deleting your account
You can delete your account at any time, in the mobile app (Profile → Account → Delete account) or on the web (Account → Delete Account). The public page describing this is at /delete-account. If you cannot sign in, contact our Privacy Officer using the details in section 2 and we will delete the account for you.
When you delete your account we permanently delete your login, email address, phone number, alias, passkeys, sessions, push notification devices and notifications.
What we keep. Organisations that use EccLogger rely on it as a record of who recorded what, and need to be able to hold the people who made an entry accountable for it. For that reason, after you delete your account your full name (first and last name only) remains attached to the logs, log updates, assignments, actions and location records you created in your organisations, and to the audit history of those records. The content of those records, including GPS location pings recorded during events (see section 3.1), is retained as part of the organisation's event record. We do not keep your email address or any other contact detail for this purpose. This retention is for the organisation's legitimate operational, safety and record-keeping purposes, and the retained name is shown to the organisation's members as a deleted account.
9. Access, correction, and complaints
Under the APPs and IPPs, you have the right to request access to the personal information we hold about you and to request correction if it is inaccurate, out of date, incomplete, irrelevant, or misleading. To make a request, contact our Privacy Officer using the details in section 2. We will respond within a reasonable period (ordinarily 30 days) and may need to verify your identity first.
If you believe we have breached the APPs, IPPs, or this Policy, you may lodge a complaint with our Privacy Officer. We will investigate and respond in writing.
If you are not satisfied with our response, you may escalate your complaint to:
- Australia: Office of the Australian Information Commissioner (OAIC) — oaic.gov.au
- New Zealand: Office of the Privacy Commissioner — privacy.org.nz
10. Children's data, other users, and changes to this Policy
EccLogger is a workplace safety tool intended for use by adult event staff and field operatives. We do not knowingly collect personal information from children through the service. Where a minor's details appear in an incident record (for example, as a member of the public involved in an incident), that information is handled under the safeguards described in section 7.
This Policy applies to users and organisations in Australia and New Zealand only. If EccLogger expands to other jurisdictions, this Policy will be updated to address the applicable requirements (for example, GDPR) before that expansion.
We may update this Policy from time to time. The "Last updated" date at the top of this Policy indicates when it was last revised. Material changes will be notified to organisations in advance of taking effect.
11. Contact us
Michael Shannon (ABN 68 770 735 262)
Email: webmaster@doteukali.net