Bloodstock AI

Privacy Policy · version 2026-09-16

Privacy Policy

This notice describes, in plain English, what personal information Bloodstock AI collects, why we collect it, where it is held and how to have it removed. It describes the app as it is built today. Where something is not collected, or is not built yet, this notice says so rather than leaving you to guess.

Who we are

Bloodstock AI is operated by the company named below.

Legal name: BLOODSTOCK AI LIMITED (company number 9400808)

NZBN: 9429053403780

Registered address: 506 Harrisville Road, RD 2, Pukekohe 2677, New Zealand

Privacy questions are handled by: Will Lieshout

Privacy questions reach that person at support@thebloodstockai.com.

What we collect

When you register we collect the account details you provide: your name, email address, and password. Your password is stored only in hashed form by our authentication provider and is never visible to us. We also hold the session data needed to keep you signed in. If you ask to be let in before you have an invitation, we hold the name and email address you give us on that request until it is approved or declined.

When you accept our Terms of Use we record which version you accepted and when, together with the network address the acceptance came from and the browser or device description your app sent with it. That record exists so we can say what a person agreed to on a given day. It is held against your account and goes when your account goes.

As you use the app we hold the material you create, scoped to your account: shortlists, tracked lots, inspection notes and checklists, saved alerts, and any feedback, data-issue reports, or reports about a message in a team that you send us. A report about a message necessarily carries that message and the account that wrote it; the Teams and messages section below says exactly what it holds and why. Notes and inspections can include photos and voice notes captured with your device's camera and microphone, with your permission; these are stored alongside your notes. If you ask the app to transcribe a voice note, the audio clip is sent to a transcription provider to produce the text, which is stored with your note. When transcription is switched on that provider is OpenAI, in the United States; when it is off the app says so and no audio leaves our storage.

If you set up buying preferences we hold what you enter: your goal, budget ceiling, sex and distance preferences, risk tolerance and preferred sires, together with any private bid ceiling you set on a lot and the match results generated from them. We treat these as commercially sensitive, use them only to run your own matching and budgeting features, and never show them to other users.

We also hold your settings (language, appearance, experience level and notification preferences) and a record of the moments you use the app: signing in, opening a sale or a lot, a search that found nothing, adding or removing a shortlist entry, opening a report, and starting a team, together with the page it happened on. The record of what you open on a lot feeds the app's own popularity signals; the rest is how we see whether the app is working. None of these records carries free text: not what you searched for, not what you wrote in a note, not a message.

If you turn on push notifications we hold the device or browser token needed to deliver them and a history of the notifications we have sent you. Notifications travel through your device platform's or browser's own push service on the way to you.

When you open a page, the service that hosts the app records the request: which page, when, the network address it came from, and the browser that asked for it. That is the ordinary record a web server keeps, and it is how the app is delivered and kept safe from abuse. We also read the address a request comes from while the request is being handled, to slow anyone hammering our sign-in or our data, and we keep no record of it for that purpose.

If you ask the app to show sales near you, your browser asks your permission first and then hands the app your approximate position. It is used on your device to sort the list in front of you. It is never sent to us and it is never stored.

We plan to collect basic error and performance diagnostics to keep the service working. The app does not collect these today; we will update this notice before that starts.

Why we collect it

To provide the service: to sign you in, keep your lists, notes and saved work available across your devices, run the matching and alerts you set up, and deliver the notifications you ask for. We do not sell your personal information. There is no advertising in the app, no analytics company is wired into it, and nothing in it follows you to other apps or websites.

Where it is held

Your account and app data are held by Supabase, our database and authentication provider, hosted in the Sydney (Australia) region. The app itself is served by Cloudflare, which keeps the request records described above. Questions you type into Ask are processed by Anthropic in the United States (see The Ask assistant below). The app takes no payments: there is nothing to buy inside it, and we hold no payment details of any kind. If that ever changes, this notice will say so before it does.

The Ask assistant

Ask is the in-app assistant. When you use it, the question you type is sent to Anthropic, a United States company, whose AI model generates the answer. The catalogue and analysis data needed to answer it is sent in the same request, and Anthropic handles what it receives under its own terms. We do not store your questions on our servers; your conversation history stays on your own device. Please do not type anything into Ask that you would not want a third party to process.

Teams and messages

A team is a few people buying a horse together. What you write in a team's threads, and any photo you add, can be read by the other members of that team. Nobody outside the team can read any of it unless a member of it sends it to us: there is no administrator view of a team's threads, and no rule in our database that would grant one. We do not read, moderate or review what you post of our own accord, and nothing is checked before it appears.

A member can report a message from the thread it is in, and that report is how a message comes to us. It carries the message itself, the account that wrote it, which team and thread it was in, when it was written, how many photographs were on it, the reason the member chose, and anything they added in their own words. It is held with the rest of the feedback people send us, against the account of the person who reported it, and a person here reads it. Where we find that a message breaks our Terms of Use we can take it down. Nobody is told who reported them. You can leave a team at any time from the people list, on the team or on any of its threads, and a team's owner can remove anyone on it.

People join a team with a code the owner generates and passes on themselves, so we never email anyone on a team's behalf, and a team cannot see anyone's Blackbook or private notes.

We keep a team's threads while the team exists. Unsharing a horse hides its thread rather than deleting it, and sharing the horse again brings it back. Deleting a team deletes its threads, messages, invites and membership records for everyone on it, and removes its photos from storage; there is no way back from that. A message you remove yourself is emptied where it stood, so the conversation still reads in order and what you wrote is gone. When your account is deleted, the messages you wrote in any team are emptied the same way with your name taken off them, your photos are removed from storage as part of the deletion, and a team you own passes to the member who has been on it longest, or is deleted if nobody else is on it.

Photos added to a team message are held in our private storage under that team's own folder, and are never published. To show one to a member we check that they are on the team and then hand their browser a link that stops working after an hour. A photo is deleted when the message it belongs to is removed, when the team is deleted, or when your account is deleted.

How long we keep it

We keep the data described above while your account exists. When your account is deleted, the data held against it is deleted with it. Where the law requires us to keep a record, we keep only what the law requires and remove the link to your identity when your account is deleted: business records are kept for seven years under New Zealand tax law, with your name and account taken off them.

Your choices and rights

Under the New Zealand Privacy Act 2020 you may ask us for a copy of the personal information we hold about you, and ask us to correct it. You may also delete your account and the personal information we hold from inside the app: open Account, choose Delete your account, and confirm. A person completes the deletion, so it is not instant; we check for new requests at least once a week, so you will hear from us within seven days, your account works as normal until it is done, you can change your mind in the same place until then, and we confirm by email when it is. If you cannot sign in, email support@thebloodstockai.com from the address you signed up with instead and a person will complete it the same way. For any of these requests, or any question about this notice, write to support@thebloodstockai.com and a person will answer.

If you are not happy with how we have handled a privacy request, you can complain to the Office of the Privacy Commissioner at privacy.org.nz.

Changes

We update this notice whenever our handling of personal information materially changes, and the version shown at the top of the page changes with it.