Privacy policy
Walk-Off Works ("we", "us") makes the InningUp app, the web app at app.inningup.com and the website at inningup.com. This page says what they collect, why, who sees it, and how to delete it. The terms of use are the other half of the agreement.
The short version
- You do not need an account to record and review on your phone. Recordings stay there until you sign in for backup. Requesting a sign-in or verification code sends the contact information needed to deliver it.
- Sign in with an email code or Sign in with Apple. Where SMS is enabled, an adult account holder can add a verified phone number and explicitly remember a device for text-code sign-in. A new or forgotten device uses email or Apple first. Accounts are for people 18 and older.
- No ads. No analytics tools in the app or the web app. No third-party software in the app that follows you. No tracking. We do not sell or rent your data.
- After you sign in, your sessions are saved to our own storage at Cloudflare, linked to your account. Your video-backup and Wi-Fi/cellular choices govern playback uploads. A session recording can include footage before, between and after attempts, not only bookmarked moments.
- You decide who can see a player: family you invite, and a coach only when you join their team. A coach sees what you allow. You can leave a team any time and the coach stops seeing the player right away.
- Parents look after their children's profiles. Children do not have accounts.
- For a new player, we ask to use recorded video to improve ball tracking as part of setup. The request is not consent. No video becomes eligible for training until that player's parent or guardian, or the adult player, explicitly agrees.
- You can delete a session, a player, or your whole account, in the app and on the web.
What the app records on your phone
- Camera video. With video recording enabled, tap Start session once and the app keeps the footage it captures until End session, including time before, between and after pitches or swings and attempts the detector misses. Detected results and optional manual bookmarks identify moments; they do not start, stop or limit the recording. Swing Studio also records a whole side-on session, and you can import a video you choose. The app may store a session in several video files while presenting it as one recording. Interruptions, dropped frames, storage or encoder failures can leave gaps or a partial recording; completed parts are kept and problems are reported. Camera preview before Start session is not the session recording. An imported video may already contain sound. If you choose to record coaching voice feedback, the app asks for microphone permission and records only that optional voice clip.
- Numbers for each pitch or hit. Speed, where the ball crossed the plate, break, a spin estimate, pitch type, exit speed, launch and spray angle, estimated distance, a quality grade, and the path of the ball. These are estimates made by the app. They are not official measurements.
- Set-up details. Which hand throws and bats, batter height, pitching distance, field, where the camera was placed.
- Players. A name, hands, height and an optional jersey number or position, for each player you add.
- What you type or correct. Session titles, corrected pitch types and outcomes, and "not a real pitch" marks.
- Your sign-in. When you sign in, the server makes up a random number for your phone and a secret token. The token is kept in the iPhone Keychain.
The app does not read your contacts or scan your photo library, and does not access health data. You can select a video for import. Optional coaching voice feedback asks for microphone permission. Where weather adjustment is used, approximate location is used briefly with Apple's weather service; coordinates are not saved in your session or sent to our account backend.
Coaching feedback and activity updates
Feedback can refer to a specific video moment and contain text, normalized drawings and an optional voice clip. Voice clips are limited to two minutes. Coaching text, drawings and voice feedback are excluded from model-training inputs. Shared coaching feedback follows the player's current family/team permissions. Staff-private feedback is visible only to its author while their staff access remains valid. Voice playback requires current permission and has no public download link.
In-app feedback and practice updates are optional and follow the preferences in Settings. They appear when you open or refresh the app or website; these settings do not enable background push, SMS or email messages. Turning them off stops new optional in-app updates. Existing updates remain readable only while their underlying player/feedback is still accessible.
Your account
- What we keep. Your email address, the name you gave (optional), the time you agreed to the terms, the players you look after, and, if you add one, your verified account phone number. A phone number belongs to the adult account holder, not a child's player profile.
- How we use your email. To send you a six-digit sign-in code, to send an invite when you ask us to invite someone, and to tell you about a change to your sign-in email. We do not send marketing email and we do not give your address to anyone else. An invite email holds a link, who invited, and the team name. It never names a player.
- Sign in with Apple. If you use it, Apple gives us a number that identifies you to us, your email address (your real one, or the private address Apple makes if you choose to hide it) and, the first time, your name. We do not get your Apple password. If you hide your email, sign-in codes and invites go to Apple's private address, and Apple passes them on. When you delete your account we also tell Apple to disconnect it from InningUp.
- Signing in. Codes expire after 10 minutes and work once. InningUp's sign-in database stores code hashes. Email and SMS delivery systems necessarily receive the code; the SMS gateway and Twilio may retain message content for delivery, logs or duplicate-send protection. On the website a session cookie keeps you signed in for up to 30 days. In the app the sign-in token stays in the Keychain. These are for authentication, not tracking.
- Optional text codes. Adding or changing your phone number requires a recent email or Apple sign-in and a verification text. You can then choose to remember this browser or phone for SMS sign-in for up to 90 days. A separate secret proof is kept in a secure, HTTP-only browser cookie or the iPhone Keychain. A phone number and a text code alone cannot enroll an unknown device. Using SMS does not extend this remembered period. A new device or expired proof returns to email or Apple.
- Signing out. On the phone, signing out keeps every session and player on the phone and stops backup. Ordinary sign-out can retain an explicitly remembered SMS device so you can sign in there again with a text code. The signed-out iPhone can remove its saved SMS proof locally. In account settings you can revoke remembered devices or unlink the number, which also ends the SMS sessions they authorized. The web and app provide controls for other active sessions and phones.
- Changing your email. We send a code to the new address first, and a short notice to the old one.
Account requests and optional backup
| What | Example | Why |
|---|---|---|
| Your email and name | an address, "Dana" | To sign you in and to show your name to the people you share with |
| Optional account phone number | an adult's number with country code | To verify the number and deliver requested text codes through our messaging gateway and Twilio; never to share with a coach or use as a training input |
| Players | name, hands, height, jersey | So each player's sessions are kept under that player, and so you can share one player and not another |
| Session and pitch or hit numbers | speed 72 mph, zone 5, quality A, ball path | A safe copy if the phone is lost, a copy on a new phone, the web view, and what a coach can see if you share |
| Session video and saved clips | the captured session from Start to End, stored in file parts, or an older saved pitch/swing clip | The phone makes H.264 playback copies for account backup and web viewing. These may differ from the original in resolution or frame cadence. Existing video-backup and Wi-Fi/cellular choices apply. A coach sees video only under your sharing choice, which can include the footage between bookmarked attempts |
| Consented training copies | eligible original-quality session parts or saved/imported video, with upload and file-integrity information | A separate private upload for later ball-tracking review. Whole-session sources require a fresh parent/guardian or adult-player confirmation covering that scope; older saved-clip permission is not expanded |
| What you typed or corrected | "Slider", "Single", a title | So your corrections are kept with the pitch |
| Practice assignments | a coach's title and instructions, optional due date, explicit completion and an optional linked session | To organize the next practice and show its status to the player's family and the issuing team's authorized staff |
| Phone details | random number, app version, "iPhone" | So the server knows which phone is signed in and you can sign one out. iOS gives apps only a generic device name, not the name you gave your phone |
The player's name is also saved inside each session's settings, so it goes up with the session. A first name or a nickname is enough.
Things you share yourself. If you export a CSV file, share a summary card or share a clip, it goes where you send it, through the share sheet. We do not see it. The CSV and the card can include the player name and the numbers.
Every upload uses an encrypted (HTTPS) connection. The server stores only a one-way scramble of your token, never the token. It answers a request only with data you are allowed to see. Something you may not see looks to you like something that does not exist.
Sessions you recorded as "examples" (the made-up ones behind "Look around with an example") are never backed up.
Young players
Players of all ages use the app, including young players, and it records video of the player.
- Accounts are for people 18 and older. Signing up asks the person to say they are 18 or older. That is their statement, not a check. A child does not get an account.
- A parent or guardian holds the account and decides who sees each child's profile: family they invite, and any team they join. They decide whether video clips are shared, how far back a coach sees, and when to leave.
- A coach can make a profile for a player (a "managed" profile) so the coach can record for them. The coach holds that profile until the family takes it over with a link. Until then the family has no access to it. Coaches agree in the terms to make a managed profile only with the parent's or guardian's permission and to hand it over or delete it when the family asks.
- We do not ask for a child's email address or phone number. The player name is required for a profile; a first name or a nickname is enough.
- If a player is under 18, a parent or guardian must decide whether their videos may help train ball tracking. The app asks separately for each player and records the account, declared relationship, policy version and date of that confirmation. Creating an account, accepting the terms, backing up a video or sharing it with a coach does not grant training permission.
- We do not knowingly collect personal information directly from children under 13. Children cannot create accounts. A child's profile exists because a parent or guardian made it, or a coach made it with a parent's permission. If you believe a child has made an account, or that a profile exists without a parent's permission, write to support@inningup.com and we will look into it and delete it where it is not right.
Coaches and sharing
A team is made by a coach. A coach invites a player's family with a link or a code. When a parent accepts, that player joins the team and the team's staff (the head coach, coaches, and assistants) can see that player's numbers. Nobody sees a player because a coach typed their name.
What a coach sees, per team, once you join. - The player's sessions, pitches and hits, with the charts and totals, from the date you chose: all of the player's history, or only sessions from the day you joined. - Video, only if "Share video clips" is on for that team. A shared whole-session recording can include footage before, between and after attempts, not just the detected or bookmarked moments. You can turn sharing off at any time and the video stops being available to that team. - Whether a coach may record sessions for the player: you choose with "Coaches can record for this player". Assistants never record. - A coach on one team does not see your other teams, and cannot see other players in your family.
What a coach never sees. The names or email addresses of the player's family, the notes the family writes, the player's other teams, and your phones or account details.
You are in charge. - You choose at joining time: which player joins, whether clips are shared (on by default, and shown clearly), and how far back the coach sees. You can change both later in the app (Settings > Back up and share) and on the web. - Leaving a team ends the coach's access right away. The coach loses the player at once, including anything that coach could see before. The coach's own phone keeps the sessions that coach recorded; they stay on that phone until the coach deletes them. - You can see who looked. The sharing screen (in the app and on the web) lists the latest times someone on a team looked at the player's numbers or watched a clip, with the person's name and the team. Looks are kept for 90 days and are written at most once an hour per person and kind of look. Your own looks and your family's are not listed. - Team numbers. A coach sees a roster and a leaderboard of the players on the team. Players and families do not see other players.
Notes. A coach can write two kinds of note on a player. A note "for the player" is visible to the player's family and to the other staff of that team. A "only me" note is visible to that coach alone: not to the family, not to other coaches. An "only me" note is deleted when that coach's access to the player ends (they leave or are removed, the family leaves the team, the profile is handed to a family, or the account is deleted). A family can write notes for itself; those are never shown to coaches. A family member who has only "viewer" access sees no notes. If a coach deletes their account, the notes they wrote "for the player" stay with the family and show "Deleted user" as the author.
Practice assignments. A head coach or coach can assign practice to a player shared with that team. The player's owner and guardians can read it, explicitly mark it complete or reopen it, archive it, or delete it. Authorized coaches can mark observed work complete; assistants can read but cannot change it. The record says who marked it complete and when. To team staff, a family member's completion is shown as "Family" without exposing that person's name or account details. Completion is a person's statement, not proof of every repetition or a measurement of workload.
An assignment can link a finished backed-up session for the same player, including a video-only review. This does not grant access to video, older history, new uploads or training. Team staff still see only their own team's assignments and currently shared sessions. Leaving a team or removing staff ends their access; the family keeps its assignment history. Deleting an assignment removes its instructions and completion record, while its linked recording stays until separately deleted. An archived assignment is still stored and can be reopened. Deleting a player removes that player's assignments. Shared assignments can remain with the family after the author's account or team is deleted, with unavailable author/team details removed.
Family. The person who owns a player can invite family as a guardian (can see and manage) or a viewer (can see numbers). The owner and guardians see the name and email of each person with access. Nobody can remove the owner. Anyone can remove themselves.
If a team is deleted by its head coach, its players are un-linked and keep all of their data. If a head coach deletes their account, the team passes to the next coach, or is deleted if there is no one.
The website
The web app at app.inningup.com shows the same data as the app and lets coaches manage teams. It is served by the same Cloudflare Worker as the app's server. It has no analytics and no advertising. The only scripts from other companies are the Cloudflare Turnstile check, which the sign-in form may show to tell people from bots (Cloudflare sees your browser and internet address when it is shown), and, only if you choose "Continue with Apple" on the web, Apple's sign-in script. The website keeps one sign-in cookie, as described above. You can export pitch and hit results as CSV, request a portable family account archive, and delete your account. The archive includes currently permitted family records, shared feedback, practice, annotations and an ordinary-media inventory; you choose whether to download available playback videos and voice feedback too. It excludes staff-private material, credentials and private training originals. It is a portable export, not an automatic app restore. Local-only recordings, local practice templates and local field-attempt ledgers are not stored in the account archive. An attempt ledger has its own explicit JSON sharing action.
The marketing site (inningup.com). It has a waitlist form. If you use it we keep your email address, and only use it to tell you when a spot opens, until you ask us to remove it. The site counts page visits with a simple analytics script that we run. It is not used for advertising and it does not follow you to other sites.
What we do not collect
Contacts, a scan of your photo library, advertising identifiers, browsing history, or purchases. Approximate location for optional weather adjustment is not saved; optional coaching voice clips are described above. The app contains no advertising or analytics software from other companies and does not follow you across other apps or websites.
Where your data is kept
On Walk-Off Works' own Cloudflare account: a Cloudflare Worker (the program that talks to the app and the website), a D1 database (accounts, players, numbers, text, notes), an R2 bucket (video clips), and Cloudflare Email Sending (sign-in and invite email). Cloudflare is our hosting company. Cloudflare handles network connections for the Worker, so it sees your internet address when you connect, and it may keep standard technical logs under its own terms. Cloudflare may process data in more than one country.
Where you choose text codes, our private messaging gateway sends the adult account number and verification message to Twilio for SMS delivery. The gateway respects SMS opt-outs. SMS is for authentication, not marketing, and declining or blocking texts leaves email and Apple sign-in available. A delivery request can be kept by our gateway for up to 24 hours to prevent duplicate sends; Twilio has its own delivery records. We do not send player videos, notes or results to Twilio.
The people who run the service can technically read what is stored. They do that only to keep it working, to answer a support request, or, where you switched it on, to improve the app.
We do not sell your data. Cloudflare hosts the service, Apple handles Sign in with Apple when chosen, and Twilio delivers optional text codes. If a court or other authority legally requires us to hand data over, we will do what the law requires and tell you where we are allowed to.
Using recorded video to improve ball tracking
For new player profiles, using eligible recorded video to improve InningUp is the default request in setup. It stays pending until you explicitly agree. Continue without training if you do not want this. Recording, reviewing, backing up and sharing with your chosen family or coaches remain available either way. Existing profiles without permission are not automatically enrolled.
If the player is under 18, only their parent or guardian may agree. An adult player may agree for themselves. A coach, assistant or viewer cannot agree through their team access, and a coach-made profile cannot participate before a family takes it over. The person confirming must declare which of these relationships applies. A confirmation for one player or account does not cover a different player or account.
With permission, eligible uploaded recordings and their associated ball-tracking results and corrections may be used to train and evaluate InningUp's pitch and hit detection. Names, notes, coaching feedback drawings or voice, practice assignments and completion metadata, email addresses and sign-in details are not training inputs. Video can still show identifiable people; removing profile details does not make the video anonymous. Permission for one player does not give us permission for other identifiable children or adults visible in the recording. The software does not verify everyone in view or automatically redact the background. Before training use, other identifiable people need their own permission or must be excluded or redacted during review.
Automatic collection after a whole-session confirmation. The current notice explains that eligible original-quality footage may include the full captured session: before, between and after attempts, missed detections, false detections, people nearby and background activity. After you give a fresh confirmation for this scope, eligible future sessions started or files newly imported by the approving family account are queued automatically while that account is signed in and its backup/network choices allow uploads. No separate per-clip upload action is needed. Collection has storage/file limits; it does not guarantee that every source or frame will upload, and it cannot recover an original that is no longer on the phone. Files keep the available source quality; a lower-resolution file is not upgraded to 4K.
An older saved-clip approval is not whole-session permission. Earlier approvals for saved clips keep that limited scope. The app asks for a fresh confirmation covering whole-session footage, with agreement unchecked by default, before that broader collection can be enabled. Existing declined choices stay declined unless you explicitly reconsider. Adding a detected result or manual bookmark to a whole-session part does not turn its surrounding footage into a separately approved short clip.
Each new app session or import keeps the player's training choice, confirmation reference, recording account and recording scope as they were at that time. Both that saved choice and the still-current confirmation must cover whole-session footage. A later approval or settings edit does not enroll an earlier app capture, replace its confirmation or enlarge its scope. A new import is a separate submission under its current confirmation; file metadata is not proof of when it was filmed. An offline confirmation must first be accepted by the account server, and conflicting offline approvals/withdrawals may require a fresh affirmation. Neither the default request nor an older unscoped approval grants whole-session permission.
You can decline or withdraw in Help improve InningUp. Withdrawal stops new collection and selection for new training work and queues removal of the separate training copies. Removal is retried if a storage operation fails; a queued copy is not eligible for use. Your ordinary playback backups stay unless you delete them separately. An old queued approval cannot restore permission, and a later approval does not restore recordings tied to a withdrawn confirmation. We keep a small consent record with the player, account, declared relationship, policy version, recording scope and times so we can enforce that choice. Withdrawal does not promise to undo a model already trained from lawfully used data.
Training permission does not change who can watch your clips. Normal backup keeps its compressed H.264 playback copy; separately approved training collection uploads an original-quality copy to private storage on our Cloudflare account. Both follow your existing video upload Wi-Fi/cellular choice, with Wi-Fi only as the default. Interrupted original uploads retry or resume. Collection has file/storage limits, and the app reports pending, collected or unavailable originals without stopping normal recording or backup. Signing out stops uploads from that account. Coaches and viewers do not receive access to these private training copies.
Earlier saved-clip confirmations do not silently authorize whole-session original collection. The app requests a fresh confirmation for the broader scope. Existing app sessions without the matching current confirmation are not enrolled retroactively when you agree later. A new import is a separate submission and needs the current confirmation when imported. Parent/guardian and account/player scope are checked again when uploads start and finish. Moving or deleting the recording, deleting its player/account, or losing the authorizing family role can end eligibility and queue cleanup.
We have not started training models from customer recordings, and there is no public training export. The consent and eligibility controls described here do not themselves start a training job.
How long we keep it, and how to delete it
- On your phone: until you delete a session (open the session, "Delete session"), remove a player, use Settings > Delete all my data, or delete the app.
- In your account: until you delete it. We do not currently delete an unused account automatically.
- Separate training copies: while the source and current permission remain eligible, subject to collection limits. Withdrawal or deletion of their source queues removal, and failed cleanup is retried. A small cleanup record can remain until removal finishes. Collection does not itself start model training or create a public dataset.
- Delete one session or one player. In the app (delete a session) or on the web (delete a session, or delete a player on My data or Sharing). It removes the numbers, notes and clips for it from the cloud.
- Delete all my data (app Settings) erases local sessions, pitches, hits, video, the saved player list, local templates, field-attempt ledgers in that session library and your settings. When you are signed in it also asks the server to delete the backed-up copies the next time the phone is online. It does not delete your account.
- Delete my account (app: Settings > Back up and share; web: Settings > Delete account) asks you to type your email, then deletes: the players only you look after, with their sessions, notes and clips; your sign-ins and phones; and the account itself. A player who has another guardian passes to the guardian who has been there longest, and you leave. A team with other staff passes to the next coach, otherwise it is deleted and its players are un-linked with their data intact. Notes you wrote "for the player" stay with the family, as "Deleted user". Your "only me" notes are deleted. Recordings and players stay on the phone, but the deleted account's local templates and field-attempt ledgers in that library are removed. Explicit sign-out-and-remove-phone-data also clears local templates and that library's records. Cleanup is scoped to the initiating account/library; a delayed response does not erase a newly signed-in account's data. Deleting clips can take a moment; the app and the website keep going until it says it is done. It cannot be undone.
- Short-lived records are removed by a nightly job: used or expired sign-in codes; counters that limit sign-in attempts (kept for a day); expired website sign-ins; phones that were signed out, 30 days after; invites 30 days after they expired or were switched off; the "who looked" log after 90 days; and unfinished email changes.
- Backups. The database has point-in-time recovery that keeps data for a short period, so a deleted record can exist in a recovery copy for up to about 30 days.
- Deleting the app from your phone does not delete your account. Delete your account first if you want it gone.
Your choices
- Stay signed out to keep session/video account uploads off. Requested sign-in codes and optional weather requests are described separately above.
- For calibrated pitching/hitting, turn off "record clips" before setup for measurements without video. Swing Studio's explicit Record session action records video. End session stops an active recording; bookmarks do not. Turn on "Wi-Fi only" to hold video uploads until Wi-Fi is available.
- Turn off "Share video clips" for a team, choose "only new sessions", or leave a team, at any time.
- Choose "Continue without training" or withdraw in "Help improve InningUp" to exclude your player's videos from new training work without losing recording or review features.
- Export pitch and hit results as a CSV file on the website.
- Ask us to delete or fix something by email: write to support@inningup.com from the address on the account. We can find your data by that address. We aim to answer within a few days.
Changes
If we change this policy we will change the date at the top. If a change means we collect or use data in a new way, the app will ask you first.
Contact
support@inningup.com · Walk-Off Works · inningup.com