MatchTempoMatchTempo

Beta draft · version 0.6 · 27 Oct 2026

Privacy

Version 0.6, published 27 October 2026 · applies to the MatchTempo beta for Apple Watch, iPhone and matchtempo.app

In short:

  • Your groups see your name, who's playing, your goals and results.
  • Your recordings and health readings are not sent to our servers or shown to your groups. They are left out of iPhone backups unless you turn that on.
  • Anyone you share a game link with can see the teams and score without signing in.
  • If your group takes payments, Stripe handles them for the manager. We never hold the money for games. A manager can also take a payment from you in person, by QR code or by tapping a card on their iPhone.
  • Managers and assistant managers can keep a private record of late drop-outs and no-shows. Players, including the player concerned, do not see it in the app. It is deleted after 12 months.
  • Your account is kept in London. Delete it any time.
  • If you sign up for updates on our website, we email you only about MatchTempo, until you unsubscribe.
  • You must be 18 or over to have an account. A parent or guardian can add their child who is under 18 as a player. We keep as little as we can about a child, and never their name outside their groups.

Nothing is sold, and nothing is used for advertising or tracking. This is a beta draft and has not yet had a legal review.

Who we are

MatchTempo is made by an independent developer in the United Kingdom, who is responsible for your data under UK data protection law. We are the controller of the data described here. Contact us at .

Two ways to use MatchTempo

Only recording on your Watch

You don't have to sign in to record your own games. Recording doesn't send your recordings or health readings to our servers. If you signed in before, signing out doesn't delete your account or your groups' history, and if you email us we keep your message as explained below.

Signed in, for groups and games

To start or join a group you sign in with Apple or Google. We then keep your account and your groups' games on our servers, so everyone in the group sees the same replies, teams and results. Your recordings and health readings stay separate from this.

What stays on your devices

These are kept on your Apple Watch and iPhone, and not sent to our servers:

Recordings move from your Watch to your iPhone, and your heart rate zones from your iPhone to your Watch, using Apple's own connection between the two devices. Apple Health and your backups may also hold copies, as explained below. If you send us a screenshot or feedback yourself, it contains whatever you put in it, so please leave out health details unless we need them to help you.

Apple Health

With your permission, MatchTempo reads from Apple Health:

When Save to Health is on in MatchTempo, and you have allowed it, MatchTempo writes the workout, with its route, active energy and distance, to Apple Health.

Using Apple Health is your choice, and you can change it at any time in the Health app or in Settings. Turning it off stops MatchTempo reading or writing from then on; it doesn't remove what is already saved. Health data is never sent to our servers, never used for advertising, never sold and never shown to your groups.

Location, motion, Bluetooth and camera

Location is used only while you're recording, to measure distance and save your route. Motion data helps describe your movement during a recording. Bluetooth is used only to connect a heart-rate strap you choose. The camera is used only when you choose Take photo for a group picture, and the photo stays on your iPhone.

When a manager searches for a venue, the search goes to Apple Maps. The venue they pick (name, address and map location) is kept with the group on our servers.

What we keep when you sign in

Your account

Your groups and games

Keep reasons and notes short and factual. Don't put health details, such as an injury, or anything private about someone else in them.

Payments for games

A manager can choose to take payment for games in the app. Card payments, including Apple Pay and Google Pay, go through Stripe straight to the manager's own Stripe account. The manager runs the game and receives the price. We never hold the money for games; we receive only our fee, which is shown before you pay.

When you pay, we keep: who paid, for which games and places, the price, our fee and the total, whether it succeeded, refunds, money carried over to later games, payments the manager marks as made outside the app, reminders sent, and Stripe's references for the payment. Stripe receives these references and the amounts, not players' names. Stripe handles your card details; we never see or keep them.

A manager who takes payments gives their own identity and bank details to Stripe, not to us, and becomes Stripe's customer. We keep their Stripe account identifier and whether it is ready to take payments and pay out.

Before setting up payments, a manager gives us their mobile number. We check it is theirs by sending a code by text message, and we keep the number and when it was checked. We pass it to Stripe for the manager's Stripe account, and we use it to contact the manager about payments, refunds, disputes or a problem with their group. We don't use it for marketing. We also give it to Stripe as the support phone number for the manager's payments, so Stripe may show it to players on card receipts, statements or Stripe's payment pages. The manager can change it by checking a new mobile number in the app. MatchTempo itself never shows it to players or assistant managers.

A manager can also take a payment from you in person. They can show you a QR code, or take a card payment on their own iPhone (Tap to Pay on iPhone). The payment goes to the manager's Stripe account in the same way, and Apple and Stripe handle the card details: we never see or keep them. For each payment we also keep how it was taken (in the app, on the website, by QR code or by tapping a card) and, for a payment the manager took in person, which manager took it.

A QR code opens a one-off payment page on matchtempo.app, which then passes you to Stripe's payment page. The link holds a random code and works for 30 minutes. We keep only a scrambled (hashed) copy of the code, so we cannot read it back. To stop people trying links over and over, each time the page is opened we keep a scrambled (hashed) form of the visitor's IP address for at most 2 days and use it to count recent tries. We cannot read the IP address back from it. The page sets no cookies. Our hosting service and Stripe also keep their own technical logs, as described under Logs and security.

If a manager takes a payment from one player but it should have been another player's, the manager can move it to the right player in the same game. No money moves: only our record of who paid changes. We keep a record of each move: which payment, who it moved to, which manager moved it, when, and a short reason if the manager types one. The manager sees this record. The first player sees that the manager moved the payment, but not the manager's name or the reason.

