Privacy Policy

1. Introduction

Welcome to Third Team. We respect your privacy and are committed to protecting your personal data. This privacy policy explains how we collect, use, and safeguard your data when you connect third-party platforms (like Intervals.icu) to our service.

2. Data We Access & Collect

When you authorize Third Team to connect to your Intervals.icu account, we only access and collect:

• Your Intervals.icu Athlete ID and display profile information.
• Physiological metrics (CTL, ATL, TSB, and wellness metrics).
• Your historical and daily training activities (for match log enrichment).
• The heart rate, distance and GPS positions recorded during your matches. Heart rate is health data and positions are location data: they are fetched from Intervals.icu only when you open a match, shown only to you (positions only as a heat map of the pitch during play, never as a track), kept in the server's memory for at most 30 minutes, and never stored in our database or backups. To draw the pitch we look up its outline on OpenStreetMap using the venue's address coordinates, never your positions.

When something goes wrong, an error report (what failed and where in our code, without your personal data) goes to Glitchtip, our error tracker.

When we send you an email, your email address and the message go to Scaleway (France), our email provider, which delivers it. Our logs note that an email was sent, never your address or what it said.

3. How We Use Your Data

We use the retrieved information solely to run the core features of Third Team:

• Training Coach: Tailoring and projecting your training plan relative to your upcoming referee match assignments.
• Activity Sync: Enriching completed workouts with referee match details to give you accurate logs.
• Match page: Showing your heart rate over the match, with figures per half, on that match's page.

We do not share, sell, or distribute your training, physical, or personal data to any third-party marketing or analytics services.

4. Your Matches and Your Crew

Third Team reads your assignments from Fogis with your own login. For each match we keep the details of the referees you work with (names, phone numbers, email and addresses), so the crew can reach each other before the match and about its follow-up: reports, fees and travel.

