Privacy Policy

Version 2026-11-18 · Last updated: 18 November 2026

This Privacy Policy explains how VQS Capital Pty Ltd (ABN 69 682 623 990), trading as Serosta ("we", "us"), collects, uses, holds and discloses personal information through the Serosta mobile app, admin web app and public website (together, the "Service"). It reflects our obligations under the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs).

1. Information we collect (APP 3 + APP 5)

What we collect depends on your role (security guard, manager, admin, super admin) and which features your employer has enabled.

Account & identity

Website enquiries and demo requests

Your name, company, email address, optional phone number and staff-count band, and the message you choose to send. We use these details to answer your enquiry or arrange a demo. These forms do not request incident records, identity documents, banking details or tax file numbers; please do not include them.

Employment & HR (guards only)

Banking & tax (guards only, opt-in)

These categories are stored in a separate profile_payroll table with stricter access controls only the guard themselves and the org owner/admin can read them. Managers cannot.

Licensing & compliance

Operational activity

Communications

Third-party information you enter

When you use the Service to record information about people who are not Serosta users, that information is also stored. Categories include:

Your employer is the data controller for this third-party information. Their incident-management and watchlist practices must comply with the Privacy Act and any state laws on photographing / recording the public.

Technical & device

Sensitive information

Incident reports may include sensitive information under APP 3 (for example: details of a medical incident, intoxication state of a patron, or a recorded BAC reading). Banking and tax data is also sensitive personal information. We treat both categories with the heightened protections APP 3.3 and APP 11 require.

2. Why we collect each item

3. Who can see your information

When information is shared between organisations

Shifts your employer covers for another company (subcontracting). A company using Serosta can send shifts to another Serosta company that it subcontracts work to. This needs a link between the two companies: the sending company adds the other company by its ABN, and an owner or admin of the receiving company must confirm it. Either company can end the link. If your employer puts you on a shift another company sent it, that company's owners, admins and managers can see, for that shift only:

Apart from anything written on that timesheet, it is not given your surname (unless "Show full name" is on), your profile photo, contact details, address, licence details, bank details or any other record of yours, and it sees nothing about shifts it did not send. It can correct the hours it counts for a shift it sent, giving a reason, and your employer is shown each correction, before and after, with the reason and the name of the person who made it. Your own sign-on records stay with your employer, and the other company cannot change them. Both companies see each other's company name and logo, and your employer receives the venue's name, address and location, the shift's times and any notes the sending company adds.

The sending company keeps its copies of your times, hours and first name, its corrections and the timesheet photo as its own records. They are not deleted automatically (see §6), even after the link ends, and the timesheet photo stays with it if your employer deletes its own copy. Alerts are deleted after 30 days. Your full name and your sign-on location are not copied into its records: they are read from your employer's records each time they are shown. So your full name leaves its screens as soon as "Show full name" is turned off or the link ends, and your sign-on location stops being available to it when the coordinates on your employer's record are removed after 12 months (see §6).

If you work for more than one company that uses Serosta. You have one Serosta account, so:

4. Optional AI and licence reading

AI Help is optional. Before you allow it, we identify Google Gemini and explain what it receives. The website and updated phone versions offer permission for future questions, remembered for your account and company in that browser or on that phone. It lasts until you withdraw it. You can withdraw it in Help: Withdraw permission on the website, or Options > Withdraw permission on the phone. A change to the provider or sharing disclosure requires fresh permission. Earlier phone versions ask for each request. When we ask, you can cancel without sending. You can clear Help history in Help.

Public help mode (Gemini free tier). Serosta receives your latest question and matches it to a fixed public Help topic. Google receives only that fixed question and a public guide to Serosta features. Google does not receive your typed text, conversation, account or company identifiers, role, page path, records or attachments. An unmatched question gets a local reply without contacting Google.

Google may process the public Help prompt outside Australia and use it and the generated reply to improve its products. Human reviewers may review that content. Google separately handles service and technical metadata under its Gemini API terms. Avoid entering personal, confidential or sensitive information in Help.

Separate paid mode, if enabled. With your permission, Google receives the question and recent conversation. On the website this also includes role and page path. This can include information you type. The assistant has no direct database access. Google says paid-service prompts and responses are not used to improve its products. Processing may occur outside Australia, including temporary storage, caching and abuse monitoring. See Google's terms and abuse-monitoring policy for handling and retention.

In updated phone versions, licence-photo text recognition runs on the phone. It suggests details for you to check; it does not verify authenticity or approve the licence. Normal saving of licence details and photos to Serosta is separate. Website licence details and PDFs use manual entry. The former cloud master-licence reader is retired; earlier phone versions may need an update to read a photo locally.

5. Where your information is stored (APP 8)

Primary storage is in Australia in the Supabase Sydney region (ap-southeast-2). All data is encrypted at rest (AES-256) and in transit (TLS 1.2+).

The admin web app is hosted by Vercel. Its page, report and file-delivery functions run in Sydney (syd1). Its login/session routing runs on Vercel’s global infrastructure. To deliver the pages, reports and files you request, Vercel processes authentication/session information and the relevant company, staff, incident and financial information, as well as technical request data such as IP address, browser details and URL paths. The primary database and file storage remain in the Supabase Sydney region.

