SafetyBeam Privacy Policy
SafetyBeam Legal

Privacy Policy

SafetyBeam keeps your safety records on the device that created them. There is no account to sign in to, no server holding your data, and nothing sent anywhere unless you choose to send it.

Effective26 Aug 2026
App version3.3.0
Applies toiOS & Android
In short

Your records stay on your device. Projects, hazards, incidents, inspections, toolbox talks and their photos are written to a database inside the app on your phone or tablet. We do not run a server that receives them, and we cannot see them.

Nothing is sent until you send it. Data leaves the device only when you email a report, use the share sheet, or export a backup — and it goes to the destination you pick.

No accounts, no tracking, no ads. SafetyBeam has no sign-up, no analytics or telemetry, no advertising identifier, and no third-party tracking of any kind.

01About this policy

SafetyBeam is an offline-first construction safety management app for iOS and Android. This policy explains what information the app holds, where it lives, and what we do and do not do with it. “We” and “us” mean the publisher of SafetyBeam.

It applies to the SafetyBeam mobile app. It does not apply to anything your own organisation does with the reports you export from it, or to other apps and services you send those reports to.

We handle personal information in line with the Privacy Act 1988 (Cth) and the Australian Privacy Principles. By using SafetyBeam you agree to this policy.

02Who is responsible for the information in SafetyBeam

SafetyBeam is a tool you run on your own device. The records you create in it — including the names, contact details, signatures and injury details of workers — are held by your organisation, not by us. Your employer or principal contractor is the entity responsible for how that information is collected, used, retained and disclosed.

We never receive that information, so we cannot search it, correct it, or produce it on request.

If you are a worker whose details appear in SafetyBeam and you want to see, correct or query them, contact the employer or principal contractor operating the app on your site. They hold the records.

03What SafetyBeam stores

Everything below is created by you as you use the app, and is stored only on your device.

Record type What it can contain
Projects and areas Project name and code, site address, client, project and safety manager names, contract number and value, dates, notes
Companies and people Contractor, subcontractor and supplier names, contact name, email address, phone number, ABN
Hazards Description, location on site, likelihood and severity ratings, people involved, actions taken, evidence photos, who it is assigned to, due and close dates
Incidents Description and type, severity, date and time, location, injured parties, witnesses, a contact number, evidence photos, root cause and corrective actions
Breaches and actions Breach type and severity, description, issue and due dates, assigned actions and their status
Toolbox talks Topic, presenter, date, duration, notes, action plans, and for each attendee: name, company, sign-on time and a drawn signature image
Inspections Checklists and templates, results and comments, defects raised, photos, inspector name, and recurring inspection schedules
Attachments Photos and files you attach, held in the app’s private storage with an integrity hash
Audit log An append-only, hash-chained record of what changed, when, and on which record — so a register cannot be quietly altered after the fact
App settings Your preferences, and — if you choose to set one up — the host, port and username of your own outgoing mail server

Sensitive information

Incident records can contain health information — injuries, treatment and the names of injured people — which is sensitive information under the Privacy Act. SafetyBeam gives you the fields because WHS record-keeping requires them. Your organisation is responsible for collecting that information lawfully, keeping it to what is necessary, and controlling who can see the device and the reports you export.

Information we hold about you

The only personal information we ever receive is what you send us directly — for example, your name and email address if you email us for support. We use it to answer you and for nothing else.

04Where it is stored

  • Records go into a SQLite database inside the app’s private storage area, which the operating system isolates from other apps.
  • Photos and attachments you add are copied into that same private storage, so the app keeps working offline and the record survives changes to your camera roll.
  • Your outgoing mail server password, if you configure one, is stored in the iOS Keychain or the Android Keystore — the operating system’s protected credential store — not in the database.
  • Nothing is written to a cloud service by the app. There is no sync, no backup service of ours, and no account.

If your device has iCloud Backup or Google Backup turned on, your device manufacturer’s backup may include app data. That is a setting on your device, controlled by you and governed by Apple’s or Google’s privacy policy.

05When information leaves your device

Only when you ask it to. There are four ways that happens, and you choose the destination every time:

  • Emailing a report. SafetyBeam builds the PDF or ZIP and hands it to your device’s mail app with the recipients you entered. The email then travels through your own mail provider, under their terms.
  • The share sheet. You pick where the file goes — AirDrop, Files, Drive, Teams, a messaging app. Once it leaves, that service’s privacy policy applies.
  • Exporting a backup. The app writes a ZIP containing your database and images to the location you select.
  • Your own mail server. If you configure outgoing mail server (SMTP) details in Settings, mail is sent using those credentials through the server you nominated.

