Service status: Live status Request access

Legal

Privacy Policy

Effective date: 16 October 2026

This policy explains what personal information we collect through PaddockPath, what we use it for, who else handles it, where it is kept and for how long, and how to contact us about it.

"We" are Quinence Australia Pty Ltd (ABN 54 687 576 290), Suite 302, 13–15 Wentworth Ave, Sydney NSW 2000. We run PaddockPath: the Feedlot, Producer and Farm web apps, the PaddockPath Feedlot app for iPhone and iPad, shared report links, our help site at docs.paddockpath.com, our newsletter, the presentation decks we share at events, and paddockpath.com (together, "the Service").

Our customers are businesses, most of them feedlots. Your company decides who has an account and what goes into its records. Most of what PaddockPath holds is business information about cattle, feed, health and money. This policy covers the personal information within those records and around them.

1. What We Collect

Your account

  • Your name, email address and role, and the company you work for.
  • Each attempt to sign in: a hashed form of the email address used, the IP address and whether it worked. For a demonstration login, we keep the email address itself and the browser details as well.
  • Your signed-in sessions, including the IP address and the browser or device each one came from.

Your company's records

The records your company keeps can include personal information about other people, for example:

  • names, email addresses and phone numbers of contacts at partner businesses, agents and transport companies, including drivers
  • names on consignment paperwork such as NVDs, and signatures added to documents
  • the names of staff on the records they made, and who changed a record and when

Photos and files

  • Photos taken in the iPhone app of arrival paperwork and of mortalities.
  • Documents and spreadsheets uploaded to the web apps.

These are stored in your company's own file storage. Some are also read by an AI service, as section 4 explains.

Voice search in the iPhone app

The app turns speech into text on the device, and the audio is never sent anywhere. What it heard, and what you changed it to, are saved with your company's records. Pairs of what it heard and what it was corrected to, with counts of use, are also copied to our own systems so we can measure how well recognition works.

Feedback and support

  • Feedback sent from the web apps goes through a form run by Userback. It collects your message, your email address, a screenshot if you add one, the page you were on and your browser details.
  • Feedback sent from the iPhone app includes your message, a screenshot if you add one, the app version, device model and iOS version, your feedlot and when it last synced, together with your name and email address.
  • Emails you send us.

How the Feedlot web app is used

Which pages and features are used, errors, and recordings of sessions with the page's text, form entries and images hidden. Section 3 explains.

  • When your team shares a report, files or a mob with someone outside your company, we keep the recipients' email addresses. When a recipient opens the link, we record their email address, IP address and browser details, and the single-use codes we send them.
  • For reports and shared links sent by email, we record whether each email was delivered, bounced or marked as spam.

Our websites, newsletter and presentation decks

  • The request access form on paddockpath.com sends us your name, role, email address, phone number, business details and anything you write in it.
  • If you sign in to view one of our presentation decks, we collect your email address and name, your IP address, the country it points to and your browser details, and we tell our team in Slack that you signed in.
  • If we invite you to our newsletter, we keep your name, email address and company. For each sign-in code we send you, we record the IP address it was requested from. Each time you open an edition, we record your email address, IP address, browser details and the country the IP address points to.
  • The newsletter and the presentation decks keep these records in a Supabase database in AWS's Sydney region, separate from our customers' databases.
  • paddockpath.com sends PostHog which pages are opened, what is clicked and the city your IP address points to, without cookies, as section 3 explains. Videos on our changelog, help site, newsletter and presentation decks stream from Mux, with its viewer analytics turned off.

2. How We Use It

  • To sign you in and keep accounts secure.
  • To run the Service for your company: to store, sync and show its records, and to send the emails your team asks us to send.
  • To send records to another PaddockPath company, or to a person outside your company, when your company sets that up.
  • To answer support requests and find and fix problems.
  • To understand how the apps and paddockpath.com are used so we can improve them, using the analytics in section 3.
  • To know when someone opens a link to paddockpath.com that we sent them, as section 3 explains.
  • To bill your company, from its daily head counts.

We don't sell personal information, and we don't share it with advertisers or data brokers. We don't use your company's records to train AI models.

3. Analytics and Session Recordings

The Feedlot web app sends PostHog, an analytics service in the United States:

  • which pages are opened and which features are used, including the element that was clicked but not its text
  • error reports from the browser and from our servers, which can include the text of an error message
  • logs of the requests our servers handle: the address called, its result and how long it took, with your account's ID number
  • recordings of sessions in the web app

A recording hides the words and numbers shown on the page, the labels and tooltips that go with them, anything typed into a form, and all images, video and embedded documents. It keeps the layout of the page and where the pointer moved and clicked. The browser console isn't recorded. The addresses of the pages you open, of the links on them and of the requests the app makes are sent without the part after "?" or "#", which is where a search or a sign-in code can appear. A link that starts an email or a phone call is sent without the address or the number.

We identify you to PostHog by your account's ID number and your role, and we attach the name of your feedlot. We don't use your name or email address to identify you.

