Privacy Policy

Version 2.10 · Effective 2026-11-11

1. Who we are and what this covers

ONYX1 LIMITED, a New Zealand Limited Company, company number 9453894, NZBN 9429053908322, registered 23 August 2026. Registered office: 189 Upper Harbour Drive, Greenhithe, Auckland, 0632. ONYX1 LIMITED operates ONYX1, a job-management service for New Zealand trade businesses. This policy explains how we collect, use, store and disclose personal information under the Privacy Act 2020 and its Information Privacy Principles. It covers four groups of people, and the rules are not the same for each: Staff users: the people a trade business invites to use ONYX1 at work (owners, office, technicians, contractors). Portal users: people who set a password on the ONYX1 client portal to view files a trade business has shared with them. A portal login is an ONYX1 account. It is not an account of any one trade business. Email contacts: people a trade business stores as a customer or a contact, who may receive invoices, quotes, site reports or reminders by email without ever logging in. Outside people on site: people who are not on a trade business's team, such as contractors from another firm, but who sign that business's site documents on a team member's phone (section 7C). If you are a portal user, an email contact or an outside person on site, "you" in the sections that follow means you, not the trade business.

2. What we collect

Staff accounts: name, email, phone, role, and password (stored only as a secure hash). Business information: company name, NZBN, contact details, branding. Service content: the jobs, customers, quotes, invoices, photos, reports and messages the business enters. Technical information: sign-in times, IP addresses, device and browser type, and service logs kept for security and support. Location at clock-in: if the trade business has clock-in location capture switched on, we record the worker's device position (latitude, longitude and how accurate the reading was) at the moment they clock in, and whether that position was on or off the job's site. The device is asked for its most accurate fix. It is taken at clock-in only, never continuously, and never while someone is off the clock. It is used to flag an off-site clock-in for whoever approves the timesheet, and it never stops anyone starting work. A worker can see their own; the people who run the business can see everyone's, as with the rest of the timesheet. This setting is ON unless an owner or admin turns it off, and while it is off nothing is recorded. Payment card details for a trade business's ONYX1 subscription are collected only by Stripe. Card numbers never touch our systems. Portal accounts: email (unique across all ONYX1 customers), name if we have one, password hash, two-factor secret (encrypted), notification preferences, an outstanding sign-up token, an outstanding request to change the sign-in address together with the address it would move to, and session records (token hash, expiry, IP address, user-agent). We also hold a flag recording that the address has been checked. It is set when a sign-up link we emailed to the address is used to set a password, and when a new sign-in address is confirmed from a link we send to that address. A sign-up link the trade business passed to you itself does not set it, because a link held by staff proves nothing about who reads mail at the address. We collect the password from you when you set it. We usually receive the email and name from the trade business that invited you, or from you if you request a sign-up link yourself. Email contacts: name, email, phone, role label, and which kinds of mail the trade business has marked you to receive. That information is typed or imported by the trade business. We also store an unsubscribe token and the time you last unsubscribed. Business correspondence: This business may receive email through a Microsoft 365 mailbox or through its configured email-forwarding service. When ONYX1 Office checks Microsoft 365, each participating person connects and opts in their own account. ONYX1 reads only that person's Inbox through Microsoft Graph and does not read Sent Items. That limit applies to correspondence handling; section 7A covers the separate Microsoft 365 tools a person can ask ONYX1 Office to use. For forwarded email, ONYX1 processes the verified copy received by the business's configured forwarding address. ONYX1 processes sender and recipient details, subject, message text, received time and attachment filenames to classify email as a new enquiry or existing job correspondence. It does not open or store attachment files. If ONYX1 Office is enabled, it may prepare an internal task, private job note, cost-approval flag or variation proposal. It may also save a reply draft in the opted-in person's own Drafts. A person reviews and sends any reply from Outlook; ONYX1 does not send it automatically. The business can use the message to identify the customer and job it relates to. ONYX1 purges the stored email message, attachment filenames, mailbox and Graph identifiers, correspondence private notes and action payloads 365 days after receipt, or earlier if the linked enquiry, job or customer is deleted or the message is classified as not an enquiry. Content-free provider-event and duplicate-match hashes remain until 365 days after receipt only to prevent a retry or another opted-in Inbox copy from restoring purged content. Tasks, variation proposals and active cost-approval flags created from a message remain as business records under their own retention rules. Staff records: a trade business can keep an HR record for each staff user (legal name, date of birth, IRD number, tax code, KiwiSaver status, bank account, home address, employment dates and next of kin). Only the business's owners and admins can see it. A business can also attach photos or PDFs of a staff user's licences, tickets and certificates to its compliance register, such as a driver licence, a rope access card or a first aid certificate. These certificate files can show the person's photo, date of birth, address and card number. The business, or the staff user for their own certificates, adds them. Incident investigations: when a trade business investigates a workplace incident, it can record the person involved (their name, address, phone number, age and length of employment) and, for an injury or illness, what happened to them: the type of injury, the part of the body, how serious it was, the treatment they had, whether WorkSafe was told and whether they returned to work. The person involved can be a staff user or someone else, such as a visitor or a member of the public. This is health information under the Health Information Privacy Code 2020. The business's investigator records it, and an owner or admin signs the investigation off. Chippy chats: the questions a staff user asks Chippy, the in-app assistant, its answers, and records of how much each person uses it and of any misuse signals (section 7D). Company announcements: the text of each announcement a business's owner or admin sends to their team, who sent it, who it went to, and when each person pressed Got it (section 7E). We do not have to collect a portal password for you to be on file as a contact. Setting a password is optional and is what opens the client portal.

