Privacy Policy
EMD Agency Limited
1. About this policy
This policy explains how EMD Agency Limited collects, uses, stores, shares and protects personal information. It is written to meet our obligations under the New Zealand Privacy Act 2020 and the 13 Information Privacy Principles set out in section 22 of that Act.
We have tried to write it in plain language. If anything in it is unclear, or you want more detail about something we do, email us at support@emd.agency and we will answer you.
“Personal information” means information about an identifiable individual. That is the definition the Privacy Act uses, and it is the definition we use here.
2. Who we are
EMD Agency Limited is a New Zealand digital marketing agency. We build and maintain websites, run search and social advertising, do SEO, set up CRM and marketing automation systems, and produce performance reporting for our clients.
| Legal name | EMD Agency Limited |
|---|---|
| Trading as | EMD Agency, EMD |
| Country of incorporation | New Zealand |
| NZ company number | 9424033 |
| GST number | 148-570-493 |
| Website | https://emd.agency |
| Privacy contact | support@emd.agency |
| General enquiries | info@emd.agency |
| Phone | 0800 323 500, or +64 7 211 6450 |
Under section 201 of the Privacy Act 2020 we are required to have a privacy officer. Ours can be reached at support@emd.agency.
3. We have two different roles, and this policy covers both
Most privacy policies describe only a company’s own website. Ours has to do more than that, because we handle personal information in two quite different situations.
Role one. Our own business. When you visit emd.agency, contact us, send an enquiry through one of our ads, apply for a job with us, or become a client, we collect information about you for our own purposes. Part A covers this. In the language of the Privacy Act, we are the agency collecting and holding that information, and we are accountable for it.
Role two. Work we do for our clients. Our clients are businesses. They give us delegated access to their own marketing and CRM systems so that we can run campaigns and produce reporting for them. Some of what sits inside those systems is personal information about their customers and enquirers. Part B covers this. In that situation we are acting on our client’s instructions and for our client’s purposes, and the client is the organisation that decides what happens to that information.
Part B is the part that matters if you are a customer of one of our clients rather than a visitor to our site.
Part A. Our own website and business
4. When you visit our website
4.1 Server and security logs
Our website is hosted on SiteGround’s servers in Sydney, Australia. Like almost every web server, it records technical information about each request. That includes your IP address, the date and time, the page requested, your browser type and, where your browser sends one, the page you came from.
The security software on the site (the SiteGround Security plugin) also keeps a short log of visitor IP addresses and of failed login attempts, so that we can block automated attacks on the site. An IP address can be personal information in some circumstances, so we are telling you about it here rather than leaving it out.
We use these logs to keep the site running, to diagnose faults and to defend the site against attack. We do not use them to build a profile of you, and we do not sell them.
4.2 Google Analytics
We use Google Analytics 4 to understand how people find and use our site. It is loaded through a Google tag on every page. The site also loads a Google Tag Manager container, which is the tool we use to manage the advertising tags described in section 4.3.
Google Analytics tells us things like how many people visited, which pages they looked at, roughly where in the world they were, what device they used, and which pages people leave from. We use that to work out what is useful on the site and what is not.
Google Analytics sets cookies in your browser and sends information to Google. Google is a United States company and processes this information on servers outside New Zealand. We have IP anonymisation on by default in Google Analytics 4, and we have excluded logged-in site administrators from tracking, so our own visits do not distort the numbers.
You can stop Google Analytics collecting information about you by installing Google’s own opt-out browser add-on, available at tools.google.com/dlpage/gaoptout, or by blocking cookies as described in section 5.
We also use Google Search Console, which shows us how our site appears in Google search results. Search Console reports aggregate search data to us. It does not identify individual searchers.
4.3 Advertising tags
At the date of this policy, emd.agency carries two advertising tags. They are Google Ads conversion tracking and the Meta pixel. There is no LinkedIn insight tag on the site, and we do not use Google Ads remarketing or audience lists on this site.
Here is what the Google Ads tag does. When you arrive at our site from one of our Google ads, Google adds a click identifier to the link. Our site stores that identifier in a cookie for up to 90 days. If you then enquire with us, by submitting our contact form or by tapping our phone number on a mobile device, the tag tells Google Ads that the click led to an enquiry. That is how we find out whether our advertising is worth paying for.
Here is what the Google tag does not do. It does not send Google your name, your email address, your phone number, or anything you typed into a form or the chat assistant. It is not used to build an audience, to show you our ads on other sites, or to personalise advertising. Google is a United States company and processes this information outside New Zealand. Section 13 explains the basis on which we send information overseas.
If you enquire with us, we may keep the click identifier with your enquiry in our CRM so that we can later confirm to Google Ads that the click led to a genuine enquiry. We use it for nothing else, and it is deleted with the enquiry under section 11.
The Meta pixel. We run the Meta pixel, supplied by Meta Platforms, on every page of emd.agency. We use it to measure whether our Facebook and Instagram advertising works.
What it collects. The pixel tells Meta which pages a browser viewed, and when someone submits an enquiry form (Meta calls this a Lead event). It also uses a feature called automatic advanced matching. When you submit a form, the pixel reads the contact details you entered, such as your email address, phone number, name, city or region, postcode and country. It scrambles each one into a code (a hash) in your browser and sends the codes to Meta. It does not send Meta the text of your message. Meta can match those codes against its own records to link your visit to a Facebook or Instagram account if you have one, so we treat them as personal information.
Why we use it. To see which of our ads lead to enquiries, to improve how our ads are delivered, and to report on results. Meta may also use the information for its own purposes under its own terms, which are set out in the Meta Privacy Policy at facebook.com/privacy/policy.
Where it goes. To Meta Platforms, a United States company, which processes it outside New Zealand. Section 13 explains the basis on which we send information overseas.
Conversions API. We are also setting up the Meta Conversions API. It reports enquiries to Meta from our server rather than from your browser. When it is running, it will send the same enquiry event and the same scrambled contact details described above, and this section covers it. If what it sends changes, we will update this section first.
How to opt out. You have these options.
- Manage the ads Meta shows you, and the use of your activity for ads, in your Meta ad preferences at facebook.com/adpreferences. Meta also lets you review and switch off activity that businesses share with it at facebook.com/off_facebook_activity.
- Block or delete cookies, use a private browsing window, or install a tracking protection or content blocker in your browser, as described in section 5. This stops the pixel in your browser.
- Email or phone us instead of using a form on the site. Server-side reporting through the Conversions API cannot be blocked from your browser, so this is the way to keep your details from being reported to Meta. You can also tell us at support@emd.agency and we will leave your enquiry out of any report to Meta.
4.4 Maps
Some pages embed a map. We use OpenStreetMap for this rather than Google Maps.
5. Cookies and similar technologies
Cookies are small files a website asks your browser to store. We use them for three things.
Necessary cookies. WordPress, the software our site runs on, sets cookies that make the site work. If you log in as an administrator it sets a session cookie. These cannot be turned off without breaking the site.
Analytics cookies. Google Analytics sets cookies to recognise a repeat visitor and to group page views into a single visit.
Advertising measurement cookies. Google Ads conversion tracking sets a cookie called _gcl_aw that holds the Google click identifier described in section 4.3. Our site also sets a cookie called emd_click that holds the same identifier, together with any campaign labels on the link you arrived by, so that they can be attached to your enquiry if you make one. Both last up to 90 days. Those two cookies are used to measure whether our advertising works. They are not used to build a profile of you or to show you advertising.
Meta pixel cookies. The Meta pixel sets a cookie called _fbp and, when you arrive from a Meta ad, a cookie called _fbc. They identify your browser to Meta, normally for up to 90 days, so that Meta can connect a visit to an enquiry and work out which ads are performing. Section 4.3 explains what else the pixel sends and how to opt out.
We do not show a cookie consent banner on emd.agency. New Zealand law does not require one in the way European law does, and we would rather tell you plainly what is set than show you a banner. You can also control cookies yourself. Every major browser lets you block or delete cookies, and most have a private browsing mode that discards them when you close the window. If you block analytics or advertising cookies, the site will still work normally.
Earlier versions of this policy said we would ask for your consent before sending an advertising platform a personal identifier such as a hashed email address. This version changes that, because the Meta pixel described in section 4.3 now sends hashed contact details to Meta when you submit a form on our site. We do not ask for consent first. We tell you here instead, and section 4.3 explains how to opt out. If we change how we use the pixel in a way that affects you, we will update this policy first.
6. When you contact us
You can reach us by email at info@emd.agency, by phone, through the contact form on our Contact page, or through a Facebook or Instagram lead form as described in section 7. The contact form is supplied by GoHighLevel and asks for your name, phone number, email address and what you need. What you submit is stored in our CRM, which runs on GoHighLevel, and an alert comes to us by SMS and email so that we can reply quickly. GoHighLevel is listed in section 13.
When you email or phone us, we collect what you choose to tell us. That is usually your name, your email address or phone number, the name of your business, and whatever you wrote or said. Our email runs on Microsoft 365.
We use that information to answer you, to prepare a quote or proposal if you asked for one, and to keep a record of what was agreed. If you become a client we keep it as part of the client record. If you do not, we keep the enquiry for the period set out in section 11 and then delete it.
We will not add you to a marketing list because you sent us an enquiry.
7. Meta lead ads
We advertise on Facebook and Instagram. Some of our ads use Meta’s instant forms, which let you send us an enquiry without leaving the app.
What we collect. The form asks for your name, phone number, email address, company and what you need. Meta may fill in some of these fields from your Facebook or Instagram profile, and you can change them before you submit.
Why we collect it. To answer your enquiry and to talk to you about the work you asked about.
Where it goes. Meta receives what you submit and passes it to us. It is synced into our CRM on GoHighLevel, the same CRM described in section 6, and an alert goes to us by SMS and email. Meta is a United States company and processes what you submit outside New Zealand. Meta also keeps its own record of your interaction with the ad, under its own terms. Meta and HighLevel are listed in section 13. We keep the enquiry for the period in section 11.
How to opt out. Submitting a lead form is entirely optional. You can email or phone us instead. You can manage the ads Meta shows you in your Meta ad preferences at facebook.com/adpreferences. If you have already submitted a form and want your enquiry deleted, email support@emd.agency and section 15 applies.
8. The PROVE the R calculator
We host a public technical calculator called PROVE the R on our domain. It works out the R-value of an insulation sample from its dimensions and weight. It was built for a client in the insulation industry and it currently sits on our server while it is being finished.
If you use it, this is what happens.
- The measurements you enter, the density we calculate, and the product we match are written to a usage log so that we can see whether the tool is working and how it is being used. The log does not record your IP address, your name, your email address or any other direct identifier.
- Your IP address is used in two ways at the moment you make a request. It is converted, using a database held on our own server, into a coarse location (country, region, city and a rounded latitude and longitude) which is written to the same log. It is also hashed and used to enforce a rate limit, so that no single user can overload the tool. The hashed value is short-lived and the IP address itself is not stored in the log.
- The calculated result is sent to Anthropic, an artificial intelligence provider in the United States, which turns the numbers into a readable sentence. Only the measurement and result data goes to Anthropic. No personal identifier is sent, because none is collected.
The arithmetic is done by our own software, not by the AI. The AI only phrases the answer.
9. If you apply for a job with us
We advertise roles at emd.agency/careers and take applications through the form at emd.agency/apply-now.
What we collect. The form asks for your first name, last name, email address, phone number, current employment, your right to work in New Zealand, a cover letter, and a CV as a PDF or Word document. All of these are required. We do not ask for your date of birth, your age, your gender, your ethnicity, your marital or family status, your health, or a photograph, and we do not want you to send them.
Why we collect it. To assess whether you are suited to the role, to contact you about your application, and to meet our obligations as an employer. The right-to-work question is asked because we are required to check that anyone we employ is entitled to work in New Zealand.
Where it goes. Your application is stored as a private record in our website’s database, and your CV is stored in a protected folder on the same server. An email notification goes to Chris Ewing at chris@emd.agency. Applications are reviewed by Chris Ewing. We do not send your application to a third-party recruitment platform, we do not add you to our CRM, and we do not add you to any marketing list.
Referees. We will not contact a referee without asking you first.
How long we keep it. See section 11.
If you would like your application deleted at any point, email support@emd.agency and we will delete it and your CV.
10. Clients, prospective clients and suppliers
If you are the contact person at a business we work with, or want to work with, we hold your name, work email address, work phone number, job title and our correspondence with you. We hold this to run the engagement, to invoice, to provide support and to keep the records the Companies Act 1993, the Tax Administration Act 1994 and the Goods and Services Tax Act 1985 require us to keep.
Our accounting runs on Xero. Project and task records sit in our own systems.
Part B. Personal information we handle for our clients
This part is here because we think you are entitled to know what an agency actually does with the systems it is given access to. Skip it if you only came here about the website. The sections that follow Part B apply to everything in this policy.
B.1 The relationship
Our clients are businesses. Each of them owns a set of marketing and customer systems. To do our job, the client gives us delegated access to some of those systems. We use that access to run their advertising, maintain their website, and produce their performance reporting.
The client decides what happens to the personal information in those systems. We act on the client’s instructions and for the client’s purposes. We do not use a client’s customer data for our own marketing, we do not sell it, and we do not move it between clients. If you are a customer of one of our clients and you want your information corrected or deleted, the fastest route is to contact that business directly. You can also contact us at support@emd.agency and we will pass your request to them and help them action it.
B.2 What we connect to
Depending on what a client has engaged us to do, we may hold access to some or all of the following.
| Platform | What we use it for | What personal information is involved |
|---|---|---|
| Google Analytics 4 | Website performance reporting | Aggregated visitor statistics. No names or contact details. |
| Google Ads | Running and reporting on search and display advertising | Aggregated campaign performance. Some audience lists can contain contact details. |
| Google Search Console | Search visibility reporting | Aggregated search data. No individuals identified. |
| Google Business Profile | Local listing management and reporting | Business listing content, review text and reviewer display names. |
| Meta (Facebook and Instagram) advertising | Running and reporting on social advertising | Aggregated campaign performance. Lead form submissions can contain contact details. |
| Reporting on a client’s own LinkedIn page performance | Aggregated page and post statistics for the client’s own page. | |
| SE Ranking | Keyword ranking and site audits | No personal information. |
| GoHighLevel | CRM, marketing automation, booking and messaging | Customer and enquirer names, email addresses, phone numbers, message content and enquiry history. |
| Zoho CRM | CRM used by some clients | Customer and enquirer names, email addresses, phone numbers and lead records. |
Access to Google Business Profile and to LinkedIn page analytics is being set up at the date of this policy and is not yet in use.
B.3 The level of access we hold
We ask for the narrowest access that will do the job, and where a platform offers a read-only level of access for reporting we use it. Our analytics, search and social reporting connections are read-only by design. Our reporting software is built so that it can only issue read requests, and it refuses any request that would change something.
We should be straightforward about the exception. Some of the work clients engage us to do cannot be done with read-only access. Building a campaign, correcting a CRM record, tagging a contact or fixing a broken automation all require access that can make changes. Where a client has engaged us to do that kind of work, we hold access that can make changes to that client’s account, and we use it only for the work we have been engaged to do.
B.4 Where client data goes
To produce a report we pull figures from the platforms above and assemble them into a document for the client. Those figures are stored on our own server while the report is produced and afterwards as the record of what was reported.
Most of what we pull is aggregate. Some client reports include a list of the leads generated in the period, and for some clients that list includes the lead’s name and contact details, because the client needs to know who to follow up. Where that is the case, the report goes to that client and to nobody else.
Our server is a private virtual machine hosted with Amazon Web Services in Sydney, Australia. It is not shared with anyone outside our business.
We also sometimes hold a copy of client data outside the platform, for example an export taken during a migration from one CRM to another. Section 11 explains how long we keep that.
11. How long we keep information
The Privacy Act (IPP 9) says we must not keep personal information for longer than we need it. These are the periods we work to.
| Information | How long we keep it |
|---|---|
| Website server and security logs | Up to 12 months |
| Google Analytics data | 14 months, which is the retention period set in the property |
| General enquiries that do not become work | 12 months from the last contact |
| Meta lead ad submissions | 12 months from the last contact, the same as general enquiries |
| PROVE the R usage log | Kept while the tool is in development, then handed to the client it was built for or deleted |
| Job applications from unsuccessful applicants, including CVs | 12 months from the date we tell you the outcome, then deleted |
| Client records, contracts and correspondence | 7 years after the engagement ends, to meet tax and company record-keeping requirements |
| Client reporting data and reports | For the term of the engagement and 12 months after it ends |
| One-off exports of client data, for example a CRM migration file | Deleted once the migration is complete and the client has confirmed the result |
Two honest qualifications. First, deleting something from our live systems does not immediately remove it from our backups. Backups are overwritten on their own cycle, and anything in them is deleted when that cycle turns over. Second, where a client’s data sits inside the client’s own platform account rather than ours, the client’s retention settings govern it, not ours.
12. Who we share information with
We do not sell personal information. We do not trade it, and we do not share it for anyone else’s marketing.
We share it in these situations.
- With service providers who run our systems. These are listed in section 13. They may only use the information to provide the service to us.
- With our client, where we are doing work for that client. This is the Part B situation.
- Where you have asked us to. For example, where you ask us to introduce you to another supplier.
- Where the law requires it. For example, in response to a court order or a lawful request from a government agency with the power to compel it.
- If our business is sold. If the business or part of it changes hands, records may transfer to the buyer, who would be bound by this policy.
13. Sending information overseas
This section is here because of Information Privacy Principle 12, which governs disclosing personal information to someone outside New Zealand. We have included it rather than leaving it out, because almost every tool a modern marketing agency uses is operated from another country, and you should be told that before you decide to deal with us.
Our own infrastructure is in Australia. Our server is with Amazon Web Services in Sydney, our backups are in the same region, and our website hosting is with SiteGround on servers in Sydney.
The following providers are based in the United States and hold or process information there or in other countries.
| Provider | What it handles |
|---|---|
| Google (Analytics, Ads, Search Console, Business Profile, Workspace) | Website analytics, advertising data, client marketing data |
| Meta Platforms | Advertising performance data, website pixel data, lead form data for our own ads and for clients who use it |
| LinkedIn (Microsoft) | Page analytics for clients who engage us for it |
| Microsoft (365, Exchange Online) | Our email and calendars |
| HighLevel (GoHighLevel, LeadConnector) | Our own CRM for enquiries, and CRM and marketing automation for clients who use it |
| Zoho | CRM for clients who use it |
| Anthropic | The AI that phrases results in the PROVE the R calculator |
| Mailchimp | Email marketing for clients who use it |
We rely on IPP 12(1)(f), which permits disclosure to a foreign person or entity that is subject to privacy safeguards comparable to those in the Privacy Act. Each of these providers is bound by its own contractual terms and privacy commitments to us and to our clients.
We want to be plain about the limits of that. Once information is held offshore, New Zealand law does not reach it in the same way it reaches information held here, and we cannot promise otherwise. If that concerns you, tell us and we will discuss what we can do. For most of what appears on our website there is a simple answer, which is that you can email or phone us instead of using a tool that sends data offshore.
14. How we look after information
We take security seriously and we would rather describe what we actually do than make claims we cannot stand behind.
- Our server is a private machine, not shared hosting. Access to it is by SSH key only. Password logins are disabled. A firewall restricts it to the ports it needs, and intrusion-blocking software runs on it.
- Traffic to and from our website and our systems is encrypted with TLS.
- Two-factor authentication is enabled on our hosting account and on our Microsoft 365 accounts.
- Access to client platforms is held by a small number of people and, where the platform allows it, at the narrowest permission level the work requires.
- Uploaded files, including CVs, are stored in a directory that will not execute code and that cannot be browsed as a list. File names are randomised so that they cannot be guessed.
- We take regular backups, they are held in a separate location, and we test that they restore.
No system is completely secure, and we are not going to tell you that ours is. If you send us something highly sensitive by email or through a web form, understand that neither channel is a secure delivery method. Ask us and we will find a better one.
15. Your right to see your information and correct it
Under Information Privacy Principle 6 you have the right to ask whether we hold personal information about you, and to ask for a copy of it. Under Information Privacy Principle 7 you have the right to ask us to correct it if it is wrong.
To make a request, email support@emd.agency. Tell us what you are looking for and give us enough detail to find it. We may need to confirm who you are before we release anything, which protects you as much as us.
We will tell you our decision as soon as reasonably practicable, and no later than 20 working days after we receive your request. That timeframe comes from section 48 of the Privacy Act 2020. If we need longer we will tell you why, as the Act allows.
There is no charge for a request from an individual for their own information in the ordinary case. If a request is unusually large we may charge a reasonable cost, and we will tell you before we do.
There are a small number of grounds in the Act on which we can refuse a request, for example where releasing the information would disclose someone else’s personal information. If we refuse, we will tell you which ground we relied on and that you can complain about it.
If you are a customer of one of our clients, we may hold your information only on that client’s behalf. In that case the right way to get it is usually to ask the business directly, because they hold the full record and they decide. Contact us anyway if you are not sure who to ask, and we will point you to the right place.
16. Making a complaint
If you think we have mishandled your personal information, tell us first. Email support@emd.agency and set out what happened. We will look into it and come back to you.
If you are not satisfied with our response, or you would rather not come to us, you have the right to complain to the Office of the Privacy Commissioner, which is the independent regulator for privacy in New Zealand.
- Website www.privacy.org.nz
- Email enquiries@privacy.org.nz
- Phone 0800 803 909
- Post PO Box 10094, Wellington 6143, New Zealand
You do not need our permission to complain to them, and you do not need a lawyer.
17. If something goes wrong
Part 6 of the Privacy Act 2020 requires us to notify the Privacy Commissioner, and the people affected, if we have a privacy breach that it is reasonable to believe has caused or is likely to cause serious harm.
If that happens, we will notify the Commissioner and the affected people as soon as we practicably can, and we will tell you what happened, what information was involved and what we are doing about it. Where the breach involves information we hold for a client, we will tell that client immediately so they can meet their own obligations.
18. If you are outside New Zealand
We are a New Zealand business serving New Zealand clients. Our website is available worldwide, so people outside New Zealand do reach it.
We are not established in the European Union or the United Kingdom, we do not target our services at people there, and we do not monitor the behaviour of people there. On that basis we do not consider the General Data Protection Regulation applies to us, and we have not written this policy around it. We have used the New Zealand Information Privacy Principles instead, because those are the rules we are actually bound by.
If you are in the EU or the UK and you think we hold information about you, email support@emd.agency and we will deal with your request on its merits. In practice the access and correction rights in section 15 give you much of what you would expect, and we will not refuse a reasonable request on the technicality of where you live.
19. Children
Our services are sold to businesses and our website is not aimed at children. We do not knowingly collect personal information from children through our own website.
Some of our clients do serve families, and their systems can contain information about children entered by a parent or caregiver. Where that happens, the information belongs to the client, we handle it only to do the work they have engaged us for, and we do not use it for anything else. If you are a parent or caregiver and you want information about your child corrected or removed, contact the business you dealt with, or contact us and we will help you reach them.
20. Changes to this policy
We will update this policy when what we do changes. The version number and effective date at the top will change with it. If we make a change that materially affects how we handle information we already hold about you, we will take reasonable steps to tell you rather than relying on you noticing.
Version 1.1 added Google Ads conversion tracking to sections 4.2, 4.3 and 5, narrowed the consent commitment in section 5, and updated section 6 for the contact form on our Contact page.
Version 1.2 added the Meta pixel and the Meta Conversions API to sections 4.3 and 5, replaced the commitment in section 5 to ask for consent before sending a hashed identifier to an advertising platform, replaced section 7 (the website chat assistant, which we no longer use) with Meta lead ads, and updated sections 3, 6, 11 and 13 to match.
21. How to contact us
For anything in this policy, including an access request, a correction request or a complaint, contact our privacy officer.
Email support@emd.agency
Phone 0800 323 500, or +64 7 211 6450