nXT Craft Privacy Policy
Version 1.1 · Effective 22/11/2026 · Last updated 22 November 2026
This policy explains what personal information nXT Craft collects, why we collect it, what we do with it, who else sees it, how long we keep it, and what you can ask us to do about it. It covers our control panel at portal.nxtcraft.net, our content editor at cms.nxtcraft.net, our website at nxtcraft.net, and the services we provide to our clients.
We are an “agency” under the Privacy Act 2020 and we follow its thirteen Information Privacy Principles. This policy is organised so you can see which principle each part answers.
The short version
- We collect what we need to build and run your website, bill you for it, and support you. Nothing else.
- We never see your password. Sign-in is handled by Auth0, and no password ever reaches us.
- We never see your card number. Cards are entered on Stripe’s own pages. We hold the brand, the last four digits and the expiry so you can tell one card from another.
- We don’t track you. No advertising pixels, no third-party trackers, no tracking cookies. Visitor analytics on our website and the sites we run are cookieless and count visits, not people.
- Enquiries sent through a client’s website belong to that client. We hold them on the client’s behalf for 12 months, then delete them.
- We share your information only with the providers who make the service work, and we name every one of them in §7.
- You can ask for a copy of what we hold, ask us to fix it, and ask us to delete it. §6 tells you how.
- If you’re not happy with how we’ve handled your information, you can complain to us and then to the Office of the Privacy Commissioner. §16.
Contents
- Who we are, and who this policy is about
- What we collect and why · IPP 1, 3
- Where we get it from · IPP 2, 3A, 4
- How we use it · IPP 8, 10
- How we keep it safe · IPP 5
- Seeing it, and correcting it · IPP 6, 7
- Who else sees it · IPP 11
- How long we keep it · IPP 9
- Information that goes overseas · IPP 12
- Identifiers we use · IPP 13
- Cookies, browser storage and tracking
- Marketing and messages from us
- Your clients’ and visitors’ information
- Email we host for you
- Privacy breaches
- Complaints
- Changes to this policy
- Contact us
1. Who we are, and who this policy is about
1.1 This policy is issued by nXT Craft.
1.2 It covers personal information about:
- people at our client businesses: the owners, staff and contacts who use the control panel or the content editor, or deal with us;
- people who enquire about our services, including through the form on our website;
- visitors to our own website; and
- people whose information appears in what a client gives us: for example a staff member named on a website we are building.
1.3 It does not cover how our clients handle information about their own customers, such as the enquiries people send through a client’s website. That is the client’s responsibility, and §13 explains the split.
1.4 Our Privacy Officer. As required by section 201 of the Privacy Act 2020, we have a Privacy Officer: Matthew Kurian, Founder, reachable at hello@nxtcraft.net.
2. What we collect and why
Information Privacy Principles 1 and 3: we collect only what we need for a lawful purpose connected to what we do, and we tell you at the time.
2.1 We collect the following, and nothing that is not on this list without telling you first.
Your identity and contact details
| What | Why we need it |
|---|---|
| Your full name | Invoices, the Service Agreement you sign, and the audit trail of who did what |
| Email address | Signing in, invoices, notices, and support |
| Phone number | Reaching you about your build or your account |
| Job title | Knowing who we are talking to inside a business |
| Business name and location | Identifying your account and putting the right details on your invoices |
| Your role on the account (owner, editor or billing) | Deciding what you can see and do in the Portal |
Note on your name. We do not take your name from whatever account you signed in with. A Google display name or a nickname derived from an email address is not what belongs on an invoice. We ask you for it directly, with your phone number, on the welcome screen, and nothing later overwrites your answer.
People you invite. If you invite a colleague to your account, we hold the name, email address and role you give us, so they can be linked to your account when they sign in.
Your business and billing details
Legal entity name, billing address, billing email, a GST number if you choose to give one, and whether you are a New Zealand or an overseas customer (which decides which payment options are offered). Your payment preference: automatic card payment, paying each invoice yourself, or bank transfer.
Payment information
We never receive or store your card number. Card details are entered on payment pages hosted by Stripe. What comes back to us and what we store is: the card brand, the last four digits, the expiry month and year, and an identifier Stripe uses for that card. That is enough to show you which card is on file and no more.
If you pay by bank transfer, we record that you told us a transfer was on its way, the reference you used, and when we confirmed it arrived. Our own bank statement will show the name and account the money came from, as any bank statement does.
We also store the status and history of your invoices and payments, and whether each was paid on time.
What you tell us about your business
Your onboarding brief and everything in it: what your business does, your trade, your story, what you want the website to achieve, your brand colours and fonts, your intended launch date, your current host and what your existing site was built with, and any migration notes. Also the physical address and country of your business.
Your sites and services
Domains, DNS records, mailbox addresses and how much of their storage quota is used, subdomains, deployment and commit history, the current state of each site, and for custom app projects the milestones, who accepted each one, and when.
Content you put in the editor
For CMS sites, the content editor holds the name, email address, sign-in identifier and role of each person who edits your site, and everything they enter: pages, posts, events, staff profiles, documents and images, with a history of earlier versions so changes can be undone.
How your site is performing
Whether your public site is up (we check every five minutes), its speed, accessibility and quality scores, and aggregate visitor figures from Cloudflare: page views, requests, response codes and Core Web Vitals. These are totals for the site. They do not identify any visitor, and our analytics set no cookies.
Things you send us and ask us for
Messages in the Portal inbox, change requests, approval requests, and the reasons you give when you ask to cancel a service, ask for a copy of your data, or ask us to close your account. We ask for these reasons because a person reads them before acting, not because we file them away.
Enquiries
- Enquiries to us, through the form on nxtcraft.net or by email: your name, email address, phone number if you give it, your business, which plan you are interested in, and your message.
- Enquiries to our clients, through the contact form on a website we run: whatever the form asks for, usually a name, email address, phone number and a message, plus the page it was sent from. We hold these on the client’s behalf (§13).
Records we generate about your account
- An audit trail. Every significant action on a site and on an account is logged: what happened, who did it (you, us, or an automated process), and when. This is how we can answer “what happened to my site on the 14th”, and it is why we keep it.
- Internal working notes. Our staff record notes about how a client relationship is going: a risk, a win, a billing arrangement, something said on a call. §6.4 explains your right to ask for these.
- Derived business analysis. We calculate, from your invoices and payment history, things like how long you have been a client, what your account is worth, how promptly invoices are paid, and a resulting internal rating. These are calculated when we look at them, never stored, and they are our assessment of the commercial relationship rather than a record of you.
Technical information
- IP addresses, held briefly in memory to enforce rate limits and to detect and stop abusive traffic, repeated failed sign-in attempts and form spam. This is a security measure, not analytics.
- Server logs: the requests made to our systems, timestamps, and error information, used to run and debug the service.
- Diagnostic data from the portal in your browser: errors the page runs into, how long pages and requests take, and which part of the portal made them. It carries a random identifier for the visit, not your name, email or account, and web addresses are stripped of their search terms before they leave your browser. It goes to monitoring systems we run ourselves, not to a third-party service, and is used only to find and fix problems.
- Your interface preference (light or dark mode).
2.2 Why we collect it. In summary: to provide, build, host and support the services you have asked for; to bill you and collect payment; to communicate with you about your account; to pass enquiries to the client they were sent to; to keep the service secure and detect abuse; to measure your site against the nXT Standard; to keep records we are legally required to keep; and to run our business, including deciding how to manage a commercial relationship.
2.3 What we do not collect. We do not collect health information, information about your race, religion, political opinion or sexual orientation, biometric information, government identifiers (an IRD or driver licence number), or criminal history, and you should not send them to us. We do not use automated decision-making that has a legal effect on you.
2.4 Giving us information is voluntary, with consequences. You do not have to give us any of this. But we cannot open an account without a name, a phone number and an email address, cannot invoice you without billing details, and cannot build a site without a brief. Where a field is optional, we say so.
2.5 Children. Our services are for businesses and organisations. We do not knowingly collect information about children. If you believe we hold information about a child, tell us and we will delete it.
3. Where we get it from
Information Privacy Principles 2, 3A and 4: we collect from you where we can, we tell you when we collect from somewhere else, and we never collect by deception or unfair means.
3.1 From you, directly, in almost every case: when you enquire, sign up, complete the onboarding wizard, edit your profile, send a message, edit content, or raise a request.
3.2 From our identity provider (Auth0). When you sign in, we receive your verified email address and an identifier for your login. We use the email address only to fill a blank and to link you to an invitation sent to that address. Once you have set your own email address in the Portal, the identity provider stops overwriting it. We do not take your name from it.
3.3 From our payment provider (Stripe). Card metadata, invoice and payment status, and subscription state.
3.4 From domain registries and registrars. Domain availability, price, registration and expiry information for domains you ask us about or that we manage for you. Some of this is public in registry records.
3.5 From Cloudflare. Aggregate traffic and performance figures for the sites we host (§2).
3.6 From visitors to our clients’ websites, when they send an enquiry through a contact form we run. We tell them, and the client tells them, through the client’s own privacy statement (§13).
3.7 From our own systems. Server logs, audit trail entries, deployment records, uptime checks, quality scores, and the analysis described in §2.
3.8 From your colleagues. If someone at your business gives us your name and contact details so we can set up your login or reach you, or invites you to their account, this policy is how we tell you what we then hold. Ask us at any time.
3.9 Fair means only. We do not collect personal information by deception, by covert monitoring, or in any way that is unfair or unreasonably intrusive. We do not buy contact lists.
4. How we use it
Information Privacy Principles 8 and 10: we check information is accurate before we use it for something that matters, and we do not use it for a purpose unconnected to why we collected it.
4.1 We use personal information to:
- set up and run your account, decide where you land when you sign in, and decide what each person on your account can see and do;
- design, build, deploy and host your website, and publish the changes your editors make;
- register and manage your domain and DNS, and set up your mailboxes;
- raise invoices, take payment, match bank transfers, and chase overdue amounts;
- send you service messages: previews ready for review, invoices and receipts, payment failures, renewal and expiry notices, suspension warnings, and your monthly report;
- pass enquiries from your website to you;
- answer your support requests and act on the changes you ask for;
- keep an audit trail of what was done to your account and by whom;
- check your site’s uptime, speed and quality against the nXT Standard;
- detect, investigate and prevent abuse, fraud, spam, security incidents and misuse of our services;
- decide how to manage the commercial relationship: credit, payment arrangements, and whether to take on more work;
- meet our legal obligations, including tax and record-keeping; and
- with your consent, feature your finished website in our portfolio.
4.2 AI tools. We use AI tools to help draft builds and changes. Where that means sending your content or brief to an AI service, we send only what the task needs, and only to services whose terms exclude training on it. A person reviews everything before it reaches you or your live site.
4.3 Accuracy. Before we use your information for something that affects you (an invoice, a legal notice, a decision about your account) we take reasonable steps to check it is accurate, complete, up to date and relevant. The best protection here is you: keep the details on your profile current.
4.4 We do not sell your personal information, rent it, trade it, or share it with anyone for their own marketing.
5. How we keep it safe
Information Privacy Principle 5: reasonable safeguards against loss, misuse and unauthorised access.
5.1 Passwords never reach us. Sign-in to the Portal and the editor is handled by Auth0. We hold no passwords and cannot see yours. Two-factor authentication is available and we recommend turning it on.
5.2 Access tokens are validated on every request. Every call to our API is checked against the identity provider’s signing keys, including who issued the token, who it was issued for, and whether it has expired.
5.3 One client cannot see another’s data. Separation between client accounts is enforced in the database query layer, not in the interface, so a request for another client’s record fails whether it comes from a browser, a stale tab or a script. A client account that is not attached to an organisation sees nothing rather than everything. The content editor separates each client’s site the same way, and a person can only edit the sites we have given them access to. This is covered by automated tests, because getting it wrong is the worst thing that could happen here.
5.4 Roles within your account. Editors on your account cannot see billing; billing contacts cannot change your sites. Only owners can sign agreements and manage the people on the account.
5.5 Staff access is explicit. Staff-only areas (pricing, other clients’ records, internal notes) require a staff role that is granted deliberately and read from the access token on every request. Nobody can promote themselves by editing their own profile.
5.6 Your public site holds nothing to steal. The websites we host are static files. They have no database, no login page and no admin panel, and they never call the Portal or the editor while a visitor is reading them. Content is pulled from the editor only when a site is built, using a key that can read that one site’s published content and nothing else.
5.7 Transport and browser protections. Everything travels over HTTPS. The
control panel ships a strict Content Security Policy that blocks injected and
third-party scripts, and API responses are marked no-store so another client’s
data is never left in a cache, and cannot be framed by another site. Messages
between our own systems are signed, and rejected if the signature does not
match.
5.8 Abuse limits. Requests are rate-limited per address, with a much tighter budget for failed authentication, which is what stops a credential-guessing or stolen-token loop. Contact forms are protected by Cloudflare Turnstile and limited per site.
5.9 Payment security. Card details are handled entirely by Stripe, a PCI-DSS Level 1 certified provider, on Stripe’s own pages. Our systems are never in the path of a card number.
5.10 Audit trail. Significant actions are logged with who, what and when.
5.11 People. Access to client information is limited to staff who need it, and our staff are bound by confidentiality obligations.
5.12 Backups. The Portal’s database and the editor’s database are each replicated continuously to private Cloudflare R2 storage, with a daily snapshot. Portal backups are kept for 30 days; editor backups for 30 days. Images and documents uploaded to the editor are stored privately in R2. Site code and its full history are kept in GitHub.
5.13 No system is perfect. These measures reduce risk; they do not eliminate it. §15 says what we do if something goes wrong.
6. Seeing it, and correcting it
Information Privacy Principles 6 and 7: you have a right to see the personal information we hold about you, and to ask us to correct it.
6.1 See it yourself. Your profile page in the Portal shows your name, email, phone, job title, company and location, and lets you change them. Your sites, invoices, requests and account history are all readable in the Portal at any time, including after a service is cancelled.
6.2 Ask for a copy. In the Portal, under Your data, you can request a copy of everything we hold on your account. A person puts it together and emails it to you. It includes your profile and the people on your account; your sites, plans, domains and mailboxes; your invoices, payments and billing details; every request and approval; your design requests; and your account activity. For each site you can also download the exit kit at any time, which holds the site’s code, content, images, DNS records and invoices.
6.3 What that export leaves out. The export does not include our internal staff notes or the derived commercial statistics described in §2. Those are our working records about the relationship rather than a record we keep about you, and the export says so on its face rather than silently omitting them.
6.4 But you can still ask for them. The Privacy Act gives you a right of access to your personal information, and that right is not limited by what our export happens to include. If you want the internal notes and assessments as well, ask us in writing at hello@nxtcraft.net and we will consider your request under the Act. We may withhold information only on a ground the Act allows, for example where it is evaluative material given in confidence, where releasing it would breach someone else’s privacy, where it is legally privileged, or where it would reveal a trade secret. If we withhold anything, we will tell you that we have, and tell you why, and you can complain to the Privacy Commissioner about that decision.
6.5 How to make a request. Use the Portal, or email hello@nxtcraft.net with enough detail for us to find what you want. We may ask you to confirm your identity, because we will not hand your information to someone who is not you. There is no charge for a reasonable request. We will acknowledge it within one business day and respond as soon as we can, and within 20 working days, as the Act requires. If we need longer, we will tell you within that period, and why.
6.6 Correcting it. If something we hold is wrong, fix it on your profile or tell us and we will. If we do not agree that a correction is needed, you can ask us to attach a statement of the correction you sought, and we will attach it to the record so anyone who reads it in future sees it too.
6.7 Deleting it. In the Portal, under Close your account, you can ask us to close your account and delete what we hold on you. A person reads the request. Before anything closes, we hand your domains and your site code back to you. Ninety days after a site ends, its content and data are deleted. We keep only the records we are legally required to keep. See §8.
6.8 Someone acting for you. We will deal with a lawyer, accountant or other representative on your written authority.
7. Who else sees it
Information Privacy Principle 11: we do not disclose personal information except for a reason the Act permits.
7.1 Our service providers. We share only what each one needs to do its job:
| Provider | What they get | What they do with it |
|---|---|---|
| Auth0 (Okta, Inc.) | Your email address and login identifier | Runs sign-in to the Portal and the editor, verifies your email, holds your password (we never do) |
| Stripe, Inc. | Your name, email, billing address, and your card details entered on their pages | Issues invoices and receipts, processes card payments, runs subscriptions, fraud screening |
| Cloudflare, Inc. | Site content, domain and DNS data, registrant details for domains we register through them, visitor traffic to sites we host, contact form submissions in transit, and our encrypted backups and editor media | Hosting, CDN, DNS, SSL, firewall, form spam protection (Turnstile), cookieless analytics, domain registration, storage (R2) |
| Porkbun, LLC | Registrant details for domains we register through them; mailbox addresses and the contents of the mailboxes we host for you | Domain registration and renewal; email hosting, reached through Porkbun’s webmail or its IMAP, POP3 and SMTP servers |
| GitHub, Inc. (Microsoft) | Your site’s source code and commit history | Source control and automated quality checks |
| Amazon Web Services | The editor’s database and the content your editors enter | Runs the server the content editor is on |
| Sendinblue SAS (Brevo) | Your name and email address, and the content of each message we send you, including enquiries forwarded from your website | Sending service email: invoices, notices, enquiries and reports |
| Anthropic, PBC (Claude) | The brief or content needed for a specific build or change | Helping draft builds and changes, under terms that exclude training on it |
7.2 Domain registries. When we register a domain for you, your registrant
details go to the registry and, depending on the TLD and your privacy settings,
some of them may appear in public registry records. For .nz domains this is
governed by the Domain Name Commission’s policies. Tell us if you want to use a
registry’s privacy option where one is available.
7.3 Our professional advisers, meaning accountants, auditors and lawyers, under obligations of confidentiality.
7.4 If we are required or permitted by law. We may disclose information where the Privacy Act allows it: where the law requires it, in response to a valid court order or a lawful request from a regulator or enforcement agency, to establish or defend a legal claim, or where necessary to prevent or lessen a serious threat to someone’s life, health or safety. We will tell you when this happens unless we are legally prevented from doing so.
7.5 If our business changes hands. If we sell or merge the business, client records may transfer to the buyer, who would be bound to handle them under this policy or one no less protective. We will tell you.
7.6 Debt collection. If an amount stays unpaid after we have reminded you and given you time to pay, we may pass the details necessary to recover it to a debt collection agency or our lawyers.
7.7 With your consent, for anything else, including featuring your site in our portfolio.
8. How long we keep it
Information Privacy Principle 9: we don’t keep personal information longer than we need it.
| What | How long | Why |
|---|---|---|
| Your account and profile | While your account is open | To run the service |
| Invoices, payment records, tax records | 7 years from account closure | Required by the Tax Administration Act 1994 and the Companies Act 1993 |
| The account audit trail | 7 years from account closure | We have to be able to show what we did, and when: for you, for a dispute, and for a regulator |
| A site’s content, code and data after it ends | 90 days, then deleted | So you have time to take the exit kit or ask for anything you missed |
| Enquiries sent through a client’s website | 12 months, then deleted | Long enough to reply and follow up |
| Enquiries to us that did not become clients | 12 months | So we know we have spoken before |
| Mailbox contents after a mailbox is removed | 30 days, then destroyed | A grace period to recover something removed by mistake |
| Earlier versions of content in the editor | Up to the last 50 versions of each page or post, fewer for other content, while the site is with us | So a change can be undone |
| Uptime checks | 7 days of individual checks; monthly results in your reports | Measuring the nXT Standard |
| Exit kit download links | The link works for 7 days from when the kit is made | So a copy of your site is not downloadable indefinitely. |
| IP addresses held for rate limiting | Minutes, in memory only | Security and abuse prevention |
| Server logs and diagnostic data | 14 days | Security, abuse prevention and debugging |
| Backups | Portal: 30 days. Editor: 30 days | Disaster recovery: deleted records persist in backups until the backup rotates out |
8.1 When an account is closed we record the date the retention period ends, and the record is destroyed then. Changing our retention policy later does not move the date on an account already closed under the old promise.
8.2 Backups. When we delete something, it may persist in a backup until that backup expires on the schedule above. We do not restore deleted data from a backup other than for genuine disaster recovery.
9. Information that goes overseas
Information Privacy Principle 12: we only send personal information overseas with proper protection.
9.1 Our Portal server is in New Zealand, on hardware we control. Several of the providers in §7 store and process information outside New Zealand:
| Provider | Where |
|---|---|
| Auth0 (Okta) | Australia |
| Stripe | United States, Ireland and other locations Stripe operates in |
| Cloudflare | A global network; content, DNS and form traffic are handled in many countries. Backups and editor media are stored in Cloudflare R2’s Oceania region |
| Porkbun | United States |
| GitHub | United States |
| Amazon Web Services | Australia (Sydney) |
| Brevo | European Union (France) |
| Anthropic | United States |
9.2 On what basis. Before we send personal information to a provider outside New Zealand, we satisfy ourselves under IPP 12 that the recipient is required to protect it with safeguards comparable to those in the Privacy Act 2020, through the contract we have with them (including standard data protection clauses where they are offered), and because several of them are subject to privacy laws providing comparable protection, including the European Union’s GDPR.
9.3 What this means in practice. Once information is held overseas it may be subject to the laws of that country, including lawful access by its authorities. We cannot control that. If you would prefer your information not to leave New Zealand, talk to us before you sign up. We will tell you honestly whether we can provide the service on that basis.
10. Identifiers we use
Information Privacy Principle 13: limits on assigning unique identifiers.
10.1 We assign our own identifiers to accounts, users, sites, jobs, invoices and enquiries, so that our systems can refer to a record unambiguously. We also store identifiers assigned by our identity provider and our payment provider.
10.2 We do not assign or require a government-issued unique identifier such as an IRD number or a driver licence number, and we do not use one as your account identifier. Where you give us a GST number, that is a business identifier, not an identifier for you as an individual.
10.3 We do not use our identifiers for any purpose other than running the service, and we do not require you to disclose an identifier assigned by another agency.
11. Cookies, browser storage and tracking
11.1 We do not track you. The control panel contains no analytics, no advertising pixels, no third-party trackers, and no cross-site tracking cookies. It loads no third-party scripts at all, and a Content Security Policy enforces that.
11.2 What the control panel stores in your browser. Only what it needs to work:
| What | Why | Cleared by |
|---|---|---|
| Your sign-in session | So you stay signed in between page loads | Signing out, or clearing site data |
| A short-lived sign-in cookie | So signing in works across tabs | Expires when sign-in completes |
| Small interface preferences (for example, light or dark mode, and which notices you have dismissed) | So the panel does not repeat itself | Clearing site data |
11.3 The content editor sets the cookies it needs to keep you signed in while you edit. It runs no analytics or trackers.
11.4 Other people’s pages. When you are handed to Stripe to pay or to save a card, or to Auth0 to sign in, those pages are theirs and may set their own cookies under their own privacy policies. We link to them in §18.
11.5 Our website, nxtcraft.net. Our website counts visits with Cloudflare Web Analytics, which is cookieless: it does not set cookies, does not fingerprint your device, and does not identify you. Our contact form is protected by Cloudflare Turnstile, which checks signals from your browser to tell people from bots, under Cloudflare’s privacy policy. What you send through the form is emailed to us through Brevo and may be kept in our enquiries inbox (§8). We run no advertising or social media trackers.
11.6 Do Not Track. We do not track you, so there is nothing for a Do Not Track signal to switch off.
12. Marketing and messages from us
12.1 Service messages. We will always send you messages about your own account: invoices and receipts, payment failures, previews ready for review, renewal and expiry notices, suspension warnings, security notices, and your monthly account update. These are part of the service and you cannot opt out of them while you hold an account.
12.2 Preview and invoice emails. The Portal has a preference for these under Preferences. Turning it off reduces what we send; it does not stop notices we are required to give you.
12.3 Marketing. We do not send marketing email.
13. Your clients’ and visitors’ information
13.1 Whose responsibility. Where we build and host a website for you and that website collects personal information about your customers (a contact form, a booking, an order, a newsletter sign-up) you are the agency responsible for that information under the Privacy Act 2020. We hold it on your behalf, as a provider acting on your instructions.
13.2 What that means for you. You need your own privacy statement on your own website, telling your visitors what you collect and why, including what happens to contact form enquiries. You are responsible for responding to access and correction requests from your own customers, and for notifying a privacy breach affecting them.
13.3 What that means for us. Under section 11 of the Privacy Act, information we hold solely as your agent is treated as held by you. We do not use it for our own purposes, we will not disclose it except on your instructions or where the law requires, and we will help you respond to a request from one of your customers. Tell us if you need that help.
13.4 Contact form enquiries. An enquiry sent through your site’s contact form is checked by Cloudflare Turnstile for spam, emailed to you through Brevo, and, where your enquiries inbox is switched on, stored in your Portal for 12 months and then deleted. Anyone on your account with the owner or editor role can read it.
13.5 Visitor traffic. Our hosting provider processes visitor traffic to your site (IP addresses and request data) to serve pages and to protect against attacks. We see only aggregate figures, such as page views and response times, which we use for your monthly report and the nXT Standard. We do not build profiles of your visitors.
13.6 Things you add to your site. If you embed a video, a map, a newsletter sign-up form or a booking tool from another provider, that provider may collect information from your visitors under its own terms. Our videos and maps load only when a visitor chooses to play or open them, but what the provider does after that is between you, your visitor and them. Your privacy statement should cover it.
14. Email we host for you
14.1 Where we host mailboxes for you, the contents of those mailboxes are yours. We do not read your email.
14.2 Our systems necessarily process message content to deliver, store, index for search, and filter spam and malware. Staff will access a mailbox only: when you ask us to, to investigate a fault you have reported, to deal with a security or abuse incident, or where the law requires it. Where we do, it is recorded.
14.3 Removing a mailbox archives its contents for 30 days and then destroys them. Export anything you need before that.
14.4 Email in transit crosses networks we do not control. Do not use email for information that needs stronger protection than that.
15. Privacy breaches
15.1 If we have a privacy breach that it is reasonable to believe has caused, or is likely to cause, serious harm to anyone affected, we will notify the Office of the Privacy Commissioner and the people affected as soon as practicable, as Part 6 of the Privacy Act 2020 requires. We assess a suspected breach against that test on the day we learn of it.
15.2 We will tell you what happened, what information was involved, what we have done about it, and what you should do. We will not wait until we have every detail before telling you something has happened.
15.3 We keep a record of privacy breaches, including those that do not meet the notification threshold, and review them.
15.4 If you become aware of a security or privacy problem with our systems, please tell us at hello@nxtcraft.net. We will not pursue anyone who reports a genuine vulnerability to us in good faith and does not exploit it or access other people’s data.
16. Complaints
16.1 Come to us first. If you think we have mishandled your personal information, contact our Privacy Officer at hello@nxtcraft.net. We will acknowledge within one business day, investigate, and tell you what we have found and what we will do.
16.2 Then the Privacy Commissioner. If you are not satisfied, you can complain to the Office of the Privacy Commissioner:
- Website: privacy.org.nz
- Phone: 0800 803 909
- Email: enquiries@privacy.org.nz
- Post: PO Box 10094, Wellington 6143
You can complain to the Commissioner at any time. You do not have to come to us first, though it is usually quicker.
17. Changes to this policy
17.1 We may update this policy. The version number and date at the top tell you which version you are reading.
17.2 If we make a change that materially affects how we handle your personal information, we will tell you by email and in the Portal before it takes effect.
17.3 We keep earlier versions and will provide one on request.
18. Contact us
Privacy Officer Matthew Kurian, Founder nXT Craft, Tāmaki Makaurau Auckland
- Privacy questions, access and correction requests: hello@nxtcraft.net
- Security reports: hello@nxtcraft.net
- General and support: hello@nxtcraft.net, or through the Portal
Our providers’ privacy policies
- Auth0 / Okta · https://www.okta.com/privacy-policy/
- Stripe · https://stripe.com/nz/privacy
- Cloudflare · https://www.cloudflare.com/privacypolicy/
- Porkbun · https://porkbun.com/legal/agreement/privacy_policy
- GitHub · https://docs.github.com/en/site-policy/privacy-policies
- Amazon Web Services · https://aws.amazon.com/privacy/
- Brevo · https://www.brevo.com/legal/privacypolicy/
- Anthropic · https://www.anthropic.com/legal/privacy


