TeamArc

Privacy Policy

Version 2026-11-14 · Effective November 14, 2026

Previous version: 2026-11-12

1. Who we are

TeamArc (“TeamArc”, “we”, “us”) is a coaching app by Semperity, operated by Semperity LLC, a Utah limited liability company. Coaches and clubs decide what information goes into TeamArc about their teams and tryouts; we process it to provide the app to them, to the families and players they share with, and, where a parent or guardian approves it, to a guest coach (section 5). This policy covers the TeamArc app, this website, and the emails and links TeamArc sends. Questions: privacy@getteamarc.com. Mail: Semperity LLC, 13 Rollingwood Ln, Sandy, UT 84092.

2. What we collect

  • Coaches: name, email address, phone number if added, team name and season, and sign-in records for your devices. When you start a team yourself, we record which versions of our Terms and this policy you accepted, when, and that you confirmed you are an adult coach or team administrator. If you send us feedback from the app, we keep it with basic details such as the app version. If you save a description of how you write (section 4), we keep that too. If you give a separate email address for the families on a team, we keep that too.
  • Plan and trial status: whether your team is in a trial period, or on a founding plan, a paid plan, a plan your club pays for, or a plan we’ve given; for a paid plan, its size (“Up to 12 players” or “13 to 22 players”, called Small-sided and Full-sided before 2026-11-12) and when it ends; when the trial started and when it ends; when your team’s first note was captured, because that date sets the trial’s length; and, for a plan we give, who gave it, why and until when. If you buy in the iPhone app, Apple handles the payment. We receive a record of the purchase from Apple (a transaction number, the product and the date), never your card or your Apple account details. To match a purchase to your team, the app gives Apple an opaque team number, not your name or email address. If you, your club, or another payer you arrange pays by invoice, we keep the invoice and the payer’s billing contact with the invoice only; it is never linked to a player. Whether and when you added the 7 extra days to a trial period, and whether you turned off trial reminder emails, and when.
  • Trial record: so that each coach gets one trial period, we keep a short record when you start a team yourself: a scrambled form of your email address (a keyed hash made with a secret key that only our servers hold, ignoring capital letters and any “+” label), with when your trial period started, when your first note was captured, when it ends, and whether and when you added the 7 extra days. It holds nothing else: no name, team, player, device, IP address or location. We use it only to continue the same trial period if you start again with the same email address, and it stays even if you delete your account. We delete it 24 months after your trial period ends.
  • Tryout evaluators (adults a club invites to help evaluate one tryout with a join code): name, email address (confirmed with a one-time code), your confirmation that you are 18 or older, whether you have a child in that tryout (and, if so, that child’s bib number or name), which versions of our Terms and this policy you accepted and when, and the notes and labels you add at the tryout. Your access covers that one tryout only (section 13).
  • Guest coaches (adults a team’s coach invites for a short guest spell with a player, where TeamArc has made this available): name, email address (confirmed with a one-time code), the team name the inviting coach typed for you, your confirmation that you are 18 or older and that you will use what you see only to coach those players during the guest spell, which versions of our Terms and this policy you accepted and when, sign-in records, when you first opened a player’s page, and the notes and shout-outs you write (section 5).
  • Team managers and club administrators (adults a team’s head coach invites as team manager, or we invite as a club administrator at the club’s request, where TeamArc has made this available): name, email address (confirmed with a one-time code), phone number if added, sign-in records, which versions of our Terms and this policy you accepted and when, and your confirmation that you are 18 or older. We keep who wrote each announcement, team email and text you send. For a club administrator, we also keep a record each time you open a team’s list or send a message: which team and how many, never a player’s name or anyone’s contact details (section 5).
  • Product-email choice: for tryout evaluators, whether you ticked the box described in section 7, whether it started ticked, when you chose, and the wording you saw. To decide whether the box starts ticked, we use your phone’s region setting (for example, US) and keep it with that choice.
  • Players (entered by their coach or team manager): name, jersey number, nicknames the coach uses for them, team, the coach’s notes about the player and the day or team event each note is about, notes a guest coach writes about the player (section 5), summaries of those notes, the player’s goals, development plan and check-ins, the updates and shout-outs the coach shares, whether the player was at a practice or game, if the coach marks it, and, if the coach removes a player from the team, the reason the coach picks (for example, moved or out long term).
  • Player RSVPs: a player 13 or older with their own sign-in can answer RSVPs (yes, no or maybe) for their own team events, if their team has this turned on; we keep the answer and that the player gave it. We don’t ask players for a reason.
  • Player goals: a player 13 or older with their own sign-in can set and change their own goal, say why it matters and describe what progress looks like, if their team has this turned on. The player’s family members can see it and can add suggestions. If a player doesn’t have a sign-in, a parent or guardian can set the goal; where a club requires it, that person must be signed in and marked as a parent or guardian. A head coach can clear a goal; nothing is deleted, and the earlier wording is kept with the goal’s earlier versions. Where their team has it turned on, a head coach can also suggest a goal, or write a goal together with a player who has no sign-in. A goal a coach suggested or wrote is shown with the coach’s name, and we keep each suggestion and whether it was used.
  • Tryouts (entered by the host club’s coaches and evaluators): a player’s tryout number or name, tryout notes and labels, and, if the club adds them from its registration list (or a coach types them in), the player’s birth year and a parent or guardian’s name, email address and phone number. The name is used only to greet them in an offer. The phone number is used only by the coach, who can text or call from their own phone; TeamArc does not send texts to it. If the club makes an offer, we keep the offer and the text it was prepared with, and, if it was emailed through TeamArc, to whom it was sent (section 13). If a coach emails a parent or guardian feedback about a tryout through TeamArc, we keep the words the coach wrote, the address it was sent to, who sent it and when (section 13). If the coach shares that feedback from their own phone instead, we keep the words, who shared it and when; we don’t know who received it.
  • Family members (entered by the coach, the team manager or the family member): name, relationship to the player, email address and phone number, whether they’ve agreed to notifications or text messages, RSVPs (yes, no or maybe, with a reason picked from a short list if the answer is no, and, when they answer while signed in, which family member answered), goals they submit for their player, including what they write about why a goal matters and what progress looks like, and suggestions they add to their player’s goal. We keep each earlier RSVP answer too, so the coach can see when an answer changed. If a parent or guardian approves a guest coach for their player (section 5), we keep who approved, when, for which player and guest spell, the end date and the wording they saw.
  • Team schedule: events, times, places, opponents and practice themes the coach adds or imports from a calendar link, and coaches’ own RSVPs for team events.
  • Volunteer jobs: where TeamArc has made this available for a team, the jobs the coach or a team manager the coach invites adds to a team event or for the whole season. Each job is a short title, such as Snacks or Equipment, and nothing else; there is no field for allergies, food or health details. We keep which adult family member holds each job, who gave it to them and when, and whether we sent that person the reminder (section 7).
  • Other people: a coach’s notes can mention other people, such as an opposing team.
  • Technical: push-notification tokens for devices that turn notifications on (and, where volunteer jobs are on, which signed-in family member turned them on, so a job reminder reaches only that person), whether a message was sent and delivered, and security logs. To limit repeated sign-in and tryout-join attempts we use your email address, your device’s IP address and the code you tried, and store them for that purpose only in scrambled (hashed) form. When the app hits an error, it sends TeamArc an error report: the app version and update, the phone’s operating system and version, the screen it was on, and the error’s type, message and technical trace. Before we store it, we remove email addresses and long strings of numbers. We don’t tie an error report to an account, person, team or device, and we don’t store your IP address with it. We use error reports only to find and fix problems, and delete them after 30 days.

