RedCall Privacy Policy

Effective 29 October 2026

1. Who we are

RedCall is a staff safety alert service operated by Valmere Group Pty Ltd (ABN 13 702 167 780, ACN 702 167 780), trading as RedCall ("RedCall", "we", "us", "our"). This policy explains how we collect, use, disclose and protect personal information when you use the RedCall mobile application and our website at redcall.com.au (together, the "Service").

We are bound by the Australian Privacy Principles in the Privacy Act 1988 (Cth).

Privacy enquiries: info@redcall.com.au

2. Workplaces and their team members

RedCall is provided to workplaces, such as hotels. A workplace decides who is added to its team and is responsible for keeping its team list accurate. Accounts are created by a workplace. There is no public sign up.

Where we handle personal information for a workplace, we do so to provide the Service to that workplace and for no other purpose.

3. Information we collect

3.1 Account information. Your name, mobile number, email address, preferred language, role (staff, Admin), the workplace or workplaces you belong to, and whether your account is frozen. A workplace must provide an email address for every staff member it adds. We use it for service notices, such as updates to the app and changes to these terms, and not for marketing. For Admins we also keep a mobile number on record, so that we and the workplace can reach them in an emergency. A workplace also gives us a report email address, to which we send incident reports as described in section 7.

3.2 Alert information. When an alert is raised we record the type of threat chosen, an optional place description, the time, who raised the alert and who ended it, whether it was a drill, each person's reply (safe or not safe) with the time of the reply, messages sent in the alert chat (including broadcasts from Admins), and the resulting incident record.

3.3 On site status. If you allow location access, your phone compares its own position with the position of your workplace. That comparison takes place on your phone. We receive only the result, which is either "inside" or "outside" for each of your workplaces, together with the time. We do not receive, store or see your coordinates. We keep only the latest result for each workplace, and we do not keep a history of where you have been. The result is deleted when you sign out, and a result older than 24 hours is no longer used. Admins of your workplace can see whether you are recorded as on site, off site or unknown, and when your phone last reported. They cannot see your coordinates or a map of where you are. We also store the geographic position of each workplace that uses the Service. That is information about the workplace and not about any person.

3.4 Device information. A push notification token for each device you use with RedCall, and the type of device. When you sign out, the token for that device is removed. Admins of your workplace can see whether your phone is registered to receive alerts, how many devices are registered, whether RedCall is open and connected on your phone at that moment, and when it was last open. They cannot see anything else about your device.

3.5 Sign in information. Staff sign in with their mobile number and a code sent by text message. Admins sign in with an email address, a code that we send to that email address, and a code from an authenticator application. Admins do not use a password.

3.6 Activity and technical records. A short record of actions in the app, such as signing in and out, and a record of changes an Admin makes to a staff member's name, mobile number or email address, adding, freezing or removing staff, who made each change and when, raising an alert, replying safe or not safe, an alert failing to send, and application errors, with the time, the app version and the type of device. These records do not contain messages, locations or passwords. We also keep basic server records, such as the time of a request and any error message. We use them to keep the Service secure, to find out why an alert did not reach someone, and to correct faults.

3.7 What we do not collect. We do not collect your contacts, photos, camera or microphone data, or advertising identifiers. We do not use analytics, advertising or tracking tools. We do not sell personal information.

4. How we use personal information

We use personal information to:

(a) verify your identity and sign you in;
(b) deliver alerts, reminders and chat notifications to the members of your workplace's team;
(c) decide whether an alert should sound on your phone, as described in section 5;
(d) show Admins who has replied safe or not safe during an alert, and whether each person is recorded as on site, off site or unknown;
(e) keep an incident record for your workplace;
(f) send text messages in the circumstances described in section 6, and send service notices and incident reports by email;
(g) keep the Service secure, correct faults and meet our legal obligations; and
(h) respond to your questions and requests.

We do not use personal information for marketing, advertising or profiling.

5. Location

RedCall asks for location permission so that a loud alert sounds for the people who are at the workplace, and does not wake people who are off duty. The iPhone setting "While Using the App" allows the check to run each time you open RedCall. The setting "Always" also allows your iPhone to tell RedCall when you arrive at or leave your workplace while RedCall is closed. In that case iPhone decides when to report the change, and it can be delayed by several minutes or more. For that reason RedCall also checks each time you open it, and the result may not reflect where you are at every moment. A result that is more than 24 hours old is treated as unknown, and your result is cleared when you sign out.

You may decline, or change your choice at any time in your iPhone settings. If you decline, you will still receive every alert as a notification and you can open it and reply. A loud alert will sound on your phone only if your workplace has placed you on its always loud list.

A workplace may place any member of its team on the always loud list, so that a loud alert sounds for that person wherever they are.

6. Text messages

We send text messages through Twilio in three situations. Our text sender is waiting for approval from our provider. Until it is approved, text messages may not be sent, and the descriptions below show how text messages will work once they are switched on.