Exports and backups are not encrypted or password-protected, and can contain worker names, contact details, signatures and injury details. Send them only to people entitled to see them, and store them somewhere your organisation controls.

06Device permissions

SafetyBeam asks for a permission only at the moment it needs one, and only for the task you started:

  • Camera — when you tap to photograph a hazard, incident or inspection defect.
  • Photo library — when you choose an existing photo to attach.
  • Files — when you import a backup or attach a document.

Decline any of these and the rest of the app keeps working; you simply cannot attach photos or files that way.

SafetyBeam does not request location services, contacts, microphone, calendar, health data, push notifications, or an advertising identifier. The “Location” fields on projects, hazards and incidents are free text you type — the app never reads your device’s GPS.

07What we do not do

  • No user accounts, sign-in or password held by us
  • No analytics, telemetry, usage tracking or session recording
  • No advertising, ad networks or advertising identifiers
  • No tracking of you across other apps or websites
  • No selling, renting or sharing of your information — there is nothing for us to sell
  • No cloud sync, and no remote access to your device or its records
  • No automated decision-making or profiling
  • No use of your safety records to train machine learning models

This is why SafetyBeam is declared as “Data Not Collected” on the Apple App Store and reports no data collection or sharing on Google Play.

08Third-party services

SafetyBeam works fully offline. Two connections exist outside your control, and neither carries your safety records:

  • Expo Application Services (EAS Update). On launch, the app checks for an app update. That request necessarily tells Expo your IP address, platform and app version — the ordinary technical details of any download. No project, hazard, incident or worker data is ever included. See the Expo privacy policy.
  • Apple App Store and Google Play. They handle distribution and installation, and if you have opted in at the operating-system level they may send Apple or Google crash and usage statistics. Those go to them, not to us, under their own privacy policies.

Beyond those, the only third parties involved are the ones you choose: your mail provider, your outgoing mail server, and whatever destination you share an export to.

09How long information is kept

For as long as you keep it. Because the data is yours and local, retention is entirely in your hands:

  • Delete an individual record in the app.
  • Use Settings → Clear all data to erase every project, hazard, incident, inspection and toolbox talk on the device.
  • Uninstall the app — iOS and Android remove the database and attached files with it.

Clearing data and uninstalling cannot be undone, and we hold no copy. WHS laws in your state or territory set minimum retention periods for incident and training records — check your obligations and export a backup before you erase anything.

10Security

What the app does:

  • Stores records in the app’s private, operating-system–sandboxed storage, out of reach of other apps.
  • Keeps mail server credentials in the iOS Keychain or Android Keystore rather than the database.
  • Maintains a hash-chained audit log, so tampering with a register after the fact is detectable.
  • Records an integrity hash for every attachment.
  • Holds no data on a server of ours — there is no remote system to breach.

What you control, and what matters most:

  • Set a passcode or biometric lock on the device. Device-level encryption depends on it, and anyone holding an unlocked device can open the app.
  • Keep the operating system up to date.
  • Treat exported PDFs and backup ZIPs as confidential records.
  • Avoid installing SafetyBeam on jailbroken or rooted devices, where sandboxing can no longer be relied on.

No app or device can be made completely secure, and we cannot guarantee the security of information held on a device we do not control.

11Your rights and choices

Because the data sits on your device, the app itself is how you exercise most privacy rights:

  • Access — open any record in the app, or export a report or full backup.
  • Correction — edit any record; the audit log notes the change.
  • Erasure — delete a record, clear all data, or uninstall.
  • Portability — export to PDF or ZIP and take it wherever you like.

Requests about worker information held in a site’s copy of SafetyBeam go to the organisation running it — see section 2. For the limited information we hold (support correspondence you sent us), email us and we will respond within 30 days, as the Australian Privacy Principles require.

12Children

SafetyBeam is a workplace tool for construction professionals. It is not directed at children, and we do not knowingly collect information from anyone under 16. Where a young worker or apprentice appears in a site record, their information is handled by the organisation operating the app under the same obligations as any other worker’s.

13Using SafetyBeam outside Australia

The app is built for Australian WHS practice, but it runs anywhere and stores data locally wherever the device is. We do not transfer your records across borders, because we never receive them.

If you are in the UK or the European Economic Area, the organisation operating SafetyBeam is the controller of the personal data entered into it, and we are not a processor of that data — it never reaches us. We will honour access, correction and erasure requests for the limited information we do hold.

14Changes to this policy

We update this policy when the app changes what it does with information. The effective date and app version at the top of the page always show the current revision, and we call out material changes in the release notes. Continuing to use SafetyBeam after an update means you accept the revised policy.

SafetyBeam — Privacy Policy Effective 26 August 2026 · v3.3.0