Optimizing CRM Data Privacy: A How-To for NZ Businesses - Web Maniacs

Optimizing CRM Data Privacy: A How-To for NZ Businesses

  • Admin
  • 16, Nov, 2026
  • Blog

Quick Summary

Good crm data privacy for a New Zealand business starts with the Privacy Act 2020, which applies to any business holding personal information in a CRM regardless of size. Map each of its 13 Information Privacy Principles to your CRM, collect only the data you need, and restrict access by role.

  • Map each of the 13 Information Privacy Principles to the places your CRM collects, stores and shares data.
  • IPP 3A applies to agencies collecting personal information indirectly from 1 May 2026.
  • Use role-based permission sets, field-level visibility and MFA on every account.
  • Set a retention table with defined periods, triggers and owners, then verify deletion across connected systems.
  • Review connected apps every few months and remove any integration you no longer use.
Is your CRM keeping customer data safe?Web Maniacs reviews CRM access, integrations and retention settings for NZ businesses.

Audit Your CRM Privacy

Table of Contents

Mapping the Privacy Act 2020 Principles to Your CRM

If your business holds customer details in a CRM, the Privacy Act 2020 applies to you, and good crm data privacy practice starts with that obligation. The Act is run by the Office of the Privacy Commissioner, and its 13 Information Privacy Principles (IPPs) cover how personal information is collected, stored, used and shared.

Start by walking through each principle and asking where it touches your CRM. A few examples:

  • Collection (IPP 1-4): Every form, sign-up page and phone script that feeds the CRM needs a clear purpose.
  • Storage and security (IPP 5): Access controls and encryption protect what sits in the database.
  • Access and correction (IPP 6-7): Customers can ask to see and fix what you hold about them, so your CRM must make that possible.
  • Use and disclosure (IPP 10-11): Marketing emails and third-party integrations count as uses and disclosures.

IPP 3A is the one to watch right now. Agencies collecting personal information indirectly are expected to comply with it from 1 May 2026, according to DLA Piper’s guide to New Zealand data protection laws. If your CRM imports leads from purchased lists, social platforms or partner referrals, you need to make sure those people know how their details will be used.

Watch out: Many small businesses assume the principles only apply to large companies. They apply to any business that holds personal information, regardless of size.

Collecting Only the Customer Data You Need

The simplest way to protect customer data is to hold less of it. Under the Privacy Act, you should only collect personal information that serves a clear, lawful purpose for your business, because strong crm data privacy depends on it. This is often called data minimisation.

Before adding a new field to your CRM, ask three questions:

  • Do we need this to deliver the service or respond to the customer?
  • Would a customer expect us to ask for this?
  • What will we do with it, and for how long?

If you can’t answer all three, leave the field out. A lean record is easier to secure, cheaper to maintain and simpler to correct when something goes wrong.

Office of the Privacy Commissioner guidance for small business sets out practical advice on this, including checking whether each piece of information is genuinely needed.

CRM Data Security Best Practices

Security is where most CRM privacy problems start.

Small business owner in a New Zealand office managing crm data privacy settings on a laptop
Small business owner in a New Zealand office managing crm data privacy settings on a laptop

Work through these controls in order. For the website side, harden your WooCommerce store against malware and brute-force attacks before customer data reaches the CRM.

  • Role-based access via permission sets, not shared logins. Build roles around job function (sales, service, finance, admin) and assign permission sets that grant the minimum object and field access needed. A common pattern is to give sales staff read/write on their own accounts and read-only on accounts owned by others. Never let staff share a single login; shared credentials destroy the audit trail and make offboarding unreliable.
  • Field-level visibility for sensitive data. Most cloud CRMs let you hide specific fields from specific roles. Use this for anything that is not needed to close a deal or resolve a case, such as date of birth, home address, payment references or health notes. Hiding a field is stronger than training staff not to look at it.
  • Multi-factor authentication on every account, enforced at the organisation level. Turn on MFA for all users, not just admins, and require it for API and integration accounts. Where the CRM supports IP allow-listing or login-hour restrictions, apply them to admin roles first.
  • Encryption in transit and at rest, plus export controls. Confirm the CRM uses TLS for all connections and encrypts stored data. Then restrict who can export records or run bulk reports, because an export is the fastest way for a large volume of personal information to leave your control. Log every export and review the log monthly.
  • Audit logs and a review cadence. Enable audit logging for record views, edits, exports and permission changes. A monthly review of admin actions and a quarterly review of export activity catches both mistakes and misuse. Keep logs long enough to support an investigation.
  • Joiner, mover, leaver process. Remove access on the day someone leaves, and review role changes within a week. A quarterly access review that lists every user, their role and their last login is a simple control that satisfies the reasonable-steps test.
  • Backup and recovery testing. Confirm how the provider backs up data, how long recovery takes, and whether you can restore a single record or a whole org. Test a restore at least once a year.

Staff training matters as much as technology. A short, regular briefing on phishing, password managers and the risks of exporting contact lists prevents many breaches. Record who attended so you can show you took reasonable steps.

Watch out: Every connected app inherits the permissions of the user who authorised it, so an unused integration can quietly hold broad access to your CRM long after the project that created it has ended.

If you run a WooCommerce store that feeds customer data into your CRM, Web Maniacs guide to securing a WooCommerce store covers the website side of the same risk.

Consent is about making sure customers know what you will do with their information. Under the Privacy Act, people should understand why you are collecting their details. For marketing, you also need to respect their choices about receiving messages.

