fbpx

Privacy Policy

We respect your right to privacy and have a number of policies to ensure it is upheld at all times.

Our website address is: https://360newzealand.com.

We can be contacted at:
info@360newzealand.com
PO Box 311, Wanaka, NZ
+64 (0)3 443 4467

General website use and personal information

Data about how and when users visit this site and what browsers they use is stored in our logs. We use this data to improve our service and the performance of this website. Traffic data is not combined with any personal details or contact information.

There are areas of this web site where you may be asked to enter personal information or contact details into an interactive form to help us carry out a service request. We have a duty to store this information securely. Contact information will not be used for any direct marketing or surveys, and is at no time shared with any third parties.

What personal data we collect and why we collect it

Cookies

If you use a contact form on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.

Cookies are small files that a site or its service provider transfers to your computer’s hard drive through your web browser (if you allow) that enables the site’s or service provider’s systems to recognise your browser and capture and remember certain information. We also use cookies to help us compile aggregate data about site traffic and site interaction so that we can offer better site experiences and tools in the future. We may also use trusted third-party services that track this information on our behalf. You can choose to have your computer warn you each time a cookie is being sent, or you can choose to turn off all cookies. You do this through your browser settings. Since all browsers are a little different, look at your browser’s Help Menu to learn the correct way to modify your cookies. If you turn cookies off it won’t affect your user experience.

Embedded content from other websites

Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.

These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracing your interaction with the embedded content if you have an account and are logged in to that website.

Email communications

Some of our email communications are administered through MailChimp, and we may store some of your Personal Data – including your name, email address and contact preferences – on a MailChimp server.

MailChimp is a U.S. based company and is certified under the EU-US Privacy Shield framework. For more information, see MailChimp Privacy Policy.


Data Collection in Detail

Activity Log

Data Used: To deliver this functionality and record activities around site management, the following information is captured: user email address, user role, user login, user display name, WordPress.com and local user IDs, the activity to be recorded, the WordPress.com-connected site ID of the site on which the activity takes place, the site’s Jetpack version, and the timestamp of the activity. Some activities may also include the actor’s IP address (login attempts, for example) and user agent.

Activity Tracked: Login attempts/actions, post and page update and publish actions, comment/pingback submission and management actions, plugin and theme management actions, widget updates, user management actions, and the modification of other various site settings and options. Retention duration of activity data depends on the site’s plan and activity type. See the complete list of currently-recorded activities (along with retention information).

Data Synced: Successful and failed login attempts, which will include the actor’s IP address and user agent.

Protect

Data Used: In order to check login activity and potentially block fraudulent attempts, the following information is used: attempting user’s IP address, attempting user’s email address/username (i.e. according to the value they were attempting to use during the login process), and all IP-related HTTP headers attached to the attempting user.

Activity Tracked: Failed login attempts (these include IP address and user agent). We also set a cookie (jpp_math_pass) for 1 day to remember if/when a user has successfully completed a math captcha to prove that they’re a real human. Learn more about this cookie.

Data Synced: Failed login attempts, which contain the user’s IP address, attempted username or email address, and user agent information.

Google Analytics

Data Used: Please refer to the appropriate Google Analytics documentation for the specific type of data it collects. Google Analytics does offer IP anonymisation.

Activity Tracked: This feature sends page view events (and potentially video play) over to Google Analytics for consumption.

WordPress.com Stats

Data Used: IP address, WordPress.com user ID (if logged in), WordPress.com username (if logged in), user agent, visiting URL, referring URL, timestamp of event, browser language, country code. Important: 360newzealand.com does not have access to any of this information via this feature. For example, we can see that a specific post has 285 views, but we cannot see which specific users/accounts viewed that post. Stats logs — containing visitor IP addresses and WordPress.com usernames (if available) — are retained by Automattic for 28 days and are used for the sole purpose of powering this feature.

Activity Tracked: Post and page views, outbound link clicks, referring URLs and search engine terms, and country. Jetpack also tracks performance on each page load that includes the Javascript file used for tracking stats. This is exclusively for aggregate performance tracking across Jetpack sites in order to make sure that our plugin and code is not causing performance issues. This includes the tracking of page load times and resource loading duration (image files, Javascript files, CSS files, etc.).