3. Who is responsible (the agency)

Trade-business files. When a trade business stores its customers' and contacts' details, jobs, invoices, quotes, photos and reports in ONYX1, that business is collecting that information and must have a lawful basis to hold it. We host and process it to provide the service. Requests about those files (a wrong address on an invoice, a photo that should not have been shared) should go to that business. We will help them meet an access or correction request. Portal logins. ONYX1 LIMITED is the agency for the client-portal account itself: the email, password, sessions, two-factor settings and notification preferences. No trade business can see your password or your other providers' files. A trade business can invite or revoke access to its own files only. Requests about the login go to support@onyx1.app. Staff records. The trade business is the agency for its HR records and certificate files, as the employer that collects them (section 2). A staff user's request to see or correct them goes to that business, which can download the files to answer it. We will help them meet the request. Incident investigations. The trade business is the agency for its incident investigations, including the details of the person involved and their injury (section 2). A request to see or correct them goes to that business. We will help it meet the request. Chippy chats. ONYX1 LIMITED is the agency for Chippy chats (section 7D). The trade business does not hold them and cannot read them. Requests about them go to support@onyx1.app. If a request covers both (for example "delete me"), we will deal with the login and tell each linked trade business so they can deal with their own file.

4. One login, several trade businesses

A portal email address can only exist once on ONYX1. That is deliberate: so you are not asked to keep a separate password for every plumber or electrician you use. It has a consequence we want to be honest about. If a second trade business puts your email on their customer record and invites you, we will attach their files to the same login. Their staff will be able to see that the address is already an ONYX1 client. They will not be told which other business you use, and they cannot open that other business's files. You can change the sign-in email from your account page. The new address does not take effect until you confirm a link we send to it, so a change typed wrongly, or made by somebody else, stops there. The new address must be one no other ONYX1 client is already using. A trade business can revoke its own link at any time; that hides their files from you and does not delete the login.

5. Why we use information

Staff and business information: to provide and secure the service, to support you, to bill you, to send service messages (trial reminders, security notices), and to understand aggregate usage so we can improve the product. We send marketing to a trade-business contact only with consent, and every such message has a working unsubscribe, as the Unsolicited Electronic Messages Act 2007 requires. Portal information: to authenticate you, to show you the files each linked provider has shared, to honour the email preferences you set, and to keep the account secure, including the sign-up link and the address confirmation you ask for yourself. We do not sell personal information. We do not use service content or portal content to train AI models.

6. Email we send to customers and contacts

