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 current React Native build does not include advertising SDKs or third-party analytics trackers.

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,
• pace-plan entries, and
• station arrival and departure times recorded by the crew.

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.

The app may request notification permission for on-device race alerts, such as finish-related reminders. In the current app, these notifications are local to your device; the app does not register a separate remote push token with us 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.

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.

The log is not sent automatically. It leaves your device only if you choose to share it.

The app configuration includes camera and microphone permission strings for planned post-race feedback features. The current build described by this policy does not automatically record or upload audio or video in the background.

If a future build adds an in-app feedback recording flow, we will update this policy to describe how those recordings are handled.

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

• 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. If you have used crew sync and want synced crew data or account-linked data deleted from our systems, contact us at the address below.

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.