Privacy Policy & Livestock Data Security | DairyPro

DairyPro.app operates as an advanced smart dairy farm management system. We collect telemetry, herd records and team activity for one purpose: to help dairy operations optimise herd performance, cut feed waste and protect animal health. Data is never a product we sell — it is an operating asset your farm owns, and this policy explains exactly how DairyPro Technologies keeps it that way.

As an AgriTech company building secure dairy management software, we apply data minimisation by default: every module requests only the fields it needs to function. Farm telemetry is ingested to flag mastitis risk, drops in yield or a ration that no longer matches your CP and ME targets — not to profile you, and not to build advertising audiences.

This policy covers the DairyPro web platform, the mobile apps and any connected sensors or APIs you enable. By using DairyPro you accept the practices described here; if anything is unclear, write to contact@dairypro.app and a person, not a bot, will answer.

We group everything we store into four categories. Nothing outside these categories is collected deliberately.

We also keep technical logs — IP address, device type, browser, timestamps and error traces — for farm software security monitoring. These logs let us detect brute-force attempts, replay attacks and abnormal export volume, and they are retained for a limited window before being aggregated.

Every processing purpose below is tied to a feature you switched on. We do not repurpose farm data for anything else.

Aggregated, anonymised benchmarks — for example "average litres per cow across farms of your size" — may be produced to improve the platform. Aggregation removes farm, cow and user identifiers before any analysis runs, so benchmarks can never be traced back to your operation.

Farm data is encrypted in transit with TLS 1.3 and at rest with AES-256. Our secure dairy management architecture runs on a hardened Supabase database with row-level security: every query is filtered to the farm workspace the requesting user belongs to, so an Admin in one operation cannot read records in another.

• End-to-end cloud encryption for telemetry, milk records, images and documents.
• Strict access controls with role-based permissions for Veterinary, Admin and Farm worker accounts.
• Multi-factor and one-time-passcode authentication for every team login.
• Continuous auditing: export, delete and permission-change events are logged and reviewable.
• Encrypted, geographically redundant backups with tested restore drills.
• Contractual confidentiality and security training for every employee with infrastructure access.

No system is immune to every threat, and we will not pretend otherwise. If a breach ever affects your cloud farm records, we notify affected farm administrators without undue delay, explain what was exposed and publish the remediation steps we took.

DairyPro relies on a short, named list of processors. Each is bound by contract to handle data only on our instructions, for the single purpose listed here — a core part of our AgriTech data compliance posture.

Payment processing, where enabled, is handled by PCI-DSS certified processors; full card numbers never reach DairyPro servers. We review every integration annually and remove any provider that no longer earns its place.

You control your farm's data. On request we will give you a portable export of your records (CSV, JSON or PDF), correct anything inaccurate, restrict processing, or delete your account and every associated cloud farm record. Deletion is irreversible: milk production logs, breeding history and feed ration archives are removed from active storage and purged from backups on a scheduled cycle.

Requests are handled from our corporate headquarters in Miami, Florida — Global Operations & Dairy Intelligence Center. Farm administrators may self-serve most actions inside the app; anything else reaches a named human within one business day.

We may update this policy as DairyPro grows; material changes are announced in-app and by email, and the "Last Updated" date above always reflects the current version.