ONYX1 sends some messages to people a trade business works with. The platform sender is ONYX1 LIMITED, a New Zealand Limited Company, company number 9453894, NZBN 9429053908322, registered 23 August 2026. Registered office: 189 Upper Harbour Drive, Greenhithe, Auckland, 0632. Contact: support@onyx1.app. The trade business authorises its customer mail and must provide accurate contact details under section 13 of the Unsolicited Electronic Messages Act 2007. The From line looks like "Acme Plumbing (via ONYX1)" and uses our sending address. Reply-To is the trade business's own email when they have given us one, so a reply reaches them. What goes out automatically (invoices, quotes, overdue payment reminders, a copy of an approved site report) is chosen by the trade business: they mark which contact receives which kind of mail. If you also have a portal login, invoices, quotes and overdue reminders also honour the choices on your account page. Those portal choices start off. Site-report copies follow the trade business's contact flags; there is not yet a portal switch for those. The Unsolicited Electronic Messages Act 2007 requires consent for commercial electronic messages. A current business relationship may support inferred consent, but a stored address or a contact flag does not by itself establish it. The classification and consent basis for each message type have not yet been settled with a lawyer. The trade business must have the right to send each message. A portal login's own switches, where they exist, are express choices on top of that. Automatic customer mail selected by the notification system includes an unsubscribe link that stops further automatic mail to that address from that trade business. Confirming it takes one extra click so that mail scanners cannot unsubscribe you by opening the link. We honour it as soon as you confirm. A person at the trade business can still send a specific invoice or quote by hand after that. The app tells them you unsubscribed and records if they send anyway. You can also email the trade business, or us at support@onyx1.app, and ask to be removed. Account email about your portal login is not marketing, and each message identifies ONYX1 when it goes out. Four kinds come straight from us, and all four are sent whether or not the automatic mail below is switched on. You did not ask for two of them: a sign-up link you asked for yourself, using the form on the portal; a sign-up link your trade business asked us to email you, which you did not ask for and which arrives from us rather than from them; the confirmation of a new sign-in address, sent to the new address, which is what makes the change take effect; notice that the sign-in address on an account has changed, sent to the old address, so that a login being moved is never silent. Automatic email to customers, meaning the invoices, quotes, overdue reminders and report copies a trade business schedules, has been switched on since 9 September 2026 and is delivered to the contacts the trade business has marked to receive it, or to the customer's own email address if the customer has no contacts. If we switch it off, these messages are recorded but not sent, and are not sent later, and we will say so here. A trade business may also hand you a sign-up link itself, outside ONYX1, by whatever means it chooses.

7. Where information is stored and who processes it

ONYX1 is a New Zealand company. The service is hosted on cloud systems that may store or process information outside New Zealand: Vercel (application hosting and private file storage for photos, signatures, PDFs and documents), Neon (database), Resend (email delivery and, when a business configures email forwarding, receipt and processing of forwarded email), Stripe (subscription payments by the trade business), Apple (Apple Wallet and its push service for passes) and Google (Google Wallet) when a person adds their business card to a wallet (section 7B), and Microsoft Graph/Microsoft 365 when an opted-in person connects their own account for correspondence. If a trade business connects Xero, customer and invoice information they choose to sync is sent to Xero. Address lookup uses OpenStreetMap Nominatim and Photon (komoot.io). The dispatch map draws its background from the OpenStreetMap tile servers (tile.openstreetmap.org), which the browser contacts directly, so those servers see the viewer's IP address and which area of the map is on screen. If a staff user enables browser push, the push service for their device (for example Apple, Google or Mozilla) receives a device endpoint. In the ONYX1 phone apps, notifications are sent through Google Firebase Cloud Messaging and, on iPhone, Apple's push notification service. They receive the device's push token, each notification's title and text, and the in-app link it opens. Cloudflare carries ONYX1's connection to a business's ONYX1 Office server when that business uses ONYX1 Office (section 7A). Cloudflare also runs the security check on public enquiry forms, and the visitor's browser contacts Cloudflare directly for it. For Microsoft 365 correspondence, each opted-in person's own delegated account is used; ONYX1 does not connect an assumed shared mailbox. Microsoft Graph requests use `/me` for that signed-in person. A Reply All draft is saved in that person's Drafts in the original thread for them to review and send. The business must tell people when it forwards their email to ONYX1 and link its own privacy statement. The existing enquiry intake keeps each enquiry with its lead or enquiry record. Active leads and enquiries have no automatic age-based deletion period. When ONYX1 Office is enabled, it can classify a verified forwarded message and prepare an internal result. ONYX1 does not send a reply automatically. PostHog Inc. processes staff app session recordings and error reports in the United States under its Data Processing Agreement for support, bug fixing and product improvement. PostHog receives the staff user ID, tenant ID and role as identification properties; the app does not add staff names or email addresses to those properties. Form inputs are masked. Text shown on screen and page attributes can appear in recordings, and PostHog's standard retention settings apply. Anthropic, PBC processes Chippy requests (section 7D). GitHub, Inc. hosts our private issue tracker and receives a problem report only when a staff user chooses to log one through Chippy (section 7D). AI assistants and ONYX1 Office, which a trade business chooses and holds with its own AI provider, are covered in section 7A. Airwallex (customer Pay Now) and iPayroll are not live. They will be named here before they receive personal information. Pay-now card details, when that feature is live, will be collected by the payment provider, not by us.

7A. AI assistants and ONYX1 Office

