← Catch

Catch Privacy Policy

Last Updated: 2026-09-07

This Privacy Policy explains how [Catch LLC], a New York limited liability company (to be formed) ("Catch," "we," "us," or "our"), collects, uses, shares, and protects information in connection with the Catch rowing-team management application (the "Service").

Placeholder notice: the bracketed entity name above is a placeholder until the LLC is formed and named. This document has not yet been reviewed by an attorney — see the cover note delivered alongside this file for what still needs legal review before this is treated as final or published to real users.


1. Who This Policy Covers

This Policy applies to coaches, athletes, recreational users, and any other person who creates an account or whose information is entered into the Service by a coach or team administrator ("you," "users").

The Service is intended for use by rowing teams and their members. It is not directed at children under 13, and self-registration is not permitted for anyone under the age of 16 — see Section 6 ("Children's Privacy") for details.


2. Information We Collect

We collect only what the Service needs to function. We do not run any analytics, advertising, or tracking SDKs in the app today, and we do not collect more than the categories below.

2.1 Account & Profile Information

  • Email address and password (managed securely by our authentication provider, Supabase — we do not store your password in plain text or have direct access to it).
  • Display name, role (athlete / coach / recreational), and, for coaches, coaching tier (Head, Assistant, or Freshman/JV Coach) and squad assignment.
  • Team affiliation (which team/organization you belong to).

2.2 Athletic & Performance Information

  • Seat and side preferences, lineup and boat assignments.
  • Erg (rowing machine) results and training history, including data captured via on-device photo scanning of erg monitor displays (see Section 2.5).
  • Attendance records, practice schedules, and season/training-plan data.
  • Regatta and race-day results.

2.3 Sensitive / Safeguarding Information

Some information the Service handles is more sensitive, particularly for users under 18:

  • Weight, where a team has enabled weight tracking. For users the Service identifies as minors, weight is never displayed at the individual level to non-coach viewers (teammates, in exported rosters, etc.) — only in team-level aggregates.
  • Medical notes and injury logs, entered by coaching staff. These fields are restricted to coaching staff only and are never visible to athletes, teammates, or recreational users.
  • Staff-only coaching observations, visible to coaching staff only, never to athletes.

We treat this category of information with the highest level of access restriction the Service supports. It is never sold, and it is not used for any purpose beyond operating the team-management features it supports.

2.4 Location Information

  • A team's general location (e.g., city/region) may be set by a coach at team creation, used solely to show locally relevant weather conditions for practices. This is a team-level location, not a tracked location of any individual user's device.
  • We do not track or store the real-time or precise location of any individual user's device.

2.5 Photos & Media

  • Erg monitor "scan" photos are processed entirely on your device using an on-device optical character recognition (OCR) library — these images are not uploaded to Catch's servers or any third party for processing.
  • Profile photos and chat/photo-sharing features are planned but not yet built as of this Policy's last-updated date; this Policy will be updated before any such feature launches.

2.6 Communications

  • In-app messages, announcements, and comms sent through the Service are stored to make the feature work and are visible to their intended recipients within your team, per each feature's own visibility rules.

2.7 Payment Information

  • As of this Policy's last-updated date, the Service does not process real payments — dues/fee tracking features record balances and reminders you or your team enters manually, not actual transactions.
  • If and when paid subscriptions or licenses are introduced, payment card information will be collected and processed by a third-party payment processor (e.g., Stripe), not stored directly by Catch, and this Policy will be updated to name that processor before that feature launches.

2.8 Device & Technical Information

  • Standard technical information necessary to operate the Service (e.g., authentication session tokens). We do not currently use any analytics, crash-reporting, or advertising SDKs.

3. How We Use Information

We use the information above only to:

  • Operate the core features of the Service (rosters, lineups, attendance, erg tracking, scheduling, communications, etc.);
  • Enforce the role- and safeguarding-based access rules described in Section 2.3;
  • Provide locally relevant weather information for scheduled practices;
  • Communicate with you about your account or the Service;
  • Maintain the security and integrity of the Service;
  • Comply with legal obligations.

We do not use your personal information for targeted advertising, and we do not build advertising profiles.


4. How We Share Information

We do not sell, rent, or trade your personal information to any third party. This is true today and is a deliberate business decision — our revenue comes from team subscriptions/licenses to use the Service and from affiliate or brand partnership arrangements (see Section 4.2), not from monetizing your data.

4.1 Service Providers

