Privacy notice

1. What we collect

Identity and access: name, site code, company, role, and optional contact numbers used on journey plans, sign-on sheets, and messages.

Work records you or your supervisor create: daily reports, photos, voice notes, incidents, JHMS forms, rosters, licences or tickets if entered, plant hours, map pins, purchase requests, and files in a backup.

Sensitive work information may appear in incidents, injuries, or fitness notes if someone types it in. Only collect that if the job needs it.

Technical data: crash reports you send, basic visit counts, device type if you install the home-screen app, and the approximate map area you load.

2. Why we collect it

To run the workspace you asked to use: access control, job records, safety paperwork, routing, and backups.

To isolate one customer’s data from another, and to let a super user support a company when asked.

To fix faults and understand whether the product is being used, not to profile you for advertising.

3. Where it is stored

On a trial browser session, most records stay in that browser until you export a backup. Closing the tab, clearing site data, or filling the browser quota can delete them.

On a published host, records may also be stored on the operator’s configured database and file storage so the crew can share them.

Hosting and build infrastructure may be outside Australia (for example the published web host). If that happens, personal information can be disclosed overseas to those processors solely to run the product.

4. Who else may see it

People in your company who have been given access to that site or module.

A contractor or client only sees what the customer has allowed for that relationship.

Map and weather providers see a location request when you open those screens, not the full job file.

If Google sign-in is turned on and you use it, Google authenticates you. We receive the account we need to open the session.

We do not sell personal information. We do not use incident photos or job files for advertising.

5. Isolation and shared directory

Job files stay in the customer’s tenancy. Other customers cannot browse them.

A company may publish a limited profile (name, trade, public site) to a shared contractor directory. That is opt-in. Private reports do not go with it.

6. Cookies and local storage

We use essential browser storage to keep you signed in, remember the chat icon position, and hold unsaved work on a trial session. That is not advertising tracking.

You can clear site data in the browser. That will sign you out and may delete local records that were not exported.

7. How long we keep it

We keep records for as long as the customer account needs them for the job, plus any period the customer must keep safety or project files.

You should export backups if you need a copy outside the product. Local trial data is not an archive.

8. Your choices

Ask your supervisor to correct your name, company, or access.

Use Export my data in the workspace menu. That download is a ZIP of your PDFs, uploads, and a project snapshot so you can put those records back later. It does not include the Fiorentino application. Operators who need a full archive use Backup.

To ask for access, correction, or deletion of personal information the operator holds, email privacy@fiorentino.global. We may need to confirm who you are and may refuse a request that we must keep for law or safety.

If you are not satisfied, you may complain to the Office of the Australian Information Commissioner (oaic.gov.au).

9. Children

The workspace is for working adults. Do not create a profile for anyone under 18 unless they are a lawful worker on that site and a supervisor has a work reason to record them.

10. Law

This notice is meant to align with the Australian Privacy Principles. If the product is later offered to people in other countries, this notice must be extended before that launch.