3. Voice

A coach can speak instead of typing in the TeamArc app on a phone: a note about a player or the team, a check-in, an announcement to the team, and the description of how they write (section 4). A tryout evaluator can speak a tryout note. In each of these places the app asks the phone’s own speech recognition to turn the speech into text on the device, and only on the device. To help the phone recognize names, the app can give the phone’s speech recognition a short list of words to expect: player names, nicknames a coach has typed, and opponents’ names from the schedule. TeamArc receives only the text. TeamArc never records the audio, never receives it, and never sends it to an AI provider or to anyone else. If the phone reports that it can’t do this on the device, the app offers the keyboard instead; TeamArc does not send the audio to an online speech service. The app is built to stop listening when it is no longer in front on the phone, for example when the phone is locked or another app is opened, and coming back to the app does not start it again by itself. The text of a spoken check-in or announcement is handled like any other text the coach writes: the words are shown to the coach, nothing is saved or sent until the coach chooses, section 5 says who sees it, and section 4 says how AI is used with it. If a coach uses the keyboard’s own dictation or voice typing instead, the phone or keyboard maker’s own settings apply. If a coach uses voice in TeamArc in a web browser, the browser’s own speech recognition is used, and the browser maker (for example Google, for Chrome) may process the audio under its own policy; TeamArc never receives or stores the audio.

