Pinga
Pinga · 2M Systems Pty Ltd

Privacy Policy

How Pinga handles personal information when you visit, sign in or receive an alert.

Last updated: 30 September 2026

ABN 20 613 465 900 · [email protected]

1. Who we are and how to contact us

Pinga is operated by 2M Systems Pty Ltd, ABN 20 613 465 900. This policy covers our handling of personal information through Pinga, including information about our website, the Pinga Me Android and iPhone apps, account holders and alert contacts who may not have a Pinga account.

For privacy enquiries, access or correction requests, account closure or complaints, email [email protected].

2. Information we collect

Pinga Me notifications and diagnostics

Pinga Me uses Google Firebase Cloud Messaging to deliver push notifications. On iPhone, notifications also pass through Apple Push Notification service (APNs). This involves app installation identifiers, push registration tokens and notification content, which may include alarm details, welfare alerts and names. We associate the registered device with your Pinga account so alerts reach the right person. These identifiers are used for service delivery, not advertising profiles. Notification previews may appear on your lock screen; you can control previews and notification permissions in your phone settings.

The apps send operational diagnostics to Pinga to help us identify delivery, connection and permission problems. These include event names, timestamps, app and operating-system versions, device registration and permission status, and notification handling results. Android may also send crash error details. The iPhone app sends operational diagnostic events rather than recording your screen or conversations. Diagnostic records are linked to your registered device and accessible for authorised support and troubleshooting. Recent device diagnostic logs are limited to a rolling 48-hour window and a bounded number of entries; separate alarm delivery and response records follow the retention rules below.

Optional Team location

If you enable Team location in Pinga Me and grant location access, we collect your phone’s coordinates, accuracy and timestamps during your chosen sharing hours, including while the app is in the background. The initial sharing schedule is all day, every day, with no automatic one-hour cutoff. Sharing requires your agreement and phone permissions. If you choose a work-hours schedule and agree to callout sharing, accepting a fault outside those hours starts additional sharing until you confirm that you have left site. A bar in Pinga Me lets you end that extra sharing and return to your normal schedule. Pauses and sharing off still take priority, except for the separately disclosed working-alone session behaviour below. Existing off, pause and custom schedule choices are preserved on upgrade. Your organisation’s administrators can view your latest shared position and recorded journeys. You can view your own records in the app. Organisation administrators may also grant team members access to your shared positions and recorded journey history within their assigned sites. Team app access is unavailable while your sharing is paused or off; your sharing schedules still apply.

You control sharing, temporary or indefinite pauses, weekly hours and private date ranges. Paused and excluded periods stop location collection, except while you have explicitly started a working-alone session as described below. Turning sharing off does not stop alarm notifications or calls. Previously shared positions remain available as history until they expire; they are labelled with their recorded time. Location records are kept for 30 days, with expired records removed automatically. Permitted points may be temporarily stored on your phone when offline.

With your phone’s motion or physical activity permission, Pinga Me detects whether you are still, moving or travelling in a vehicle. This helps reduce battery use, avoid false journeys caused by GPS drift and show movement on team maps. Movement classifications and driving indicators may be uploaded with shared location points, together with speed, accuracy and timestamps, and viewed by people authorised to view your location. They follow the same location-sharing controls and 30-day location retention. You can revoke motion access in your phone settings; location tracking can still operate but movement detection and battery optimisation may be less effective. Pinga Me does not read Apple Health or Health Connect records.

Map backgrounds are supplied by OpenStreetMap. Viewing the map sends your browser’s IP address and requests for the displayed map area to its tile service; we do not send team names or journey records to that service. Location records are not sent to our AI interpretation provider. System support access is restricted to authorised support work.

Optional working-alone check-ins

If you start working-alone check-ins, we record your session times, check-in responses, task notes, linked alarms, nominated escalation contacts and follow-up history. These records are used to request check-ins and notify your chosen people if you request help or miss a response. Authorised organisation users can view the resulting welfare incidents.

Starting a new working-alone session requires background location permission and enabled location sharing. Your location is shared throughout the session, including outside normal hours and during scheduled pauses or private date ranges. Finishing the session restores your usual sharing schedule. Turning sharing off or revoking permission stops collection but does not cancel check-ins; your organisation may see that location updates have stopped. Your last shared location, accuracy and recorded time may be included in welfare notifications to your escalation contacts. Copies included in notifications and welfare incident history follow our alarm-record retention described below, rather than the 30-day map-point retention period.

3. Where it comes from

