← PaddIQ · Terms of Service · Data sources

Privacy Policy

Last updated 28 October 2026

This policy explains what information PaddIQ collects, why, where it goes and what control you have. It is written to comply with the Australian Privacy Principles under the Privacy Act 1988 (Cth).

The short version

Your farm data belongs to you. We store it only to run PaddIQ for you and the people you invite.

Our commitments

  • We don't sell your data or share it with advertisers, and we don't use advertising cookies or tracking pixels.
  • We don't use your farm data to train general-purpose AI models — ours or anyone else's. Your paddock results help tune PaddIQ's own recommendations only if you switch the Response Bank on.
  • We never see, ask for or store your John Deere password. You sign in on John Deere's own page.
  • Your farm records go to an AI service only when you use an AI feature (reading a document, or Ask PaddIQ), and anything it proposes is shown to you before it is saved.
  • We access your data only to run PaddIQ for you and the people you invite, to fix a problem you have reported, or — only if you say yes to sharing — to run the Response Bank from the paddock results you chose to share.
  • PaddIQ never supplies your data to anyone else. It only leaves PaddIQ when you send it — for example a report to your agronomist, or a prescription to John Deere Operations Center. The services that host and run PaddIQ, listed in the Privacy Policy, handle it only to run the features you use.

What we collect and why

  • Your account: your email address and a hashed password, for signing in, and the farm you own or were invited to.
  • Your farm data: what you enter or import (paddocks, records, prices, machinery, inventory, plans, tests, invoices and photos), stored so your devices and team see the same thing.
  • John Deere: what you approve on John Deere's consent screen when you connect Operations Center. The access token is kept encrypted on our server, per account.
  • Ask PaddIQ: each question and a short preview of its answer, logged against your email so wrong answers can be found and fixed. Deleted with your account.
  • Security logs: standard server logs from our host (IP address, time, page), kept for a short period for security and rate limiting only, and our sign-in provider's record of the IP address and browser of each sign-in, sign-up and password reset, for security.
  • The Response Bank, only if you say yes to sharing (it is off unless you do): your harvested paddock-season results — crop, yield, protein, rain totals, nutrients applied, soil type and the soil test values PaddIQ's recommendations use, paddock size in 50 ha bands and your district as a 1° square — with names, paddock keys, boundaries and exact locations removed, filed under a random code. Results from John Deere only if you tick that too. Other farms never see your rows. Switching it off deletes them.

How your data is protected

  • Encrypted in transit. Every connection uses HTTPS, and browsers are told never to fall back to an unencrypted connection (HSTS).
  • Each account reaches only its own data. The database enforces this row by row (row-level security). A team member you invite can see all of your farm's data; the tab settings you choose control which screens they see and what they can edit. Every server route that handles your farm data checks the sign-in before it does anything.
  • Passwords are never stored in plain text — our authentication provider stores them hashed. John Deere access tokens are encrypted at rest (AES-256-GCM) and can be read only by our server.
  • Uploaded files are private. They are kept in private storage under your own account's folder, with limits on size and file type.
  • Protection against abuse. Every route that costs money or sends email is rate limited, a bot check is available on sign-up, and security headers stop another site from embedding PaddIQ.
  • Deleting your account removes your farm data, uploaded files, team, Ask PaddIQ log and John Deere connection, then the sign-in itself, and tells you what was removed. We keep only the record that your email accepted the terms (date and version); copies in our hosting provider's routine backups expire on its schedule.
The full policy

What we collect

Account details: your email address and password (stored hashed by our authentication provider), and the farm you belong to or own.

Farm data you enter or import: paddocks and boundaries, operations and records, prices, machinery and maintenance, inventory, budgets, plans, soil and tissue tests, invoices, statements and photos you upload.

Data from services you connect: when you connect John Deere Operations Center, the fields, operations, equipment and map layers you authorise on John Deere's consent screen.

Locations you place: paddock boundaries, pins for rain gauges, sheds, silos and other places on your farm, and the weather station or gauge you choose for rainfall and forecasts.

Basic technical information: device and browser type and the page you were on when you send feedback or report a problem, and standard server logs from our host (IP address, time and page requested), kept for a short period for security and rate limiting. Our sign-in provider (Supabase) records the IP address and browser of each sign-in, sign-up and password reset, for security.

Why we use it

To provide PaddIQ to you and the members you invite — storing, syncing and displaying your farm data, running the calculations you ask for, and reading documents you upload.

To support you and fix problems. To improve PaddIQ using aggregated, de-identified usage patterns — never your identifiable farm data, and never to train general-purpose AI models. Your paddock results help tune PaddIQ's own recommendations only if you switch the Response Bank on.

Only if you say yes to sharing with the PaddIQ Response Bank (asked at sign-up or when you accept the terms, and in Settings → Data → Share with the Response Bank; off unless you say yes, and "Decide later" is no): to calibrate PaddIQ's yield and fertiliser models, and to show district benchmarks to growers who share, from a copy of your harvested paddock-season results pooled with other growers who said yes. The copy carries crop, season, yield, protein, rain totals, N, P, K and S applied, soil type and the soil test values the recommendations use (rounded), paddock size in 50 ha bands and your district as a 1° square — no names, paddock keys, boundaries, exact locations, products, dates, email or account. Results from John Deere go in only if you tick that line as well. The copy is filed under a random code. It is pseudonymised, not anonymous: PaddIQ keeps the link from that code to your account so the copy can be deleted, the PaddIQ operator's view of the pooled rows does not show it, and we never use it to identify you. A figure built from shared results is shown to growers only when at least 5 farms are in that crop, district and season and no one farm supplies more than half of it. The key that tells your paddock-seasons apart is made from a secret kept on your own device, never sent to PaddIQ. Switching sharing off, or deleting your account, deletes the copy.