4. How we use AI

We use Google’s Gemini API to help organize coaches’ notes: for example, working out which player a note is about, summarizing a player’s notes for the coach, and drafting updates, shout-outs, check-ins, summaries and practice themes. We also use it to sort feedback coaches send us. To do this we send Google the note text and the team’s player names, nicknames and jersey numbers, and, for a draft about one player, that player’s goal (including what the player or a family member wrote about why it matters and what progress looks like), their focus area, and event details such as the opponent. For a coach’s own recap we also send the coach’s name. AI drafts are private to the team’s coaches until a coach reviews and chooses to share them. AI does not make decisions about players on its own; the coach decides what is kept and what is shared. We don’t use information in TeamArc to train AI models. RSVPs and RSVP reasons are never sent to AI. A goal a coach suggests is sent to AI only if it is used and becomes the player’s goal.

My voice. Where TeamArc has made this available, a coach can save a short description of how they write: how long, what tone, how they address families, a sentence in their own words and a sign-off. We use it only to shape the drafts that coach asks for. It is sent to Google with the draft request, except the sign-off, which TeamArc adds afterwards. Names on the team’s records are replaced before the coach’s sentence is sent, and we ask coaches to leave other names out. Other coaches can’t read it. The coach can change it in Settings, and it is cleared when the coach deletes their account.

Guest coaches’ notes. Where guest coaches are available (section 5), a guest coach’s notes can be sent to Google to help the player’s coaches: for a summary of those notes that only the player’s coaches see, and for the development review and check-in drafts a coach asks for. They are sent marked as coming from a guest coach of the team named for them, with the date. TeamArc doesn’t add the guest coach’s name to what is sent. A guest coach’s notes are not used for the AI-drafted summary a coach shares with a family; what a guest coach saw reaches that summary only through what the player’s own coach writes. Guest coaches aren’t offered AI drafts; a guest coach’s shout-out is written by the guest coach.

