FarrierFlow does not collect your farrier records.

FarrierFlow iPhone App

Local-first business records

FarrierFlow stores its operational business records locally on your iPhone. These records include business identity, clients, horses, service locations, appointments, visits and work performed, work notes, hoof photographs, invoices, payment status and evidence, and next appointments.

FarrierFlow does not upload the contents of these records to its analytics or subscription services. Names, contact details, addresses, notes, photographs, invoice contents, payment details, and local record identifiers are not sent to PostHog or RevenueCat.

Records may leave the device only when you deliberately use an operating-system feature such as sharing an invoice or photograph, or when you enable a device backup or transfer service. Those actions are controlled by you and the applicable operating-system or destination service.

Anonymous product analytics

FarrierFlow uses PostHog to understand whether important product workflows are working. It sends a small set of events describing transitions such as onboarding progress, creating an appointment, completing a visit, creating or sharing an invoice, and changing an invoice to Paid. Subscription interaction events may include only the selected plan type: monthly or annual.

PostHog creates, persists, and transmits a random anonymous installation or device identifier so events can be analyzed across sessions without a FarrierFlow account. FarrierFlow does not attach names, email addresses, phone numbers, customer identifiers, or business-record contents to it, and does not combine it with the RevenueCat identifier. PostHog person profiles are disabled and FarrierFlow does not identify users to PostHog.

Custom events may include limited technical context supplied by the SDK, such as the app and SDK versions, Apple device model and type, operating-system version, screen size, language, time zone, network reachability, distribution environment, random event and session identifiers, and timestamps. FarrierFlow does not send the user-assigned iPhone name or carrier name. Events may be queued on the device for later delivery to PostHog's United States service at https://us.i.posthog.com.

Each event instructs PostHog not to perform GeoIP enrichment. The PostHog project is configured to discard client IP data rather than retain it with events. FarrierFlow does not use Core Location for analytics and does not send GPS coordinates or business addresses to PostHog.

FarrierFlow disables PostHog session replay, screenshots, screen-view capture, application-lifecycle autocapture, element-interaction autocapture, surveys, feature-flag events and preloading, logs, and automatic error or crash capture.

Subscriptions and purchases

FarrierFlow uses Apple's App Store and RevenueCat to offer and manage FarrierFlow Pro subscriptions. Apple processes the purchase. RevenueCat receives and processes App Store receipt and subscription information, purchase history, product and entitlement status, renewals, cancellations, and restores so FarrierFlow can determine whether Pro features are available and so subscription performance can be analyzed.

FarrierFlow does not have an account system. RevenueCat creates a random anonymous App User ID, caches it on the device, and uses it to process purchases and subscription status. FarrierFlow does not assign or transmit a custom user or account ID, and does not provide RevenueCat with a name, email address, phone number, business identifier, client identifier, advertising identifier, or other custom customer attribute. The RevenueCat identifier is not sent to PostHog or stored in FarrierFlow business records.

Apple may separately hold payment information for your Apple Account. FarrierFlow and RevenueCat do not receive your card or bank-account details from the App Store purchase flow.

Apple Ads attribution

FarrierFlow enables Apple's Standard AdServices attribution through RevenueCat. When Apple supplies attribution, RevenueCat can associate the anonymous subscription customer with Apple Ads source, campaign, ad group, keyword, ad attribution, and claim context for FarrierFlow's advertising, marketing, and subscription analysis. RevenueCat's Apple Ads connection has Read Only access and cannot create or edit campaigns.

RevenueCat's SDK requests the Apple-provided attribution token and sends it to RevenueCat in the background. FarrierFlow does not manually fetch, decode, or store that token, and does not send Apple Ads campaign, ad-group, keyword, claim, or token values to PostHog or to business records.

FarrierFlow does not request App Tracking Transparency permission, access the IDFA, use AdSupport, fingerprint a device, or implement cross-app tracking. Standard AdServices attribution does not require the ATT prompt.

Third-party services

• Apple provides App Store distribution, subscriptions, receipts, and Standard AdServices attribution.
• RevenueCat provides anonymous subscription identity, receipt and entitlement processing, subscription analytics, and Apple Ads attribution.
• PostHog provides anonymous product-usage analytics in its United States service region.

Retention and deletion

Local business records remain on the iPhone until you delete individual records or remove the app's data. Deleting the app can remove local records, so preserve any backup you need first.

PostHog and RevenueCat retain service data according to their service terms, the FarrierFlow project configuration, and applicable legal requirements. Deleting FarrierFlow removes the providers' locally cached identifiers and queues, but does not by itself delete records already processed by those providers or Apple. Contact FarrierFlow for assistance with data-access or deletion questions. Subscription and transaction records may remain where Apple, RevenueCat, or applicable law requires them for purchase processing, fraud prevention, accounting, or legal compliance.

App privacy declaration

FarrierFlow declares anonymous Purchase History for App Functionality and Analytics; Product Interaction, Other Usage Data, and a Device ID for Analytics; and Advertising Data for Developer's Advertising or Marketing and Analytics. These data types are not linked to your identity and are not used for tracking. FarrierFlow declares no User ID, Crash Data, Other Diagnostic Data, or tracking.

FarrierFlow Website

FarrierFlow-operated collection

FarrierFlow uses no site-owned analytics, advertising trackers, tracking pixels, or nonessential cookies on this website.

Appearance preference

The website may store your explicit light or dark appearance preference in browser local storage. This remains a local display setting and is not used by FarrierFlow for analytics, advertising, profiling, or tracking.

Vercel hosting

Vercel hosts this website and may process ordinary request, infrastructure, performance, abuse-prevention, and security data under Vercel's own privacy terms as the hosting provider.

Changes to this policy

FarrierFlow may update this policy when the app's data practices change. The effective date above identifies when this version of the policy took effect.

Contact

Questions about this policy can be sent to:

farrierflow.support@gmail.com