ONYX1 has no AI model of its own and does not use AI to make decisions about you. Apart from Chippy, the in-app assistant described in section 7D, ONYX1 does not send your information to an AI provider itself. Otherwise, information reaches an AI provider when a business's connected assistant or ONYX1 Office asks ONYX1 for it, as described below. ONYX1 can start ONYX1 Office work automatically, for a new enquiry, an email or a standing order. The check ONYX1 runs on uploaded photos reads markers inside the file, on our own servers. ONYX1 sorts incoming business email into enquiries and job correspondence with fixed rules, not AI. We do not use service content or portal content to train AI models. Apart from Chippy, AI can reach information held in ONYX1 in two ways. In both, the trade business decides whether to use it, chooses the AI provider, and holds the account with that provider. If we add another feature that sends personal information to an AI provider, we will update this policy before it does. Connected AI assistants. A person at a trade business can connect their own AI assistant, for example Claude or ChatGPT, to ONYX1. This is available on plans that include AI & integrations and during a free trial, and each person connects separately. The assistant asks ONYX1 for information when that person asks it something; ONYX1 does not push information to it. It can read and change only what that person's role allows in ONYX1, so a technician's assistant cannot see invoices, for example. Depending on the role, it can read jobs, customers and their contact details, sites, quotes, invoices, timesheets and other business records, including files the business has shared with a portal user. Marking an invoice paid, creating a quote or invoice, approving a timesheet and similar actions need a connection set for sensitive actions. ONYX1 then asks the assistant to read that exact action back to the person, and acts only on their confirmation. Through ONYX1, an assistant cannot take a payment or print, and it cannot write and send an email or text message, except an ONYX1 Office email the mailbox owner has confirmed, as described below. An action it takes can trigger ONYX1's usual notifications to staff, as the same action by the person would. What the assistant receives is processed by its provider under that provider's agreement with the trade business or the person, and it may be processed outside New Zealand. An owner or admin can see the business's connections and disconnect any of them in Settings, and a disconnected connection stops working straight away. ONYX1 Office. ONYX1 Office is an optional paid add-on. ONYX1 switches it on for a business, and an owner or admin of that business then sets it up and turns it on. It is a team of AI agents (a Chief of Staff and five specialist roles) that does office work for people at the business. It works on requests people make, on standing orders, and, where the business has set them up, on new website and emailed enquiries and on opted-in email. The agents run on an Office server: a Mac mini the business buys and owns, which the ONYX1 team sets up. After setup, the ONYX1 team removes its own administrator and remote access to it. The agents use Claude, Anthropic's AI service, signed in with a Claude account the business chooses, either a shared account or the business's own. The business decides which. What ONYX1 Office can access. Each agent role has its own key, and ONYX1 lets each key use only the tools listed for that role. An agent works only on a task ONYX1 has passed to it for a named person at the business, and ONYX1 answers it with that person's own permissions. For a new website enquiry, or an enquiry sent to the business's enquiry address, that person is the business's owner. For email that ONYX1 Office handles for a person who has opted in, it is that person. An agent never sees more than that person could see in ONYX1. Depending on the task and the person's role, it can read jobs, customers and their contact details, sites, leads and enquiries, quotes, invoices, timesheets, leave, safety documents and the business's own documents. If that person has connected their own Microsoft 365 account, an agent can also read their email in any folder, their calendar and their files when a task needs them, and save drafts in their mailbox. ONYX1 does not pass email attachment files to an agent. Scheduled work. An owner or admin can set up standing orders, which ask an agent to do a routine task at set times. Each one runs with the permissions of the person who set it up, and ONYX1 checks those permissions again before every run. Email correspondence (section 2) is a separate opt-in for each person. After ONYX1's fixed rules sort a message, an ONYX1 Office agent reads it to prepare the internal task, note, flag, proposal or draft. What needs a person's approval. ONYX1 Office cannot send an email through ONYX1 until ONYX1 has shown that exact message to the person whose mailbox it is, through that person's own connected assistant, and they have confirmed it. ONYX1 then sends it at most once, from that person's own mailbox. ONYX1 gives ONYX1 Office no way to make or take a payment, post to a website or social media, or print. Without a further approval, it can make the changes inside ONYX1 that its role's tools and the person's permissions allow, such as creating or updating customers, jobs, leads and tasks, or adding a job note. A customer, site, job or quote prepared from a new enquiry, and a proposed variation, wait for a person at the business to approve them. The agents also run software on the Office server outside ONYX1. ONYX1's setup instructs them to ask for approval before contacting a customer, publishing, spending money or making a change that is hard to undo, but ONYX1 cannot enforce what happens outside ONYX1. Whether the agents may use the web, files and commands on the Office server is the business's decision. Where ONYX1 Office processing happens. An agent reads ONYX1 information on the Office server and sends it to the business's AI provider. By default that is Anthropic, which processes requests in its standard processing locations, as other cloud services do. Those locations may be outside New Zealand. When the ONYX1 team sets up the Office server, ONYX1 reaches it through a Cloudflare tunnel, and the agents reach ONYX1 directly. Whoever administers the Office server can see the agents' working records on it. After setup that is the business, not ONYX1. ONYX1 keeps only the connection ONYX1 Office needs to pass work to the agents, collect their results and approval requests, and check that the server and its agents are running and set up as installed. If the business pairs the server for updates, the server also checks ONYX1 for ONYX1 Office updates and reports its update status and the health of its agent connections, until the pairing is revoked. Activity records. ONYX1 records in the business's audit log each tool an assistant or ONYX1 Office agent uses and each record or prompt it reads, with the person it was for, the tool, and whether it worked. For most requests it keeps a shortened summary of what was asked, which can include a short excerpt of the words. For Microsoft 365 email, files and calendar, and for Office results, hand-offs and correspondence drafts, it keeps only their length. It does not record what was sent back. The business's owner, admins, dispatchers and office staff can read the audit log, and nobody at the business can edit or delete it. It is kept for the business's activity-history window (section 9). How long ONYX1 Office records are kept. ONYX1 keeps each Office task's instructions and results, approval requests, enquiry proposals and the documents Office creates. For each email an agent asks to send, it also keeps the To and Cc addresses, the subject, up to 2,000 characters of the text and the outcome, including after the email is sent or rejected. We currently keep these records for seven years, or until the business's data is deleted after its account closes (section 9) if that is sooner. We may change this period, and will update this policy if we do. Working records on the Office server, including the AI service's session records, are the business's data on the business's computer. ONYX1 only provides a service on that computer, so the business decides how long to keep them, and ONYX1's deletion does not reach them. The AI provider keeps what it receives under its own terms with the business. Who is responsible. The trade business decides whether its people use an assistant or ONYX1 Office, which provider and plan they use, and who may use them. We hold the business's information on its behalf (section 3). When the business has its assistant or Office agents read that information and send it to an AI provider, the business is the agency that discloses it, and ONYX1 acts on the business's behalf in passing it to the business's own assistant or Office. Where the business chooses a provider outside New Zealand, the business is responsible for meeting Information Privacy Principle 12 for that disclosure. Some AI plans may allow the provider to use conversations to improve its models, depending on the plan and its settings. We strongly recommend that businesses use a business plan that does not train on their data, and each business is responsible for its own plan's data settings. Turning it off. An owner or admin can disconnect any assistant and turn ONYX1 Office off in Settings. While ONYX1 Office is off, its agents' keys stop working. The owner can switch off or delete any standing order, and an admin their own. Each person can opt out of Office email handling on their own account page, which stops ONYX1 checking their Inbox and handling email forwarded to them. Agents can still read that person's Microsoft 365 mail for their tasks until they disconnect Microsoft 365, also on their account page. The ONYX1 Office add-on stays on while the business's plan is active and includes AI & integrations. It ends when the business asks us to remove it, which it can do at any time, or when its account closes. If you are a customer or contact of a trade business, ask that business how it uses AI with your information. You can also contact us at support@onyx1.app.