5. Who sees what

  • Coaches’ notes are private to the team’s head coaches; a guest coach can also read the notes they wrote themselves, as described below. Team managers and club administrators never see them. Coaches also see the family contact details for their team, each player’s RSVPs with any reason given and who answered (a family member or the player), the attendance they mark, and goals and suggestions players and families submit.
  • A family member sees only what the coach has shared about their own player (updates, shout-outs, shared check-ins, a shared development plan, an approved summary) and the team schedule and announcements. They see the goal their player set, any goal a coach suggested for their player, and the RSVPs their player gives. They never see anything about another family’s child, except the team RSVP list and the RSVP totals below.
  • Coach and team manager contact details. Where TeamArc has made this available for a team, signed-in family members on that team see the name, role and email address of each coach, or instead a separate email address a coach gives for that team’s families, and of each team manager who has agreed to this in the app. A coach’s or team manager’s phone number is shown only if that person turns it on for that team. Players, private family links and calendar links never show them. Tapping an email address or number opens the family member’s own mail, phone or messaging app; TeamArc doesn’t send, carry or see those messages.
  • Shared development plan. Where TeamArc has made this available for a team, a coach can choose to share what a player is working on with that player’s family: the focus area, the current focus, what progress looks like and the goal, in the coach’s own saved words. The family sees the version the coach last shared, marked with the coach’s name and the date; later edits stay private until the coach shares again. It never includes scores or ratings. If the coach stops sharing it, it disappears from the family’s view the next time they open TeamArc.
  • Team RSVP list. Where TeamArc has made this available for a team and the coach turns it on, families and players on that team can see each player’s RSVP status (not reasons) for team events. The list shows each player’s first name and last initial with their answer (yes, no, maybe or not answered yet), and the coaches’ own answers. It never shows reasons, which family member answered, contact details, or anything from a tryout, and players who have left the team aren’t listed. Each team’s coach decides whether the list is shown: it starts on for teams created on or after September 28, 2026, and off for earlier teams until a coach turns it on. RSVP reasons are seen only by the team’s coaches. Within a household, family members can see who in their household answered. The list is never included in calendar links, exports or AI.
  • RSVP totals. Where TeamArc has made this available for a team, signed-in family members and signed-in players can see, for their own team’s events, how many players on that team said yes, no or maybe. These are numbers only, never names or reasons. On a small team a number can make another family’s answer easy to work out, so totals aren’t shown for a team with fewer than five players. Totals aren’t shown on a private family link or in calendar links.
  • A player who has their own sign-in sees only their own shared updates, shout-outs, approved summary, goal and development plan (and check-ins the coach shares with them), plus the team schedule and announcements and, where they’re on, the team RSVP list and RSVP totals. A player 13 or older can answer their own RSVPs, set and change their own goal, and answer a goal a coach suggests, if their team has this turned on. A goal a coach suggests to a player is always shown on the family’s page too. Their family members see the goal and can add suggestions. A parent or guardian’s answer replaces the player’s. Coaches and the player’s family members see who answered.
  • A tryout evaluator sees only that one tryout: its players, notes, labels and summaries, never the player they name as their own child and never any family’s contact details, and only until the tryout ends (section 13).
  • Team managers. Where TeamArc has made this available for a team, its head coach can invite a team manager for that one team. A team manager sees the players’ first and last names and jersey numbers, the team schedule, each player’s RSVP answer (never a reason or who answered), the team’s announcements and, unless the head coach turns it off, the names, email addresses and phone numbers of the players’ adult family members, never a player’s own contact details. A team manager can add, change and cancel events, send team announcements, team emails and texts (section 7), add and edit players, add and edit family members’ contact details and send family invites (while they can see contact details), remove a player from the team, and mark attendance if the head coach turns that on. A team manager never sees the coaches’ notes or anything drawn from them, the practice plan, AI drafts, summaries, goals, development plans, check-ins, shout-outs or updates, RSVP reasons, or anything from a tryout. When a team manager is added, every family on the team is told in the app, by name, and whether the manager can see their contact details. The head coach can remove a team manager at any time.
  • Club administrators. Where TeamArc has made this available for a club, the club can have club administrators, whom we invite at the club’s request. For that club only, a club administrator sees each season team’s name, season and head coaches’ names, each current player’s first and last name, jersey number and team, and each player’s adult family members: name, relationship, email address, phone number, whether they’ve been invited or have signed in, and whether text alerts are on. A club administrator can send announcements, team emails and texts to the teams they choose (section 7), resend a family member’s existing invite, and tap to email or call a family member from their own phone. A club administrator never sees the coaches’ notes or anything drawn from them, AI drafts, goals, development plans, check-ins, shout-outs, updates, RSVP answers or reasons, attendance, anything from a tryout, a family link, or a player’s own contact details, and TeamArc gives them no export of the list. When a club turns this on, its families are told in the app that the club’s administrators can see their name and contact details.
  • Volunteer jobs. Where TeamArc has made this available for a team, the coach or a team manager the coach invites can add jobs to team events or for the whole season, and give a job to an adult family member on the team. A signed-in family member can take an open job on their own player’s team, or give back their own. Other signed-in families on the team see who holds a job as that adult’s first name and last initial, never a child’s name. The coach sees the holder’s full name. A private family link shows no jobs.
  • Guest coaches. Where TeamArc has made this available for a team, a coach can ask to share a player’s shared record with a guest coach from another team for up to 30 days. Nothing is shown until a signed-in parent or guardian of that player approves. The guest coach then sees only these things the family already sees about that player: the approved summary, the current goal, a shared development plan, updates and shout-outs. They also see a short note the player’s coach writes about that player for the guest spell, which that player’s family sees too and no other family does. The guest coach does not see the coaches’ private notes, contact details, the schedule, teammates or RSVPs. The guest coach can write their own notes about the player, up to a limit we set. Those notes are read by the player’s coaches, marked with the guest coach’s name and team, and the coaches can draw on them in what they share with the family (section 4 says how AI is used with them). The guest coach can send the family a shout-out; it is shown to signed-in family members only, not to the player and not on a private family link, and the player’s coach sees it too. A player with their own sign-in is told who their guest coach is and until when. A parent or guardian or the player’s coach can end the guest spell at any time, and the family can see who has access and until when. Ending it can’t recall what the guest coach has already seen.
  • Some families open their page with a private family link instead of a sign-in. Anyone holding that link can see that family’s page, including the contact details the family has given, and can do what the page allows: answer RSVPs, submit or suggest a goal, answer a goal a coach suggested, correct the family’s contact details, turn on notifications for their device, and turn text alerts off. So keep it private. A family link can’t change or fill in the email address of a family member who signs in, has an invite waiting, or is marked a parent or guardian. Where a club requires a parent or guardian for goals, a family link can suggest a goal but not set one or answer a coach’s suggestion. Text alerts can be turned on only by a signed-in family member. A goal submitted through a family link is recorded as coming from a parent or guardian.
  • The team schedule can be added to a calendar app through a private link, which coaches and family members are offered in the app. Anyone holding that link can see the schedule (times, places, opponents and practice themes, never the coach’s notes or RSVPs). If a family or calendar link has spread further than it should, write to us and we’ll replace it.
  • Semperity staff can see team information only as described in section 11.