A parent or guardian pays for the children they look after. Those payments are kept under the parent's account, as their own payments, and the manager sees who paid.

The manager and assistant managers see who has paid for each game, how, what is still owed and any money carried over. Only the manager sees how a payment was taken and which manager took it. You see your own payments. Other players don't see what you paid, and game links never show payments.

Kick-off weather

If a venue has a map location, our server asks Apple Weather for the forecast at kick-off. Only the location, rounded to about 1 km, is sent to Apple, with no names or other details. We use a forecast for at most 12 hours and remove old ones every hour. We never store forecasts with results.

Logs and security

When the app or a browser talks to our servers, our hosting and sign-in services record technical logs, such as IP address, time, the request made and any error. We also keep a record of important changes in each group, and short-lived records that stop an action happening twice if your connection drops. These use account and group identifiers rather than names, but can still relate to you. We use them to keep the service running and secure. How long each is kept is below.

How you found us, and counting groups

When a manager creates a group, the app can ask them once how they found MatchTempo, from a short list of answers. It is optional and can be skipped. We keep the answer with the group and use it only to see which routes bring in groups. We read it only as counts, never as a list, and it is not shown to anyone in the group. We also count groups in our own database, by the week each group was created and whether it still has games after 8 weeks. These counts hold no names, players or votes.

Who sees what

Players who don't use the app

A manager can add players and guests who don't use MatchTempo. If you do this, tell them first what the group and anyone with a game link can see, point them to this page, and add only what the game needs, such as a first name. They can ask the manager to leave them out of stats or remove them, or email us directly, without needing an account. Removing a player doesn't change games they have already played.

Email updates

You can sign up on matchtempo.app/updates for an email when the beta opens and, now and then, news about MatchTempo. This is separate from your MatchTempo account, and you don't need an account to sign up.

We ask only for your email address. Brevo, our email service, sends you an email to confirm it, and keeps a record of when you signed up and confirmed, and the IP address you used, as proof that you asked. Every email has an unsubscribe link. Brevo may count how many emails are opened and how many links are clicked, but we have set this so the counts are not linked to you. The sign-up form loads nothing from Brevo, so it sets no cookies.

Why we use your data

We don't use your data for advertising, we don't sell it, and we don't send marketing, apart from the email updates you sign up for. We don't make decisions about you that have legal or similarly serious effects. Places in a game are given out by the group's own rule, and the manager or an assistant manager can always change them.

Who helps us

Testing through TestFlight

During the beta, Apple's TestFlight may share crash reports, basic device information (such as model and software version) and any feedback or screenshots you choose to send with us. A screenshot can show personal or health details, so check it before you send it. Apple's privacy policy covers how Apple handles this.

Backups

Your recordings are left out of your iPhone's iCloud or computer backups unless you turn on "Include recordings in iPhone backups" in Settings. Your heart rate history is always left out. Backups are handled by Apple under your own Apple account, not by us. Turning the setting off doesn't remove recordings from backups made before, and Apple Health keeps its own copies under your Health settings.

How long we keep data

Children

You must be 18 or over to have an account. Children under 18 can't sign in, and we never ask them for anything. A parent or guardian can add their child as a player they look after, from You in the app. The child can then play in the parent's groups whose minimum age they meet, once the manager or an assistant manager says yes. Each group is for people aged 18 and over unless its manager chooses a lower minimum age.

About a child, we keep:

We don't keep a child's email address, phone number, photo, health or Watch data, or notes about them. The parent's Watch records only the parent. Messages about a child, such as a place or a team, go to the parent and use the child's first name only. Nothing is sent to the child.

Group members see the child's shown name with an "U18" marker. The manager and assistant managers also see their last name and their parent. Game links, share images and share text show the child only as "Under-18 player", never their name.

The parent can remove a child at any time. This deletes the child's first name, last name and year of birth, and past games show "Removed player". Deleting the parent's account does the same. A manager can take a child out of their own group only. Payments the parent made are kept under the parent's account for the time shown above.

From 1 January of the year a child turns 18, the parent can send them a one-time link, which works for 30 days. The young person signs in with their own Apple or Google account and confirms they are 18 or over, as any new account does. They then take over the same player, with their name, places, games, goals, awards and table points. Their year of birth is deleted. Payments the parent made stay in the parent's payment history, and any money carried over for the child's places is refunded to the parent. If the sign-up shows they are still under 18, nothing moves.

A parent can use the rights below for their child, and so can the child. If you think someone under 18 has an account, or has been added to a group other than by their parent, please email us and we'll remove them.

Cookies

We don't use analytics, advertising or tracking of you. The game page and matchtempo.app set no cookies. The app keeps what it needs to work, such as your sign-in, on your device. Apple and Google's sign-in pages have their own policies.

Your rights

You have rights under UK data protection law, including to get a copy of your data, to correct it, to have it deleted, to limit how we use it and to object to how we use it. These rights have some legal limits, and if we can't do what you ask, we'll tell you why. You can do much of this yourself in the app. For anything else, or for a copy of your data, email . If a manager added you or a guest to a group and you don't use the app, you can email us too.

If you're unhappy with how we've handled your data, email us. We'll confirm we have your complaint within 30 days, look into it, keep you updated and tell you the outcome as soon as we can. You can also complain to the Information Commission, the UK's data protection regulator (formerly the ICO), at ico.org.uk.

Changes to this policy

Each version of this policy has a number and a date, shown at the top of this page. For a big change, the app will tell you what has changed and ask you to agree again the next time you open Play. Small changes, such as clearer wording, only update the date and version.