paddockpath.com also sends PostHog:

  • which pages are opened, the site that linked to them and how far down each one is read
  • which links and buttons are clicked, with their words, and where on the page each click lands, but never what is typed into a form
  • when a film is started and when it is watched to the end
  • that a request for access was sent, with the form and products it named but none of its answers
  • the country, state and city your IP address points to

It sets no cookies and keeps nothing in your browser. With each page, PostHog receives your IP address and your browser's details, such as its type, language and screen size. It uses your IP address and browser to count each visitor once a day instead of a cookie, then drops the IP address. Our host, Vercel, looks up the country, state and city your IP address points to, and the site sends PostHog that place with each page. paddockpath.com makes no recordings.

A link to paddockpath.com that we send you ourselves can end in a short code that is yours alone. PostHog gets the code with the page the link opens, and can tie the other pages you open that day to it, so we can see that you opened the link and what you read. Only our own list says whose code it is: PostHog never gets your name or email address. If you forward the link, its code goes with it.

The Producer and Farm web apps and the iPhone app don't send anything to an analytics service.

4. AI

Reading documents and imports

When you ask PaddockPath to read something, we send it to Google's Gemini model through OpenRouter. Both are in the United States. This includes:

  • photos of arrival paperwork taken in the iPhone app. When the phone has signal, every arrival photo is sent this way; without signal, the app reads the photo on the device instead
  • documents and spreadsheets uploaded to the Feedlot web app to bring in animals, carcase results, feed, medications, service fees or arrival paperwork
  • documents and spreadsheets uploaded to the Producer and Farm web apps, such as invoices, sales orders, NVDs, dispatch and kill sheets, and weighbridge and NFAS dockets
  • the figures in a cohort report, when you ask for a written summary of it

With a file, we send the lists needed to match it to your records, such as your pen names or product names. What comes back is a draft, and nothing becomes a record until someone at your company checks it and saves it.

We don't use your company's records to train AI models. OpenRouter and Google handle what we send under their own terms, and may keep it for a limited time.

Your company's own AI assistant

If your company asks us to turn it on, a connector lets an AI assistant your company uses, such as Claude or ChatGPT, read your PaddockPath records. The connector currently runs in one of Vercel's United States regions. What the assistant reads goes to that AI provider under your company's own account with it. We keep a record of each query the assistant runs through the connector, and of any feedback it sends us about an answer, with your account's ID number.

Our own use of AI

We use Claude, from Anthropic in the United States, to build and support PaddockPath.

  • Our support assistant uses Claude to look into a support request when someone on our team starts it. It runs on GitHub's servers. Each time it runs, it can read only the database of the company whose request it is looking into, through a login that can't change anything there. It can't contact you: what it finds goes to our team as notes. What it reads is sent to Anthropic.
  • Our engineers use Claude when they investigate a problem, and it can see records from your company's database while they do.

5. Who Else Handles It

Our team

People on our team can see your company's records when they support you or run the Service.

Our service providers

These companies handle personal information for us, to run the Service:

  • Supabase, a United States company, runs your company's database, sign-in accounts and file storage on Amazon Web Services in Sydney, and backs the database up daily. Its own service logs and management systems, which include sign-in events and IP addresses, may process data outside Australia, including in the European Union and Singapore.
  • PowerSync (JourneyApps) keeps the iPhone app in step with your company's database. Your feedlot's sync service runs in PowerSync's Australian region and holds a copy of the records the app syncs. PowerSync's control systems are in the United States.
  • Vercel (United States) hosts our web apps. Our app servers run in Vercel's Sydney region. Requests pass through Vercel's global network on the way, and Vercel keeps request logs. Some background tasks, and the AI connector in section 4, may run in Vercel's United States regions.
  • Cloudflare (United States) runs our domain names and the services behind shared links, exchange between PaddockPath companies, the Xero integration, release notes and our status checks. These run on Cloudflare's global network, which keeps their logs and stores some shared-link details, including viewers' email addresses and IP addresses. Email sent to a paddockpath.com address passes through Cloudflare on its way to our team.
  • Postmark (United States) sends our email. Section 6 explains.
  • PostHog (United States) handles analytics, error reports, server logs and session recordings for the Feedlot web app, and analytics for paddockpath.com, as section 3 explains.
  • OpenRouter and Google (United States) read documents and files with Google's Gemini model, as section 4 explains.
  • Anthropic (United States) provides Claude, which our engineers and our support assistant use, as section 4 explains.
  • GitHub (United States) holds our source code and runs our support assistant. It also keeps the support assistant's notes, and files we work with while fixing a problem, and both can include records from your company's database.
  • Userback runs the feedback form in our web apps and stores what it collects with Amazon Web Services in the United States.
  • Linear, a United States company, holds our support tickets: feedback from the web form and the iPhone app, with any screenshots, and our replies.
  • Slack (United States) carries messages to our team, including request access forms, requests to add people to a company's account, and sign-ins to our presentation decks.
  • Better Stack (European Union) hosts our status page at status.paddockpath.com. It checks that our services respond. We send it none of your company's records.
  • Mux (United States) streams the videos on our help site, changelog, newsletter and presentation decks, with its viewer analytics turned off. It sees the IP address of each device that plays one.
  • Open-Meteo (Europe) supplies the weather for your feedlot, from the feedlot's location.