In practice, a consent process in your CRM should:

  • Record when and how each person agreed to be contacted
  • Keep marketing preferences separate from service information
  • Make it easy to withdraw consent, with unsubscribe options in every message
  • Stop marketing to anyone who has opted out, even if they are still a customer

Keep privacy notices short and specific. Tell people what you collect, why you collect it and who you share it with. Avoid burying key details in long legal text.

Cloud CRM Privacy Considerations

Most small businesses now run cloud-based CRMs. These systems can be secure, but you remain responsible for the personal information you put in them, including what the provider does with it.

Before you choose a provider, check: how a SaaS integration connects and shares data between tools, since each connection changes who can see your records.

  • Where the data is stored, and whether it leaves New Zealand
  • How the provider handles security incidents and notifies customers
  • What integrations are connected, and what data each one can read
  • Whether the provider uses your data to train its own products

Privacy obligations can apply when personal information is sent overseas, so check how the receiving party protects it. A recent Datacom State of AI Index report found that 83% of senior leaders worry about offshore data risks, yet only 35% have policies for managing critical data.

Watch out: Every app connected to your CRM is another place personal information can leak. If you are weighing up a connection to accounting software, see whether a Xero API integration is worth it for a small business.

CRM Data Retention Policy and Secure Deletion

Holding personal information forever is a privacy risk.

A workable retention policy is a table, not a paragraph. For each record type, define the purpose, the retention period, the trigger that starts the clock, the owner who approves deletion, and the method of deletion. A common starting point looks like this:

  • Marketing leads that never converted: retain for 12 to 24 months from last engagement, then delete or anonymise. Trigger: no opens, clicks, calls or meetings in the period.
  • Closed customer accounts: retain for the period required by tax and contract law, then delete operational data. Trigger: end of the statutory retention period.
  • Support cases and complaints: retain for 24 months after resolution, then delete, unless the matter is part of a legal dispute.
  • Attachments and email threads: apply the same schedule as the parent record; do not let them outlive it.
  • Backups: align the backup retention window with the policy so deleted records age out of backups on a known schedule.

Translate the table into CRM mechanics. Most cloud CRMs support scheduled reports that surface records past their retention date, and some support automated deletion rules or field-level anonymisation.

Deletion is more than pressing delete. Check four places before you consider a record gone:

  1. The CRM record itself, including related notes, attachments and activity history.
  2. Connected tools that sync contacts, such as email marketing platforms, accounting software and helpdesks. Deleting in the CRM does not always propagate.
  3. Exports and spreadsheets held by staff. A quarterly reminder to clear old exports is a practical control.
  4. Backups, which should age out on the schedule you set with the provider.

Accuracy sits alongside retention. Build a review into your CRM workflow: prompt account owners to confirm key contact details annually, and give customers an easy way to correct their information.

Watch out: Deleting a contact in the CRM often leaves the same person in marketing lists, support tickets and backups, so a deletion that is not verified across connected systems is not a deletion at all.

The article sets out a starting retention schedule for each record type, so here is a summary a reader can scan.

Record type Retention period Trigger
Marketing leads that never converted 12 to 24 months from last engagement No opens, clicks, calls or meetings in the period
Closed customer accounts Period required by tax and contract law End of the statutory retention period
Support cases and complaints 24 months after resolution Resolution, unless part of a legal dispute
Attachments and email threads Same schedule as the parent record Parent record’s deletion date
Backups Aligned with the policy Backup window set with the provider

Your Next Step: Auditing Your CRM Privacy Settings with Web Maniacs

Start with one practical task this week: export your CRM user list and check who still has access. Then compare your forms against the principles above and remove any field you can’t justify.

If you want help building a privacy-aware CRM setup, from access controls to integrations and retention rules, Web Maniacs can review your current configuration and suggest practical fixes. Get started with a privacy audit of your CRM and make customer trust part of your growth plan.


Frequently Asked Questions

How can a business improve privacy in its CRM?

Start by mapping what personal information your CRM holds and why, then apply the Privacy Act 2020 principles to each field. Restrict access by role, enable multi-factor authentication, switch on audit logs, and review settings at least twice a year. Document these steps in a short internal policy so staff know what is expected, and check that any integrations with email or payment tools also meet the same standards.

What customer information should a CRM store?

A CRM should store only the personal information needed for a clear, stated purpose, such as name, contact details and a record of past orders or enquiries. Under the Privacy Act 2020, collecting unnecessary data increases your compliance risk. Remove sensitive fields you do not need, avoid free-text notes containing health or financial details, and review each field annually to confirm it still serves a purpose.

How long should customer data be kept in a CRM?

Keep customer data only as long as it is needed for the purpose it was collected for, and no longer. Set a retention period for each category of record, such as inactive leads or closed accounts, and schedule regular deletion or anonymisation. Check your obligations under the Privacy Act 2020, and make sure backups and archived copies are also covered by your deletion process.

What should a business do if personal information in its CRM is exposed?

Act quickly to contain the breach by disabling compromised accounts and changing passwords. Assess what information was affected and who it relates to, and decide whether the breach is likely to cause serious harm. If it is, notify the Office of the Privacy Commissioner and the affected individuals as soon as practicable. Record the incident, review what failed, and update your controls to prevent a repeat.

We Will Maximise Your Business’s
Online Impact and Growth

We craft unique strategies to supercharge your online growth, strengthen your digital presence, and drive remarkable results.