7B. Digital business cards

Digital business cards are an optional feature for trade businesses on a plan that includes it. A trade business turns cards on, and each person on its team chooses whether to make a card and whether to publish it. What a card shows. A card shows the details the person types into it (their name, and where the business allows it their job title, mobile number, email address and photo) together with details the business sets for every card (its name, logo, website, office phone, address and a short description). Nothing is published until the person turns their card on. The person can turn it off at any time, and an owner or admin of the trade business can switch any other person's card in that business off (a person turns their own card off with its Card is live switch). A card also stops being shown when the person is deactivated, when the business turns cards off, when the business's plan no longer includes the feature, or when the business's account is suspended. Who can see it. A published card is a public web page. Anyone who has its link or QR code can open it without an account. The link contains a long random code, the page is marked so that search engines do not list it, and it is not listed anywhere on ONYX1. The person can issue a new link, which stops the old one working. Because a published card is public, do not put information on a card that you do not want a stranger who has the link to hold. The trade business is responsible for the card details its staff publish. Adding to a wallet. A person can add their card to Apple Wallet or Google Wallet. When they do, the details on the card are sent to Apple or Google, which store the pass on the person's devices under their own privacy terms. Apple receives the name, and where the business allows them the job title, mobile, email and photo, plus the business's name, logo, colours, website, office phone, address and description, and the card's link. Google receives the name, and where allowed the job title, mobile and email, plus the business's name, logo, colours, website and the card's link. When the card is later changed, switched off or the link is reset, we send the update or removal to that wallet. Apple also tells us a device identifier and a push token so the pass can be updated, which we keep only while that pass is installed. Removing the pass from the wallet stops those updates. People who open a card. We do not ask a person who opens a card for any information, and we do not use cookies, advertising or analytics services on the card page. We count how many times each card page is opened as a simple total for that card, shown to the card's owner and to the business's owner and admins. We do not store who opened it. To stop guessing and scraping we count requests from each device. The counter is stored under a scrambled form of the device's address (a keyed hash that cannot be turned back into the address without our server secret) and holds only that scrambled value, a time window and the count; the address itself is not stored in it. A weekly clean-up deletes counters once they are more than a day old, so a counter can remain for up to about eight days. Separately, our hosting provider keeps ordinary service logs that include the address of the device that made the request (see section 2, technical information). The page offers a button that downloads the card's details as a contact file to the person's own device, and links that open their phone's call, text, email, maps or browser apps. Those apps, and the trade business's own website, are not run by ONYX1.

