Effective date: 27 October 2026 (updated for version 3.5.3)
F+R 90 ("the app") is a companion tool for retained firefighters of Fire and
Rescue NSW Station 90 Menai. It is operated by InteractiveWebs
(interactivewebs.com) on behalf of the brigade.
What the app collects
Your Gartan username and password are used to verify
your identity and perform Gartan timesheet actions (such as closing a job).
On iOS they are stored in the device's Keychain until you
sign out. On Android your password is encrypted with a key held in the
Android Keystore and kept, with your username, in the app's
private storage, which is excluded from backups and device transfer; both
are removed when you sign out. Your password is transmitted over HTTPS to
Gartan (retained.fire.nsw.gov.au), not to our pager server.
Your name, member initials and Gartan username are kept
on your device so the app knows who you are. Our server keeps your initials,
surname and the first two letters of your first name, when you signed in,
and a one-way hash of each signed-in device's session, and uses them to
attribute your statuses, reports and changes to you. Signing out removes only
that device's session hash. Your Gartan username is not sent to our
server.
Responder status you set during an incident is shared
live with other signed-in brigade members (including on CarPlay and Android
Auto) and kept in that incident's history on the brigade server.
Job addresses and coordinates, tanker-duty choices, tanker
online/offline changes, maintenance reports and notes, and job
close-offs are stored on the brigade server with the member identity
and timestamps for operational use and history. These records show your name
or initials to other signed-in brigade members. A tanker online/offline
change is shown with your name to other signed-in brigade members and is
sent, with your name and the time, as a notification to other members who
have turned on availability alerts.
Availability alerts (optional): if you turn on
availability alerts, that choice is stored on the brigade server against
your member initials, and the server sends you a notification when station
availability changes or a member marks the tanker online or offline.
Availability alerts name the members whose Gartan availability changed and
their hours, so your own availability as recorded in Gartan can appear by
name in alerts sent to members who have turned them on, whether or not you
have.
Push notification token: after you sign in, the app
registers this device's push token with our server against your member
identity (on iPhone once you allow notifications; on Android at each
sign-in, even if notifications are turned off), with the platform and the
time it was added, so the server can send tanker duty, maintenance,
availability and tanker status alerts through Apple's push notification
service (iPhone) or Google Firebase Cloud Messaging (Android). Notification text, which can include members' names, availability hours and maintenance notes, passes through that push service. The token is
removed from our server when you sign out, or when the app next connects if
you signed out offline.
Your live location (optional, version 2.2+): when you
mark yourself as responding to a current incident and have allowed location
access, the app shares your position (precise, or approximate if you allow only approximate location) — with its accuracy and, when your
phone provides them, your heading and speed — live with the other signed-in
brigade members on the responder map, so the crew can see who is on the way.
Once you have allowed location access, sharing starts automatically each
time you mark yourself responding, including from CarPlay, Android Auto or a
voice command. Sharing continues while the app is in the background or the
phone is locked; Android shows an ongoing "Sharing your response location"
notification with a Stop sharing button, and iPhone shows its location
indicator. In CarPlay and Android Auto, shared positions are used to
estimate each responder's driving time to the station; on iPhone that
estimate is calculated by Apple Maps, which receives each position and the
station's location. The server accepts updates only during the current-job
window (up to 60 minutes after the page). The app stops sharing when it
detects the job has ended, when you clear your response status, tap Stop or
sign out. Locations are held in memory only on the brigade
server — never written to disk — and a position not updated for 2 minutes is
discarded, so your last position can stay visible for up to 2 minutes after
sharing stops. You can decline location access and still use every other
feature of the app.
What the app displays
The app shows brigade-operational data sourced from public pager feeds,
Gartan and the operator: incident pages; station availability, including each
member's name and available hours, which our server reads from Gartan with a
brigade service login whether or not that member uses the app; incident
history showing who attended each incident (from Gartan timesheets) and who
responded in the app; platoon rosters; and a station contact list, maintained
by the operator, that includes members' and platoon staff's names, ranks,
staff numbers, qualifications and mobile numbers. Six-month incident
attendance figures show only your own attendance, except that the brigade
captain and the app administrator can see every member's figures.
Brigade data on our server is available only to devices signed in as a
Menai 90 roster member; "signed-in brigade members" in this policy means those
devices. The app checks your Gartan username and password with Gartan, on your
phone, before it signs you in; your Gartan password is never sent to our
server. A minimal roster of names and initials remains available before
sign-in for client compatibility. These access controls do not make the
underlying public pager feed private.
What the app does not do
No advertising, and we use no analytics or tracking SDKs of our own. On
Android, some Google components send Google limited technical information to
run and improve their services: ML Kit (the address scanner) sends
diagnostics such as device model, OS and app version, a per-install
identifier and performance figures — never camera images or recognised text;
Firebase Cloud Messaging uses a per-install Firebase ID and device and SDK
details to deliver notifications; and Google Maps (ERG mode) loads map data for the area you view and sends Google usage, crash and diagnostic information about the map.
No data is sold or shared for advertising. Gartan, Apple or Google
notification and mapping services, and OpenStreetMap's map tile servers (the
Android responder map), process data needed to provide the features you
use.
The optional camera scanner recognises station printout text on-device.
Camera images are not uploaded; only the address/coordinates you confirm
are sent to the brigade server. The app does not read your personal contacts
or photo library. Location is used only
for the optional live location sharing described above and, in ERG mode, to
show your position on the incident map on your device — never for
advertising, profiling or tracking across apps.
Voice commands are recognised by your phone's own voice services — Siri
on iPhone; Google Assistant or the phone's speech recognition service on
Android — which may process the audio under their own privacy terms. The app
does not record audio itself; it receives only the recognised words, and only
the resulting status, report or address is sent to the brigade server.
Driving directions: tapping a job's address or coordinates hands that
destination to a maps app on your phone — Google Maps, or from version 3.5.1
the one you choose in Settings (Apple Maps or Waze on iPhone; any maps app
on the phone on Android) — or to Google Maps in your browser when no maps
app is installed. What that app does with the destination is covered by its
own privacy policy. So that it can list them, the app asks your phone which
maps apps are installed; the answer is used on the phone and is not sent
anywhere.
Data retention and deletion
Signing out immediately removes the local pager snapshot, saved identity,
Gartan credentials and active session cookie. The recreatable snapshot is kept
in the app's private storage (with Data Protection on iPhone) and excluded from
backups, and on Android from device transfer too. If offline, the old cookie is
retained only in a device-only cleanup queue (the Keychain on iPhone, app
storage that is never backed up on Android) to retry server session revocation
and notification unregistration when the app next connects. Server
notification cleanup cannot complete while offline. Operational history is not
deleted by sign-out. You can ask us to remove any data the brigade server holds about you — your sign-in record, push tokens, statuses, maintenance reports and notes, job addresses, tanker status and duty history, and your alert choice — by contacting the operator below.