This Data Processing Agreement is part of the Terms of Service between Breed Ledger ("Processor") and the club, association or registry that signs up ("Club" or "Controller").
What this covers.
Breed Ledger processes personal data about the Club's members and contacts only to provide the platform to the Club. This includes names, emails, contact details, membership and dues records, registrations, animal and pedigree records tied to a person, event entries, payment status, messages and uploaded documents ("Member Data").
A member's own profile holds a name, an email address, a city and state, a website and a short introduction. Breed Ledger does not ask for government identification numbers or health information about people, and Breed Ledger is not directed to children under 13.
Roles.
The Club decides why and how Member Data is used. Breed Ledger processes it on the Club's instructions, which are this agreement, the Terms of Service, and the Club's use of the platform settings.
For data Breed Ledger collects for its own purposes (sign-in security, product analytics, billing, error reports), Breed Ledger acts for itself and handles that data under its Privacy Policy.
What Breed Ledger will do.
- Process Member Data only on the Club's instructions, and tell the Club if an instruction would break the law.
- Keep Member Data confidential, and limit access to staff and service providers who need it.
- Use the security measures described in section 008.
- Not sell Member Data, and not use it to train AI or machine learning models.
- Help the Club answer requests from members to access, correct, export or delete their data, through the admin area where a tool exists, and by email at the address in section 012 where there is none.
- Tell the Club without undue delay after Breed Ledger becomes aware of a security breach affecting Member Data.
- Give the Club the information it reasonably needs to show it has met its own duties, and allow reasonable audits as in section 009.
What the Club will do.
The Club will use the platform lawfully, give its members the notices and obtain the consents the law requires, keep its administrators' access under control, and decide who sees what in its public pages.
Export and deletion.
The Club can export its data at any time. This applies during the trial, on the free plan, on a paid plan and after the trial has ended. A full export is a promise we make to every Club, and is not tied to a paid plan.
A full export is a bundle of JSON and CSV files with a manifest that gives a SHA-256 fingerprint for each file. It holds the Club's profile, members, animals and pedigree links, registrations and transfers, events and entries, payment records, pages and posts, the history behind those records, and the files the Club stored on its animals, registrations, pages and members.
The export leaves out private notes on animals and private health results that members keep private, registrations an owner recorded with an outside registry, copies of pedigree links that another organization keeps, the image files of events, passwords, sign-in tokens, API credentials and payment processor identifiers, and the usage counters and platform operations records that Breed Ledger keeps for itself.
The Club can ask us to delete Club data and Member Data at any time, by closing the account or by email.
- Closing the account: after a Club closes its account, we keep the Club's data for 90 days so that the Club can still export it, and we delete it if the Club asks us to, except for the records this agreement says we keep for longer.
- An individual's account: when an individual asks us to delete their own account, we remove their personal profile and program data within 30 days, as section 005 of the Privacy Policy states.
- Records we must keep by law: records such as billing records are kept for the period the law requires, which the Privacy Policy gives as 7 years for billing records required for tax purposes, and are not used for anything else.
- Verification pages: a public registry verification page shows the organization name, the animal's registered name and registration number, the status and issue date, the verification code, and the animal facts, parents and designations the Club chose to print. It does not show an owner name, an email address or contact details.
Trial end: when a trial ends, the Club moves to the free plan. Published events become read-only on the free plan; nothing becomes private or deleted because the trial ended, so no deletion occurs at trial end.
Subprocessors.
The Club agrees that Breed Ledger may use the following subprocessors to process Member Data.
| Provider | Purpose | Data region | Privacy Policy |
|---|---|---|---|
| Supabase | Stores accounts, animal records, registrations, member records and uploaded files, and handles sign-in. | Supabase, US West (Oregon) region (us-west-2). Documentation | View |
| Vercel | Hosts the platform and runs its scheduled jobs, measures page views and page speed, manages organization custom domains, and routes requests to Anthropic through the AI Gateway. It also screens self-serve organization signup requests for bots. | Vercel, United States. Documentation | View |
| Stripe | Takes card payments for plan subscriptions, memberships and event entries. | Stripe does not have a region set by Breed Ledger. See its documentation for where it holds data. Documentation | View |
| PostHog | Measures page views and feature use, and receives application logs. | PostHog Cloud, United States region (us.i.posthog.com). Requests may pass through Breed Ledger's reverse proxy at go.breedledger.co, which forwards to that region. Documentation | View |
| Sentry | Receives error reports when part of Breed Ledger fails, so that we can find and fix the fault. A report carries the error and its message, where in the code it happened, web addresses reduced to page patterns, with query strings removed and names, record identifiers and access tokens replaced by placeholders, email addresses in messages partly hidden (we keep at most the first two characters and the domain), the organization's identifier when a server error is tied to one, the addresses of recent page changes and requests, and, where available, the browser, device, operating system or server software names and versions. Reports are not linked to an account. An error message is written by our code or by the software that failed, and can occasionally contain other details such as a name or an identifier. We collect no cookies, request headers, request bodies, screen recordings or performance traces. | Sentry stores error reports in its United States region. Documentation | View |
| Resend | Sends the platform's email to members, breeders and organization staff. | Resend, United States. Documentation | View |
| FedEx | Receives the shipment and address details needed to quote, check or track a package when a shipment is handled on the platform. | FedEx does not have a region set by Breed Ledger. See its documentation for where it holds data. Documentation | View |
| Anthropic | Reads pedigree and health documents that a breeder uploads for import, and drafts website text and search titles and descriptions. | Anthropic does not have a region set by Breed Ledger. See its documentation for where it holds data. Documentation | View |
| Google sign-in | Signs a member in with a Google account when the member chooses Continue with Google. | Google sign-in does not have a region set by Breed Ledger. See its documentation for where it holds data. Documentation | View |
Breed Ledger also uses DocuSeal, Cal.com, Meta Platforms, Google Fonts and YouTube. They are used on Breed Ledger's own marketing and public pages, or for contracts between a breeder and a buyer, and do not receive Club records.
Breed Ledger will update this list when it adds or replaces a subprocessor. It will give the Club 30 days' notice by email to the account owner before a new subprocessor handles Member Data. A Club that objects may export its data and close the account.
Where data is held.
The subprocessor list states the region of each service where it has one. Several services have no fixed region set by Breed Ledger. We do not promise that Member Data stays in the United States.
Security.
Breed Ledger uses:
- TLS in transit.
- Encrypted storage at rest through Supabase.
- Row-level security to separate each organization's data.
- Hashed passwords through Supabase Auth.
- A hashed (not stored) IP address for rate limiting.
Audits and information.
On reasonable written request, once a year, Breed Ledger will give the Club the information it needs to confirm Breed Ledger meets this agreement, such as a description of its practices and its subprocessor list. Breed Ledger does not offer on-site audits.
Liability.
Liability under this agreement follows the limits in the Terms of Service.
Term.
This agreement lasts as long as Breed Ledger holds Member Data for the Club. Sections 005 (retention and verification pages) and 010 survive closure.
Contact.
For questions about this agreement, privacy requests and security reports, contact:
Breed Ledger
Email: dmumphrey@builtbydusty.com
Last updated: November 15, 2026