7C. Outside people who sign on site

A trade business can record people who are not on its team but work on its sites, such as contractors from another firm, so they can sign the same site documents as its crew (for example a pre-start, a permit to work, an incident report or an end-of-day report). The outside person has no ONYX1 account and does not use ONYX1 themselves. They sign on a phone held by a member of the business's team. What is recorded. The outside person's name and, if given, their company, typed by the team member; the days and jobs they were recorded on site; and each signature they draw, with the time, the document it was given on and the team member whose phone captured it. The business keeps a list of outside people it has worked with so it does not have to type them again, and can edit or archive that list. A signature keeps the name as it was when the person signed. Who can see it. The business's own team, by role, and anyone the business sends the signed document to, such as its customer through the client portal or by email. Signed site documents are health-and-safety records and are kept as section 9 describes. Client-issued site documents. Some clients require their own site paperwork in place of ONYX1's. A trade business can then file a photo or PDF of that client's own site document, which may show the names and signatures of the people who signed it. ONYX1 stores it as that day's site document, and the business reviews and approves it like its own. The trade business is responsible for this information (section 3). It should tell outside people that it records their name, company and signature in ONYX1, and requests to see or correct those records go to that business. We will help it respond.

7D. Chippy, the in-app assistant

Chippy is an assistant built into the ONYX1 staff app, on the web and in the ONYX1 phone apps. A staff user can ask it how to use ONYX1 and ask about their business's records. Portal users, email contacts and outside people on site cannot use it. Chippy only reads: it cannot create, change, send or delete anything. Each person can hide it with the Show Chippy switch on their own account page, or in More in the phone apps. What is sent to Anthropic. Chippy runs on Claude, the AI service of Anthropic, PBC. When a staff user asks Chippy a question, ONYX1 sends Anthropic the question, the conversation so far, the person's role and plan, the page they are on, the help-centre text that relates to the question, and the records Chippy looks up to answer it. Chippy looks up records with that person's own permissions and never sees more than the person could see in ONYX1. Those records can hold personal information about the business's customers, contacts and staff, such as names, contact details and job details. ONYX1 does not add the person's name or email address to the request, but they can appear in what the person types or in a record Chippy looks up. How Anthropic handles it. Anthropic processes these requests for ONYX1 under its commercial terms, which do not allow it to train its models on them. Anthropic is a United States company, and requests may be processed outside New Zealand, including in the United States. We remain responsible for this information under the Privacy Act 2020, including for keeping it secure (Information Privacy Principle 5) and for its processing outside New Zealand (Information Privacy Principle 12). We have asked Anthropic not to retain Chippy requests (zero data retention). Until Anthropic confirms that, its standard retention applies: it deletes requests and responses within 30 days, except that it may keep them for up to 2 years, and safety classification scores for up to 7 years, where its automated trust and safety systems flag a request, and for longer where the law requires. We will update this policy when zero data retention is confirmed. Who holds and reads chats. ONYX1 LIMITED holds Chippy chats as its own information, not on behalf of the trade business, and uses them to provide Chippy, answer support requests and improve ONYX1 and its help centre. Each person can see only their own chats. Nobody at the trade business, including its owner and admins, can read another person's chats. Apart from a chat a person sends us with Send to support (below), ONYX1 staff can read chats only through ONYX1's separate administration console, to answer a support request, to look into a problem report, to review misuse or to improve the service, and each time they open one it is recorded. We keep each chat for 90 days and then delete it. Send to support. If a person asks Chippy to reach a person, Chippy shows a Send to support card in the chat, with a message the person can change. Nothing is sent until the person selects Send to support on that card. Then ONYX1 emails the message, the chat, the person's name, company and role, and the page they were on, with the business's plan, the app they used (web, iPhone or iPad) and its version, and the last "Why?" explanation they opened in that chat, to our support team at support@onyx1.app through Resend, with the person's email address to reply to. That email is kept with our support correspondence. Problem reports. If a person tells Chippy about a fault in ONYX1 or asks for something ONYX1 does not do, Chippy may show a card offering to log it for the ONYX1 team, with a title, summary and steps the person can change. Nothing is sent until the person selects Log it on that card. Then ONYX1 removes email addresses, phone numbers and links from that text and sends it to our private issue tracker on GitHub (GitHub, Inc., a United States company), with the business's name, account number and plan, the person's role, the part of ONYX1 it is about, the page they were on, the app and its version, the date, and a link that only ONYX1 staff can use to open the chat in our administration console (each opening is recorded). The report does not include the chat, the person's name or email address. If the same problem is already logged, the report is added to it. We keep our own record that a report was logged, without its text, for 90 days. The report stays in our issue tracker as part of our development records. Topics and gaps. For each answer we record the general topic of the question (for example jobs or timesheets) and, as a code, whether Chippy found no help article, offered Send to support, could not show something to the person's role, or gave no answer. We use these codes, counted across all businesses, to improve ONYX1 and its help centre. Where Chippy found no help for a question, or gave no answer, ONYX1 staff can see that question in our administration console, with the name of the business. We do not show who asked, but anything the person typed in the question is visible, apart from email addresses, phone numbers and links, which we remove. Each time they look, it is recorded. They may write a short answer in their own words, without business or personal names, which Chippy can give anyone who asks something similar. Chippy does not learn from chats. What's new. Chippy can show a short note about new features. We record when each person last dismissed a note, or which app version's note they last saw, so each note shows once. Limits and misuse. To apply Chippy's limits we record how many questions each person asks and how much of the AI service they use. When a request shows a sign of misuse, such as an off-topic question, an attempt to get around Chippy's rules, a burst of requests or a very long question, we record the kind of signal and the time, not the chat text. The ONYX1 team can see these records and can pause or switch off Chippy for that person.

