Privacy

What you enter stays on your device

The feed tool does all its calculations in your browser. The diets you build, the feed prices you edit, your currency choice and any saved scenarios are stored locally on your device (using your browser’s local storage) — not on a server. They never leave your device unless you choose to share them (see below). Clearing your browser data for this site removes them.

Importing a lab PDF

When you import a lab report (e.g. a Hill Labs Certificate of Analysis), the PDF is read in your browser. The file is not uploaded to us or to anyone else — only the numbers you confirm are added to your diet, and they stay on your device like everything else.

Sharing a diet by link

If you use the “Share” button, the diet is encoded into the link itself. That data isn’t sent to us — but anyone you give the link to can open it and see the diet, so only share it with people you intend to.

If you contact us

When you send a message through our contact form, the name, email and message you enter are emailed to us so we can reply. We don’t store contact messages in a database, and we only use them to answer you.

The “Send feedback” button inside a Feedwise account works differently: that message is saved to our database, together with your email address and the date, so we can read it, reply and keep track of what’s been actioned. We use it only to improve Feedwise and to get back to you. It’s deleted with your account.

Hosting

The site is hosted on Cloudflare Pages. Like any website host, Cloudflare automatically processes basic technical information needed to deliver the site and keep it secure — such as your IP address, browser type and the pages requested — in short-lived server logs. We don’t use that information to identify you.

Cloudflare also sits in front of the signed-in app at app.feedwise.co.nz (not just this website), so the same technical information passes through it when you use your account. The app itself, and your data, run on our own server — see If you have a Feedwise account.

Analytics

We use Cloudflare Web Analytics to understand how many people visit and which pages are useful. It is privacy-first: it doesn’t use cookies, doesn’t track you across other websites, and doesn’t build a profile of you. It only gives us aggregate numbers (like total page views, referring sites, country and browser) — never anything that identifies you personally.

Separately, the four free calculators send us a one-line anonymous count when a tool is opened, first used, or printed — literally which of the four it was and which of those three things happened. No cookie, no identifier, no account, and none of your farm figures: the diet you built is not included and never leaves your device. We keep it as a daily total per tool, so it tells us that (say) the pasture tool was opened 40 times yesterday and nothing whatsoever about who opened it. It’s how we know which tools are worth improving.

Cookies

The free tools use no cookies at all — and never any tracking or advertising cookies. The only thing this site stores in your browser is the local storage described above, which exists purely to make the tool work and remember your inputs between visits. If you sign in to a Feedwise account, a single strictly-necessary login cookie is used to keep you signed in — see If you have a Feedwise account below.

What we collect when you have an account

Only what you give us to make the product work:

• Your sign-in details — your name, email address and password. Your password is stored only as a one-way encrypted (hashed) value; we never see or store the password itself.
• Branding you add (optional) — if you set up branded reports: your firm name, contact details, a brand colour, a footer line and a logo image.
• The farm work you save — the farms you create and the analyses, feed scenarios, comparisons and reports you save under them (the animals, feeds, soil tests, prices and notes you enter). We treat this as yours.
• A login cookie — a single, strictly-necessary cookie that keeps you signed in. It isn’t used for advertising or cross-site tracking.
• Basic technical logs — like any web app, our server keeps short-lived logs (such as IP address and requests) needed to run the service and keep it secure.

We use this information only to provide the account — to sign you in, save and show your work, and generate your reports. We don’t sell it, and we don’t use it to build an advertising profile.

Where your account data is stored

Account data is held in our own PostgreSQL database on a private server we run with Vultr, located in Sydney, Australia. This means your account information is stored in Australia rather than New Zealand. Australia has privacy laws broadly comparable to New Zealand’s, and we rely on Vultr only for the underlying infrastructure — they don’t use your data for their own purposes.

Backups. We take a nightly backup of the database so an outage or a mistake doesn’t lose your work. One copy stays on that same server. A second copy is encrypted first (AES-256) and stored with Cloudflare R2, set to the Oceania region. The encryption key never leaves our server, so the off-site copy is unreadable to Cloudflare or anyone else who obtained the file. How long we keep those is under How long we keep it.

Who else is involved (sub-processors)

We keep outside services to a minimum. Currently:

• Vultr — hosts the server and database for the signed-in app (Sydney, Australia).
• Cloudflare — serves this website, sits in front of the signed-in app, provides the cookieless analytics above, and holds the nightly encrypted database backup (R2, Oceania region — encrypted before it leaves our server, so Cloudflare cannot read it).
• Resend — sends the handful of automatic emails the app needs: a password-reset link when you ask for one, and an invitation when someone adds you to their account. They receive the recipient’s email address and the message itself. We do not send marketing email, and there is no mailing list.

We don’t use a payment processor (there’s nothing to pay for yet), an advertising network, or any analytics beyond what’s described above. If we add a sub-processor we’ll list it here — and we’ll do that before it starts handling your data, not after.

Keeping it secure

Traffic to and from the app is encrypted in transit (HTTPS), passwords are stored hashed, and access to the database is restricted. No system is perfectly secure, and this is a beta — we take reasonable steps to protect your information and will keep improving them as the product matures. If a privacy breach occurs that is likely to cause serious harm, we’ll notify those affected and the Privacy Commissioner as required by the Privacy Act 2020.

Your privacy rights

We follow the New Zealand Privacy Act 2020. For the free tools we hold no personal information about you, so there’s little to access or correct. If you have an account, you have the right to ask for a copy of the personal information we hold about you, to have it corrected, or to have it deleted — just get in touch and we’ll help. If you’re ever unhappy with how we’ve handled your information, you can also raise it with the Office of the Privacy Commissioner.

Children

Feedwise is a tool for farmers and farm advisers. It isn’t directed at children, and we don’t knowingly collect personal information from anyone under 16.

Changes to this policy

If we add features that change how data is handled, we’ll update this page and the “last updated” date above. As the account product moves out of beta — and before we take any payment — we’ll formalise the operating entity and revise this policy accordingly.