Privacy policy

Effective 12 October 2026.

Qunei is operated by The Ravenshield Corporation (New Zealand) Limited (“we”, “us”). This policy explains how we handle personal information. It is structured around the information privacy principles (the IPPs) of the New Zealand Privacy Act 2020, and each heading names the principles it answers.

What we collect, and why (IPP 1)

We collect only what running the service requires:

Where it comes from (IPPs 2, 3 and 4)

We collect personal information directly from you, or from your AI agent acting on your instructions inside your workspace. We tell you what we collect at the point we collect it, and we collect it openly and lawfully. We do not buy information about you and we do not gather it from third parties behind your back. The third parties we read from are your bank, through Akahu (only after you switch that on yourself; you can switch it off on your Bank feeds page at any time), and Postmark, when you forward email to a ledger's forwarding address. If you use email to your ledger, Postmark receives the email sent to your ledger's forwarding address and passes it to us. We keep each attachment (or the email's text, when no attachment is kept), its file name, the sender's address, the subject, the spam score Postmark assigned, and the email's Postmark message ID, in that ledger's inbox, where your AI reads them. We do not keep the rest of the email.

Storage and security (IPP 5)

Your data is encrypted in transit. Access to production systems is limited to the people who operate the service, and every ledger is isolated to its own workspace. We never hold your bank password: you sign in at your bank, and the access token Akahu gives us is encrypted at rest. Hosting: Fly.io, with the application and your data hosted in Sydney, Australia.

Seeing and correcting your information (IPPs 6 and 7)

You can ask us for a copy of the personal information we hold about you, and ask us to correct anything that is wrong. Your books themselves need no request at all: your workspace can always read and export every ledger in it, whatever the state of your subscription.

Accuracy and retention (IPPs 8 and 9)

The ledger is append-only by design: a correction is a new entry that links back to what it corrects, so the record of what changed, when, and by whom, is never lost. Because of that, the email address recorded against an entry stays in the books’ history, even after that person leaves the workspace. We keep your books for as long as you keep your workspace. If your trial or subscription lapses, the workspace becomes read-only and nothing is deleted. If it stays read-only for 30 days, we end our access to its bank connections at Akahu, after emailing the people concerned a week before. If you ask us to delete your workspace, we will, and backups clear within 30 days. Disconnecting a bank deletes the access token and the account list at once. Transactions already fetched are your accounting records and stay with your books, read-only like everything else, until you ask us to delete your workspace.

Use and disclosure (IPPs 10 and 11)

We use your information to run your workspace, bill your subscription, and answer your support messages. Nothing else: no selling, no advertising, no profiling. We disclose personal information only to the service providers below acting on our instructions, when you ask us to, or when the law requires it.

When you connect an AI agent to Qunei, it reads your books, including bank-feed transactions, when you ask it to, and its provider handles that data under its own terms.

Inside a workspace, the people you invite see what their access allows. People with a member role, such as your accountant or bookkeeper, choose which of the workspace's ledgers a connected bank account feeds, and everyone with access to those ledgers sees its bank-feed transactions. The workspace's billing owner sees everyone's bank connections and can disconnect them.

When you connect a bank, we send Akahu your email address the first time, or your Akahu user ID after that, so that Akahu can fill in its sign-in for you. We keep your Akahu user ID after you disconnect, so that reconnecting lands in the same Akahu account; ask us and we delete it.

Who processes data for us (IPPs 11 and 12)

Unique identifiers (IPP 13)

We do not ask for, assign, or store government identifiers such as IRD numbers as account identifiers. Your email address is how we know you. A connected bank account's number is held only to identify that connection, never as an identifier for you.

People who appear in your books

Your ledgers may hold personal information about your customers, suppliers, and staff. You collect that information and you decide what goes in the books; we store and process it on your behalf and apply the same protections described above. Details that arrive through a bank feed, such as a payer's name or a payment reference, are part of those books and are treated the same way.

No trackers

This site makes no requests to third parties from your browser and runs no analytics service. The one thing we count is how many visits and new workspaces come from links we tag, such as an ad: a daily total for each tag, kept in our own database. The count sets no cookie, keeps no IP address, and records nothing about which visitor or workspace it was. What you do here stays between you and us.

Complaints and contact

Questions and requests go to our privacy officer, Rahul Pandey, at hello@qunei.ai. If you are not satisfied with our answer, you may complain to the Office of the Privacy Commissioner at privacy.org.nz.

Changes

If this policy changes, we will post the new version here with a new effective date, and tell you about any change that matters.