Privacy Policy

• Your race, course, runner, pace plan, and station check-ins are stored locally on your device by default.
• Location is used only while the app is open to help identify which station you are at, and the app does that matching on-device.
• Crew sharing is optional. If you sign in and join or create a crew, the shared crew data syncs through Supabase so other crew members see the same plan and station updates.
• Importing a pace plan from a photo, PDF, or exported CSV is optional. If you use it, the file is sent to Claude AI (operated by Anthropic) to read your plan; we do not store the file, and Anthropic does not use it to train its models.
• The app does not include advertising SDKs or cross-app tracking. It sends anonymous usage statistics to TelemetryDeck (which screens are used, which race is selected, and whether a crew is synced) and technical diagnostics logs to us, both described below.

Crew Companion stores your selected race or custom course, aid stations, runner name, Trackleaders link if you add one, pace-plan entries, recorded arrival and departure times, recent tracking snapshots, app settings, onboarding state, and optional sign-in session data on your device.

That local data remains on your device until you delete it, restore from a different backup, use the app's reset flow, or uninstall the app.

You can use Crew Companion without crew sync. If you choose to create or join a crew, the app syncs shared crew data through our Supabase-hosted backend so your crew stays in sync across devices.

The synced data can include:

• your crew membership and app account identifier,
• an optional handle you provide for your crew,
• the runner name, selected event, or custom course definition,
• the Trackleaders link if you configure one,
• the runner's bib number if you enter one,
• pace-plan entries,
• station arrival and departure times recorded by the crew,
• station notes and checklists written by the crew,
• photos the crew shares, with the station and the time each was taken, and
• whether the runner has dropped out of the race.

Everyone in your crew can see this shared data. How long it is kept is described under Retention and deletion.

The app does not sync your live device location as part of crew sharing.

Crew sync requires signing in. Supported sign-in methods can vary by platform and build, and may include Sign in with Apple and other identity providers such as Google.

When you sign in, our authentication provider may receive your provider user ID and, depending on the provider and the choices you make there, details such as your name or email address. We use that information to authenticate you, restore your session, and determine which crew data you are allowed to access.

With your permission, the app can use foreground location while the app is open to detect the nearest aid station and pre-select it for check-in. That matching happens on your device.

We do not collect, store, or sync your GPS coordinates to our servers for this feature. If you decline location permission, the app still works and you can choose stations manually.

With your permission, the app shows race alerts. Some, such as finish-related reminders, are created on your device.

If you are signed in and part of a crew, the app can also send you crew notifications, for example when a crew member records a check-in, shares a photo, or marks the runner finished or dropped. You choose which of these you receive in Settings. To deliver them, the app registers your device's push notification token with our server, along with your platform and account identifier, and your notification choices for each crew. Notifications are sent through Expo's push service, which passes them to Apple or Google. The token is removed when you sign out or delete your account. We use it only to deliver crew notifications, never for advertising or tracking.

If you add a Trackleaders URL for your runner, the app fetches that public Trackleaders page directly from your device to show status, distance-to-next-waypoint, and estimated arrival information.

This means Trackleaders receives the request for that public page. We do not proxy those requests through our own server.

Instead of typing your pace plan in by hand, you can import it from a photo, PDF, or a CSV your runner exported from another planner (for example UltraPacer). This feature is optional, and the app asks for your permission before the first upload. If you decline, you can still enter your plan manually.

When you use it, the app sends the file — by way of our own server — to Claude AI, a service operated by Anthropic, so it can read the plan and turn it into station names and times. The extracted details come back to you to review, and nothing is saved until you confirm them.

We do not keep the file you import. It is not stored on your device and it is not stored on our servers; only the plan details you review and confirm are saved (locally, and through crew sync if you have joined a crew). The file itself is discarded once the plan has been read.

We do not send Anthropic your name, sign-in account, or crew membership — only the file itself, along with the race name, its start time, and the list of aid-station names, which help it read the plan more accurately. Under Anthropic's commercial API terms, Anthropic does not use the file to train its models and automatically deletes it within 30 days.

The app lets you export a backup file of your local race data, restore from a backup file, share a plain-text runner update, share a crew invite link, and share a diagnostics log. These actions are optional and happen only when you choose them.

Once you share a file, message, or link through your device's share sheet or save it to another service, that copy is then governed by the destination app, service, or recipient.

The app sends anonymous usage statistics to TelemetryDeck so we can see how the app is used: when it is opened, which screens are viewed, which race is selected and its approximate distance, and whether you are using crew sync. These signals carry an anonymous identifier for this installation, not your name, email, or location, and are not used for advertising.

Crew Companion keeps an on-device diagnostics log to help with troubleshooting. It records technical events such as auth, sync, GPS, network, and Trackleaders activity, along with app and platform version details.

While the app is open, it also sends new log entries to our server about every five minutes so we can find and fix problems. Each upload includes a random identifier for this app installation, your account identifier if you are signed in, the app version, and your platform and operating-system version. Location coordinates are removed from the log before it is sent. We can switch these uploads off remotely, and we keep uploaded logs for 30 days.

You can also share the full log yourself, for example when you send feedback.

The app uses the camera only when you choose to take a photo: a station photo to share with your crew, or a picture of a pace plan to import. When you take a station photo, the full-size original is saved to your own photo library (the app can add to your library but cannot read it), and a smaller copy is shared with your crew. You can also pick an existing photo instead.

The current app does not record audio or video. If a future build adds a recording feature, we will update this policy to describe how those recordings are handled.

We do not sell your data. The app currently relies on:

• TelemetryDeck for anonymous usage statistics.
• Expo to deliver crew push notifications through Apple and Google.
• Supabase for authentication and optional crew-sync storage.
• Apple and other supported identity providers for optional sign-in.
• Trackleaders for public runner-tracking pages when you configure a tracker link.
• Anthropic (Claude AI) to read a pace plan you choose to import from a photo, PDF, or CSV.

Local app data stays on your device until you remove it: delete the race, use Erase everything in Settings, or uninstall the app.

Shared crew data on our servers (synced times, notes, checklists, photos, the plan, and the course) is deleted automatically 30 days after your race ends. During the last week the app shows the date it will be removed and saves your crew's photos to your phone. A crew that is still being used is not removed until it has had no activity for 7 days. The copy on each crew member's phone is not affected.

When shared crew data is removed, we keep only an anonymous summary for our own statistics: the race, the year, how many people were in the crew, how many stations were recorded, and whether the runner finished. It contains no names, account identifiers, notes, photos, or exact times.

Diagnostics logs sent to us are kept for 30 days.

To delete your account, open Settings in the app and choose Delete account, or contact us at the address below. Deleting your account deletes the crews you own for everyone (including their photos), the photos you took in other crews, and the feedback and diagnostics you sent us. Times and notes you added to other people's crews stay with that crew without your name. Records of purchases are kept, without a link to your account, for sales and refund purposes.

Crew Companion is not directed to children under 13, and we do not knowingly collect personal information from children under 13.

We may update this policy as the app changes. If we do, we will post the revised version here with a new effective date.

Questions about this policy or your data? Email wes@automaticduck.com.