6. Children

TeamArc is used by coaches and the families they invite. Information about players, who are often minors, is entered by their coach for team and development purposes. Player sign-ins are available only by invitation from us, at the coach’s request, and only for players a parent or guardian confirms to us in writing are 13 or older. We don’t knowingly give a sign-in to anyone under 13. Apart from what’s needed to keep them signed in, and error reports that aren’t tied to them (section 2), the only information we collect from a player through their own sign-in is their RSVP answers, their goal, and their answer to a goal a coach suggests, where their team has this turned on (section 2). A parent or guardian can ask to review their child’s information, have it corrected or deleted, or stop further collection, by contacting the coach or writing to privacy@getteamarc.com. We don’t use children’s information for advertising, and we don’t sell it. We never send product emails to players.

If Apple tells us whether the person using a device is an adult or which age range they’re in (in some states it does), we use that only to apply age rules in the app (for example, coach, team manager, club administrator, evaluator, guest coach and family accounts are for adults), and we don’t keep it or share it.

7. Messages

Service messages. We send email for sign-in, sign-up and tryout-join codes, invitations and family links, and team messages a coach, team manager or club administrator chooses to send by email. We send push notifications, to devices that turn them on, for things a coach shares, and for team announcements and schedule changes. A notification can show the start of what was shared or announced on the phone’s lock screen. Where they’re on for a team, we also send a coach’s reminder to families who haven’t answered an RSVP yet, an after-practice reminder to a coach who turns it on, and, on the same devices, a notice to a head coach when a family member or a player sets or changes a goal. That notice has the player’s first name and never the goal’s words. Where volunteer jobs are on for a team, the adult family member holding a job on a team event gets a reminder the day before, only on the devices they turned notifications on for while signed in, never on the rest of the household’s phones. Where guest coaches are available, a signed-in family member whose device has notifications on can get a notice when a guest coach shares a shout-out; that notice doesn’t include its words. These messages are part of how TeamArc works; saying no to product emails doesn’t stop them.

Messages from a team manager or club administrator. Where TeamArc has made these roles available, team announcements, team emails and texts can also come from the team’s manager or from a club administrator. A club administrator’s are labelled with the club’s name and their own name. A team manager’s are shown with the manager’s name, to the families who get them and to the team’s head coach, and families are also told by name when a team manager is added (section 5). They go to the whole team, never one-to-one to a player, and texts go only to adult family members who turned text alerts on.

Trial reminders. If you start a team yourself, we may email the team’s coaches twice during its trial period: when 5 days are left and on the last day. These emails never go to families or players, and they never include a player’s name or anything from a note; they may say how many notes you’ve saved. Each one has a link to stop trial reminders, and replies go to sales@getteamarc.com. We keep a record of which reminders we sent and when, without the email’s words or your email address.