• For 60 days after a match we keep following it (fees, observer reports, your recording) with the crew's details, in the app and in your calendar feed.
• If you subscribe to the optional Match day calendar, it shows your travel plan's times and pickups (who drives, who is picked up where) while the plan is kept, as the match page does. Nothing more is stored for it.
• After 60 days the other referees' details are removed. The match stays in your calendar for good, with only the teams, time, venue and your own role. If its page shows the other referees after that, it asks Fogis for them at that moment, with your login, and doesn't store them.
• If you import your match history (switched on for you), we fetch every past season Fogis has for you, with your login, and keep each match the way a match older than 60 days is kept: the teams, time, venue and your own role, never the other referees' details. Each match's events are kept reduced, without anyone's name or shirt number, as described below.
• Lineups (players and team officials) and match events (goals, cards and substitutions, with the players' names) are public: Min Fotboll and svenskfotboll.se publish them. They're fetched from Fogis with your login, or the login of another referee in the match's crew, and a copy per match is kept so the match page works when Fogis doesn't answer. Players' accumulated cautions and suspensions are never stored. 60 days after the match, the lineups are deleted and the events are reduced to what happened (the minute, the team and the score) without anyone's name or shirt number; that is kept, so the match page keeps its timeline.
• For an upcoming match, the page shows both teams' recent results and their other meetings this season. Fogis lists them per team with your login, or the login of another referee in the match's crew, for the two teams of your match only. We keep the teams, dates and results (public, and kept for good as they stood at kickoff, like the competition's table from Min Fotboll); the clubs' contact people that come with Fogis's list are never stored.
• For each upcoming match with a crew, a travel plan suggests who drives and where to meet. It is worked out from the crew's home addresses in Fogis (looked up on a map service, OpenStreetMap's Nominatim) and shown to the crew on the match page and the travel plan map. The drive times come from openrouteservice (HeiGIT, Germany), or OSRM when it's unavailable: they get the homes' and the venue's positions rounded to about 100 metres, never an address or a name. Like the other referees' details, the names in a plan are removed 60 days after the match. If you set "I don't drive" (with an optional end date), we keep that setting so the plan never makes you a driver; the crew sees only what the plan implies, such as who picks you up. If you don't drive and no car in the crew can take you, the plan finds public transport there and home with Trafiklab's ResRobot: we send it your home's position rounded to about 100 metres and the venue's, never your address or name, and check the journey again the day before the match. If no stop is within walking distance, we ask it for the stops within 8 km of that rounded position and plan from the best station; the answer is kept in memory only, and the plan keeps just the station's name and how far it is from your home (the distance is removed with the names). The same is done when the plan puts you on a train for a long trip; if you can drive, openrouteservice also works out the drive from your rounded home position to that station, and the plan keeps how many minutes it takes (removed with the names, like the distance). For one match, you can also mark yourself "not driving", or mark a crew member who isn't on Third Team: the crew sees the mark and who set it, and it is deleted 60 days after the match.
• On the match page you can say whether the travel plan works for you (👍 or 👎), and with a 👎 what you would have done instead. We keep your vote, your text and a copy of the plan as it stood, with roles instead of names and no addresses, to improve the planner. Your 👍 also holds the plan for your crew, and when everyone in the crew who uses Third Team has given a 👍 the plan is confirmed; your crew mates on Third Team see who gave 👍 or 👎, never your text, and when your 👍 is the first, those who haven't voted get one notification with your name asking whether the plan works for them. When the plan changes for real (the crew, the kickoff, a train), the votes are kept as votes on the earlier plan. The admin reads them, and gets a notice of a 👎 on Telegram without your text. Don't put names or phone numbers in the text; it is never written to the logs.
• The crew's meeting time is one per match. It comes from your usual arrival time per competition (if you're the head referee, or the highest-ranked crew member on Third Team), unless someone in the crew sets one for the match. When you set one, the rest of the crew sees your role ("set by AD1") and gets a notification.
• A crew member on Third Team who connects their Telegram account can have a Telegram group created for a match: the crew are added by the phone numbers in Fogis, and the group gets the travel plan and the match's follow-up. Third Team keeps the group's ID and invite link with the match. Notifications to you alone come only as push, not on Telegram.
• If you connect your Telegram account, its login (the session and the api_hash from my.telegram.org) is stored encrypted with the app's key, as your Fogis login is. Disconnecting deletes both.
• In a series where SvFF's travel rules have Grand Travel book the trains, the travel plan's own page can draft the booking email: the match, the series' account, and the trains the plan has each crew member take, with their names. Third Team never sends it: it opens in your own mail app, or you copy the text. The draft is put together when the page is shown and is never saved or logged, and a shared plan never shows it.
• Sharing the travel plan. Any crew member on Third Team can share a match's travel plan with a link, for crew mates who aren't on Third Team. Anyone who has the link sees the plan with roles instead of names, as Fogis writes them (Dom, AD1, AD2, 4D): the times, trains, stations, car parks and the venue, "at home" instead of an address, no map, and how many of the crew agreed to the plan by role. Crew members who are logged in see the full plan as usual. The link stops working a day after the match, when the match is cancelled, or when someone in the crew stops sharing it. We keep the link with the match (who made it, when, and when it was stopped) and delete it once it no longer works. We count how often a shared plan is opened, per match, never by whom: no address of the device or browser is stored. The link is never written to our logs. The shared plan has no buttons to answer it; it points crew mates to signing up instead, and when someone signs up from a shared plan we note that with their new account (only that it came from a shared plan: not which plan or match, nor anything about the device or browser).
• Your match notes. If you keep notes of a match's events in Third Team (for example as 4th official, to check them against the report afterwards), they are stored with your account and never sent to Fogis: for each note the player's id in the match and shirt number, the team, what happened, the time and the period, and for a team official's card Fogis's id for that official (its person id, so the note follows them if their card is cleared and they're added back) and their id in the match. No names: they're taken from the match's lineup in Fogis, with your login, when the notes are shown. They are shared with the crew of that match, by role, never by name: the others in the referee crew who use Third Team see them, read-only, labelled with your role (such as AD1), and only you can change them. A referee taken off the match no longer sees the crew's notes, and theirs are hidden from the crew. Why: you asked to keep them, to compare with the report, and the crew checks its notes against each other's. They are deleted 7 days after the match's kickoff, whether or not the report has been submitted, and with your account.
• If you report a match's final result from Third Team, it is sent to Fogis with your Fogis login, only after you confirm it, and then read back from Fogis to check it arrived. Only the score is sent. The result is public and kept with the match, like its events.
• Your referee number (domarnummer) is read from Fogis with your login, from the old Fogis client's Arkiv → Uppgifter page, when you save your Fogis login and each time the app reads your days off or open assignments there; it is never typed in. Nothing else on that page (your address, phone or email) is read or stored. The number is kept with your account so the app knows which place in a match's crew is yours, and is deleted with it.
• If days off are switched on for you, your days off in Fogis (the dates, times and reason) are read from Fogis with your login about twice a day, to show them in your Matches list. They're kept only in the server's memory, never stored or logged, and are gone when you switch the feature off or the server restarts. When you add, change or delete a day off here, it's sent to Fogis with your login once you confirm, and Fogis's list is read back; nothing of it is stored. A repeat is saved (or several days off deleted) one day at a time the same way; while that runs, and until the server restarts, its days and what came of each are kept in the server's memory so the page can show the outcome.
• Who you refereed with. So you can see which matches you did with a colleague (tap them in a match's crew), we keep, with each of your matches, the other referees' Fogis referee IDs and their roles: the ID only, never a name, referee number or contact details. A name is shown only when the match page already shows it, fetched from Fogis with your login. The IDs come from the same match lists Fogis gives the app with your login (also for your past seasons, read once in the background), are only ever searched within your own matches (never another referee's history, never across accounts), are kept as long as your account and deleted with it. Referees with a protected identity in Fogis are never stored. Why: your interest in your own work history weighs more than the small effect on colleagues, since who refereed a match is public with some effort and the ID leads to a name only for someone with a Fogis login (legitimate interests). If you're a referee and want your ID removed from every account, contact us (section 6): it's removed and never stored again.
• If open assignments are switched on for you, Fogis's list of open assignments ("Lediga uppdrag": the match, its time, ground, competition and role) is read from Fogis with your login in the same visit as your days off, to list them under Settings. It's kept only in the server's memory, never stored, and is gone when you switch the feature off or the server restarts. The other referees Fogis names next to each assignment, and their phone numbers, are never read. The list also shows which ones you've applied for, with the date and your comment: they're read and kept the same way. When you apply for one here, the application and your comment are sent to Fogis with your login once you confirm, and Fogis's list is read back; nothing of it is stored or logged. The ones you've applied for, and (if you choose) open ones that match your watches, also show among your matches in your Matches list, from the same memory; then the list is read every 3 hours between 07:00 and 22:00 instead of twice a day. Only your choice to show them there is stored with your account. So that the app can tell you when a match you applied for went to someone else (or was cancelled), it stores which matches you've applied for: the match number and the role, with the match's public facts (the teams, kickoff, ground and competition), when it first saw the application and when it left the list. Never your comment or the date you applied. These are deleted once the match is yours, at kickoff, and with your account.
• The watches you save for open assignments (roles, words for the teams, competition and ground, days, times and dates you choose) are stored with your account. So that the same open assignment is never notified twice, Fogis's id for each open assignment seen on your list is stored too, with when it was first seen, notified and dismissed: no match details and no names. Ids no longer listed are deleted after 60 days; all of it is deleted with your account.
• A venue's heads-up (its surface, what's missing there such as parking or a dressing room, and the notes) is written by referees for every other user of Third Team: whatever you write in it is shown to all of them, and kept until someone changes it (the last five versions are kept so a bad change can be undone). Who made a change is stored for handling abuse, never shown, and the notes are never written to our logs. Please leave out door codes, names and phone numbers.
• Your observer grades. Each observer report you have in Fogis is read once in the background, with your login, for your own grade (the FIFA grade in your section of the report). Only your own grade and the observer's name (to show who observed you) are stored, with the report, encrypted with the app's key (as your Fogis login is), as long as your account and deleted with it. Reports read before the observer's name was kept are read once more for it, quietly in the background. The observer's home town, the other referees' grades and names and the report's written text are never stored, and no grade or name is logged.
• Observer reports you open in Third Team. When you open one of your observer reports here, it is fetched from Fogis with your login at that moment and shown as Fogis shows it to you (the whole report, the other referees' sections and the observer's name included). It is kept in the app's memory for at most 10 minutes so going back doesn't fetch it again, and is never stored, logged or kept by your browser; only your own grade and the observer's name from it are stored, as above.
• Season Wrapped (under Reports) counts your season or career from what is already stored about your matches and observer reports; nothing new is saved. Its kilometres are straight lines from your home's position (already worked out for travel plans) to each ground and back, calculated each time you open it and never saved or logged. Other referees never appear in it.
• The fees and expenses Arvoden lists for your assignments, on the Fees page under Reports. They are fetched from Arvoden (arvoden.fogis.se) with your Fogis login when you open that page, shown only to you, kept in the server's memory for at most 30 minutes (forgotten earlier when you change your Fogis login or delete your account), and never stored in our database or backups. We keep only the names of the kinds of payment Arvoden uses (such as "Arvode" or "Parkering"), never an amount. We never open your receipts, bank details or address in Arvoden.
• Logging in. To stop anyone guessing passwords, failed logins are counted per email address (the address and the times of the tries, never the password) in the server's memory: after 10 in 15 minutes that address can't log in for 15 minutes. The count is never stored or logged. A try stops counting after 15 minutes and is cleared from memory at the next failed login; an address's tries are cleared when it logs in, and all of them when the server restarts.
• Signing up and checking Fogis logins. So nobody can use Third Team to try out Fogis passwords, we count new accounts (only the times) and checks of a Fogis login (your account id and the times, never the username or password) in the server's memory: at most 10 new accounts an hour in total, and 5 checks per account in 15 minutes and 30 an hour in total. Past that, the form asks you to try again later. The counts are never stored or logged; a try is cleared from memory once it no longer counts (after 15 minutes or an hour), and all of them when the server restarts.
• When you turn on notifications on a device, we keep that device's push address (from your browser) to send you notifications, until you turn them off or the browser stops accepting them.
• We record the day you last used the web app and the day your calendar app last fetched your calendar feeds, so that accounts nobody uses any more can be deleted. We also count, with your account, when your calendar app fetches your calendar feeds and when you view a travel plan (at most once a day per match on each of the match page, the plan's own page and Next up): the day, and for a plan which match and whether you're its only referee. Nothing about what the plan says, and nothing about your device or browser (calendar fetches counted before this also hold the name your calendar app sends; they go with the rest). We use the counts to delete unused accounts and to decide which plans to calculate first; they're kept for 13 months and deleted with your account.
• When you sign up we also count, with your account, the steps of getting started: that you signed up, first saw the form for your Fogis login, each time you save a Fogis login (only whether Fogis accepted it, never the username), and your first sync that worked (only whether it found a match). Nothing about you, your device or browser. We use the counts to see where getting started is hard; they're kept for 13 months and deleted with your account. When you delete your account, one count is kept without your account or anything else about you: how far you got in getting started.
• The start page. When you check your Fogis login on the start page, the login (username and password), Fogis's answer, your referee number and your next five matches (the date, time, teams, venue and your role) are held in the server's memory for up to 30 minutes, behind a random code in a cookie, so the next step can show them. They're forgotten if you don't save your account within those 30 minutes, and when the server restarts: nothing of it is stored or logged before you save. Without any account, we count that the start page was opened and each Fogis check there (only whether Fogis accepted it).
• Forgot your password. To set a new password without email, you prove it's you with your Fogis login: it's checked with Fogis, and only if Fogis accepts it do we look for the account that holds it. Your Fogis login is then held in the server's memory for up to 15 minutes, behind a random code in a cookie, until you set the new password, which also saves that Fogis login to your account; it's forgotten after 15 minutes or when the server restarts, and is never logged. To stop anyone trying out Fogis passwords this way, the tries per Fogis username (the username, lowercased, and the times) are counted in the server's memory: 3 a day. The count is never stored or logged, and a try is cleared from memory after a day. The admin is told the account's id (nothing else) when a password is set this way.
• Server backups are kept for 7 days.

5. Consent & Revocation

You can disconnect your Intervals.icu integration at any time from your settings dashboard. Disconnecting instantly deletes our local storage of your access keys and metrics. You can also revoke access directly from your developer settings page inside Intervals.icu.

6. Contact

If you have any questions regarding this policy or the security of your data, please contact us.