Privacy Policy

Last updated: 15 October 2026 · Developer: Expedite Electrical (REC 25724) · Contact: support@safetycheckpro.com.au

This Privacy Policy is incorporated into, and forms part of, our Terms of Service. We handle personal information in accordance with the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs).

Safety Check Pro (“the app”) is a tool for tradespeople and inspectors to record inspections, checklists and reports, using the built-in report types or forms you build yourself, and to produce PDF reports.

The short version: the app works fully offline with no account. If you sign in, your reports sync to your own private cloud space so your devices match. We don't use third-party analytics, advertising or tracking, and we never sell or share your data. The app does send technical crash and error reports so faults can be found and fixed.

Using the app without an account

No account is needed. Everything you enter (addresses, customer details, inspection answers, readings, notes, photos, signatures, the forms you build, and generated PDFs) stays on your device. The only things sent to us before you sign in are your device identifier, used to run the free trial fairly, and technical crash and error reports (both covered below).

On Android, the app does not take part in the phone's Google backup. On an iPhone, reports and photos on the phone may be included in the phone's own iCloud backup.

What we collect if you sign in (optional sync)

Signing in enables sync across your devices. To provide this, the following is stored in our cloud database (Google Firebase, operated under Google's privacy and security terms):

This data is stored in your own private space, protected by security rules so only your signed-in account can access it. We do not read, mine or sell it.

Overseas storage and processing

Some of the providers we use to run Safety Check Pro, including Google Firebase (cloud database, authentication, hosting and crash reporting) and Apple's mapping service, store or process data on servers located outside Australia, including in the United States and other countries where those providers operate data centres. Before we disclose your personal information to an overseas recipient, we take reasonable steps to ensure it is handled consistently with the Australian Privacy Principles, including by relying on our providers' contractual and security commitments. Overseas recipients may not always be subject to the Australian Privacy Principles or regulated by an Australian court or the Office of the Australian Information Commissioner. By signing in and using sync, you consent to your personal information being handled in this way.

Device identifier (free trial & one-device use)

To run the 30-day free trial fairly and to keep a subscription tied to one device, the app records your device's identifier (on Android, the Android ID; on iOS, an identifier for the app on your device) in our cloud database. This is a device ID, not your name or contact details. It is used only to remember when your trial started (so uninstalling and reinstalling can't restart it) and, where enabled, to stop one login being shared across many devices. It is never used for advertising or tracking, is never shared or sold, and is removed when you delete your account.

The same record also holds the version of the app that device last ran and the date it was last opened. It is there for one reason: so we can see which versions are still in use before releasing a change that only works properly once every device has updated. It is not used to build a profile of you, it records nothing about what you do inside the app, and it is never shared. It is written at most once a day.

Crash and error reports

To find and fix faults, the app sends crash and error diagnostics to Firebase Crashlytics (a Google service, used under Google's privacy and security terms). A report is sent when the app crashes, and when the app runs into a handled fault worth investigating (for example, a PDF that failed to build on our server, or a sync step that was refused).

These reports contain technical information only: the fault and where in the code it happened, the app version, the device model and operating system version, the state of the device at the time (such as available memory and storage), and an identifier for your installation of the app that Crashlytics generates. They also carry a short technical label for the operation that failed, whether the device was signed in at the time, and whether the fault was a permissions problem or a network problem.

They do not contain your reports or anything in them, your customers' names or addresses, photos, signatures, email addresses, or any other detail you have typed into the app. Crash and error reports are used only to fix faults and keep the app reliable. They are never used for advertising, and are never sold or shared.

Security logs

A few things our server does have to work when you are signed out, the main one being sending a password reset email. When the app, the website or the dashboard makes one of those requests, our server records it: the time, the internet (IP) address it came from, the kind of app or browser that sent it, and the email address it named, shortened so it cannot be read in full.

This is kept for two reasons. It lets us tell an ordinary request apart from an attempt to misuse the service, and it lets us answer you if you ever ask why you received an email you did not request. These records are held by Google Cloud for 30 days and then deleted automatically. They are used only to keep accounts secure and the service running. They are never used for advertising, and are never sold or shared.

Teams (businesses)

If you create or join a business in the app, reports made by team members are shared within that business: every member's reports appear in the shared history, and business admins can see report summaries (address, report type, who created it, and whether follow-up work is flagged) on the dashboard. Joining a business is always an explicit action. Your reports are never shared with anyone unless you create or join one. Leaving a business stops new sharing; reports already shared remain with the business.

Procedures. A business's owner and admins can write the business's own procedures (steps, photos and PDFs) on the web dashboard or in the app (Settings > Procedures), and a sole trader can write their own. A photo or PDF is only uploaded when you add it to a procedure, from the camera, your photo library or your phone's files. They are stored with the business's reports, only the business's members can read them (a sole trader's, only that sole trader), and each member's phone keeps a copy so a procedure can be read with no signal. Unpublished drafts are visible only to the owner and admins. The app has no way to share or export a procedure.

What we never do

Device features the app uses

Sharing reports

When you share or email a report, the PDF leaves your device only via the recipient and method you choose (e.g. Mail, Messages, Files, your job-management platform).

Your customers' information

Reports typically contain information about your customers and their properties. You are responsible for handling that information in line with your obligations (for example, the Australian Privacy Principles where they apply to your business). The app helps by storing report data securely and never using it for anything other than showing it back to you and your business.

Data retention and deletion

Children

The app is intended for professional/business use and is not directed at children.

Changes

We may update this policy; the “last updated” date will change accordingly. Material changes will be noted in the app's release notes.

Contact

Questions about this policy: support@safetycheckpro.com.au