We collect information from you, your identity provider, your organisation’s administrators, connected equipment and systems, and notification providers. An organisation can add you as an alert contact without creating an account for you. Contact that organisation or us if you believe your details have been added incorrectly.

If required contact or authentication details are not supplied, we may be unable to provide account access or deliver the relevant notifications. Do not send unnecessary sensitive information, credentials or secrets in alarm messages.

4. How we use information

We use information to authenticate users, administer organisations, match and interpret alarms, run escalation steps, deliver alerts and recovery messages, record responses, troubleshoot issues, protect the service, respond to requests and meet applicable legal obligations. Information is not collected by Pinga for advertising profiles.

Organisation administrators and authorised users can see the records available to their organisation. Alert recipients receive the information included in their notification and the associated response page. Only share alarm information with contacts authorised to receive it.

5. Service providers and AI

We disclose information as needed to providers supporting the service:

We may also disclose information to professional advisers or authorities where reasonably necessary for legal obligations, dispute handling or protection against misuse. Providers may maintain their own operational, security and account records under their terms and privacy notices.

6. Storage and overseas processing

Pinga’s application and database are hosted on our own servers in Australia, reached through Cloudflare. The inbound email storage and Lambda forwarding setup uses AWS’s Sydney region. Some processing occurs overseas: the Twilio SMS integration uses its US1 region, and other providers operate international infrastructure. Australia and the United States are relevant processing locations; other locations depend on the provider, network routing and account configuration.

Using an Australian domain or Australian phone number does not mean all information stays in Australia. Contact us for current information about provider locations if your organisation has data residency requirements.

7. Security and cookies

Pinga uses HTTPS, access controls, organisation-scoped data access, expiring response links and authenticated provider endpoints to protect information. No service can guarantee absolute security. Protect your account and notification links, and report suspected unauthorised access to us.

Pinga uses essential session and sign-in cookies to maintain login and protect authentication. Infrastructure and identity providers may use cookies for their own security or sign-in functions. The public website uses a first-party cookie, pinga_visit, to count unique browsers each day in Adelaide time. It expires at the end of the day. We retain aggregate daily visitor and page-view counts and, for each counted browser, its first recorded IP address, estimated country supplied by Cloudflare, browser name and major version inferred from its user-agent information, visit time, page-load count, referring website hostname and campaign tags supplied in the arrival URL. Search terms are recorded only when supplied by a recognised search engine’s referral URL or in a campaign tag; we do not receive most Google search terms. We do not store full referring URLs. Only the system owner can view these details. Visitor details are kept for 30 calendar days; separate deduplication entries are kept for up to two days. Expired entries are removed when the website next receives a counted visit. Aggregate totals are retained without an automatic expiry. We also record which public page paths each browser visits, the view count for each path and its first and last view times, with the same 30-day retention. Page records exclude URL query strings and fragments, and do not include private app pages or webhooks. Blocking or clearing the cookie can affect counts. We do not use advertising trackers. Blocking essential cookies can prevent sign-in.

8. Retention and deletion

You can delete your personal app identity, device connections and stored journeys in Pinga Me under My Phone → Delete my Pinga Me account. Linked contact details and attributable personal report content are removed; shared operational records retain a Deleted contact label and other people’s responses. Separate web-portal accounts remain unchanged. For details or a wider request to delete your personal Pinga Me account and associated data, request account deletion here. You do not need to be an organisation administrator.

We keep information for operating the service, maintaining alarm history, handling support and disputes, and meeting applicable legal requirements. Alarm history and original inbound email archives do not currently have a universal automatic deletion period. Retention depends on the record, your organisation’s needs, configured storage policies and applicable obligations.

Authorised administrators can request closure or deletion by contacting us. We will confirm the scope, verify authority and explain any information that must be retained and the expected handling timeframe. Removing a contact or monitor does not necessarily erase historical alarm records. Copies may remain in backups until they are replaced or expire, and notifications already delivered may remain with recipients or providers.

9. Access and correction

You can ask what personal information we hold about you and request access or correction using the email above. Provide enough information to identify the relevant account, organisation or alert. We may verify identity and authority before responding and will explain any lawful reason for refusing a request. Where information was supplied by an organisation, we may need to work with its authorised administrator while respecting your rights.

10. Complaints and changes

For a privacy complaint, email us with the issue and your preferred outcome. We aim to respond within 30 days; if more time is needed, we will explain why. If you are not satisfied, you can contact the Office of the Australian Information Commissioner for information about available complaint pathways and whether it can consider your complaint.

We may update this policy as the service or our practices change. The date above identifies this version. We will provide notice of material changes where appropriate.