Where it is stored and who sees it

Your data is stored in your browser on each device you use and synced to our cloud database and file storage (Supabase) and served by Vercel. Those providers host on infrastructure that may be located outside Australia (including the United States); by using PaddIQ you agree to your data being stored there under those providers' security commitments.

When you use an AI-assisted reading feature, the document or photo you upload is sent to Anthropic's API (United States) to be read. When you use Ask PaddIQ, your question and the farm records needed to answer it are sent the same way. Anthropic's commercial terms do not permit it to train on that data. We do not send your farm records to AI services unless you use one of these features, and any change they propose is shown to you to check before it is saved.

Each Ask PaddIQ question, which parts of your data it read and a short preview of the answer are logged, with your email, so wrong answers can be found and fixed. The PaddIQ operator can read that log. It is deleted with your account.

When you connect John Deere, data flows between PaddIQ and John Deere under the permissions you approve on John Deere's consent screen. We never see or store your John Deere password. The access token John Deere issues is stored on our server encrypted (AES-256-GCM), for your account only, and is deleted when you disconnect or delete your account. We never use information received from John Deere to send unsolicited marketing.

People you invite to your farm as team members can see all of your farm's data, including what came from John Deere and the documents you uploaded. The tab settings you choose for each person control which screens they see and what they can edit. Remove a member and they lose access.

Weather, rainfall and satellite features send the map area or station coordinates involved to the services that hold that data: Open-Meteo (forecasts) and the Queensland Government's SILO (rainfall and radiation history) through our server, and the Earth Search catalogue on Amazon Web Services and Digital Earth Australia (Sentinel-2 imagery) directly from your browser. Map tiles come from Esri and OpenStreetMap and are fetched directly by your browser, so those providers receive your IP address and the map area on screen. Those requests carry a location, not your name or account.

Account emails (sign-in links, invitations, password resets, and feedback you send us) go out through Resend, an email delivery service. It handles the address and the content of those emails to deliver them, and keeps delivery logs for a short period.

Sign-up can be protected by Cloudflare Turnstile to keep bots out. When it is on, Turnstile runs in your browser and sends Cloudflare the signals it needs to tell a person from a script; we see only pass or fail.

PaddIQ never supplies your data to anyone else. It only leaves PaddIQ when you send it — for example a report to your agronomist, or a prescription to John Deere Operations Center. We do not sell your data or share it with advertisers. The providers above handle it only so the service works, and we disclose it where the law requires.

Automated processing

PaddIQ's recommendations (for example fertiliser rates, yield forecasts and cost estimates) are calculated automatically from your data and published agronomic references. They are shown to you as suggestions to accept, change or ignore — no decision that affects you is made automatically without you.

Security and data breaches

Every connection is encrypted (HTTPS with HSTS). The database enforces row-level security, so an account can read and write only its own rows; a team member can see all of the farm's data they were invited to, and the owner's tab settings control which screens they see and what they can edit. Every server route that handles your farm data verifies the sign-in before acting. Passwords are hashed by our authentication provider; John Deere tokens are encrypted at rest and readable only by the server. Uploaded files sit in private buckets with size and type limits under your own account's folder. Sign-up can carry a bot check, routes that cost money or send email are rate limited, and security headers stop PaddIQ being framed by another site. Delete account removes your farm data, uploaded files, team, Ask PaddIQ log and John Deere connection, then the sign-in.

If a data breach occurs that is likely to cause serious harm, we will notify you and the Office of the Australian Information Commissioner in line with the Notifiable Data Breaches scheme.

How long we keep it

For as long as you have an account. If you ask us to delete your account we delete your data from our systems within 30 days, except where we must keep records by law. We keep a record that your email address accepted these terms (the date and the version) after the account is deleted, as a legal record. Copies inside our hosting provider's routine backups are not edited; they expire on the provider's schedule.

Earlier versions of your farm data are kept for 30 days so a change or a deletion can be undone (Settings → Data → Change history), then deleted. Only the farm owner can see them, and they are deleted with your account.

Emails from us

We send emails needed to run your account (sign-in, password reset, billing, important service notices). We only send marketing emails if you have opted in, every one identifies us and has a working unsubscribe, and unsubscribing takes effect within 5 business days.

Your choices and rights

You can view, correct and export your data in the app at any time. You can disconnect John Deere from the John Deere page. You can ask us to delete your account and data, or to tell you what personal information we hold, by emailing admin@paddiqag.com — we respond within 30 days. If you are unhappy with how we handle a request you can complain to the Office of the Australian Information Commissioner (oaic.gov.au).

Cookies and local storage

PaddIQ uses browser storage to keep you signed in and to hold your farm data on your device. We do not use advertising cookies or tracking pixels.

Changes and contact

We will update this policy as PaddIQ changes and show the date at the top. Questions: admin@paddiqag.com.