HHoofFlow

Fair Use Policy

Last updated: [TBD: publish date]

Draft — pending legal review. This page describes HoofFlow's architecture and data-handling practices accurately as of today, but it has not been reviewed by a lawyer and is not a final legal document. Placeholders marked [TBD: …] require a real business decision before this page can be relied on.

The short version

Ordinary professional use of HoofFlow — including voice notes, AI-drafted owner summaries, route planning, and photo storage — has no visible hard quota. We monitor usage to protect the service from abnormal, abusive, fraudulent, or technically harmful activity — never to limit a working farrier's normal day.

What we monitor

We track aggregate, non-content usage signals per organization, including:

  • AI voice/transcription requests and minutes
  • Map/route-planning requests
  • Owner communication emails sent
  • Photo uploads

This monitoring is for cost/abuse protection only — it is never used to bill you differently or to throttle normal use.

What counts as abnormal

We look for patterns far outside a real farrier's working day — for example, automated/scripted request volume, AI usage disconnected from any real visit or horse record, or a sudden spike orders of magnitude above your account's own history. A busy week, a large barn visit, or catching up on backlogged records is never flagged.

What happens if usage looks abnormal

We respond proportionally, and always preserve your core records:

  • We monitor and may reach out to understand what's happening.
  • If necessary, we may temporarily suspend one specific capability (AI, mapping, or email sending) for your organization — never your ability to view, search, or export your existing client/horse/visit records.
  • In a genuine emergency (e.g. a compromised account driving runaway provider cost), we may act faster and follow up afterward.

We do not lock a customer out of their historical hoof-care records because of abnormal AI or mapping usage.

Questions

If your organization was flagged and you believe it was a mistake, contact [TBD: support contact email] — we'll review it directly with you.