7E. Company announcements

A trade business's owners and admins can send short announcements to the people on their team in ONYX1. For each announcement we store its text, who sent it, who it went to, and whether and when each person pressed Got it (a read receipt). The business's owners and admins can see the read receipts. An announcement shows in each person's notifications and in Chippy, and can reach their phone or browser as a notification, depending on their notification settings (section 7). We delete each announcement and its read receipts 6 months after it was sent. An announcement's text is not sent to Anthropic. If an owner or admin asks Chippy to help write one, their request is a Chippy chat (section 7D) and nothing is sent until they press Send.

8. Security

Information is encrypted in transit and at rest. Every business's data is isolated at the database layer (row-level security), access within your business is controlled by roles you assign, passwords are hashed with a modern algorithm, and two-factor authentication is available for every account. Certificate files are private files, never public links. Only the staff user the certificate belongs to and the people the business lets see its compliance register (its owners, admins, office staff, dispatchers and site supervisors, and anyone it gives access to the register) can open them. Only an owner or admin can delete one. Only the business's owners, admins and site supervisors can see the person involved and their injury in an incident investigation; other staff who can see the incident register see the incident without them. No system is perfectly secure, but security is engineered into the product, not added on.

9. How long we keep information

While a trade business's account is active, three kinds of operational data age out on that business's plan window, which is 1 year on Basic, 3 years on Pro and 5 years on Enterprise: site photos, in-app notifications and activity history. A monthly job deletes them once they are older than the window, automatically and with no warning beforehand, so anything worth keeping should be exported while it is still inside the window. Financial and statutory records, including the health-and-safety register and signed site reports, are never rotated and are kept for the life of the account in line with New Zealand record-keeping law. Correspondence content is stored with its related enquiry or job record for up to 365 days from receipt. A daily job purges the message text, attachment filenames, mailbox and Graph identifiers, duplicate-matching fingerprints, correspondence private notes and action payloads after that period. The same content is purged sooner when the linked enquiry, job or customer is deleted or when a message is classified as not an enquiry. Content-free provider-event and duplicate-match hashes remain until 365 days after receipt only to prevent a retry or another opted-in Inbox copy from restoring purged content. Tasks, variation proposals and active cost-approval flags created from correspondence remain as business records under their own retention rules. Chippy chats are kept for 90 days and then deleted (section 7D). Company announcements and their read receipts are deleted 6 months after they were sent (section 7E). HR records and certificate files are not on the plan window. An HR record is kept for as long as the business's account is open: the business can correct it but cannot delete it. A certificate file is kept until an owner or admin deletes it, or until the account closes. Replacing a certificate file keeps the old one as a previous file, because the business may need it as evidence under the Health and Safety at Work Act 2015. A business should delete copies of identity documents and licences it no longer needs, for example for people who have left (Information Privacy Principle 9). Incident investigations are part of the health-and-safety register. They, with the details of the person involved and their injury, are kept for the life of the account like the rest of the register, because the Health and Safety at Work Act 2015 requires a business to keep records of notifiable events for at least 5 years. ONYX1 Office task records, approval requests and documents are currently kept for seven years, and Office working records on a business's own Office server are the business's to keep or delete (section 7A). When a trade business's account closes, that business has 30 days to export its data, after which we delete personal information unless we are legally required to keep it. Closing an account also ends its people's ability to sign in, so a closed business cannot export by itself: email support@onyx1.app within those 30 days and we will either restore access long enough for you to export or produce the export for you. Ask before you close if you can. Portal accounts are separate from trade-business accounts. Revoking the last provider link does not delete a portal login. The retention period for an unlinked portal login and its acceptance records is not yet determined; contact support@onyx1.app to request closure or ask what remains held.