Vercel uses a global delivery network and global service and security infrastructure. Some request, technical and service information may be processed outside Australia, including in the United States. Configuring the page and report functions for Sydney does not mean that all Vercel processing occurs only in Australia.

Push notifications are delivered via Apple Push Notification Service and Firebase Cloud Messaging. The push token and the notification payload (a short message and a deep link) pass through those services' global infrastructure. No incident body content, banking details, or sensitive information is included in notifications.

Optional AI requests may be processed outside Australia as described in §4. The primary database and file storage remain in the Supabase Sydney region.

Signing in with Google, Apple or Microsoft is optional. If you choose to, you sign in on that company's own page, it learns that you are signing in to Serosta, and it returns your name, email address and an identifier for your account to us. Google (Google LLC) and Microsoft (Microsoft Corporation) operate globally and Apple (Apple Inc.) is in the United States; each handles your sign-in under its own privacy policy. We send them no Serosta records. Signing in with your email address and password involves none of them.

If your employer connects an accounting integration (Xero), banking, tax, timesheet and venue contact data is transmitted to that integration to create payroll records and invoices. Xero stores that data per Xero's own privacy policy.

Emails the Service sends are delivered through Resend (Plus Five Five, Inc.). Our serosta.com sender uses Tokyo, Japan (ap-northeast-1) for sending; Resend stores email and log data in the United States. Choosing Tokyo does not keep that stored data in Japan or Australia. That covers invitations, password resets, notifications, invoices and quotes, paysheets, and files an admin chooses to email, such as money files sent to an accountant or bookkeeper. The recipient's address and the email's content and attachments pass through Resend.

Website contact and demo forms are processed by Vercel and sent through Resend to our business mailbox. Our role-address email routing uses Cloudflare and the receiving mailbox uses Google Workspace; these services use global infrastructure and may process the correspondence outside Australia, including in the United States. Resend may process a small sample of emails using automated trust-and-safety checks; it states that customer content is not used to train or fine-tune models. We do not use its AI Editor or AI Support Agent to handle enquiries.

Maps and address suggestions on the website use Google Maps Platform (Google LLC). Google operates globally and may process this information outside Australia, including in the United States. When your employer's office opens the Live Operations or patrol monitoring map, the map is placed around the sign-on positions of guards who are signed on now and around each active patrol's latest positions and recent trail, so Google receives requests for that map area and can see the general area where those guards are working. Those guards include another company's guard who signed on to cover one of your employer's shifts (see §3). Address text typed into an address field, including a home address on a profile or staff record, is sent to Google to suggest matching addresses, and a venue's address can be sent to Google to find its location for the sign-on and sign-off check. Requests made from your browser also give Google technical information such as your IP address and browser details.

Maps in the iPhone app use Apple Maps (Apple Inc.), which may process this information outside Australia, including in the United States. When the Live Ops map is opened, the phone requests the map area framed around the sign-on positions of guards who are signed on now, and when a patrol's details screen is opened, the map area centred on that patrol's latest recorded position, which can be at street level. So Apple receives requests for those map areas and can see the area around those guards' recorded positions. On the Live Ops map, those guards include another company's guard who signed on to cover one of the company's shifts (see §3). In updated phone versions, a shift you have not yet signed on to shows its site on a map, and the phone requests the map area around that site, so Apple can see the area around the site. That map shows the site only: it does not read or send your own position. If you tap Directions, Apple Maps opens on your phone with the site as the destination. We pass it the site's location only. What Apple Maps does with your own location is controlled by your phone's settings and Apple's privacy policy. These requests also give Apple technical information such as the phone's IP address.

A full list of third-party services we use is at /subprocessors.html.

Our website contact and demo forms use Cloudflare Turnstile to detect automated abuse. Cloudflare processes technical information such as your IP address, browser and device information and challenge results using its global infrastructure, which may involve processing outside Australia. Our server sends the verification token to Cloudflare to check it; we do not include your enquiry text or contact fields in that verification request. Cloudflare also uses these technical signals to improve its bot detection. See Cloudflare's Turnstile Privacy Addendum.

6. How long we keep your information

Records we keep for a minimum period

We keep these for at least the period shown, because your employer is legally required to be able to produce them.

Records we keep no longer than necessary

Nothing requires these to be retained, so we hold them for the shortest period that still lets the Service work.

How deletion actually happens

It is easy to write "deleted automatically" and be wrong, so we will be exact about this.

This section describes what the Service does today, not what we intend it to do. We will update it when that changes, and not before.

7. Security (APP 11)

We protect your information with:

8. Your rights (APP 12 + APP 13)

9. Children

The Service is intended for adults employed in the security industry. We do not knowingly collect information from anyone under 18.

10. Changes to this policy

We may update this policy. Material changes will be communicated through the Service and by email to admin contacts. The "Version" string at the top of this page increments on each material change.

11. Contact

Privacy questions and requests: privacy@serosta.com

Security-vulnerability disclosure: security@serosta.com (see also /.well-known/security.txt).

General support: support@serosta.com