6.1 Invitation. When a workplace adds you to its team, we send one text message to your mobile number. It says that you have been registered with that workplace on RedCall and gives a link to download the app or visit our website.

6.2 Login codes, to the mobile number of the person signing in.

6.3 Emergency back up. If an alert is a silent type, or if no threat type is chosen within 15 seconds of an alert being raised, we send one text message per incident to the mobile numbers of the members of that workplace's team. The message states the type of alert and the name of the workplace and asks the recipient to open RedCall. This gives a second route to the same people when the alert cannot sound. A text is a back up route and does not guarantee that an alert is delivered. A text message is delivered by your mobile network and may make the sound your phone uses for messages, according to your phone's settings.

7. Who can see your information

7.1 Members of your workplace's team who are part of an alert can see the details of that alert, the names of the team and who has replied safe or not safe.

7.2 Admins of your workplace can also see the team list, change your name, mobile number and email address, whether each phone is registered to receive alerts and whether RedCall is open on it, whether each person is recorded as on site, off site or unknown, the always loud list, incident reports and the activity records of their own workplace.

7.3 When a real incident has ended and it was not a test or an accidental trigger, we email a PDF incident report to the report email address the workplace gave us. When a practice drill ends, we also email a PDF report clearly marked as a drill, for recordkeeping. The report is sent to that address only. We send it so that the workplace has its own copy. It is not a promise that we will keep the report for the workplace, as explained in section 10.

7.4 A limited number of RedCall personnel can access information where needed to provide support, keep the Service secure and meet legal obligations.

7.5 We do not disclose your personal information to anyone else, except to the service providers listed in section 8, or where the law requires or permits it, including where we reasonably believe disclosure is necessary to lessen or prevent a serious threat to the life, health or safety of a person.

8. Service providers and overseas disclosure

We use the following providers to deliver the Service.

Supabase, for our database and sign in. Data is hosted in Singapore.

Google (Firebase Cloud Messaging) and Apple, to deliver push notifications. These providers receive your device token and the content of the notification. They operate in the United States and other countries.

Twilio, to send text messages. Twilio is based in the United States.

Resend, to send the emails that carry sign in codes to Admins, the incident report emails with their PDF attachment, and service notices. Resend receives the email address, the content of the email and its attachment. Resend is based in the United States.

Because of these providers, your personal information may be held or handled outside Australia, in Singapore and the United States. Before we disclose information to an overseas provider we take reasonable steps to ensure the provider handles it in a way that is consistent with the Australian Privacy Principles. Information is sent over encrypted connections.

9. Security

We protect personal information with encryption in transit, access controls that limit each person to the information of their own workplace, and a sign in code sent to their email address together with a second step (an authenticator code) for Admins. Access by our personnel is restricted to what is needed for their role.

No system is completely secure. If an eligible data breach occurs we will notify the people affected and the Office of the Australian Information Commissioner as the Privacy Act requires.

10. How long we keep information, and deleting your account

10.1 You can delete your account in the app by choosing Profile and then Delete my account. When you do, you are removed from your workplace's team straight away, your registered devices are removed, and you stop receiving alerts. The Admins of your workplace are told that you have left. You then have 30 days to change your mind by signing in again, which restores your account as it was.

10.2 On the 31st day your login, your mobile number and your email address are permanently deleted.

10.3 Incident records remain. Your name stays on the records of alerts you raised, on the roll call of alerts you were part of, and on messages you sent in an alert chat, because those records form part of your workplace's own records. After deletion the record is no longer linked to a login or to any contact details.

10.4 We keep a workplace's incident records and alert chat for as long as that workplace uses the Service. When a workplace closes its account, we delete or de identify its records within 12 months, unless the law requires us to keep them for longer. The workplace is responsible for keeping its own copies of its incident reports. We email each report to the workplace when an alert ends and the workplace should also save its reports from the app. We provide the report, and we are not an archive or the official record keeper for any workplace. We recommend that a workplace saves a copy of all of its reports at least once a year, and before it closes its account.

10.5 We keep only the latest inside or outside result for each person and workplace. It is deleted when you sign out and when the account is deleted. Activity records are kept for 90 days. Other server records are kept for a limited period for security and fault correction.

11. Access, correction and complaints

You may ask for access to the personal information we hold about you, or ask us to correct it, by emailing info@redcall.com.au. Your workplace may be the better contact for information in its own team list. We will respond within 30 days.

If you are not satisfied with how we have handled your personal information, please write to us first so that we can try to resolve the matter. You may also contact the Office of the Australian Information Commissioner at oaic.gov.au.

12. Children

RedCall is a workplace service. It is not directed to children and is not intended for people under 16. We do not knowingly collect personal information from a child.

13. Changes to this policy

We may update this policy from time to time. The current version is always on this page, with its effective date at the top.

14. Contact

Valmere Group Pty Ltd, trading as RedCall
ABN 13 702 167 780, ACN 702 167 780
info@redcall.com.au