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
- Full name (first + last)
- Email address
- Mobile phone number
- Role (super admin, admin, manager, employee/guard, patrol guard flag)
- Profile photo (optional)
- If you choose to sign in with Google, Apple or Microsoft: the name and email address that provider shares with us, its identifier for your account, and any profile picture link it includes. If you use Apple's Hide My Email, we receive a private relay address instead of your real one.
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)
- Residential address (street, suburb, state, postcode)
- Date of birth
- Emergency contact name, phone and relationship
- Employment type (casual / part-time / full-time / contractor), agreed weekly hours, employment start date
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.
- Bank name, BSB, account number, account name
- Tax File Number (TFN) and tax residency status
- Superannuation fund name, USI, member number, fund ABN
Licensing & compliance
- Security licence number, state, expiry date and photo of the licence card
- RSA (Responsible Service of Alcohol) certificate number, expiry and photo
- First Aid certificate expiry and photo
- Policy acknowledgments (which policy version you accepted, and when)
Operational activity
- Shift schedule, accepted / declined status, availability, leave entries
- Sign-on / sign-off timestamps (stamped by our server clock, not your phone)
- GPS coordinates at sign-on, the distance from the site at patrol arrival, and positions at patrol checkpoints and along an active patrol trail. The app checks location at sign-off without saving that check. Optional venue exit checks record distance, GPS accuracy and capture times while a guard is signed on; the coordinates used for those background checks stay on the phone.
- Timesheet adjustments (billable hours, hourly-rate edits admin only)
- Incident reports you submit (title, description, category, severity, time, venue) and any photos you attach
- Edit history for incident reports (who changed what, when)
- Patrol checkpoint scans, when patrol features are enabled
Communications
- In-app messages you send (1:1 chats and per-venue group chats), including any photos shared
- Chat block preferences; reports you submit about a user or message, including the company, reporter and reported person's names and account references, reason, details, relevant message excerpt and any referenced attachment; support review notes, actions and times
- Read-receipt timestamps
- System-generated alerts you've received and read
- Questions and recent conversation you send to the optional AI help chat (see §4 below)
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:
- Venue contact names, phone numbers and email addresses (e.g. venue manager, billing contact)
- Patron watchlist entries: photos, names/aliases, descriptions, banned-until dates, and the reason for inclusion
- People named or pictured in incident reports (patrons, visitors, third parties)
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
- Expo / Apple / Google push notification tokens (so we can send alerts to your device)
- Authentication session tokens stored locally on your device
- TOTP factor metadata if you enrol in two-factor authentication (the secret itself stays in your authenticator app)
- Standard server access logs (IP address, user-agent, paths) for security and abuse detection
- Crash reports from the mobile app: when the app hits an error or closes unexpectedly while on screen, it records the error message and technical trace, the screen you were on, the app version, build and update, your phone's model and operating system version, and the time. The report is linked to your account and your organisation. Email addresses, phone numbers and long runs of digits are removed from the error text on your phone before it is stored. It never includes form contents, photos or the records you were working on.
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
- Website enquiries and demo requests: to respond to you and arrange the demo you requested. We do not add form submissions to a marketing mailing list.
- Identity & contact: to operate your account and reach you about your shifts.
- Sign-in provider details (optional): to let you sign in with Google, Apple or Microsoft instead of a Serosta password, and to match you to the account your employer set up for you.
- HR data (address, DOB, emergency contact): employer record-keeping obligations under Fair Work Australia; we hold them as processor on your employer's behalf.
- Banking & tax: so your employer can pay you, lodge superannuation contributions, and report PAYG. Stored only because the payroll integrations we offer (Xero, MYOB coming) need them on file.
- Licence details and photos: to meet NSW SLED Master Licence record-keeping obligations on behalf of your employer, and to power expiry warnings in the app.
- Location checks and patrols: to verify you are at the site when you sign on or off, and to record and follow a patrol you have started. During an active patrol, the app records positions about once a minute or after moving 50 metres, and at checkpoint scans. The current sign-off check is not saved. Venue exit checks require the company to enable them, issue a current tracking notice and obtain the guard’s acknowledgement, plus background location permission. They run only during an ordinary venue shift, including while the phone is locked, and stop at sign-off. After the company’s set time of continuous reliable outside readings (from 10 minutes to 2 hours, shown in the guard’s notice), the finish is recorded at the first outside check. A guard may sign off outside by choosing a reason. Missing or poor GPS does not count as leaving. Phone and operating-system restrictions may delay or prevent checks; these are not a guarantee of exact background timing.
- Incident reports: to maintain the electronic incident register your employer is required to keep under the Security Industry Act 1997 (NSW) and equivalent state legislation.
- Watchlist: so guards rostered at a venue are aware of patrons of concern before incidents escalate.
- Messages: to enable operational communication between guards, managers and admins within an organisation.
- Chat safety: to apply your chat block preferences, investigate reports of objectionable content and record Serosta support's review and moderation actions.
- Shifts covered for another company: so a company that sent a shift to your employer can see that it was covered, follow it on the day, check and pay for the hours, and invoice its venue (see §3).
- Push tokens: to deliver shift, sign-on, licence-expiry, message and acknowledgment alerts.
- Optional AI: to answer questions about using the app.
- Server access logs: security monitoring and breach detection.
- Crash reports: to find and fix faults in the mobile app, such as a screen that stops working or an app that freezes.
3. Who can see your information
- You: your own profile, shifts, incidents, licences, banking/tax details, message threads, and policy acknowledgments.
- Your employer's admins and super admin: your full profile, HR fields, banking & tax (admin/super_admin only), licence photos and details, shift records, sign-on/off events, stored shift GPS coordinates and patrol locations, incident reports you filed, your message threads with them, your hourly pay rate, and crash reports the mobile app sent from your account while you were working in their organisation.
- Your employer's managers: the same as admins except they cannot see banking & tax or the audit log.
- Other guards in your organisation: only what's relevant to a shared shift your name in venue group chats you're both members of, your name on shared shift assignments. Not your contact details, HR data, banking, or licence numbers.
- Serosta (us): crash reports from the mobile app, so we can fix the fault. We read them in the same Sydney database; they are not sent to any crash-reporting service. Authorised Serosta support staff who have verified two-factor authentication can also review chat reports, the relevant reported message and referenced attachment, and review history. A report does not give support access to the whole private conversation through the reporting tools. Company owners, admins, managers and guards cannot read these support reports merely because of their company role.
- Other organisations using Serosta: by default, nothing. Row-level security in our database keeps each organisation's records to that organisation. The exceptions are set out under "When information is shared between organisations" below. Each one passes only the items listed there, and no organisation is given general access to another organisation's records.
- We do not sell your information to third parties. We do not use it for advertising or for any purpose unrelated to operating the Service.
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:
- your first name, or your full name if your employer turns on "Show full name" for that shift or for all its shifts. Only your employer can turn this on or off;
- whether you have accepted the shift;
- when you signed on and off, the hours worked and the break, whether you signed on late, and the reason recorded for each sign-off (for example, an automatic sign-off when you left the venue);
- where you signed on, which its Live Operations map shows;
- alerts and push notifications naming you by first name when you sign on, sign on late or sign off, or have not signed on 10 minutes after the rostered start;
- a copy of the photo of the venue's signed timesheet, if you send it in for that venue, labelled with your employer's name and your first name. The photo shows whatever is written on the sheet.
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:
- Your account name and profile photo are the same in every company you have joined, and a company that adds you takes the name already on your account. A company can also give you a different name on its own screens; its records still use your own name.
- When another company adds you, the app asks whether to share your existing details with it. If you choose "Share my details", we copy your details from your existing record into that company's record: your name, phone number, date of birth, address, emergency contact, security licence, RSA and first aid details and photos, and your bank account, tax file number and super details. Other licences you have added (such as a white card, Working with Children Check, driver licence or firearms licence) become visible to it too. Afterwards, when any of those details changes in one of your companies, the change is copied to each company you agreed to share with. If you choose to enter your details yourself, nothing is copied. Each company keeps its own copy, and who in that company can see what follows the rules above.
- When you change your own security licence, RSA or first aid details (unless you are an owner or admin of that company), the change waits for an owner or admin to confirm it, and the owners and admins of every company you have joined are told and can see the change you asked for.
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.
- Incident reports and attached photos: 7 years from the incident date. The legal minimum is shorter than that: 3 years under the Security Industry Regulation 2016 (NSW) and the Liquor Act 2007 (NSW), and 5 years under the Work Health and Safety Act 2011 (NSW) for an incident that has to be notified to the regulator. Because whether an incident is notifiable often is not known when it is recorded, we apply the longest of these to all of them. A legal hold extends this indefinitely.
- Sign-on / sign-off records: 7 years from the date of the shift. For a casual employee these timestamps are the record of hours worked, which the Fair Work Act 2009 (Cth) requires an employer to keep for 7 years.
- Pay rates, payroll and superannuation records: 7 years, for the same reason.
- Patrol sessions and checkpoint scans: 7 years, as deployment records.
- Bank statement lines an admin imports (a company with no accounting software can upload a CSV from its bank to match against its own records): 7 years from the transaction date. A description can name the person or business paid, and that stays for 7 years even if that person deletes their account. Card numbers in descriptions, and account numbers that follow a BSB or a label such as "ACC" or "account", are hidden before they are saved. The file itself is read in the admin's browser and is not kept.
- Policy acknowledgments: 7 years. This one is our own choice rather than a legal requirement, and it keeps them alongside the employment records they relate to.
- Audit log of changes (who edited what, when): retained indefinitely, append-only. We deliberately do not shorten this: the audit log is the evidence that a register record was not altered or destroyed inside its retention period, and destroying such a record is an offence under the Security Industry Act 1997 (NSW).
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.
- Venue exit checks: distance, accuracy and capture times are kept for 30 days, or 12 months when supporting an automatic sign-off. Legal holds suspend deletion. These records are available to the guard’s company owners, admins and managers. Raw coordinates used for these checks are not sent to Serosta.
- GPS coordinates captured at sign-on / sign-off: 12 months, after which the coordinates are removed and the sign-on record is kept without them. The security-industry record requires the address of the location, not your coordinates.
- Patrol GPS breadcrumb trail: 30 days.
- In-app messages: our ordinary retention period is 24 months from the date sent; general expiry is on request as explained below. Final account closure separately removes your ordinary authored chat messages and reactions. Incident cards and records kept as incident or support evidence follow the relevant retention rules. Files are removed through background cleanup after their ordinary references have been cleared; independent incident copies and retained support evidence remain.
- Bank account and BSB details (the banking details on your profile): 12 months after the last payment made using them.
- Tax file numbers: only for as long as taxation law requires, then securely destroyed. We do not apply a fixed period to these. The Privacy (Tax File Number) Rule 2015 places that destruction obligation on us directly, not only on your employer.
- Chat safety records: identifying report details, message excerpts, attachment references and review notes are removed 90 days after Serosta support explicitly closes a report. Hiding a message or restricting chat does not itself close the report. Open investigations and documented holds retain their evidence. Removing a hold after the 90-day deadline makes the evidence due for removal. Expired evidence is hidden from support reads immediately and cleared by the daily background job. We keep only the control identifiers and integrity checks needed to enforce an active restriction or hidden-message decision until that control ends; evidence expiry does not lift it. Private block preferences are removed when account closure becomes final after the restoration window. Technical message identifiers may remain to prevent deleted content being reused. Contact privacy@serosta.com about these records.
- Alerts and notifications: 30 days.
- Crash reports from the mobile app: 90 days from when we receive them. A report the app could not send yet is kept on your phone for at most 30 days.
- Website enquiry and demo correspondence: Resend states that email and log data on our plan is retained for 30 days. Copies delivered to our business mailbox are separate: we retain them while needed to respond and manage the enquiry, and remove them when no longer needed unless a legal obligation requires retention. This is a manual review, not an automatic website deletion job. You can request access, correction or deletion through the contact below.
- AI help chat history: kept locally in your browser or phone until cleared. Recent turns sent with a question are processed by the AI service as described in §4; local storage does not establish the provider’s retention period.
How deletion actually happens
It is easy to write "deleted automatically" and be wrong, so we will be exact about this.
- Deleted automatically, once a day: alerts and notifications, patrol GPS breadcrumbs, crash reports from the mobile app, and identifying closed-report evidence whose 90-day period has expired without a hold.
- Deleted automatically, checked every hour: final account closure after the 30-day restoration window, ordinary authored chat and reactions associated with that closed login, and queued personal-file cleanup. Contention or a Storage failure causes a retry; physical file removal may finish later than the account-profile cleanup. Retained incident or support evidence is excluded while required.
- Deleted on request: everything else. We do not run a general automated expiry purge across incident, shift, payroll or message records. Final account closure and the specific support-evidence cleanup described here are separate. In practice that means those records are kept for at least the periods above, and at present are kept rather than destroyed at the end of them. No record we hold has yet reached the end of any period in this section.
- Deleting your account (in the Serosta app or on the website, in Settings, whatever your role) closes it straight away: you are signed out on every device and removed from every company you work with. For 30 days you can sign in again and restore it, and it comes back as it was, except that your shifts from the day you deleted it onward are given back to your employer to fill, and a company that removed you from its staff in the meantime does not take you back. After 30 days your login and your personal details are removed from your account profile: your contact details, address, date of birth, emergency contact, RSA number, profile and licence photos, and bank and tax details. Ordinary authored messages and reactions are also removed through the final-closure cleanup, with physical files handled in the background. Separate support evidence can remain identifiable while an investigation, documented hold or its 90-day closed-report period requires it; active controls keep their minimal enforcement data. Each company you worked for keeps your name and your security licence details (licence number, class, state and expiry, and when you started and finished with them) in its staff register, because the law requires a licensed security business to keep a register of the people it engages. The other records your employer is required by law to keep, such as incident reports, sign-on records and the audit log of changes, are kept for the periods above, and they may still show your name and licence number as they were recorded at the time.
- A company's subscription when its last owner or admin deletes their account: the subscription is set to end at the end of the period already paid for (or when its free trial ends), and it does not renew. The company's other staff can keep using the Service until then. If the account is restored within the 30 days and the subscription has not ended yet, it is switched back on, unless the company removed that person from its staff in the meantime. If other owners or admins remain, the company and its subscription carry on unchanged.
- Being removed by your employer (off-boarded from their staff list) is different: it revokes your access to that company only, and your record there is marked closed rather than erased, because the incidents you filed and the shifts you worked form part of a register your employer is required by law to keep. An owner or admin can also remove you while your deleted account is waiting out its 30 days; if you then restore it, you come back to your other companies but not to that one, and the restore screen tells you so beforehand.
- Personal information we are not required to retain is also erased on request: email privacy@serosta.com and we will respond within 30 days.
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:
- Encryption at rest (AES-256) and in transit (TLS 1.2+).
- Row-level security on every personal-information table, which keeps each organisation's records to that organisation. The sharing between organisations described in §3 is done by specific rules on our server that pass only the items listed there; no organisation is given general access to another organisation's records.
- Stricter RLS on banking, tax and superannuation data managers are explicitly blocked, only you and the org admins/super_admin can read it.
- Multi-factor authentication available for every account; we recommend it for admins, managers and super admins.
- An append-only audit trail for changes to incident records, Master Licence details, organisation settings and staff data.
- Server-stamped timestamps for sign-on/off your phone clock cannot tamper with attendance records.
- Anomaly detection that alerts admins to unusual rates of compliance-relevant actions.
8. Your rights (APP 12 + APP 13)
- Access: download a copy of your information by emailing privacy@serosta.com. We respond within 30 days.
- Correction: update your details from My Profile → Edit account, HR or Banking & Tax. Contact us if you cannot correct them yourself.
- Deletion: delete your account in the Serosta app (Settings → Account & security → Delete account) or on the website (in Settings: Account and security for owners, admins and managers, and your own Settings page as a guard or venue manager), whatever your role. It closes straight away and you can restore it for 30 days by signing in again; after that your login and personal details are removed, and your name and security licence details stay in each company's staff register, as §6 describes. Records we are required to keep for compliance are retained for the periods in §6; to have anything else erased, email us and we will action it within 30 days.
- GPS consent: you can revoke OS-level location permission at any time in your phone's Settings app. Sign-on will not work without it talk to your employer if you need an alternative.
- Notification consent: opt out of any notification category from Settings → Notifications (web) or the Settings screen on mobile. Push notifications can also be disabled at the OS level.
- Complaint: if you believe we have mishandled your information, contact us first; if unresolved you may complain to the OAIC at oaic.gov.au.
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