Product emails. When you join a tryout as an evaluator, you’ll see a box beside the words “Send me up to 3 emails about using TeamArc for my own team.” The box starts ticked only if your phone’s region is the United States, and it is never shown to anyone who tells us their child is in the tryout. We don’t send product emails today. If we start, we’ll send at most 3, only about coaching with TeamArc, only to evaluators whose email address was confirmed and who left the box ticked, unless they untick it or unsubscribe. Every product email will have a one-click unsubscribe link and our mailing address, and we won’t track whether you open them. We never send product emails to family members or players, or to an email address we collected before September 28, 2026. We don’t send product emails to guest coaches.

Tryout offers. If TeamArc sending is turned on and a club emails a tryout offer through TeamArc, we send it to the player’s parent or guardian. A player 14 or older may be copied on the same email, but only alongside a parent or guardian, never on their own; a player 13 or younger is never emailed. The offer is written by the coach and club and says so, replies go to the coach, and the email says how to stop getting emails like it. It never includes tryout notes, labels or summaries. A coach can also send an offer from their own phone, in which case it’s their message, not ours.

Tryout feedback. A head coach can write a short note to the parent or guardian of a tryout or trial player and email it through TeamArc. The words are the coach’s own. TeamArc doesn’t write them and adds nothing from tryout notes, labels or summaries. It goes only when the coach sends it, to one parent or guardian address the coach holds for that player, never to the player, and no more than once in 7 days for a player. It says who wrote it, replies go to the coach, and it says how to ask the coach to stop. A coach can also send the note from their own phone, in which case it’s their message, not ours.

Text messages. If a family member turns on text alerts, we text them the team announcements a coach, team manager or club administrator chooses to also send by text, only to the number they gave and only after they agreed in the app, and at most 5 a month for each team. We never text players. A tryout family member’s phone number, if the coach adds one, is used only by the coach; TeamArc does not send texts to it. Reply STOP to opt out or HELP for help; message and data rates may apply. We never sell or share phone numbers or messaging consent for marketing.

8. Service providers

We use these providers to run TeamArc, and share only what each needs: Neon (database), Railway (servers), Vercel and Cloudflare (web hosting), Google (Gemini AI processing, and our own email), Resend (email delivery), Apple (app delivery, and payment for any purchase made in the app through the App Store; Apple’s own privacy policy covers the payment details you give Apple), Apple and Expo (app updates and push notifications), and Twilio (text messages, for family members who turn on text alerts). Our database is in the United States; some providers may process information elsewhere.

9. What we don’t do

We don’t sell personal information. We don’t show ads. We don’t track you across other apps or websites: the app contains no advertising, analytics or third-party crash-reporting code (its error reports go only to TeamArc, section 2), and this website uses no cookies, analytics or third-party scripts. The page a family invitation link opens on this website reads the invitation code on your own device; the code isn’t sent to our website. We do count how teams use TeamArc from the records we already keep (for example, how many notes a team has added) to support coaches and improve TeamArc.

10. Keeping and deleting information

TeamArc is built to remember a player’s development over time, so we keep information while the team uses TeamArc, and after that until a coach, parent or guardian asks us to delete it. When a coach edits a note, the earlier version is kept so changes can be undone; when a coach removes a note or a player, it is archived (hidden) rather than erased. If a trial or plan ends without a new purchase, nothing is deleted or hidden. Error reports (section 2) are deleted 30 days after we receive them.

A coach can delete their account in the app (Settings → Delete account). Their sign-ins end on every device, and their name, email and phone number are removed from their account on every team they coach. The notes they wrote stay with the players’ records. If they were a team’s only coach, that team is archived. A team manager or club administrator can delete their account in the app the same way. Their sign-ins end and their name, email and phone number are removed. The announcements, team emails and texts they sent stay with the team, without their name. Copies of their email address can remain in our records of emails sent and in our record of their acceptance of our Terms; write to us if you want those removed too, and we’ll remove what the law lets us. Our trial record (section 2) also stays after an account is deleted, for up to 24 months after the trial period ends, so that a new account with the same email address continues the same trial period. It contains no name and no readable email address.

A coach who coaches more than one team can move their own note to another of their teams. It then belongs to that team only, and anything made from it on the first team is removed. A note already shared with a family can’t be moved. We keep a record that a note was moved, without the note’s words.

