LineUp Privacy Policy

What we collect

• Your account. Your name, email address, date of birth, gender and country, and, for an account made with email, a password (stored only as a secure hash, never as the password itself). If you sign up with Apple or Google, they give us your name and email, the app asks you for date of birth, gender and country, and the account has no password: you sign in with the same button. You can add one later with Forgot password, which also lets you sign in by email if you stop using that provider. Date of birth is collected to confirm account holders are 16 or over, and an account cannot create or join a team until it has been given.
• Your identity within a team. The name and relation you give when you join a team, for example "Sam Taylor, Parent". This is per team, so joining a second team does not rename you on the first.
• Team information. The team name, region, sport, game format, season end, team colour and logo, schedule of games and trainings, venues and their map coordinates, notes, scores, awards, goals scored, and playing-time records, entered by the team's manager.
• Player information. Player names, and optionally shirt numbers and playing positions, entered by the manager or a parent. Players are usually children; see the section on children below.
• Availability. RSVP responses (in or out) for games and trainings, and who they were made by.
• Team chat. The messages, announcements and replies you post in your team's room, with your name and the time. Also the time you accepted the chat house rules, when you last read the room, the people you have blocked, and any report you make (the reason, what you wrote, and a copy of the reported message).
• Nudges. When a manager asks the families who have not replied about a game, we record which child, which game, which guardian was asked and when, so the same family is not asked again for 24 hours.
• Notifications. If you allow notifications, we store a push token for that device so we can send your team's reminders and messages to it, plus your per-team settings: game and training reminders, chat message notifications, and quiet hours. We also keep a copy of each notification sent to you (apart from chat messages) for 30 days, so the app's notification list is the same on every device you sign in on.

What we do not collect

• No advertising inside the app, and no tracking of you across other apps or websites.
• One measurement tool and nothing else: Google Analytics for Firebase records that the app was opened and that a sign-up was completed. It uses a random app-instance id, and on Android the device's Advertising ID, so we can tell whether our own Google Play adverts bring in people who go on to use the app. It never receives your name, email address, team or any child's name. On Android you can reset or delete the Advertising ID under Settings, Privacy, Ads. No sale or sharing of personal information with data brokers.
• No precise device location. The app never asks for location permission. Venue maps are static images of the address the manager typed in.
• No access to your contacts, microphone or camera. The only use of your photos is a manager choosing a team logo through the device's own photo picker; the app receives the one image chosen and nothing else.
• No reading of your calendar. Adding a game to your calendar opens your device's own "new event" screen with the details filled in; you save it, and the app never sees your calendar.
• No photos, videos or voice in team chat. The room is text only.

Children

LineUp accounts are held by people aged 16 or over: managers and parents or guardians, and occasionally a player-manager or older sibling. Children do not create accounts and cannot sign in. Player names are added by the adults running the team so that lineups and availability make sense, the same information that would otherwise sit on a paper team sheet.

A player's information is visible to the members of that team and to nobody else. Linking yourself to a child who is already on a roster is a request the team's manager has to approve, so holding an invite link is not enough to become listed as a child's guardian.

Team chat is for the adults around a team, every message carries the sender's name, and the house rules ask members not to post more about a child than the team needs. Any report that raises a child-safety concern is treated as urgent, and we cooperate with the Police and other authorities on it.

Notifications

If you turn notifications on, LineUp sends your team's reminders the evening before a game or training, a short summary when a game finishes, a note when a game is added, moved or cancelled, and your team's chat messages. A chat notification shows the sender's name and the text of the message, and a full-time summary can include a player's first and last name, for example when a player of the day has been picked; like any notification these may appear on your lock screen. A nudge from your manager names your child and the game ("Is Mia playing?") and opens the reply buttons when tapped.

You can turn game and training reminders and chat message notifications off per team in Settings. Quiet hours are on by default: chat notifications are held between 9pm and 7am New Zealand time and arrive as one summary at 7am. On Android, chat has its own notification channel, so you can silence chat in your phone's settings and keep the game reminders. You can turn notifications off entirely for the app in your device's settings.

Signing out unregisters that device. If that fails, because there is no signal or the app is closed straight afterwards, the app retries the next time it is opened, and any device that has not checked in for 60 days is dropped automatically.

Data stored on your device

So the app still works without a signal, it keeps a copy of your current team's data on the device: the roster including players' names, the schedule, RSVPs and attendance. It is held in the app's own storage, protected by the operating system's app sandbox, and is kept for at most seven days from the last time the app heard from our server, after which it is deleted. It never contains your password or your sign-in token, and the app cannot sign you in from it. Chat messages are never stored on the device; they are fetched from our server each time the room is opened. Signing out, leaving a team or deleting the app removes the copy.

