Privacy Policy
Version Identifier: HM-PRIVACY-2026-08-25-v1.3
Last updated: August 25, 2026
This Privacy Policy explains how HerdMaster LLC ("HerdMaster," "we," "us") handles information on the herdmaster.app website (the "Site"). It applies to the Site only. The HerdMaster app has its own privacy policy — see the HerdMaster app privacy tab above.
1. Information we collect
- Information you give us. When you join our waitlist or newsletter, we collect your email address. When you use the contact form, we collect your name, email address, and the message you send, and the topic you select.
- Information collected automatically. We use Google Analytics to understand how the Site is used. It sets cookies and collects standard analytics data such as your device and browser type, the pages you view, referring links, general interactions, and an approximate location derived from your IP address.
- What we do not collect. We do not collect phone numbers through the Site, and we do not send text messages. We do not take payments on the Site, so we do not collect card or bank details here.
2. How we use your information
We use it to: send you launch updates and newsletter emails you asked for; respond to your inquiries; and measure and improve the Site's content and performance. We do not use it to make automated decisions about you.
3. Cookies and analytics
The Site uses cookies and similar technologies, primarily for Google Analytics. You can control cookies through your browser settings and opt out of Google Analytics with Google's browser add-on at tools.google.com/dlpage/gaoptout. If a cookie-consent banner is enabled for your region, your choices there also apply.
4. Our customer records (CRM)
Information you submit (your email for the newsletter, and your contact-form details) is stored in AIO, our sales and marketing CRM, so we can reply and keep you informed. You can ask us to delete your information from the CRM at any time by emailing support@herdmaster.app, and we will remove it within a reasonable period, except where we must keep limited records to comply with law.
5. How we share information
We share information only with service providers who help us run the Site and our outreach: Google (analytics), our CRM and email provider (AIO), and similar processors acting on our behalf. We do not sell your personal information. We may disclose information if required by law or to protect our rights.
6. Your choices and rights
- Unsubscribe from emails anytime using the link in any message.
- Access, correct, or delete the information we hold, including removal from the CRM, by emailing support@herdmaster.app.
- Depending on where you live (for example California, or the EU and UK), you may have additional rights to access, delete, or restrict use of your data, and to lodge a complaint with a regulator. Contact us to exercise them.
7. Data retention
We keep newsletter and contact information until you unsubscribe or ask us to delete it. Analytics data is retained according to our Google Analytics configuration.
8. Children's privacy
The Site is intended for adult breeders and is not directed to children under 13. We do not knowingly collect personal information from children through the Site.
9. Security
We use reasonable measures to protect the limited information the Site collects. No method of transmission or storage is completely secure, so we cannot guarantee absolute security.
10. Third-party links
The Site links to third parties such as the App Store. Their privacy practices are their own and are not covered by this policy.
11. Changes to this policy
We may update this policy from time to time. The "Last updated" date at the top shows the latest version, and significant changes will be reflected there.
12. Contact us
Questions about privacy? Email support@herdmaster.app, or call (voice only) at (503) 943-0001.
App Policy Identifier: HM-APP-PRIVACY-2026-10-01-v1.5
Effective Date: October 1, 2026
Last Updated: October 1, 2026
This is the privacy policy for the HerdMaster mobile app.
This policy covers the HerdMaster app itself. For how this website handles information, see the Website Privacy tab above.
1. Introduction
HerdMaster LLC (“we,” “our,” or “us”) operates the HerdMaster mobile application (“the App”). This Privacy Policy explains how we collect, use, store, and protect your information when you use HerdMaster.
By downloading or using HerdMaster, you agree to the practices described in this Privacy Policy. If you do not agree, please do not use the App.
2. Age Restrictions
HerdMaster accounts may be created and maintained only by individuals who are at least 18 years old. A person who is 13 through 17 years old may use HerdMaster only through an account created and maintained by the person's parent or legal guardian. The adult is the HerdMaster account holder and contracting party. A person who is 13 through 17 years old does not create or maintain an independent HerdMaster account or separate HerdMaster credentials.
HerdMaster is not directed to children under 13. A person under 13 may not create an account or use the App. If HerdMaster learns that a child under 13 has used the App to provide personal information to HerdMaster, HerdMaster will take the steps required by applicable law, which may include deleting that information. To report such a case, contact support@herdmaster.app.
If 'Under 13' is selected, the App stores a persistent device-local eligibility block in iOS Keychain solely to prevent age re-entry. The block does not contain a date of birth, is not linked to a HerdMaster account, and is not transmitted to HerdMaster's backend. In version 1.0, the block persists across relaunch, deletion and reinstallation and there is no in-app or support reset. Because version 1.0 is signed under L&L's Apple Developer Team ID and the App will be transferred to HerdMaster LLC, a block created in version 1.0 will not remain accessible after the first update signed under HerdMaster LLC's Team ID. If the neutral age-range screen is presented again after that update, the App will not collect account information before the age selection is completed. HerdMaster does not use the block for advertising, analytics, or profiling.
3. Information We Collect
3.1 Information You Enter or Store in the App
The current release allows you to create, store, and manage account and profile information and livestock records, including animals, pedigrees, breedings, litters, kits, weights, show and health records, tasks, activity history, animal photos, and a profile image.
Payment-request records. If you use Payment Requests, HerdMaster stores the payment service you select, the payment destination you provide after HerdMaster checks its format and domain for the selected provider, the requested amount, any memo you enter, the status you assign (Draft, Requested, Paid, or Cancelled), and the dates of status changes. This validation checks only the destination's format and domain. HerdMaster does not authenticate with PayPal or Venmo and does not verify that the destination exists, belongs to the user, or can receive payment. For Venmo, the payment destination must be an official HTTPS Venmo profile or share link on venmo.com. For PayPal, the payment destination must be a public PayPal.Me handle or the corresponding official PayPal.Me link. HerdMaster may display the payment service, accepted destination, requested amount, memo, and user-assigned status as part of the Payment Request and may use the accepted destination and requested amount to create the third-party payment link you direct it to create. The requested amount is stored as an exact amount in cents.
The payment-destination field is provider-specific and validated rather than free-form. HerdMaster does not ask you to enter or store a payment-card number, bank-account number, routing number, payment-service password, or other payment-login credential in that field. These records reflect information entered or updated by you and do not mean that HerdMaster processed, received, or independently verified a payment. A status you mark as Paid is user-reported and does not independently verify that funds moved.
The fact that the App allows a category of information to be created, stored, or exported does not necessarily mean that HerdMaster receives or can access every copy of that information. The storage, transmission, service-provider, and retention practices applicable to the current release are described in the sections below.
3.2 Support Information
HerdMaster does not automatically collect your device model, iOS version, or App version as general analytics.
If you choose to send a support-ticket email from the App, the App includes your device model, iOS version, and App version in the email to help diagnose the issue. The email also contains the information you choose to include in your message. This information is transmitted only when you choose to send the email.
3.3 Information We Do NOT Collect
- We do not collect your precise GPS location
- We do not access your contacts, camera roll, or other apps without explicit permission
- We do not sell your personal information to third parties
- We do not collect payment card information — all purchases are processed by Apple
3.4 Beta, Partner and Participation/Contact Records
HerdMaster may maintain limited administrative records outside the App for beta testers, creator or other partners, individually approved participants, and internal administrators. Depending on the program, these records may include a person's name and email address, cohort or participation status, role or entitlement status, and related partner or program identifiers. Separate promo-code configuration records may include partner identifiers, display names, and promo codes.
We receive these records directly from the person, from the relevant partner or program administrator, or from our own participation and account-administration processes. We use them to administer testing, participation, access, support, partner relationships, and promo-code operations. These records are not intended to contain passwords, authentication tokens, government identifiers, payment-card or bank information, health information, or precise location information.
4. How We Use Your Information
- To provide and operate the HerdMaster app and its features
- To sync herd data across devices through Apple's CloudKit service only when the limited iCloud sync pilot is active for an approved participant who has an eligible Breeder or Show Breeder plan and enables iCloud sync (see Section 5.2)
- To administer beta testing, approved-user participation and access, creator or other partner relationships, support, and promo-code operations
- To process and validate your subscription through Apple App Store and RevenueCat
- To perform limited account-linked conversion measurement for purchase outcomes, upgrade prompts and actions, tier transitions, product/source, and optional conversion-survey responses as described in Section 9.
- To send account-related communications (subscription confirmations, support responses) and email-verification codes
- To diagnose technical issues and crashes
- To comply with legal obligations
5. Data Storage & Sync
5.1 On-Device Storage
Your animal and breeding records, including buyer information recorded on animal records, are stored locally on your device using SwiftData. After sign-in and completion of any required account checks, you can work with locally stored herd records offline. Features that require an internet connection are described separately in this policy.
5.2 iCloud CloudKit Sync
iCloud sync is a limited pilot feature. The pilot is temporarily paused, so iCloud sync is not currently available. If the pilot resumes, access will be limited to approved participants who also have an eligible Breeder or Show Breeder plan and who enable iCloud sync in the App. Being signed into iCloud on your device does not by itself cause HerdMaster data to sync, and purchasing a plan does not grant pilot access. For participants who enabled iCloud sync before the pause, previously synchronized herd data may remain stored in a dedicated record zone in their private iCloud database. The pause itself does not delete or alter that CloudKit data or the herd stored locally on the device. When iCloud sync is active for an approved participant, synchronization across devices is handled through Apple's CloudKit service and governed by Apple's Privacy Policy (apple.com/legal/privacy).
HerdMaster LLC does not have direct access to your CloudKit data.
5.3 Backend Services
HerdMaster operates a backend service hosted on Google Cloud Run. The backend handles the following account-linked records:
- Account and sign-in records: your sign-in identity, email address, account identifier, and email-verified status, held in Google Firebase Authentication; and an account profile containing your email address, account identifier, and any age band you selected with the age-policy version in effect.
- Adult-role affirmation records: when the adult account holder affirms the 13-through-17 use path, we record the account identifier, statement version and affirmation time. An affirmation completed offline is first stored on the device and reconciled with our backend before iCloud sync resumes; the backend also records when it receives that affirmation. The selection that a 13-through-17-year-old uses the App on a particular device remains stored on that device.
- iCloud sync pilot eligibility: records used to administer the limited pilot, including whether an account is currently eligible for production sync and any preserved approval record for an account previously approved for the pilot.
- Email-verification records: HerdMaster’s backend runs the four-digit email-verification process and sends the code to your email address from HerdMaster’s Google Workspace email account. It stores a keyed digest of the code, not the code itself, together with your account identifier, normalized email address, the verification status, remaining attempts, and creation, expiry, delivery, and acceptance times. A code expires after 10 minutes.
- Terms and Privacy acceptance records: the Terms version you accepted, the Privacy Policy version in effect at the time of acceptance, the acceptance timestamp, your account identifier, and associated audit data.
- Subscription, entitlement, and historical promo-code and partner-attribution records: subscription and entitlement status received through RevenueCat and the Apple App Store, and historical promo-code validation and partner-attribution records created under earlier App versions (see Section 8).
- Limited account-linked conversion measurement records and optional survey-response records, as described in Section 9.
Data transmitted to our backend is encrypted in transit using HTTPS.
Our ordinary account backend does not store your full animal records or the buyer information recorded on those animal records. Information or backup files you choose to send us for support are handled as described in this policy.
6. Third-Party Services
6.1 RevenueCat
We use RevenueCat to manage subscriptions, process entitlements, and handle subscription events. RevenueCat receives your App Store transaction data and subscription status. RevenueCat’s Privacy Policy is available at revenuecat.com/privacy.
6.2 Apple App Store
All purchases and subscriptions are processed by Apple. Apple’s Privacy Policy governs payment processing and transaction data. We do not receive or store your payment card information.
6.3 Google Cloud Run
Our backend services are hosted on Google Cloud Run. Google’s Privacy Policy is available at policies.google.com/privacy.
6.4 Apple CloudKit
If the limited iCloud sync pilot resumes and an approved participant enables iCloud sync, data sync between that participant's devices is handled by Apple's CloudKit service. During the pause, previously synchronized data may remain stored in the participant's private iCloud database, and the pause itself does not delete or alter that data. Apple's Privacy Policy governs CloudKit data storage and transmission.
6.5 Google Firebase Authentication
Account sign-in is provided through Google Firebase Authentication, which processes your email address and sign-in credentials and holds your email-verified status. HerdMaster does not use Firebase Analytics. Google’s Privacy Policy is available at policies.google.com/privacy.
6.6 Google Workspace (Gmail)
Email-verification codes are sent to your email address from HerdMaster’s Google Workspace email account (Gmail). Google’s Privacy Policy is available at policies.google.com/privacy.
7. Reserved.
8. Historical Partner Attribution and Promo-Code Records
The current App does not provide a promo-code or partner-code entry point and does not collect new promo-code or partner-attribution data through the App. Historical partner-attribution or promo-code records created under earlier App versions may remain subject to the applicable retention periods in Section 10. The Build 141 migration removes prior locally stored promo-code and partner-attribution data from the device.
9. Analytics and Subscription Events
HerdMaster does not use Firebase Analytics or general behavioral analytics. HerdMaster performs limited account-linked conversion measurement for purchase outcomes, upgrade prompts and actions, tier transitions, product/source, and optional conversion-survey responses. The survey fields are herdDescription and upgradeReason. In the app, each survey field is presented through fixed-choice buttons, including a literal 'Other' choice that does not open a text field. The backend stores each submitted answer as an account-linked, trimmed, non-empty string of up to 100 characters and does not currently enforce the interface's enumerated values. If the survey is dismissed, those answer fields are stored as null.
RevenueCat separately handles subscription and transaction events. See Section 10 for the applicable retention provisions.
10. Data Retention
Your on-device data is retained until you delete specific records or delete the App. The iCloud sync pilot is temporarily paused. If you enabled iCloud sync before the pause, previously synchronized herd data may remain in a dedicated CloudKit record zone in your private iCloud database; the pause itself does not delete or alter that CloudKit data or your local herd. When you delete your HerdMaster account, HerdMaster's account-deletion workflow is configured to delete the HerdMaster account-binding and herd-state records and any dedicated CloudKit record zone used for the synchronized herd before finalizing deletion of the HerdMaster backend account. If you never enabled iCloud sync, there is no synchronized HerdMaster herd in CloudKit to delete. This process is limited to HerdMaster records and HerdMaster's dedicated CloudKit record zone and does not delete other data in your private iCloud database. For HerdMaster backend and operational records:
- Backend conversion measurement, survey-response, and subscription-lifecycle records. Limited account-linked conversion measurement records, optional survey-response records, and routine subscription-lifecycle event records not subject to a more specific retention period below, including controlled production test records that do not produce a settled charge, refund or reversal, tax entry, or booked accounting entry, are retained for up to 12 months, then deleted or de-identified so they are no longer reasonably linkable to you.
- Beta and test-environment subscription event records. Sandbox and TestFlight event records are retained for up to 90 days from record creation, then deleted or de-identified.
- Complimentary subscription entitlement records. Event records relating to complimentary entitlements not retained as transaction-of-record data are retained while the entitlement remains active and for 12 months after it expires or is revoked, then deleted or de-identified.
- Subscription and purchase transaction records. Limited transaction-of-record fields are retained for 7 years for financial, tax, and audit purposes, then deleted or de-identified. A subscription or purchase event is not retained for 7 years merely because it concerns a subscription or purchase.
- Operational diagnostics. Deletion-operation diagnostics and subscription-event delivery, retry, and operational duplicate-payload diagnostics are retained for 30 days, then deleted.
- Email-verification records. Verification challenge records are scheduled for automatic deletion 24 hours after creation, and related rate-limit counters are scheduled for deletion within 48 hours. Deletion runs asynchronously and may occur after the scheduled time. Verification codes expire after 10 minutes.
- Beta, partner and participation/contact records. We retain these administrative records only while reasonably necessary for the applicable testing, participation, access, support, partner, or promo-code purpose. When that purpose ends, the records are deleted or de-identified when reasonably practicable, except to the extent a longer period is reasonably necessary for security, legal, audit, accounting, or dispute-preservation purposes.
- Ordinary support correspondence. Retained for 24 months after the support matter is closed, then deleted.
- Privacy-request correspondence. Privacy, access, correction, and deletion-request correspondence is retained for 3 years after the request is closed, then deleted. During that period, we retain only what is reasonably necessary to document the request and our response.
- Deletion audit record. A minimal, privacy-safe record that an account-deletion request was completed is retained for 3 years, then deleted.
- Terms and Privacy Acceptance Records. We retain records showing the Terms version accepted and the Privacy Policy version in effect at the time of acceptance, together with the acceptance timestamp, account identifier, and associated audit data, for 10 years after account closure, subject to longer retention where required for a legal hold, dispute, or applicable law.
When you request account deletion, we delete your HerdMaster account, including your Firebase Authentication sign-in record, and the account-linked backend records described in Section 5.3 within 30 days. The limited records described above may remain only for their stated retention periods or criteria. Retained support or privacy-request correspondence is not used as a substitute archive of deleted account data.
Adult-role affirmation records and iCloud sync pilot eligibility records, including any preserved prior-approval record, are deleted as part of account deletion, subject to any applicable legal hold or other legally required preservation.
11. Your Rights & Choices
11.1 Access & Correction
You can access and edit your animal and breeding records, including buyer information recorded on animal records, within the app.
11.2 Data Export
You can create a complete backup of your herd data at any time from the app. The backup is a single file in JSON format (.herdbackup) containing your animal records, pedigrees, breeding records, litters, kits, weight records, show records, health records, tasks, activity history, animal and litter photos, and your profile image.
The backup can be saved to Files, stored elsewhere, or sent to us if you need support. You can restore from a backup file at any time.
11.3 Account Deletion
When you request account deletion, we will delete your HerdMaster account, including your Firebase Authentication sign-in record, and the account-linked backend records described in Section 5.3 within 30 days. Limited records may remain after deletion only for the retention periods or criteria described in Section 10.
When you delete your HerdMaster account, the app deletes the local herd. If iCloud sync was enabled, HerdMaster's account-deletion workflow is configured to delete the HerdMaster account-binding and herd-state records and the dedicated CloudKit record zone used for the synchronized herd before finalizing deletion of the HerdMaster backend account. If iCloud sync was never enabled, there is no synchronized HerdMaster herd in CloudKit to delete. The CloudKit deletion is limited to HerdMaster records and HerdMaster's dedicated record zone and does not affect other data in your private iCloud database.
11.4 Subscription Management
You can manage, pause, or cancel your subscription at any time through your Apple ID settings. Cancellation instructions are available at apple.com/support.
12. Security
We take reasonable measures to protect your information:
- All data transmitted between the app and our backend is encrypted using HTTPS/TLS
- iCloud CloudKit data is encrypted by Apple at rest and in transit
- Our backend services use Google Cloud’s security infrastructure
- We do not receive or store your payment-card information — all transactions are handled by Apple
No method of transmission or storage is 100% secure. We cannot guarantee absolute security of your data.
13. Children's Privacy (COPPA)
The Children's Online Privacy Protection Act (COPPA) concerns the online collection of personal information from children under 13. HerdMaster is not directed to children under 13 and does not offer an under-13 user path. A person under 13 may not create a HerdMaster account or use the App.
HerdMaster account holders must be at least 18 years old. A person age 13 through 17 may use HerdMaster only through an account created and maintained by the person's parent or legal guardian. In that circumstance, HerdMaster may process personal information relating to the 13-through-17-year-old as part of providing the App through the adult-held account. The adult, not the 13-through-17-year-old, is the HerdMaster account holder and contracting party.
The adult-held account path described above applies only to users age 13 through 17. It is not an under-13 access path. If HerdMaster learns that a child under 13 has used the App to provide personal information to HerdMaster, HerdMaster will take the steps required by applicable law, which may include deleting that information. Questions or reports concerning children's privacy may be sent to support@herdmaster.app.
14. California Privacy Rights (CCPA)
California residents have the right to:
- Know what personal information we collect and how it is used
- Request deletion of their personal information
- Opt out of the sale of personal information (we do not sell personal information)
- Non-discrimination for exercising their privacy rights
To exercise these rights, contact us at support@herdmaster.app.
15. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. We will notify you of material changes by posting the updated policy in the app and updating the “Last Updated” date above. Your continued use of the app after any changes constitutes acceptance of the updated policy.
16. Contact Us
If you have questions, concerns, or requests regarding this Privacy Policy or your data, please contact us:
HerdMaster LLC
Email: support@herdmaster.app
Website: herdmaster.app
McMinnville, Oregon, USA