Where guest coaches are available, a guest coach’s notes and shout-outs are part of the player’s record on the player’s own team. The guest coach can read their own notes until 30 days after the guest spell ends. A guest coach can delete their account in the app; their sign-ins end, and their name and email are removed from their account and from the list of guest spells the player’s coaches see, which then shows “Guest coach” and the team named at the time. The notes and shout-outs they wrote stay with the player’s record, marked the same way. The family’s record of who had access to their player, and when, keeps the guest coach’s name and email address, and the count of guest days described in section 11 still includes that guest spell. If a guest coach also coaches a team of their own in TeamArc, that account stays until they delete it there; deleting it also ends their guest access. The player’s coaches can hide a guest coach’s note or take back a guest coach’s shout-out. A parent or guardian can ask to see a guest coach’s notes about their child, and they are deleted with the rest of the player’s record if a parent or guardian asks us to delete it.

Family members can delete their account in the app (Settings → Delete account). Their sign-ins end on every device; their name, email and phone number are removed; text alerts to their number are turned off and the number is kept only on our do-not-text list; they stop seeing their player’s updates. Their player’s record with the coach, and other family members’ access, are not affected. A player with their own sign-in can delete it in the app the same way; the coach’s record of the player stays with the team. A tryout evaluator can delete their tryout account in the app. Anyone can also ask us at privacy@getteamarc.com.

When a parent, guardian or coach asks us to delete information, we check the request comes from them, delete it within 30 days, and confirm by email, except where the law requires us to keep it. Records of purchases and invoices are kept for tax and accounting as the law requires. We keep a short record that an account was deleted and when (without the name, email or phone number). Deleted information may remain in our database provider’s backups for a short time until they expire.

11. Security

Information is encrypted in transit. Each club’s information is kept separate, and every request is checked against the account it belongs to. Where guest coaches are available, to limit how much guest access one adult can hold, we count a guest coach’s guest days across teams. That is a number only; no team sees another team’s information. Sign-in codes, tryout join codes and app sign-in tokens are stored only in scrambled (hashed) form. If you lose a phone that is signed in, email support@getteamarc.com and we’ll sign that device out. We (Semperity’s staff) access team information only to run and support TeamArc, or when the law requires it. No system is perfectly secure; if a security incident affects your information, we’ll tell you as the law requires.

12. Your rights and changes

You can ask to see, correct or delete your information, or for a copy of it, by writing to privacy@getteamarc.com; we reply within 30 days. If we change this policy, we’ll post the new version here with a new version date and keep earlier versions available. If the change matters, we’ll email coaches about 14 days before it takes effect, and we won’t use information already collected in a new way that needs consent without asking for it first.

13. Tryouts

A coach can record players at a tryout by number or name. Tryout notes, and the short summaries TeamArc can make from them using Google’s Gemini API (section 4), are seen only by that tryout’s coaches and evaluators. When making a summary, players are identified to Google by number, not name. Summaries never score or rank children. Tryout notes and summaries are never shown to families or players, and we never use them to train AI models. The coach’s original notes are always kept alongside any summary. When a player joins a team from the tryout, the tryout notes move with them to that team’s coaches; tryout labels and decisions stay with the tryout and never follow a player onto a team.

Evaluators. A host club can invite other adults to help evaluate one tryout with a join code. An evaluator’s access ends when the club wraps up the tryout, when the tryout’s dates end, or when the club removes them, whichever comes first. Everything an evaluator adds stays with the host club’s tryout: it doesn’t go with them if they leave, or if they later start a team of their own. An evaluator who is a parent or guardian of a player in the tryout never sees the record of the player they name as their child (by bib number or name), and their notes can never be put on that player.

Offers. A club may make a player an offer to join a team. The offer is from the club, not from Semperity, and never includes tryout notes, labels or summaries. We keep a record of the offer, the text it was prepared with, and, if it was emailed through TeamArc (section 7), to whom it was sent, so a parent or guardian can ask to see it.

Feedback. A note a coach sends a parent or guardian after a tryout, by email through TeamArc or from their own phone, is from the coach and the club, not from Semperity. We keep it with the tryout record and it is archived with that record.

Players who don’t join a team are archived 30 days after the tryout, or 30 days after an offer to them is answered or expires, whichever is later. A parent or guardian can still ask to see, correct or delete this information, including notes, decisions, offers, feedback and summaries (section 6).