Your sign-in token and any invite code you hold are stored separately, in the device keychain on iOS or the equivalent encrypted store on Android.

Who processes your information

We do not sell or share your information for advertising. The one measurement signal we share with Google is described below. We use these providers to run the service, and each one only receives what that function needs:

• Cloudflare (Workers, D1, R2). Hosting, the database and team logo storage. All team, chat and account data is stored here.
• Resend. Sends the verification, sign-in and password-reset emails, and carries chat reports to us. For a code it receives your email address and the code being sent; for a report it receives the report's reason, what the reporter wrote, the reported message, and the two names as they appear in the team.
• Expo (Expo Application Services). Delivers push notifications to Apple and Google on our behalf. Receives your device's push token and the contents of the notification, which can include a player's name or the text of a chat message.
• Apple and Google. Deliver the notification to your device. Apple and Google also verify your identity if you use Sign in with Apple or Sign in with Google.
• Google Maps. Draws the static map image of a venue. Receives the venue address or its coordinates.
• Google Analytics for Firebase. Counts app opens and completed sign-ups so we can measure our own Google Play adverts. Receives a random app-instance id, the device model and operating system version, the app version, and on Android the Advertising ID. Receives no name, email address, team or player information.
• Komoot (Photon). Suggests addresses while a manager types a venue. Receives what is typed into that field.

Who can see what

Team data is visible only to that team's members: people who joined with the team's invite link. Managers can edit everything in their team, and can see playing-time and fairness figures for the whole squad, which families have replied to each game, and which families have no app notifications. Parents can see the team's schedule, roster and results, and can set availability only for the children they are the approved guardian of. Nothing is public.

Chat messages are visible to the members of that team, and to us when a message or a person is reported. A message you delete, or a manager deletes, shows as removed to the rest of the room. Blocking someone hides their messages from you only; they are not told. Reports are seen by LineUp alone, never by the person reported or the rest of the team.

How long we keep it

• Team data is kept while the team exists. Deleting the team permanently removes the team and everything in it: players, schedule, availability, results, awards, playing-time records and chat messages.
• Removing a player hides them, it does not erase them. When a manager removes a player, that player disappears from the roster, from availability and from every screen in the app straight away. Their name and their past record stay in the database so that finished games, results and playing-time history from before they left remain correct. That information is deleted when the team is deleted. If you want a specific child's record erased sooner, email us and we will do it.
• Chat messages are deleted 30 days after the team's season ends (or after 400 days for a team that has never set a season end), and sooner if the team is deleted.
• Nudges are deleted seven days after the game they were about, or when the game is moved or removed.
• Reports are kept for a year after they are resolved, so that a pattern of behaviour can be seen, then deleted. A report outlives the message, the team and the accounts involved.
• Notifications in the app's list are deleted after 30 days.
• Sign-in codes and unfinished signups, which hold an email address, are deleted automatically the day after they expire.
• Expired invite links are deleted automatically. We only ever store a one-way hash of an invite code, never the code itself.
• Push tokens are deleted when you sign out, when you leave the team, when you reset your password, or after 60 days without the app checking in.

Deleting your account

You can delete your account inside the app: Settings, then Delete account. This permanently removes your account, your sign-in identities, your per-team identity, your personal links to players, your blocks and your nudges. Messages you posted stay in the team's room for the rest of the season, shown as from a former member, so the conversation still makes sense to the team; they are deleted on the room's normal schedule. A report you made keeps its content but no longer records that you made it. If you are the only manager of a team, either make someone else a co-manager first or delete the team (Team settings, then Delete team), so a team is never left unmanaged.

This page

This page sets no cookies, runs no analytics, and does not track you.

Security

Traffic between the app and our server is encrypted in transit. Passwords are stored only as salted hashes with a high work factor, never in a recoverable form. Invite codes and email codes are stored only as hashes. Resetting your password signs out every other device and stops notifications going to them.

Your rights

Under the New Zealand Privacy Act 2020 you can ask for a copy of the personal information we hold about you, ask us to correct it, and ask us to delete it. Email us and we will sort it out. If you are somewhere with additional rights, for example the GDPR in the EU or the UK, those apply too.

Contact

Questions about privacy, a request about your information, or a concern about something in a team chat: [email protected]

Changes

If this policy changes in a way that matters, we will note it in the app's release notes and update the date at the top of this page.