Home Team — Privacy Policy

Effective date: November 6, 2026
Who we are: Home Team is operated by Front Porch Apps LLC. In this policy, "we" and "us" mean Front Porch Apps LLC.
Contact: support@gethometeam.app · 13110 Birch Dr Ste 148 PMB 169, Omaha, NE 68164

Home Team is a phone app that puts your kids' game and practice schedules in one place and tells you when it's time to leave. It's on iPhone first, and Android is coming. Where the Android version works differently, the Android section says how. This page explains, in plain language, what information the app uses, where it goes, and how to remove it.

Early-access waitlist: If you join the early-access list on gethometeam.app, we collect your email and any optional profile answers (how many kids play sports, how many team apps you use, which apps, and your city and state). We also note how you found us: the page you first landed on, a friend's referral code if you used one, any campaign tags in the link, and which form you used (the early-access list or the grandparents guide). This website keeps those in your browser until you sign up, or until 30 days after your last visit from a tagged link. We also make a referral code for your own invite link, and note whether and when you asked for updates. We store all of this with our email provider, Resend, and each signup and profile answer is also emailed to our support inbox (support@gethometeam.app, hosted on Google Workspace). We use it only for Home Team early access and launch: to email you, and to see which links and flyers bring people in. If you check the optional updates box, we also send occasional Home Team updates (about once a month). To stop getting emails, reply to any waitlist email or write to us, any time. To delete your waitlist info, email support@gethometeam.app. This website is hosted on Vercel too: your sign-up and profile answers pass through its servers, and Vercel's basic request logs (such as IP address, time and the page requested, including the link from your confirmation email) are kept for 1 day, as for the app's server.

Website analytics: This website (not the app) uses Vercel Web Analytics to count visits. It uses no third-party cookies. For each page view it records the time, the page address, the referring site, approximate location (country, region and city), and the browser, operating system and device type. Visitors are counted using a hash of the request that is discarded after 24 hours, and nothing is tied to an IP address. We remove the code in sign-up links from page addresses before they're sent, so Vercel Web Analytics never receives your email address.

The short version

No account. You never sign up, log in, or give us an email address or phone number. The early-access waitlist on this website is separate; see Early-access waitlist.
No ads, no tracking. We use anonymous counts, like how many families finished setup or visited our site, to improve Home Team. They're never linked to you.
Your team calendars' schedules stay on your phone. Games and practices from your team calendars, your alarms and your settings are stored only on your device. Games and practices you add by hand are stored with your household so a co-parent or guest you add sees them too.
One subscription covers your Home Team. Your phone gets a household on our server, identified by random IDs rather than your name or your Apple or Google account. Your app store (Apple, or Google Play on Android) handles payment, and we never see your card details.
Your family setup is stored with your household. Your kids' first names, calendar links, pinned venues, your home address, and "who's driving" updates are stored on our server so a co-parent or guest you add sees the same schedule. Guests never receive your home address.

What stays on your phone only

These are stored in the app's private storage on your device and are not sent to us:

Your schedule (games and practices pulled from your team calendars).
Your preferences (e.g. Apple Maps vs Google Maps, alarm voice, filters, which kids you're viewing).
Leave alarms, reminders and "Time to go" alerts, and the Lock Screen countdown. These are created on the phone itself.
Your work address, and where you're leaving from for each game, including a "From here" location reading.
Anything you copy. The app can tell that a link was copied without reading it; it reads the copied text only when you tap Paste, and only to add that team or open that invite.

What leaves your phone, and why

1. Your team calendar providers

To show your schedule, your phone downloads the calendar links (ICS/webcal feeds) you add, directly from the provider that issued them — for example GameChanger, TeamSnap, SportsEngine, or Bound. For Bound events that lack a street address, the phone may also open the public Bound (gobound.com) event page to read the venue address. These requests come from your phone; the provider sees an ordinary web request (including your IP address). Their own privacy policies apply.

2. Your household and linking

The first time the app can reach our server, it creates a household for your phone. At first the household is just your phone, identified by a random ID and a secret key (below). Your subscription or free trial belongs to this household (see Subscriptions and purchases). Linking with a co-parent is optional. Your household's details are sent to and stored on our server as follows:

A random ID for your phone created by the app (not your Apple ID, phone number, or advertising ID), the household's short link code, and a secret key for your phone that proves it belongs to the household (we store only a scrambled, one-way copy of it).
Your role in the household (owner, parent or guest), which decides who can change the family setup.
The name you enter for "This phone" (e.g. "Mom"), so your co-parent sees who is who.
A push notification token, so the server can notify the other phones.
"Who's driving" updates: when you tap I'm driving on a game, the game's title and start time, and the name of the person driving.
Your family setup: your kids' first names, your team names and calendar links (these links can be private to your team), your color and leave-time settings, venues you've pinned (map coordinates and address text), and field-map links.
Games and practices you add by hand: the title, time, location (address text and map coordinates), opponent, notes, which kid it's for, and which household member last changed it.
Your household's home address and its map coordinates, so a co-parent's phone can work out when to leave without typing it again. A phone where someone typed a different address keeps its own. Guests (e.g. grandparents) never receive it.

Why: so every phone in your Home Team shows the same kids, teams and pinned venues, and so your co-parent gets a notification when you say you're driving to a game.

Linking by text message: "Text the link" sends your household's link code inside a web link. Anyone with that link or code can join your Home Team as a parent, so send it only to your co-parent.

Note on pinned venues: if you tap Pin the venue while you're there and allow location access, the app uses your phone's current location once to pin it. That pin (coordinates and address) is saved with your household's setup like any other pinned venue.

3. Push notifications (only if you've linked a co-parent or added guests)

To notify the other phones, our server sends the notification text (e.g. "Alex is driving · Soccer vs Northside"), plus the game details listed above, through Expo's push notification service, which delivers it via Apple Push Notification service on iPhone, or Google's Firebase Cloud Messaging on Android.

4. Maps, addresses and drive time

This is how it works on iPhone. Android differs; see Android.

Turning addresses into map points: the app uses Apple's built-in geocoding on your iPhone, which sends the address text (for example, your home address or a venue address) to Apple to look up coordinates.
Address search when you edit a game: typing a location sends your search text to Apple's built-in geocoding to suggest matching places. It isn't stored and never reaches our server.
Drive time: to work out when you need to leave, your phone asks Apple Maps for the driving time from where you're leaving (home, work, a place you type, or where you are when you tap "From here") to the venue, which sends both locations to Apple. If Apple can't answer, the phone estimates from straight-line distance. This never goes through our server.
Directions: tapping directions opens Apple Maps or Google Maps with the venue as the destination. Those apps' own privacy policies apply.

5. Weather

For games with a known venue location, the app sends the venue's coordinates and the game's start time to our server, which asks Apple WeatherKit for the forecast for that hour. Only the venue location and game time are sent to Apple, never your location, your home address, or anything that identifies you. Our server keeps each forecast for a short time (under an hour for games in the next 3 days, up to 6 hours for games further out) so families at the same venue share one lookup, and doesn't log the coordinates or times. Weather data is provided by Apple Weather.

6. Team invites and sharing a team

There are two ways to send a team from Home Team. Either way, the app sends that team's calendar link, its name, type (e.g. TeamSnap), color and sport to our server once, and our server gives back a short Home Team link, which is what you send. The people you send it to never see your team's real calendar link: their phones get the schedule from our server, which fetches it from the team's calendar provider at most every 15 minutes on their behalf and keeps the latest copy. When you save a new calendar link for the team, everyone's copy updates.

Invite (for other families on the team) gives a team link that adds the team's schedule for whoever opens it. Anyone who has a team invite link can add that team's schedule, so send it only to families on the team. Our server keeps a team invite while families are using it, and deletes it about 400 days after it was last created, updated or used. Its saved schedule copy is deleted 30 days after it was last refreshed.
Share (for fans, such as a grandparent) gives a view-only copy of the team, and each share link works for one family only: the first family to open it in Home Team gets the team, and anyone else who tries the same link is turned away. Along with the team details above, a share stores the first name of your kid on that team and your name if you choose to include them, so the recipient sees whose team it is, plus, once it's used, the name the recipient entered and when. You can see your shares in the app and stop sharing at any time; the recipient's copy then stops updating, and the app tells them so they can remove it. A share link nobody has used stops working after 30 days. Shared teams can't be shared again by the person you sent them to, and guests can't share teams.
The link carries only a short code. The code sits in the part of the link after the #, which web browsers never send to a server, so it doesn't reach our server's request logs. Share links made by older versions of the app (which carried the team's details inside the link) no longer work; the app asks the sender for a new one.

7. Crash reports and diagnostics

The app sends crash and error reports (device model, operating system version, app version, error type), with names, places, links and IDs removed, so we can find and fix bugs.

When the app or our server crashes or hits an error, a diagnostic report is sent to our error-monitoring provider, Sentry. We configure it to strip personal details — game titles, locations, names and calendar links are removed before sending. Reports include technical details such as device model, operating system version, app version and the error itself. Reports don't include your name, a user ID, a device ID or your IP address. They're stored by Sentry in the United States and deleted within 90 days.

8. Subscriptions and purchases

Home Team is a subscription, one per household, with a 14-day free trial for new households. Friends-and-family offer codes work the same way.

Apple processes the payment on iPhone. You buy, cancel and manage the subscription through your Apple Account and the App Store. We never see your card or payment details, your Apple ID, or your billing name or address. Apple's privacy policy applies to the payment.
RevenueCat is the subscription service we use to check purchases. It receives the purchase and subscription status from the app store (Apple, or Google Play on Android) and the app: which plan, purchase and renewal dates, trial or paid, and store transaction IDs. It also receives basic technical details such as app version, country, currency and language. All of this is keyed to your household ID, not your name. RevenueCat also uses these records to give us subscription and revenue reports. RevenueCat's privacy policy applies to what it processes for us.
Our server asks RevenueCat for your household's status and stores a small record: plan, status (trial, active, grace period or expired), expiry date, and whether the household has already used its free trial. Every phone in the household, guests included, sees the household's access status.

9. Guest invites

A parent in the household can invite a relative, such as a grandparent, as a guest (up to 4 per household). Creating an invite makes a one-time code that expires after 7 days. The code travels in the part of the link after the #, so it never reaches our server's request logs. Our server keeps the code only until it's used, revoked or expires. When a guest accepts, the guest phone's random ID and the name they enter join the household, along with its push token if they allow notifications and whether they said they sometimes drive. The guest can then see the family schedule setup and "who's driving" updates, and, if they drive, say they're driving. Guests can't change the family setup or invite others, never receive your home address, and never pay. The household's subscription covers them.

10. Invite pages and app links

Invite, link and share pages on gethometeam.app are plain web pages. If you don't have the app yet, Get Home Team copies the invite link to your phone's clipboard before opening the download page (Apple's TestFlight during early access, the App Store after launch), so the app can offer to paste it when you first open it. Nothing about you is stored when you open these pages. Printed QR codes point to gethometeam.app/get, which sends iPhones and computers to the same download page, Android phones to our Android page (Google Play once it's available), and adds to a running count for the banner or flyer that was scanned (a label in the link). It never records who scanned it or anything about their device.

11. Hosting and storage

Our server runs on Vercel, and household data is stored in a Vercel KV / Upstash Redis database. Both run in the United States (the Washington, D.C. area). Like most web services, our hosting provider automatically records basic request logs (such as IP address, time and the page requested). Vercel keeps these request logs for 1 day on our plan.

Android

Home Team for Android is coming. It works like the iPhone app, with these differences:

Notifications: the other phones' notifications are delivered by Expo's push service through Google's Firebase Cloud Messaging instead of Apple's service. The same notification text and game details are sent.
Notification and alarm permissions: Android asks whether Home Team may send notifications. Leave alarms use Android's alarm permission (shown in Android Settings as Alarms & reminders) so they ring on time, can show over the lock screen, and are set again after the phone restarts. Alarms are created on the phone and nothing about them is sent to us.
Location: Android needs location access to look up addresses, so the app asks once, before your first schedule sync, for access while the app is open. The app never asks for background location. If you say no, drive times aren't shown and the app tells you how to turn location on.
Addresses: turning addresses into map points, and the address search when you edit a game, use your phone's built-in Android geocoding service (provided by Google on most phones), which receives the address or search text.
Drive time: there's no Apple Maps on Android. Your phone estimates the drive from the straight-line distance, and every drive time and leave-by time is labelled (estimate). This is worked out on the phone and isn't sent anywhere. Hotel and named-place search aren't offered on Android.
Directions: tapping directions opens Google Maps (the app, or Google Maps on the web). Google's privacy policy applies there.
Subscriptions: Google Play processes the payment. You buy, cancel and manage the subscription in Google Play. We never see your card or payment details or your Google account. Google's privacy policy applies to the payment. RevenueCat checks Google Play purchases the same way, keyed to your household ID.
Backups: Home Team keeps its data out of Android cloud backup and phone-to-phone transfer, including the phone's secret key. A new Android phone joins your household again with a link code.

What we don't do

We don't have accounts, and we don't collect your email address or phone number. The early-access waitlist on this website does collect your email if you join; see Early-access waitlist.
We don't use advertising, ad identifiers, or tracking. The app has no analytics SDK: our own server keeps the anonymous counts, and RevenueCat's reports cover subscriptions only.
We don't sell or rent personal information, and we don't share it for advertising.
We don't use your location in the background, and we never ask for "Always" access. With your permission, the app reads your location only while you're using it: when you tap Pin the venue, when you choose From here as where you're leaving from, and on game day to check whether you need to leave earlier. The "From here" and game-day readings stay on your phone and go only to Apple Maps for the drive time.
We don't read your clipboard unless you tap Paste.

How long we keep it

On your phone: until you delete it in the app (Settings → Start over) or delete the app.
Household member and guest details (phone ID, role, name, push token): until that phone leaves the household with Unlink or an earlier-joined parent removes it. The owner can only leave, never be removed.
Family setup: for as long as the household exists. Each update replaces the previous one. When the last phone leaves, the whole household — setup, "who's driving" history and link code — is deleted.
Inactive households: if no phone in a household uses Home Team for 12 months, our server deletes the whole household: its members, setup, "who's driving" history, link code and subscription status. A household whose subscription keeps renewing isn't deleted. If a phone opens Home Team again later, it quietly gets a new household; the schedule on the phone isn't affected.
"Who's driving" updates: treated as expired after 14 days and deleted the next time the household is accessed (at most the 80 most recent are kept).
Guest invite codes: until used, revoked or expired (7 days).
Games and practices you add by hand: once an event has been over for 30 days, or was deleted 30 days ago, our server removes it the next time a phone in your household checks in. If no phone checks in, it stays until the household itself is deleted (after 12 months without use, above).
Team invites: about 400 days after the team invite was last created, updated or used. The saved schedule copy: 30 days after it was last refreshed.
Share links: a share link nobody has used is deleted after 30 days. When you stop a share, its details (your kid's name, team and its connection to your team's calendar) are deleted right away; a short "stopped" note stays for up to 90 days so the other phone can show that you stopped sharing. A share that's in use is deleted once the other phone hasn't checked it for 12 months. Ask us and we'll delete your shares sooner.
Subscription status (plan, status, expiry date, whether the free trial was used): for as long as the household exists, so a household's free trial is used only once. It's deleted with the household. Apple and RevenueCat keep their own purchase records under their own policies. Ask us and we'll request deletion of your household's RevenueCat record.
Crash reports and hosting logs: Crash reports are deleted within 90 days; hosting request logs within 1 day.
Early-access waitlist (this website): We keep waitlist information until 6 months after Home Team launches publicly, then delete it, unless you've chosen to keep getting updates; you can unsubscribe or ask us to delete it any time. Deleting it, on that schedule or when you ask, includes the signup and profile emails in our support inbox.

How to delete your data

Unlink first; we never send a link code by email.

Leave a household: open Settings → Household → Unlink. This removes your phone's ID, name and push token from our server. If you're the last phone in the household, the whole household is deleted.
Erase your phone's data: Settings → Start over, or delete the app.
Important: "Start over" and deleting the app remove data from your phone only. If you're linked with a co-parent or guests, tap Unlink first so your details are also removed from our server.
Cancel a subscription: deleting the app or leaving the household doesn't cancel it. Cancel in iPhone Settings → [your name] → Subscriptions. On Android, cancel in Google Play → Payments & subscriptions → Subscriptions.
Ask us: email support@gethometeam.app and we'll help delete household data. Because there are no accounts, we'll need your household's link code to find it. You send us the code; we never send a link code by email.
Early-access waitlist: reply to any waitlist email, or email support@gethometeam.app from the address you signed up with and we'll delete your waitlist info, including the copies in our support inbox.

Children

Home Team is for parents and guardians. It is not directed to children, and we don't knowingly collect personal information from children under 13. Parents may enter their kids' first names and schedules so the app can sort games by kid; that information is entered and controlled by the parent. If you believe a child has provided information to us, contact us and we'll delete it.

Security

Data sent between the app and our server is encrypted in transit (HTTPS). Reading or changing a household's data requires the app's server key, the household's ID, and a member phone's ID. Current app versions also prove membership with that phone's own secret key. Our server keeps only a scrambled, one-way copy of each secret, and deletes it when that phone leaves the household. Versions of the app too old to hold a secret key are being phased out. Until the cutoff, such a phone can still reach household data without a secret, and updating the app gives it its own secret the next time it opens. After the cutoff, a phone without a secret is refused, and updating the app alone does not mint a new secret for it: a parent who joined earlier must remove that phone and invite it again. If the owner's own phone has no secret, contact support. Repeated attempts to guess link codes or secrets are blocked. Anyone who has your link code (or your "Text the link" message) can join your household, so share it only with your co-parent. A link code can only add a new phone; it can't take over a phone that's already linked. A parent can remove only phones that joined after theirs, and cannot remove the owner. Removing a phone gives the household a new link code and revokes guest invitations created by that phone. No system is perfectly secure, so we keep what we store to the minimum the app needs.

Your choices and rights

You can use Home Team without linking, without notifications, and without location access. Depending on where you live, you may have rights to access or delete your personal information — contact us and we'll help.

Changes to this policy

If we change this policy, we'll post the new version on this page with a new effective date.

Contact

Front Porch Apps LLC
support@gethometeam.app
13110 Birch Dr Ste 148 PMB 169, Omaha, NE 68164