Skip to content

Privacy notice

ACOS website, web app and ACOS Staff app · Last updated 10 October 2026

Who we are and what this notice covers

ACOS (Aged and Community Operations System) is provided by ACOS Systems Pty Ltd, trading as ACOS Systems (ABN 11 995 265 921), based in Western Australia. We handle personal information in line with the Privacy Act 1988 (Cth) and the Australian Privacy Principles.

This notice covers the acossystems.com website, the ACOS web app that care providers sign in to, and the ACOS Staff app for iPhone.

Two roles. When a care provider uses ACOS, the provider collects the client, staff and care records in its workspace and decides how they are used. We hold and process those records on the provider's behalf, scoped to that provider, and do not use them for our own purposes. If you are a client, family member or worker of a provider that uses ACOS, your provider is the first point of contact for questions about your records. We collect account and billing information from provider owners directly.

Information we collect and why

  • Account information: your name, work email address and a password (stored only as a one-way hash), plus your organisation's name, chosen plan and subscription status. We use it to create and secure your account, confirm your email with a one-time code, and run your workspace.
  • Billing: subscription payments are taken by Stripe. Your card details go straight to Stripe's secure payment form and never reach our servers. We keep Stripe's customer and subscription identifiers, the plan, the billing period and payment status so we know which workspace is paid for. Stripe also receives your email address and organisation name.
  • Records a provider enters: clients and their representatives, funding and service agreements, care schedules, visits, attendance, visit notes, incidents, complaints, registers, staff profiles, credentials and screening checks, timesheets and pay summaries. Medication support records (what support was given, when, by whom and the outcome) are health information and are sensitive. These records exist so the provider can roster, deliver and evidence care; the provider must have the authority and any consents needed to enter them.
  • Invoices and payments: invoice and credit note details, the payer's name and email, amounts and payment status. When a provider emails an invoice, the payer's email address is used to send it. When a provider offers online payment, the invoice number, amount and payer email are passed to Stripe Checkout so the payer can pay by card; the card details stay with Stripe.
  • Xero: if a provider connects Xero, invoices, credit notes and the related contact names and email addresses are sent to the provider's Xero organisation. Xero access tokens are stored encrypted and can be disconnected from Settings at any time.
  • Online signing: when a provider sends a service agreement for signing, the signer's name and email are used to send the link. On signing we record the typed name, the date and time, the signer's IP address and browser details, and a copy of the agreement exactly as it was shown. This is kept as evidence that the agreement was signed, and the signer is told this before they sign.
  • Audit packs and exports: a provider can export its own records (for example an audit evidence pack, claim files or timesheet exports). These contain the records listed above and are produced only at the provider's request, for the provider.
  • Service operation: sign-in sessions, an audit log of who changed what and when, and the request and security logs our hosting providers keep to run the service and prevent abuse.

We collect only what is needed to run the service. We do not sell personal information, use it for advertising, or use it to train artificial intelligence models.

Emails and messages we send

ACOS sends transactional email only: sign-in and verification codes, team invitations, invoices and payment links, signing links, and notifications a provider asks for. We do not send marketing email. Emails are delivered by Resend on our behalf. When a provider uses ACOS to email its clients or payers, the provider is responsible for having the right to contact them.

Cookies, analytics and tracking

The website and web app use a small number of strictly necessary cookies:

  • a sign-in session cookie, so you stay signed in;
  • acos-appearance, which remembers your light or dark display choice for up to a year;
  • a short-lived security cookie while you connect Xero.

In production the website uses Vercel Web Analytics to count page views. It does not set cookies, does not fingerprint devices and does not identify individual visitors; it records the page, referrer, country and device type only. Because we use only strictly necessary cookies and cookie-free analytics, we do not show a cookie banner. There are no advertising trackers, social media pixels or third-party marketing scripts on the site. Fonts are served from our own site, not from a third-party font service.

Stripe's payment form is embedded from Stripe when you pay. Stripe may set its own cookies inside that form for fraud prevention under Stripe's privacy policy. The ACOS Staff app does not include the website analytics.

ACOS Staff app: what the iPhone app uses

ACOS Staff is the staff app for the ACOS service. Your employer or care provider supplies your account and decides which care and employment records you can access. The separately configured fictional Demo app uses sample records. The Live app connects to the ACOS server; information submitted there is stored by the service. TestFlight is a distribution method and does not by itself make an app a fictional demo.

  • Account and staff information: name, email, mobile number, staff identity, provider, qualifications and staff portrait, to authenticate you and provide staff services.
  • Work information: assigned visits, service addresses, care instructions, availability, shift responses and attendance, to help your provider organise and record care. Hours and any pay summary supplied by your provider are read-only in the app.
  • Submitted records: case notes, daily reports, incidents, selected incident photos and help requests, to document services and allow authorised staff to respond. These records may include sensitive care or health information.
  • Attendance location: your device coordinates when you confirm attendance, linked to your staff account, visit and time so authorised provider managers can verify attendance.
  • Notification registration: an Apple device notification token linked to your signed-in account, for shift notifications when delivery is configured.

