Privacy Policy

Last updated 30 October 2026

This policy explains what personal information NeatSum Pty Ltd collects when you use NeatSum, why we collect it, who else sees it, and what you can ask us to do about it. It is written to meet our obligations under the Privacy Act 1988 (Cth) and the Australian Privacy Principles.

NeatSum is accounting software. Most of what you put into it is information about your business (invoices, bills, payments, payroll), and some of that is personal information about real people: your customers, your suppliers and your employees. You are responsible for what you enter about them. We are responsible for what we do with it.

What we collect

Information you give us. Your name and email address when you create an account, and the mobile number you confirm with a code we send by text message. Your company's details, including its ABN, addresses and financial year settings. Everything you record in the product: contacts, invoices, bills, payments, bank transactions, inventory, fixed assets, and payroll records, which include employee names, pay rates, tax file number declarations where you enter them, superannuation details and bank account numbers for payment. Receipts you upload, photograph or email to your company's receipts address: the image or PDF itself, and for emailed receipts the sender's address and the subject line.

Information we generate. An audit log of actions taken in your company: what changed, when, and which user did it. Access logs recording sign-ins, IP addresses and browser user-agent strings. A record of when you last used NeatSum, which our support staff use to help you and to notice activity that looks wrong; the people you share a company with cannot see it.

Information from your bank, if you connect one. If you use bank feeds, you first connect your bank to your own openfeed account under the Consumer Data Right, with the consent you give on openfeed's and your bank's screens. You then choose which accounts openfeed shares with NeatSum, and openfeed passes us, for those accounts, their names, account numbers, balances and transactions. For a business, the connection is made by someone your bank allows to share the business's data. We never see or store your online banking credentials; you give those to your bank, not to us. You can stop sharing with NeatSum at any time in your openfeed account, and disconnect an account from Bank feeds in NeatSum; your bank also asks you to renew the connection once a year. When sharing ends we stop collecting. Bank transactions already imported stay in your books as accounting records, and are deleted with your company.

Where it is stored

In Australia. The application runs on Amazon Web Services in the ap-southeast-2 (Sydney) region, and the database is hosted by Neon in the same region. Data is encrypted in transit using HTTPS. Some of the services listed below handle particular information outside Australia; each one says where.

Who else sees it

We do not sell your information and we do not share it for advertising. We use the following processors, each of which receives only what it needs to do its job:

  • Google Firebase (Firebase Authentication), for signing in, in the United States. Receives your email address and password, and sign-in details such as your IP address and device, and sends the email-verification and password-reset emails. You sign in to NeatSum with your email address and password only. If you used to sign in with Google, Firebase also still holds the name and email address from your Google profile. Google keeps your password only in a scrambled (hashed) form; we never see or store it.
  • Neon, our database provider. Your accounting records, your account and company details, and the audit and security logs are stored in Neon's database in the Sydney region. Neon is part of Databricks, Inc., a company in the United States, whose staff may be able to access the database from outside Australia to run and support the service.
  • Amazon Bedrock (part of Amazon Web Services), for AI features, in Australia. When you use AI categorisation or the assistant, the relevant transaction descriptions, amounts, account names and contact names are sent to Amazon Bedrock to produce a suggestion, and the assistant also sends what you type and the figures it looks up to answer you, such as report and GST or BAS amounts. The AI model runs on Amazon Web Services in Australia, so this information does not leave Australia. Amazon Bedrock does not keep these questions and answers, does not use them to train AI models, and does not share them with the company that made the model.
  • openfeed (operated by Biza Pty Ltd), for bank feeds, if you connect an account. Biza is an Australian business accredited under the Consumer Data Right. openfeed holds the bank data you connect under its own terms and privacy policy, and passes us only the accounts you choose to share with NeatSum.
  • Stripe, for payments, if you pay for a subscription or use payment links. Stripe handles card details directly; we never receive your full card number.
  • Zoho (Zoho Mail and ZeptoMail), for the email we send and receive: sign-in and account notices, payment reminders to your customers, the emails you send to our support address, and, where emailing is turned on for your company, the invoices, quotes, credit notes and statements you choose to email to your customers. Zoho stores and sends this email from its Australian data centres.
  • Amazon Web Services, for hosting and storage, and for sending the verification codes for your mobile number (from the Sydney region). AWS also receives receipts emailed to your receipts address, and, if receipt reading is switched on for your company, Amazon Textract reads the receipt image to pick out the supplier, date, total and GST. Both run in the Sydney region, so the receipt does not leave Australia. Receipt reading is only switched on once we have opted out of AWS using this content to develop or improve its own services.
  • Sentry, for error reporting, when enabled, stored in the United States. Receives the technical details of a failure: the stack trace, the page or API path it happened on, and the internal numeric identifiers for your company and user account. It does not receive the contents of your forms, your session cookie, your email address, or the query part of a web address. Tax file numbers, ABNs and account numbers are masked before anything is sent. An error message can still quote a name it was handling, for example the contact a failed operation was about.
  • Crisp, for live chat with NeatSum support, in the European Union (the Netherlands and Germany), where chat is switched on for your company. Nothing is sent to Crisp until you first open the chat; after that, Crisp loads when you use NeatSum in that browser, so our replies can reach you. It receives your name, email address, your NeatSum user number, the number and name of the company you have open, your role in it and its plan, what you write in the chat and any file you attach, and the technical details every website receives, such as your IP address and browser. It also sees which screen you are on: we send it with record numbers removed, but Crisp's own chat window can see the web address of the page, which can include a record number (never an amount). It does not receive your invoices, bills, amounts, bank details, payroll or reports; please do not paste passwords, bank details or tax file numbers into the chat. When our chat plan supports it, your email address is signed by our server so nobody else can chat as you; until then, Crisp shows it as unverified and we confirm who you are before discussing your account.