10. When we disclose information

To the processors in section 7, to the extent needed to run the service; when the law requires or permits it (for example a court order or a Privacy Act request); and in a business sale or restructure, to a successor bound by this policy. Never to advertisers, and never for profit from the data itself. For correspondence intake, this includes Microsoft Graph/Microsoft 365 for each person's opted-in account and Resend for email forwarding configured by the business. ONYX1 sorts each message with fixed rules. When the business uses ONYX1 Office, its Office agents read the message and send it to the business's own AI provider to prepare any internal actions or Outlook draft (section 7A).

11. Your rights of access and correction

You may ask for a copy of the personal information we hold about you and ask us to correct it (Information Privacy Principles 6 and 7). Write to support@onyx1.app. Say whether you are a staff user, a portal user, or an email contact, and which email you use. We respond within 20 working days as the Act requires. Portal users can already change their sign-in email, password, two-factor settings and email-notification choices on the account page. They cannot change a trade business's job file (the name on an invoice, a site address) from the portal. That correction goes to the trade business. If you want the portal login closed, email support@onyx1.app. Closing the login does not by itself delete invoices or reports held for a trade business. If you are not satisfied with our response you can complain to the Office of the Privacy Commissioner, privacy.org.nz, through its website.

To ask us to delete an account and its personal data, including without the app installed, see Delete your account and data.

12. If something goes wrong

If a privacy breach occurs that is likely to cause serious harm, we will notify the Office of the Privacy Commissioner and the affected people as soon as practicable, as Part 6 of the Privacy Act 2020 requires. We will say what happened, what information was involved, and what we are doing about it. If the breach is of a portal login (emails, passwords, sessions), we notify the portal users. If it is of a trade business's job file, we notify that business so it can notify its customers, and we notify individuals ourselves where we are required to. If it is of both, we do both.

13. Cookies

ONYX1 uses cookies to keep you signed in, to keep the service secure, and to remember display choices you make. The client portal uses omni_customer_session for its 14-day sign-in session, including access to shared media, and omni_customer_mfa during two-factor sign-in. Quote links do not require an account cookie. The staff app also stores four preference cookies for a year each: hh-theme (light or dark), hh-text (text size), hh-nav-collapsed (sidebar width) and hh-view (which home screen you last used). They hold only that choice and are not used to identify or follow you. We do not use third-party advertising or cross-site tracking cookies.

14. Changes and contact

If we change this policy materially, the new version takes effect when we publish it, and we ask for acceptance then rather than after a notice period. We do not currently send advance notice by email. A trade business's owner or admin is shown the new version in the app and must accept it before they can keep using the service. A portal user is shown the current collection notice and asked to accept it the next time they sign in. The version a trade business accepted, and when, is recorded and available to that business. Contact: support@onyx1.app. ONYX1 LIMITED, a New Zealand Limited Company, company number 9453894, NZBN 9429053908322, registered 23 August 2026. Registered office: 189 Upper Harbour Drive, Greenhithe, Auckland, 0632.