The app does not use advertising trackers or request access to your contacts, microphone, entire photo library or continuous location. Do not include passwords or unnecessary client information in support requests.

Location is collected for attendance

The current app asks you to confirm before recording attendance. Check-in requires a current location and iPhone location permission. Check-out includes a location if permission is granted and a location is available; otherwise it records the time without coordinates. Older versions and their previously queued actions may omit coordinates.

There is no continuous or background location tracking. The app accepts the location accuracy allowed in your iPhone settings. Authorised provider managers can view saved attendance coordinates and open them in Apple Maps.

You can deny or revoke access in iPhone Settings. You can still read your day and use other features. If you cannot share location, ask your provider to help record attendance. Revoking permission stops future access but does not remove locations already submitted.

Photos, device unlock and notifications

Apple's photo picker shares only the image you select. You can review or remove it before submitting an incident. The app uploads the chosen image with the report and does not request camera or full photo-library access.

Face ID, Touch ID or your device passcode unlocks saved visits when you return to the app. Apple performs device authentication; ACOS does not receive biometric templates or your device passcode.

Notifications are optional and can be turned off in iPhone Settings. Turning them off does not prevent access to the app. Check your roster and offers in the app. Notifications do not accept shifts automatically.

Who we share information with, and where it is stored

Your provider's authorised staff can access records needed for their role. Each provider's workspace is kept separate, and mobile requests are scoped to your account and provider. Server audit records identify who performed recorded actions.

We use these service providers to run ACOS. They process information only to provide their service to us:

  • Vercel (application hosting and cookie-free web analytics) and Neon (database). Both may process information outside Australia; the database is hosted in the United States.
  • Stripe (subscription payments and invoice payment links). Stripe processes payment data under its own privacy policy and may do so outside Australia.
  • Resend (sending email), which processes recipient addresses and email content, including outside Australia.
  • Xero, only for providers that choose to connect it, and only the invoice and contact data described above.
  • Apple, for notification delivery and device authentication in the ACOS Staff app.

Opening an address in Apple Maps or a website link shares that request with the destination service under its own privacy terms. We do not otherwise disclose personal information unless the law requires it or you ask us to.

The ACOS Staff app keeps its session token in the iPhone Keychain and does not save your password. It uses protected local storage for saved visits and pending check-ins, check-outs and case notes. Pending actions sync when a connection is available. Signing out clears those local records, including any unsynced actions, but does not delete records already on the server.

How we protect information

Connections to ACOS are encrypted (HTTPS). Passwords are stored as one-way hashes, Xero tokens are encrypted at rest, and access to records is limited by role and by provider workspace. Changes to records are written to an audit log. No system is perfectly secure; if we become aware of a data breach likely to cause serious harm we will notify affected people and the Office of the Australian Information Commissioner as the Notifiable Data Breaches scheme requires.

Retention, access, correction and deletion

Your provider manages retention of employment and care records, which may be subject to aged care, NDIS and employment record-keeping rules. Server attendance and audit records do not currently have an automatic deletion schedule. They remain until an authorised retention or deletion process removes them. Ask your provider which retention requirements apply to your records.

Provider owners can update account and billing details in Settings and can export their records at any time. When a subscription ends, contact us to arrange an export or deletion of the workspace.

Use Help → Support → Privacy or data request in ACOS Staff to request access to or correction of your information. Use Profile → Delete my account to initiate an account and associated-data deletion request. Requests are sent to your provider for manual handling; submitting a request is not itself deletion and your account stays active until it is processed.

Account-deletion requests are handled manually within 14 calendar days. You will receive confirmation when processing is complete. Your provider must identify any records it needs to retain and explain the reason. You can also request access, correction or deletion by emailing support@acossystems.com, including when you cannot sign in. Sign-out, uninstalling the app and revoking device permissions do not delete server records.

Questions and complaints

Email support@acossystems.com for support, privacy enquiries or account-deletion requests. If an email app does not open, copy the address into your email service. Do not send passwords or client care details. We aim to respond within 30 days.

If you are not satisfied with our response, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.

Signed-in staff can send a request through Help → Support and follow its status in Help. For access problems, contact your company administrator using your usual workplace contact details.

Open ACOS support

Changes to this notice

We will update this notice when the service changes. The date at the top shows the current version.