Google (for Firebase Authentication, which everyone uses to sign in), Stripe and Sentry are located outside Australia, in the United States, and Crisp in the European Union. Neon keeps our database in Australia, but is a United States company whose staff may access it from overseas to run the service. By using NeatSum, and the features that rely on these providers, you consent to that disclosure under Australian Privacy Principle 8.

How long we keep it

We keep your records for as long as your company is in NeatSum. Australian tax law generally requires a business to keep its records for five years. NeatSum holds them for you while your company exists, so export what you need before you delete a company.

You can delete individual records in the product. A company's owner can delete the company: its records are removed from the live system straight away. A company with a locked or closed accounting period, or a finalised or lodged BAS, cannot be deleted this way, because those records must be kept; contact us if it must go. A deleted company's audit trail is kept for about 13 months (400 days) for security purposes, then deleted. Backups are overwritten on their own cycle.

You can delete your account in the NeatSum app (Settings, Delete my account), or by emailing us at support@neatsum.com. This deletes your sign-in and personal details and removes you from every company. The companies' books stay with the business, so an account that still owns a company is transferred or closed first. We keep what the law requires us to keep (such as our records of subscription payments you made to us) and our security log of your sign-ins and two-factor checks (400 days), and delete each when its period ends. See Delete your account for the steps.

Asking us about your information

You can ask for a copy of the personal information we hold about you, ask us to correct it, or complain about how we have handled it. Write to support@neatsum.com. We will 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.

Security, stated plainly

Traffic is encrypted with HTTPS. Each company's data is kept apart by our data-access layer, which refuses any database query that is not limited to one company, and every change is recorded in an audit trail you can read. Passwords are handled by Firebase and never stored by us.

Two-factor authentication is required for everyone, at every sign-in. You set up an authenticator app, and after your email and password you enter a code from it, or use a passkey (such as Face ID, Touch ID, Windows Hello or a security key) if you have added one, or one of your recovery codes. The private part of a passkey stays with you, on your device or in your password manager; we keep only its public key. The secret your authenticator app shares with us is stored encrypted, and your recovery codes are stored only as one-way hashes. Each sign-in lasts at most 23 hours before you are asked to sign in again. (API keys, which only a signed-in user can create, are not a way of signing in and do not ask for a code.) We hold no third-party security certification such as SOC 2 or ISO 27001.

Cookies and website analytics

NeatSum uses browser storage to keep you signed in and to remember preferences such as your selected company. We do not use advertising or third-party tracking cookies.

How we count visits. We count visits to our website ourselves, without cookies and without any analytics company. When you open a page, your browser tells our own server which page it was, the name of the website that sent you (for example google.com, never the page you were on there), any campaign tags in the link (such as utm_source), and whether you are on a phone or a computer. If our hosting provider tells us the country a visit comes from, we record the country too. We record the day of the visit, not the time. Our analytics do not keep your IP address or your browser's details. (Like any website, our servers' short-term technical logs record requests, including IP addresses, for security and troubleshooting; they are not used for analytics.)

To count each visitor once a day, our server combines your IP address and browser details with a random value that changes every day, turns them into a one-way code (a SHA-256 hash) and keeps only the code. The random value is held only in our server's memory, never written to our database, and is thrown away when the day ends. After that the code cannot be traced back to your IP address, and tomorrow you are a new, unrelated visitor: we cannot follow you from one day to the next or onto other websites. Visits to our website and use of the app are counted with separate codes, so they cannot be linked to each other. Nothing is shared with anyone else. If your browser sends a Do Not Track or Global Privacy Control signal, nothing is counted.

While you are on the site, the page you arrived on, the site that sent you and any campaign tags are kept in your browser's session storage, which is cleared when you close the tab. If you create an account they are saved with it, so we know which pages and campaigns bring people to NeatSum. Inside NeatSum we count which screens are opened in the same way, without your name, and we record a few milestones for your account and company (such as creating your first invoice) to see whether NeatSum is working for new customers.

Individual page-view records are deleted after 13 months. Daily totals (for example, how many visits a page or a campaign had each day) are kept.

Opting out. You can stop this browser's visits being counted at all. The choice is remembered in this browser's local storage.

Changes

If we change this policy we will update the date at the top. If a change materially affects how we handle your information, we will tell you.

Contact

NeatSum Pty Ltd (ACN 702 837 778, ABN 26 702 837 778): support@neatsum.com