If you're moving your customer data into a CRM, two Australian laws should be on your radar before you send a single campaign: the Privacy Act 1988 and the Spam Act 2003. Neither one is a reason to avoid a CRM. Used properly, a CRM like Bitrix24 actually makes it easier to stay on the right side of both, because consent, contact history and unsubscribes all live in one place instead of being scattered across inboxes and spreadsheets.
This guide walks through what each law means in practice, where Bitrix24 stores your data, and the settings we recommend for Australian teams. It's written for business owners and sales managers, not lawyers.
Quick note: this article is general information, not legal advice. Privacy law is changing, so check your own obligations with a qualified adviser or the OAIC and ACMA websites.
✓ The Spam Act applies to almost every business that sends marketing emails or SMS, regardless of size.
✓ Every commercial message needs consent, clear sender details and a working unsubscribe option.
✓ Most businesses under $3 million turnover are still exempt from the Privacy Act, but there are important exceptions.
✓ Bitrix24 cloud data is hosted overseas. If your data must stay in Australia, the self-hosted edition is an option.
The Spam Act 2003: the one that affects almost everyone
The Spam Act covers commercial electronic messages: emails, SMS, MMS and instant messages that promote your products or services. Unlike the Privacy Act, there's no small business exemption. If you send marketing messages from Australia, it applies to you. It's enforced by the Australian Communications and Media Authority (ACMA), which regularly publishes penalties against well-known brands.
Every commercial message you send needs three things:
1. Consent. Either express consent (the person opted in, for example by ticking a box on your website form) or inferred consent, where there's an existing relationship and they'd reasonably expect to hear from you. Inferred consent is narrower than most people think, and bought or scraped lists never count.
2. Clear identification. Your business name and a way to contact you.
3. A working unsubscribe. It has to be easy to use, and opt-outs should be actioned within five working days.
How to handle this in Bitrix24
• Add a Marketing consent field to leads and contacts, and record how and when consent was given (web form, phone call, event).
• Use Bitrix24 CRM forms with an unticked opt-in checkbox, so consent is captured automatically when a lead comes in from your website.
• Build marketing segments that only include contacts with consent, rather than emailing your whole database.
• Make sure every email template includes your business name, ABN or contact details and an unsubscribe link.
• Set up an automation rule that updates the contact record the moment someone unsubscribes, so sales reps can see it too.
If you're sending SMS from Bitrix24 through an Australian SMS provider, the same rules apply: identify yourself and include an opt-out such as "Reply STOP to opt out".
The Privacy Act 1988: who it applies to
The Privacy Act and its 13 Australian Privacy Principles (APPs) set the rules for how organisations collect, use, store and disclose personal information. Right now, most businesses with annual turnover of $3 million or less are exempt from the general APP regime.
That exemption has some big exceptions, though. A small business is still covered if, for example, it:
• provides a health service and holds health information (think allied health, clinics and some NDIS providers)
• trades in personal information, such as buying or selling customer data
• is a contracted service provider under a Commonwealth contract
• has chosen to opt in to the Privacy Act
The law is also moving. The Privacy and Other Legislation Amendment Act 2024 introduced new rights and obligations in stages, including transparency rules for automated decision-making that start on 10 December 2026. The government has agreed in principle to remove the small business exemption, but at the time of writing no start date has been legislated.
Our practical advice: even if you're currently exempt, set up your CRM as if the APPs apply to you. It's good practice, customers increasingly expect it, and it saves a scramble if the exemption is removed.
Where does Bitrix24 store your data?
This is one of the first questions Australian clients ask us. Bitrix24 cloud runs on Amazon Web Services. Data is generally stored in the region linked to the Bitrix24 site you sign up through, and Bitrix24's own infrastructure documents list data centres in the United States and Europe. There's currently no Australian hosting region for the cloud version.
For most small and medium businesses that's fine, as long as you're upfront about it. Under APP 8, if you're covered by the Privacy Act and personal information is sent overseas, you're expected to take reasonable steps to make sure it's protected. Your privacy policy should say that customer data may be stored overseas.
If your contracts, industry rules or customers require data to stay onshore, Bitrix24 offers a self-hosted (On-Premise) edition. You run it on your own servers, which can be located in Australia, and you control the backups and security. It needs more technical work to maintain, so it's worth discussing before you choose.
A simple privacy checklist for your Bitrix24 setup
• Collect only what you need. Don't add CRM fields "just in case". Every extra field is more personal information to protect.
• Use access permissions. Bitrix24 lets you set role-based permissions, so a sales rep only sees their own leads and deals, and sensitive fields are hidden from people who don't need them.
• Turn on two-step authentication for every user, especially admins.
• Offboard properly. When someone leaves, deactivate their account the same day and reassign their records.
• Keep your privacy policy current. Mention that you use a CRM, what you collect and that data may be stored overseas.
• Have a data breach plan. If you're covered by the Privacy Act, eligible data breaches must be reported to the OAIC and affected people under the Notifiable Data Breaches scheme.
• Clean up old data. Set a regular review to delete or anonymise records you no longer need.
Getting it right from day one
Most compliance problems we see aren't caused by bad intentions. They come from messy data: old spreadsheets imported without consent details, a shared login nobody controls, or a campaign sent to "everyone" because segments were never set up. A well-planned Bitrix24 implementation fixes all of that at the start.
If you'd like help setting up consent fields, permissions and compliant email and SMS workflows, our team can do it as part of a Bitrix24 implementation. You can also read our guides on Bitrix24 automation and Bitrix24 CRM for Australian sales teams.
Frequently asked questions
Does the Spam Act apply to my small business?
Yes. Unlike the Privacy Act, the Spam Act 2003 has no small business exemption. If you send commercial emails, SMS or instant messages from Australia, you need consent, clear sender identification and a working unsubscribe option.
Is Bitrix24 data stored in Australia?
Bitrix24 cloud data is hosted on Amazon Web Services in overseas regions such as the United States or Europe. If your data needs to stay in Australia, the self-hosted Bitrix24 On-Premise edition can run on Australian servers.
Is my business covered by the Privacy Act?
Most businesses with annual turnover of $3 million or less are currently exempt, but there are exceptions, including health service providers and businesses that trade in personal information. Check with the OAIC or a privacy adviser for your situation.
Can Bitrix24 record marketing consent?
Yes. You can add custom consent fields to leads and contacts, capture opt-ins through Bitrix24 CRM forms and use automation rules to update records when someone unsubscribes.