Privacy Policy
Version 2026-11-08. This is the privacy policy of AccurateHR ("we", "us"), the business that runs the AccurateHR service. It covers two groups of people, and it says which is which because the rules differ.
1. Who we are talking to
- Visitors and customers. People who visit accuratehr.co, use the sign-up form, start a trial, or run an AccurateHR account for their business. We decide how this information is used, so this policy is the full story for it.
- People whose details are in an AccurateHR account. An employer ("our customer") puts its staff's information into AccurateHR, and staff add some of their own. The employer decides what goes in and what it is used for. We look after the data and run the service for them (we are their service provider). If you are one of those people, your employer's own privacy policy applies to how they use your information, and you should ask them first about anything in your account. We will help the employer answer you.
2. What we collect
When you sign up or enquire (the form on accuratehr.co): your company's name, your name, your email address, how many people you have, and a record that you accepted our Terms and this policy (and which version, and when). To protect the form from abuse we also use your internet address for rate limiting, kept only as a one-way scrambled value (a hash), and we use Cloudflare Turnstile to tell people from bots.
When you use an account. What the employer and its staff enter. That can include, for each person: name, email, phone, date of birth, pronouns, photo, home address, emergency contact, job title, department, employment type, start and end dates, award and classification, leave requests and balances, timesheets and job cards, expense claims, licences and tickets with their expiry dates, documents and policies they have signed, onboarding and review records, one-on-ones, workplace safety reports (which can include injuries and other health information), and plant and asset records. Every account starts with a "Banking & super details" form that staff can fill in for payroll: bank name, account name, BSB, account number, super fund details and, optionally, a tax file number. Whether a customer uses it, and what else it asks for, is the customer's choice (they can edit or remove it). Uploaded documents can contain anything, for example a medical certificate or a copy of a licence. Bank details and tax file numbers entered on that form are stored like the rest of the account's information, behind the same protections (section 5). We do not add a separate layer of encryption to individual answers. A customer should ask its staff for a tax file number only if it is entitled to.
Technical information. Signing in to the application sets a session cookie in your browser, so you stay signed in (up to 30 days, renewed while you keep using it). It is needed for the service to work and is not used for tracking. Our public website sets no cookies of its own and loads no advertising or third-party analytics scripts.
We do count visits to the website ourselves, so we can tell which of our ads and links bring people to us. When a page loads, it tells our systems the page, the link or website that brought you here (and any campaign tag on the link), how long the page was open and how far down you read, the country, state and city your connection appears to come from, and the kind of device and browser you use, as a few general words. We do not keep your internet address, and we do not keep any number that follows you from one visit to the next: your browser holds a random visit number only while the tab is open, and a visit is counted with a scrambled value that changes every day, so people can be counted but not found. We keep these counts for 400 days. If your browser asks websites not to track it (Global Privacy Control), we count nothing. If you then sign up, we connect the sign-up to the visit that led to it, so we know which of our links worked.
Computer programs (search engines' crawlers, scripts and automated browsers) load web pages too, and we do not want them counted as people. So we also look at a few technical details of each visit and rate it as a person, probably a person, a suspected bot or a bot. They are: the kind of network the visit came from (we note the name of a cloud or hosting provider when that is what it was, and never the name of an ordinary internet provider or of a company); what your browser sends with every request, such as its language; and, from the page's own script, the width of the browser window, whether the device has touch, the browser's language and time zone, whether the browser says it is being driven by automation, and whether anything on the page was moved, clicked, typed in, scrolled with a wheel or touched. The time zone is compared with where your connection appears to come from and then forgotten, and we never see where you moved or clicked, what you typed, or when. We keep the rating, the reasons for it, the browser's language as two letters and the window width as a rough band (for example "phone-sized"), with the other counts above, and nothing that could identify you. If your browser asks websites not to track it, none of this is looked at either.
The sign-up form and the contact form load Cloudflare Turnstile, a bot check. It runs in your browser and sends Cloudflare information about the browser and how it behaves, so it can tell people from automated programs; Cloudflare's own privacy policy covers what it does with that. Our systems also keep the emails we send for an account (who they went to and whether they were delivered) so we can fix problems.
3. Why we use it
To set up and run your trial or account, to email you about it (confirming your address, signing in, and keeping in touch before a trial ends), to keep the service secure and stop abuse, to fix problems and answer questions, and to meet our legal obligations. We do not sell personal information and we do not use what is in a customer's account for advertising. We do not do marketing emails to people who have not asked for them, and if we ever start sending newsletters or offers they will go only to people who have asked, and each one will say how to stop. If you write to us, we use what you send only to reply to you and to keep a record of the conversation with the right customer.
4. Who else sees it
We use other businesses to run AccurateHR. They handle information only to provide their service to us:
- Cloudflare, which hosts the website and the application and holds the databases and uploaded files, provides the Turnstile bot check, and receives the email sent to our addresses before passing it to our systems.
- Resend, which sends the emails (sign-up confirmations, sign-in details, notifications, and our replies to you). It handles the content of each email it sends.
- If a customer connects them: Xero (payroll), Dropbox (documents) and simPRO (jobs). We only talk to them for that customer, with the customer's own account.
- Stripe, which takes card payments when a customer subscribes. You enter your card details on Stripe's own page, not ours, and we never see or keep full card numbers. Stripe tells us the customer's reference, the plan and number of people being paid for, whether the subscription is active, and whether a payment failed. Stripe's own privacy policy covers what it collects.
AccurateHR runs on Cloudflare's global network. We have not chosen a country for where information is stored, so we do not promise one. Some of these providers handle information outside Australia, for example in the United States, so information may be stored or processed there. We use them only to run AccurateHR. We may also disclose information when the law requires it.
Inside a customer's account, who sees a person's information is set by the customer: staff see their own records, managers see their direct reports, and administrators see everyone in their own company. A customer cannot see another customer's information. Our own staff who run the service use an operator console that manages companies and their plans, not their people's records, and the changes they make there are logged. When we need to look inside a customer's account to help with a support request, we can do that only if the customer has agreed to it for that request, for a limited time, and each look is logged. Access to the hosting accounts is limited to the people who run AccurateHR, and is used to run, fix and secure the service, not to read a customer's records.
5. How we protect it
Each customer's information is kept separate from every other customer's in our systems, and we test that. PINs are stored scrambled (hashed), never in readable form. Connections to the service are encrypted. An account is locked for 15 minutes after 5 wrong PINs. No system is perfectly secure. If we find that personal information has been accessed or lost in a way likely to cause serious harm, we will assess it promptly and, where the law requires, tell the people affected and the Office of the Australian Information Commissioner. For information in a customer's account we will tell the customer's administrators first, as soon as we have confirmed it, so they can meet their own obligations.
6. How long we keep it
- Sign-ups that never confirm their email: we delete the sign-up 90 days after it was made.
- Messages you send us (through the contact form or by email): we keep the conversation, as plain text (we do not keep attachments, only their names), so we can answer you and remember what was said. We keep each conversation for two years after its last message, then delete it. Messages we mark as spam are deleted after 30 days. You can ask us to delete a conversation sooner.
- Website visit counts: 400 days. A visit we rate as a bot or a suspected bot is kept for 30 days instead, and so is a test visit from our own team's connections (see section 2).
- Trials and accounts: while the account is open.
- After an account is cancelled: we keep the customer's data for 30 days so they can collect it, then delete it within a further 30 days.
- Records we must keep (for example invoices, and the payment records Stripe gives us) for as long as the law requires.
7. Your choices and rights
You can ask us for the personal information we hold about you, and ask us to correct it. For information in a customer's account, ask your employer first; we will help them respond. To ask us, or to ask us to delete a sign-up, contact hello@accuratehr.co. We will answer within 30 days. If you are not happy with how we have handled your information you can complain to us, and then to the Office of the Australian Information Commissioner (oaic.gov.au).
8. Changes
We will update this page when things change, and change the version number above. If a change matters to you we will tell the account's owner by email.
9. Contact
AccurateHR. hello@accuratehr.co.