Your company's partners

When your company sets up an agreement with another PaddockPath company, or shares a report, files or a mob through a link, the records it chooses go to that company or person.

Services your company connects

If your company connects Xero or a weather station service, we exchange the records the connection needs with that service, on your company's behalf and under your company's own agreement with it. Xero may keep data in Australia, New Zealand and the United States.

When the law requires it

We disclose personal information to a court, regulator or government agency only when the law requires us to.

6. Email

Postmark sends our email from the United States: sign-in codes, codes for opening shared links, the reports and invoices your team sends from PaddockPath, partner invitations, our newsletter, and our replies to support requests. Our emails don't contain tracking pixels, and their links aren't changed to track clicks, except that a link to paddockpath.com can carry a personal code, as section 3 explains. For reports and shared links, Postmark tells us whether each email was delivered, bounced or marked as spam. Postmark keeps a copy of each message it sends, including attachments, for a limited time.

When your team sends a report to several people in one email, each recipient can see the others' addresses.

7. Where It Is Kept

Your company's database, sign-in accounts and files are kept in a Supabase project of their own in AWS's Sydney region. Your feedlot's sync service also runs in Australia, and our web app servers run in Vercel's Sydney region.

Some personal information goes outside Australia, to the providers in section 5:

  • the United States: Supabase, Vercel, Cloudflare, Postmark, PostHog, OpenRouter, Google, Anthropic, GitHub, Userback's storage, Linear, Slack, Mux and PowerSync's control systems
  • the European Union: Supabase's service logs, Better Stack and Open-Meteo
  • Singapore: Supabase's management systems
  • New Zealand, if your company connects Xero
  • other countries where Cloudflare's and Vercel's networks run, for requests that pass through them

Most of these providers are United States companies. The laws of their home countries can let authorities there require them to hand over data they hold, including data kept in Australia.

8. The iPhone and iPad App

  • The app contains no advertising, analytics or crash-reporting code from other companies, and it never asks for your location.
  • It reads scale displays and tags with the camera on the device, and those camera frames aren't sent anywhere. Photos you take of arrival paperwork and mortalities are uploaded, as sections 1 and 4 explain.
  • It keeps a copy of your company's records on the device so it keeps working without signal. That copy is protected by iOS's own file protection, which depends on the device having a passcode, and it is left out of device backups. The app doesn't add its own encryption to it. Photos and reports waiting to upload can be included in a backup until they are sent.
  • Signing out deletes the copy from the device.
  • If you use a TestFlight build, Apple may share crash reports, and any feedback you send through TestFlight, with us.

9. How Long We Keep It

  • Your company's records are kept for as long as your company subscribes. We don't delete livestock records automatically.
  • Records of sign-in attempts are deleted after 30 days, or after 180 days for demonstration logins. Notifications are deleted after 90 days.
  • Shared-link records, including recipients and the details recorded when a link is opened, are kept with the shared record. We don't yet delete these automatically.
  • Something deleted from your company's database stays in our database provider's daily backups for up to 7 days.
  • Our providers keep their copies for their own periods, including Postmark's copies of sent email, PostHog's events and recordings, and support tickets in Linear and Userback.
  • When a customer leaves, we delete its whole database project. That removes its records, sign-in accounts, stored files and our database provider's backups of them. Some records about the account stay in our own systems afterwards, such as staff email addresses and billing head counts, and we are writing the procedure that removes those as well.
  • If you ask us to delete your personal information, we will reply within 30 days to say what we deleted and what we kept. We keep what your company's records need (your name on a treatment you recorded, for example) and what the law requires us to keep.

10. Your Choices and Rights

  • You can ask for a copy of the personal information we hold about you, or ask us to correct it. We will reply within 30 days. Records your company keeps about its own work belong to your company, so we may refer a request about them to your company's administrator.
  • You can ask us to delete your personal information, as section 9 describes.
  • Your company can export records as CSV from the main screens of the web app at any time, and we will provide a full database export on request.

To make a request or a complaint, email hello@paddockpath.com . We will reply to a complaint within 30 days. If you are not satisfied with our reply, you can contact the Office of the Australian Information Commissioner at oaic.gov.au.

11. If Something Goes Wrong

If we learn of a data breach that is likely to cause you serious harm, we will tell you or your company as soon as we can, with what happened and what you can do. To report a security problem you have found, see our vulnerability disclosure policy.

12. Children

The Service is for people working in the livestock industry and is not directed at children under 16. We do not knowingly collect information from children.

13. Changes to This Policy

When we change this policy, we update the date at the top. If a change affects how we handle your company's information, we will also email your company's administrators before it takes effect.

14. Contact Us

  • Email: hello@paddockpath.com
  • Security problems: security@paddockpath.com
  • Post: Quinence Australia Pty Ltd, Suite 302, 13–15 Wentworth Ave, Sydney NSW 2000