Create a bespoke document in minutes, or upload and review your own.
Get your first 2 documents free
Your data doesn't train Genie's AI
You keep IP ownership of your information
Co-Ownership Agreement
I need a co-ownership agreement for a residential property shared between two parties, outlining the percentage of ownership, responsibilities for maintenance, and a process for resolving disputes. The agreement should also include terms for selling the property or buying out the other party's share.
What is a Cookies Policy?
A Cookies Policy tells website visitors how your site uses small data files (cookies) to track their activity and store their preferences. It's a key document that complies with New Zealand's Privacy Act 2020 and helps build trust with your users by explaining what information you collect through cookies and why.
The policy must outline if you use essential cookies for basic site functions, analytics cookies to understand visitor behavior, or advertising cookies for targeted marketing. It should also explain how users can control or disable cookies through their browser settings, meeting both Kiwi privacy requirements and international data protection standards.
When should you use a Cookies Policy?
Your website needs a Cookies Policy when you start collecting visitor data through cookies - typically from the moment your site goes live. This requirement kicks in under New Zealand's Privacy Act 2020 if you track user behavior, remember login details, or use tools like Google Analytics.
The timing is especially critical when launching e-commerce features, adding marketing pixels, or expanding your online presence internationally. Having a clear Cookies Policy from day one helps avoid privacy complaints, builds user trust, and ensures compliance with both local privacy laws and international standards like GDPR, which can affect Kiwi businesses serving European customers.
What are the different types of Cookies Policy?
- Basic Cookie Notice: A simple policy covering essential cookies only, ideal for small business websites that don't use analytics or tracking.
- Comprehensive Cookies Policy: Details all cookie types, including analytics, advertising, and functionality cookies - suitable for e-commerce sites and digital platforms.
- Industry-Specific Policies: Tailored versions for sectors like healthcare or finance, addressing unique data handling requirements and privacy standards.
- Multi-Language Cookie Policies: Adapted for businesses serving diverse populations, ensuring compliance across English and Te Reo M��ori.
Who should typically use a Cookies Policy?
- Website Owners: Responsible for implementing and maintaining a Cookies Policy that accurately reflects their data collection practices.
- Web Developers: Handle the technical implementation of cookie consent mechanisms and policy display on websites.
- Privacy Officers: Ensure the policy aligns with New Zealand's Privacy Act and international data protection requirements.
- Legal Teams: Draft and review policy content to maintain compliance with privacy laws and minimize legal risks.
- Website Visitors: Must acknowledge the Cookies Policy and can exercise their rights regarding cookie preferences and data collection.
How do you write a Cookies Policy?
- Cookie Audit: List all cookies your website uses, including third-party tools like Google Analytics or social media plugins.
- Purpose Mapping: Document why each cookie is necessary and how it benefits your site's functionality.
- Storage Duration: Note how long each cookie remains active on users' devices.
- User Controls: Plan how visitors can manage their cookie preferences through your consent mechanism.
- Legal Requirements: Our platform ensures your policy aligns with NZ Privacy Act standards while using clear, accessible language.
- Implementation Plan: Prepare your technical team to properly display the policy and cookie consent banner.
What should be included in a Cookies Policy?
- Cookie Types: Clear categorization of essential, functional, analytical, and advertising cookies used on your site.
- Data Collection: Specific details about what information each cookie collects and how long it's stored.
- User Rights: Explanation of visitors' control over cookies and how to modify browser settings.
- Third-Party Access: List of external services accessing cookie data and their privacy policies.
- Contact Information: Details for privacy-related inquiries and complaints.
- Consent Mechanism: Description of how users can accept or decline different cookie categories.
- Policy Updates: Process for notifying users about changes to cookie practices.
What's the difference between a Cookies Policy and a Data Breach Response Policy?
A Cookies Policy is often confused with a Data Breach Response Policy, but they serve distinct purposes in your organization's data protection framework. While both relate to digital data handling, they address different aspects of privacy compliance under New Zealand law.
- Scope and Purpose: A Cookies Policy focuses on everyday data collection through website tracking, while a Data Breach Response Policy outlines emergency procedures for security incidents.
- Timing of Use: Cookies Policies are actively used daily for user consent and transparency, whereas Data Breach Response Policies activate only during security incidents.
- Legal Requirements: Cookies Policies fulfill ongoing Privacy Act transparency obligations, while Data Breach Response Policies address mandatory breach notification requirements.
- User Interaction: Cookies Policies require active user engagement through consent mechanisms; Data Breach Response Policies are internal procedures that users don't directly interact with.
Download our whitepaper on the future of AI in Legal
ұԾ’s Security Promise
Genie is the safest place to draft. Here’s how we prioritise your privacy and security.
Your documents are private:
We do not train on your data; ұԾ’s AI improves independently
All data stored on Genie is private to your organisation
Your documents are protected:
Your documents are protected by ultra-secure 256-bit encryption
Our bank-grade security infrastructure undergoes regular external audits
We are ISO27001 certified, so your data is secure
Organizational security
You retain IP ownership of your documents
You have full control over your data and who gets to see it
Innovation in privacy:
Genie partnered with the Computational Privacy Department at Imperial College London
Together, we ran a £1 million research project on privacy and anonymity in legal contracts
Want to know more?
Visit our for more details and real-time security updates.
Read our Privacy Policy.