Security

How we protect your data

Last updated 26 October 2026. A plain-English summary for farmers and advisors. The privacy policy has the full detail.

Straight answer: Paddock Pulse itself is not yet independently audited (for example, SOC 2). We build on providers that are.

Where it runs

Encryption

Everything between your phone or computer and Paddock Pulse travels over HTTPS (TLS), and browsers are told to always use the secure connection. Supabase encrypts stored data at rest (AES-256) and in transit (TLS). Netlify encrypts traffic on its network with TLS 1.2 or higher.

Your farm stays yours

Each account can only see its own farms and paddocks, plus any farm whose owner has invited it in. This is enforced inside the database itself, not just hidden in the app. Uploaded graphs are kept in private storage in a folder tied to your account; they are not on a public web link.

Payments

You pay on Stripe's own checkout page. Your card details go straight to Stripe and never pass through or sit on Paddock Pulse's servers. We only get back your email, your plan and whether the payment went through.

How your graphs are used

Deleting your data

Email lancejdale@gmail.com to ask for a copy of your data, or to have your account and farm data deleted. A few records stay, as set out in the privacy policy (for example tax invoices), and backups age out on their own cycle.

Questions

Got a security question, or need something for your organisation's checklist? Email lancejdale@gmail.com.

Privacy policy · Terms of use · EULA · User guide