Privacy Policy

All of it, in one table. There is nothing we collect that is not listed here.

Basic first-party analytics runs automatically and does not require an analytics confirmation. Optional third-party analytics can be controlled separately in Settings.

Photos are optional in Equintt. When you add one, it is stored with the visit or photo check-in you chose to create.

We strip the EXIF data before the photograph leaves your device. Every image is redrawn through a canvas in your browser, which removes all embedded metadata — including the GPS coordinates most phones record.

That matters more here than it might elsewhere. A dated series of photographs with coordinates attached tells a stranger where a named individual’s horse is kept, and at roughly what times of day somebody visits it. We do not want that data, so we make sure it never arrives.

Photographs are stored in a private bucket. They are never public, never listed, and reachable only through short-lived signed links issued to your own session.

Share cards are the one exception, and only when you make one: tapping Share renders an image from your recap which you then choose where to send. We do not post anything anywhere.

If you choose an AI photo check-in, the photograph and the context needed for that request — such as breed type, your goal and relevant earlier observations — are sent to OpenAI to generate observations and a possible next step. Ordinary goal visits and text-only visit reports do not send a photograph for analysis. The result is stored with that photo check-in.

We send the minimum the analysis needs. Your email address, your name and your billing details are not part of it.

We also keep a small reference library — body condition scoring guides, breed standards and similar published material — that the analysis draws on. It contains no user data.

Under UK and EU data protection law, our lawful bases are:

• Contract. Your account, your horses, your check-ins and your subscription. We cannot provide Equintt without them.
• Legitimate interests. Security, abuse prevention, rate limiting, and keeping the service working. We have weighed these against your rights and kept the data to the minimum each purpose needs.
• Consent. Push notifications, optional third-party analytics and using your photographs to improve our models. Each is controlled separately; you can change these choices without losing access to Equintt. Basic first-party visitor analytics is used to understand site and onboarding activity.
• Legal obligation. Records we are required to keep — mostly tax, which The payment provider may retain records as required by law.

We do not sell your data, and we never will. No advertising networks, no data brokers, no list sharing.

We use a small number of providers to run the service. Each is bound by a data processing agreement and may only act on our instructions.

We would also disclose data if the law required it. If that happens and we are permitted to tell you, we will.

Your account data and photographs are held in the region we selected when the project was created, and are not moved between regions in ordinary operation.

Some of our providers may process data outside the UK and EEA. This includes OpenAI for AI features and Telegram for basic visitor activity and support requests. The provider and processing location depend on the service configuration. Where required, international transfers rely on the provider’s applicable transfer terms, including Standard Contractual Clauses or an International Data Transfer Addendum.

You have the right to access your data, correct it, delete it, take it elsewhere, object to how we use it, and withdraw consent. Two of these are buttons rather than requests, because a right you have to email someone about is not much of a right.

For anything else, email support@equintt.com. We answer within 30 days, and usually much sooner. There is no charge.

If we get it wrong, you can complain to the data protection regulator where you live, and nothing here affects that right. We would rather you told us first, because we can usually fix it the same week.

Cancelling a subscription does not delete anything. Your horse’s history stays exactly as it is and the account becomes read-only. Someone who comes back after six months should find two years of photographs waiting, not an empty account.

Deleting your account removes everything, permanently, and cannot be undone. Verification codes are purged automatically after 24 hours. Aggregate statistics — the figures behind “you were in the top 5% for time spent with your horse” — contain no identifying columns and are not linked back to you, so they remain after deletion.

Backups are kept for disaster recovery and roll off on their own schedule. A deletion removes you from the live system immediately; residual copies in backups age out.

This section is our security statement. It describes what is actually implemented, not what we intend.

Access control

Every table in the database enforces row level security, and it is the authorisation boundary rather than a backstop — the key the browser holds can only ever reach your own rows. We test this rather than assume it: an automated suite runs on every change, acting as two different signed-in users and a signed-out visitor, and asserts that neither can read, change or delete the other’s data.

The browser’s write access is narrowed column by column. Fields that represent authority or evidence — administrator status, your lifetime totals, the stage your horse’s journey has reached — cannot be written from a browser at all, only by server-side code that has earned the right to change them.

Data protection in transit and at rest

• Everything travels over TLS. There is no unencrypted path into the service.
• Data at rest is encrypted by our infrastructure provider, including file storage and backups.
• Photographs live in private buckets and are served only through short-lived signed links scoped to your own account.
• Passwords are hashed by our authentication provider and are never visible to us.
• Verification codes are hashed with a server-side secret, so a stolen database backup does not yield usable codes.

Payments

Card data never touches our systems. The selected payment provider handles checkout; we store only the provider reference and subscription status needed to run your account. Billing events are verified before they update an account, so a lost message cannot leave your account in the wrong state.

Development practice

• Every change runs through automated type checking, unit tests, database constraint tests, the row-level-security suite and end-to-end tests before it can ship.
• Secrets are held in the platform’s secret store, never in the codebase.
• Dependencies are pinned, and the browser cannot load scripts from arbitrary origins.
• Point-in-time recovery is enabled on the database, because photographs of a horse over two years are not something that can be regenerated.

Reporting something

If you find a vulnerability, email support@equintt.com. Tell us what you found and how to reproduce it, and give us reasonable time to fix it before publishing. We will not pursue anyone acting in good faith under those terms, and we will credit you if you would like us to.

What we do not claim

We are a small team and we would rather be accurate than impressive. We are not currently certified to ISO 27001 or SOC 2. If you need a formal assurance report, ask and we will tell you honestly where we are.

If there is a breach affecting your personal data, we will notify the relevant supervisory authority within 72 hours where the law requires it, and we will tell you directly if there is a high risk to you.

We will say what happened, what data was involved, what we have done, and what you should do. We will not wait until we have a complete picture to tell you something is wrong.

Equintt is not for children under 16. We do not knowingly collect their data. If you believe a child has created an account, tell us at support@equintt.com and we will delete it.

We will update this page when what we do changes. If a change materially affects your rights or how we use your data, we will email you before it takes effect rather than quietly editing the page.