EquiDiary
Security & privacy

How we keep your records safe

Last updated 29 October 2026

A horse’s journal holds vet reports, passports, what you paid and who looks after it. Here is what we do to protect it, in plain words — and how you can check.

Private by design

Your account

Your horse’s records

On the way, and in storage

On your phone or computer

Checked against a published standard

We check EquiDiary against the OWASP Application Security Verification Standard (ASVS), version 5.0 — an open list of security requirements for web applications, written by the security community, not by us. Its Level 1 is the baseline it asks of every application, and Level 2 adds what it recommends for most of them.

The Level 1 assessment, completed on 25 October 2026, went through all 70 Level 1 requirements. Each one is met, or concerns something EquiDiary doesn’t have — operating-system commands, rich-text input, XML, WebSockets, signing in other companies’ users. Two are met by a different route than the requirement describes, and we explain why. On 31 October 2026 we went on through the 183 more that Level 2 adds. Of those, 125 are met, 46 concern something EquiDiary doesn’t have, 2 are met by a different route, and 10 we have chosen not to meet; below is what that means for you.

This is a self-assessment. We did it ourselves, on our own code and the live service. No outside auditor has reviewed it, and OWASP does not certify or endorse any application, this one included. So that you can judge it for yourself, the whole of it is published: every requirement, its result, and how it is met.

Read the ASVS self-assessment, Levels 1 and 2

We repeat it whenever something it relies on changes, and at least once a year.

What we chose not to meet

Ten of Level 2’s requirements we have chosen not to meet, each for a reason the assessment gives in full. Three are close to you. The copy of your journal on the device, with the photos and PDFs you have opened, stays, so the app works without signal, and your browser may show those photos and PDFs from its cache for a day; Level 2 wants nothing sensitive kept in the browser. And our hosting provider still accepts a few older TLS 1.2 encryption settings, which only a client offering nothing better ever uses; switching them off is a paid add-on we haven’t bought. The others concern how our own services hold their keys. One more is met by a different route: two-step sign-in is offered to every account and required only of administrators, rather than required of everyone.

Found a problem?

If you think you’ve found a security weakness, write to support@equidiary.com with what you found and how to reproduce it — the same address our security.txt gives. Please keep it private until it’s fixed; we’ll tell you when it is, and thank you by name if you’d like.

OWASP is a trademark of the OWASP Foundation, Inc. EquiDiary is not affiliated with or endorsed by the OWASP Foundation.