We share information only with the vendors necessary to run the Service:

  • Supabase (our backend database, authentication, and hosting provider) — stores account, profile, team, and feature data.
  • Open-Meteo — a free weather data API. We send only a team's general latitude/longitude to retrieve weather conditions; we do not send any personal or account information to this provider.
  • Apple/the App Store — for distribution of the app, subject to Apple's own platform terms.
  • Any future service providers (e.g., a payment processor, fitness-device integration, or push-notification service) will be added to this list, and this Policy updated, before that integration goes live.

Each provider is contractually and/or technically limited to using data only to provide their service to us — not for their own independent purposes.

4.2 Affiliate Links & Brand Partnerships

Catch may include affiliate links or brand partnerships (e.g., rowing equipment or apparel brands) as a revenue source. Clicking an affiliate link or engaging with a brand partnership does not involve us sharing your personal Catch account data with that brand unless a specific feature explicitly discloses otherwise at the time you use it. Any future feature that would share your personal information with a brand partner will be clearly disclosed, and, where required by law, will require your opt-in consent.

4.3 Legal Requirements

We may disclose information if required to do so by law, or in a good-faith belief that disclosure is necessary to comply with legal process, protect our rights, or protect the safety of any person.

4.4 Business Transfers

If Catch is ever involved in a merger, acquisition, or sale of assets, user information may be transferred as part of that transaction. We will provide notice before your information becomes subject to a different privacy policy.


5. Data Security

We take reasonable technical and organizational measures designed to protect your information, including:

  • Encryption of data in transit and at rest, as provided by our infrastructure provider (Supabase);
  • Database-level access controls (Row Level Security) restricting which rows/columns of data a given user's account can even query, enforced at the database layer, not only in the app's interface;
  • Application-level safeguards that strip sensitive fields (like medical notes or a minor's weight) from any response sent to a non-coach viewer;
  • Secure password handling via our authentication provider (we never see or store your password in plain text).

No method of transmission or storage is 100% secure. While we work to protect your information, we cannot guarantee absolute security, and no security measure is impenetrable. In the event of a data breach affecting your personal information, we will notify affected users and any relevant regulators as required by applicable law (see Section 6 below for how this applies to New York residents specifically).


6. Data Breach Notification

If we become aware of a security breach that compromises your personal information, we will notify you without unreasonable delay, consistent with applicable law — including, for New York residents, the notification obligations under New York's data security laws (the "SHIELD Act"). This notice will describe, to the extent known, what happened, what information was involved, and what steps we and you can take in response.


7. Children's Privacy

The Service is not directed at children under 13. Self-registration requires being 16 or older — an account giving a date of birth under 16 is refused at sign-up. Athletes under 16 are added to a team by their coach, and a parent or legal guardian must approve their participation through the guardian-consent process before that athlete can use the Service.

Flag for legal review: if a coach ever enters information about a team member who is younger than 13 (rather than that child creating their own account), this may still trigger obligations under the U.S. Children's Online Privacy Protection Act (COPPA) depending on the circumstances. This is a specific, open question that should be resolved with legal counsel before the Service is used by any program that includes athletes under 13 — see the cover note delivered with this document.

If we learn that we have collected personal information from a child under 13 in a manner inconsistent with applicable law, we will take steps to delete that information.


8. Data Retention & Deletion

We retain your information for as long as your account is active or as needed to provide the Service. You may request deletion of your account and associated personal information by contacting us at the address in Section 11. We will delete or anonymize your information within a reasonable time, except where we are required or permitted by law to retain it (e.g., financial records, dispute resolution).

Coach-entered records about a team (such as historical attendance or erg results tied to a team, rather than to you personally) may be retained by the team even after an individual athlete's account is deleted, since that data belongs to the team's own operational history.


9. Your Rights and Choices

Depending on your location, you may have rights to access, correct, or request deletion of your personal information, or to object to certain processing. To exercise any of these rights, contact us using the information in Section 11. We will respond within a reasonable time.


10. Where Your Information Is Stored

Your information is stored and processed by our infrastructure provider, Supabase. [Confirm and state the specific hosting region(s) here once decided/verified — not yet confirmed as of this draft.]


11. Contact Us

Questions about this Privacy Policy, or requests regarding your information, can be sent to:

[contact email — to be added] [Catch LLC — mailing address, once formed]


12. Changes to This Policy

We may update this Privacy Policy from time to time. If we make material changes, we will provide notice (such as an in-app notice or updated "Last Updated" date) before the changes take effect. Continued use of the Service after changes take effect constitutes acceptance of the revised Policy.


Terms of Service · Privacy Policy · Catch