Privacy Policy

Version 2.3 · Last updated: 2026-08-30

This policy describes how Breakout Sports AB processes personal data in the Breakout app and on breakoutsports.se. It is written purpose by purpose: for each thing we do, you can see which data is needed, on what legal basis, who receives it and how long it is kept. Because Breakout is used by people from age 13, special safeguards apply to anyone under 18 — they are marked in each section, and a simpler version of this information is available at breakoutsports.se/integritet-ung.

The essentials

  • We only collect what the service needs: account, profile, your clips and what is generated as you use the app. We never sell your data.
  • If you are 13–17 your account is private from the start and you are not visible to scouts or trainers until you choose to be.
  • Every clip is screened automatically as a child-safety measure before it is shown. Flagged content is assessed by a human.
  • All core data is stored within the EU/EEA. You can export your data or delete the account directly in the app at any time.
  • Questions or complaints: dataskydd@breakoutsports.se. You always have the right to contact the Swedish Authority for Privacy Protection (IMY).

Each section states its purpose in plain text. The details — data, legal basis, recipients and retention per processing operation — sit behind “Show in detail”, or expand everything at once.

§1. Who is responsible for your data?

Breakout Sports AB, company reg. no. 559585-5445, Mannerfelts väg 8B, SE-504 31 Borås, Sweden, is the controller for the processing described in this policy, except where stated otherwise.

We have not formally appointed a Data Protection Officer. Data protection matters are handled by the company and reached at dataskydd@breakoutsports.se.

When a club or trainer uses Breakout to administer their team — rosters, events, chat and squad selections — the club is the controller and we process the data on the club’s behalf. The same applies to scouts’ own notes, watchlists and ratings. For questions about that processing, the club or scout is your first point of contact; we will always help pass the question on. Sections 6 and 7 show which processing this concerns.

§2. How to read this policy

Version 2.2 is advance notice. Parts of what is described below do not yet exist in the app: calendar subscription (E6), reason for an absence (E7), messages from a club to its teams (H4), applying to change role (A7), and the new tags you can put on a clip (B3) together with the searches they make possible for trainers and scouts (D2). They begin only when the next app update is rolled out, and no earlier than 14 days after you have been notified in the app. Until then, none of them takes place.

Sections 3–12 list each processing operation separately. Each card states the purpose, the data involved — including data generated as you use the app, such as points and view statistics — the legal basis under Article 6 GDPR, recipients, retention and who is responsible. Providers processing data on our behalf are referred to by category (for example “our email provider”); section 13 names them and shows where they process the data. Where the basis is legitimate interests, the interest we rely on is stated; you can request a copy of the balancing assessment via dataskydd@breakoutsports.se.

One important difference applies if you are under 18: we do not rely on contract as the legal basis, because a person under 18 has limited capacity to enter binding contracts. Instead, the core processing rests on a documented balancing of interests, for which the safeguards in section 9 are a precondition. Data you choose to add is always optional: all a player account requires is an email address, password, name and date of birth. Leaving anything else blank only affects how your profile appears — never your access to the app.

§3. Account and access

So that you can sign in, so we know which role you hold, and so we can demonstrate that you accepted the terms.

Show all 8 processing operations in detail

A1Create and administer an account

Purpose
Create and administer a user account so that you can sign in, recover a forgotten password and access your own data.
Who it concerns
All users
Personal data
Email address, password in hashed form, internal user ID, time of email verification, language preference, country, and the time and version of terms acceptance. The country governs which age limit applies and is set at registration.
Legal basis
Performance of a contract (Art. 6(1)(b))For users under 18 we do not rely on contract, because a minor cannot enter a binding contract without their guardian’s approval.
Legal basis, ages 13–17
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Being able to offer 13–17-year-olds the sports service they sought out themselves, with the safeguards for minors described in section 9.
Recipients
No external recipient — the data is stored with our hosting provider within the EU/EEA, and our email provider handles delivery of the verification code. The providers are named in section 13.
Retention
Retained for as long as the account exists. On deletion the data is removed after a 30-day grace period.
Responsibility
Breakout is the controller

A2Verify email address

Purpose
Confirm that the email address belongs to you, so nobody can register an account on someone else’s address.
Who it concerns
All users
Personal data
Email address, six-digit one-time code, validity period and number of attempts.
Legal basis
Performance of a contract (Art. 6(1)(b)) and Legitimate interests (Art. 6(1)(f))
Legal basis, ages 13–17
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Preventing accounts from being created on other people’s email addresses.
Recipients
Our email provider (delivery of the code).
Retention
The code is valid for 15 minutes. Expired codes are cleared continuously and no later than one day after expiry.
Responsibility
Breakout is the controller

A3Create and verify a trainer, scout or club account

Purpose
Create an account for a trainer, scout or club and check that the person or organisation really is who they claim to be, before access to player profiles is granted.
Who it concerns
Trainers, scouts and club representatives
Personal data
Organisation, job title, licence details (type, licence number, expiry), an uploaded licence or certificate document as a PDF or an image — a screenshot of the licence is enough, which also means the document more often contains more than the licence itself — review status, and the reviewing administrator and their notes. For club accounts also club name, company registration number, contact person, phone number, address and postcode.
Legal basis
Performance of a contract (Art. 6(1)(b)) and Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Protecting players, especially minors, by checking who is allowed to search for and view their profiles.
Recipients
The document is stored privately with our file-storage provider within the EU/EEA and is only reachable via time-limited links valid for 24 hours. Authorised Breakout administrators.
Retention
The document is retained for as long as the verification applies and the account exists. We do not request a copy of an identity document — only a licence or certificate evidencing the authorisation.
Responsibility
Breakout is the controller

A4Assign and administer permissions

Purpose
Assign and administer roles and permissions, including clubs’ trainer licences, so that each user only reaches what belongs to their role.
Who it concerns
All users
Personal data
Role, administrator and manager flags, the link between a club account and a trainer account, and the licence status. When a club invites an account that already exists we also store who sent the invitation, when it was sent and when it was answered. For the club’s overview of its own trainers also the number of sign-ins and the time of last activity.
Legal basis
Performance of a contract (Art. 6(1)(b)) and Legitimate interests (Art. 6(1)(f))
Legal basis, ages 13–17
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Ensuring that only authorised parties gain access to player data.
Recipients
The club account sees this data about its own trainers.
Retention
Retained for as long as the account exists. An invitation nobody answers is deleted after 14 days.
Responsibility
Breakout is the controller

A5Authentication and sessions

Purpose
Keep you signed in, handle password resets, and be able to sign out every device if an account is suspected of being compromised.
Who it concerns
All users
Personal data
Access tokens, IP address and user agent for sessions, and one-time password-reset codes with validity period and number of attempts.
Legal basis
Performance of a contract (Art. 6(1)(b)) and Legitimate interests (Art. 6(1)(f))
Legal basis, ages 13–17
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Protecting accounts against unauthorised access.
Recipients
Our email provider when a reset code is sent.
Retention
Reset codes are short-lived and are cleared no later than one day after expiry. An access token remains valid until you sign out or we revoke it.
Responsibility
Breakout is the controller

A6Evidence of terms acceptance

Purpose
Being able to demonstrate that you accepted the terms of service and read the privacy policy, and which version applied.
Who it concerns
All users
Personal data
Type of acceptance, whether it was given, version identifier, timestamp, and IP address and user agent.
Legal basis
Legal obligation (Art. 6(1)(c))Accepting the terms of service is not in itself consent under the GDPR. We log the acceptance to meet our accountability obligation under Art. 5(2) and Art. 7(1).
Recipients
No external recipient — the log is stored with our hosting provider within the EU/EEA.
Retention
IP address and user agent are removed after 12 months. The acceptance itself — type, version and timestamp — is retained for as long as the account exists.
Responsibility
Breakout is the controller

A7Request to change role

Purpose
Let a user apply to change account type — for example from player to trainer — and let us assess the application before the change is made.
Who it concerns
Users applying to change role
Personal data
The current and requested role, a free-text motivation the user writes themselves, the status of the application, who decided it and when, and any reason given on rejection. The free-text field is required and is read by us — what it says is up to the user.
Legal basis
Performance of a contract (Art. 6(1)(b))
Recipients
Our administration.
Retention
Retained for as long as the account exists, as a record of why a role was changed.
Responsibility
Breakout is the controller
If you are 13–17
Some roles cannot be applied for by anyone under 18 — the application then cannot be submitted.

A8Signing in with Apple or Google

Purpose
Let you create an account and sign in with an account you already have, instead of choosing yet another password.
Who it concerns
Users who choose to sign in with Apple or Google
Personal data
Which provider was used, the user ID the provider gives us for Breakout specifically, and the email address present when the link was made. We never receive the password. If you use Apple’s option to hide your address, we receive a relay address instead of your real one.
Legal basis
Performance of a contract (Art. 6(1)(b))The processing takes place so you can sign in the way you chose. If you choose email and password instead, it does not take place at all.
Legal basis, ages 13–17
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Giving the young person a way to sign in that does not require yet another password to remember, which is the most common reason an account becomes inaccessible.
Recipients
Apple and Google respectively, as identity provider for the sign-in you start yourself (named in section 13). Data goes to them only at the moment you sign in, and they receive nothing about what you do in the app.
Retention
The link is retained for as long as the account exists or until you disconnect the provider. It is deleted when the account is deleted.
Responsibility
Breakout is the controller
If you are 13–17
Age is checked in Breakout and not at the provider. An account created via Apple or Google goes through the same age question and the same limits as one created with email — the sign-in method is never a way around them.

§4. Profile and content

The service itself: your profile, the clips you publish and the social activity around them.

Show all 8 processing operations in detail

B1Basic profile

Purpose
Show who you are in the app with a name and profile picture, and determine your age because it governs which safeguards apply to the account.
Who it concerns
All users except club accounts
Personal data
First name, last name, exact date of birth, gender (optional) and profile picture. Derived: your age, which is calculated from the date of birth and not stored separately.
Legal basis
Performance of a contract (Art. 6(1)(b))
Legal basis, ages 13–17
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Providing the player profile the young person created the account for, with the safeguards for minors switched on from the outset.
Recipients
Other users, according to your visibility settings. The profile picture is screened automatically by our content-screening provider (EU) — see sections 8 and 13.
Retention
Retained for as long as the account exists.
Responsibility
Breakout is the controller
If you are 13–17
The first time a date of birth is entered for someone under 18, the account is set to private and visibility to scouts and trainers is switched off. The age then follows the visibility of the profile: while the account is private, outsiders see no age at all, and those you let in — followers you have accepted, verified trainers and scouts you have opened up to, and you yourself — see your age in years.

B2Optional sports profile

Purpose
Let you complete your player profile with the sports details you choose yourself, so the profile shows what you want it to show.
Who it concerns
Players, trainers and scouts
Personal data
Position and other positions, club and club history, league or division, shirt number, preferred foot, strengths and weaknesses, bio, height, weight, nationality, region and city. For trainers and scouts also licence details, specialisations, years of experience and scouting networks.
Legal basis
Performance of a contract (Art. 6(1)(b))Every field is optional. Leaving them blank only affects how well your profile appears in search — never your access to the app.
Legal basis, ages 13–17
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Letting the young person decide for themselves what the profile shows, which is the service they sought out.
Recipients
Other users, according to your visibility settings. Region and city are never shown to other users — they are only used as filters in scouts’ searches.
Retention
Retained for as long as the account exists.
Responsibility
Breakout is the controller

B3Upload and publish clips

Purpose
Store and display the training clips you choose to publish.
Who it concerns
Players, and other people appearing in the clips
Personal data
Video file and thumbnail, title, description, location if you provide one, and the classifications you choose: position, skill category, match context, foot, phase of play, level, your own attribute words, type of clip, what happens in the clip, shirt number and shirt colour, game format, camera angle, opposition level and recording date. None of the selectable values says anything about your health. Generated: internal video ID, counters for likes, comments and views, and the clip’s duration and picture size. The recording date is prefilled for you from the file’s own creation date where there is one — you can always change it. From the recording date and your date of birth we also derive how old you were in the clip.
Legal basis
Performance of a contract (Art. 6(1)(b))
Legal basis, ages 13–17
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Providing the core feature — publishing and displaying training clips — for the young person who created the account for exactly that.
Recipients
Other users according to your settings. The video file is stored with our file-storage provider within the EU/EEA and screened automatically (see section 8).
Retention
Retained until you remove the clip or delete the account. The file is then also removed from the file-storage provider.
Responsibility
Breakout is the controller
If you are 13–17
How old you were in the clip is not shown to other users if you are under 18 — it goes only to you, to verified trainers, scouts and clubs, and to a guardian with an approved link. The same rule as for the age on your profile.

B4Comments, likes, follows and blocks

Purpose
Let you comment on, like, follow and block other users.
Who it concerns
All users
Personal data
Comment text with thread structure and any edit timestamp, likes, follow relationships per sport, follow requests and blocks. Your name and profile picture are shown alongside what you write.
Legal basis
Performance of a contract (Art. 6(1)(b))
Legal basis, ages 13–17
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Enabling the social interaction around content that the user sought out the service for.
Recipients
Other users.
Retention
Comments are retained until you remove them or delete the account.
Responsibility
Breakout is the controller

B5View counting and popularity

Purpose
Count how many times a clip has been viewed and calculate what is popular right now.
Who it concerns
All users
Personal data
One row per view with video ID, user ID where available, a session identifier and how long the clip was watched. Separately, how often a clip was shown in each feed is counted per day — those rows hold no information about who saw it. Generated: aggregated counters per clip and a trending score.
Legal basis
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Being able to show relevant content and give the uploader feedback on its reach.
Recipients
Aggregated counters are shown to other users. Individual view rows are never shown to others. How often a clip was shown in the feeds is visible only to the person who uploaded it.
Retention
Individual view rows are deleted after 12 months, feed-impression counters after 13 months. Aggregated per-clip counters are retained.
Responsibility
Breakout is the controller

B6Feed ranking

Purpose
Order the content in the Latest, Popular and Following tabs, and apply your choice of gender-matched feed if you made one.
Who it concerns
All users
Personal data
Trending score per clip, your follow relationships, your sport selection, your blocks and the gender-matched feed setting.
Legal basis
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Showing content that is relevant to you, without profiling you for advertising purposes.
Recipients
Other users, but never content from a private account: clips from private accounts appear in Latest and Popular only to those who follow the account, and to the account itself.
Retention
The trending score is recalculated every hour and replaced.
Responsibility
Breakout is the controller
Automated processing
Popular is ranked automatically based on views, likes, comments, new followers and how many trainers and scouts have viewed the profile, with weight decaying over time (seven-day half-life). This concerns the popularity of content, not individual advertising profiling. There is no advertising and no ad SDK in the app.

B7External share link

Purpose
Let you share a link to an individual clip outside the app.
Who it concerns
Players who share a clip
Personal data
The clip’s title, description, thumbnail and video file, plus the uploader’s name and profile picture.
Legal basis
Performance of a contract (Art. 6(1)(b))The feature is not available to minors: a share link does not work if the uploader is under 18 or has a private account.
Recipients
Anyone who has the link.
Retention
The link stops working when you remove the clip or make the account private.
Responsibility
Breakout is the controller

B8Your statistics summary

Purpose
Summarise your own activity day by day so you can follow how your account develops over time, even after the underlying rows have been pruned.
Who it concerns
Players
Personal data
One row per day and sport with number of views, unique viewers, total watch time, likes, likes from scouts and trainers, comments, profile visits, number of people who visited the profile, new followers, total follower count, watchlist additions, published clips and how often the clips were shown in the feeds. No other users’ names are included.
Legal basis
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
So you can see your own development over a longer period than the individual rows are kept. The summary is less intrusive than the raw data it replaces: it contains only counts, no information about who did what.
Recipients
Only you. The summary is never shown to other users and is not used in feed ranking.
Retention
The summary is deleted after 36 months, or when you delete your account. Outliving the individual rows is its whole purpose — otherwise your history would disappear after a year.
Responsibility
Breakout is the controller

§5. Your own development

Breakout includes game elements that help you follow your development: experience points (XP) for activities, levels calculated from the points, achievements for milestones, and streaks for consecutive days. The cards below show exactly what data this creates and what is visible to others.

Show all 8 processing operations in detail

C1Experience points, levels, achievements and streaks

Purpose
Let you follow your own development in the app over time.
Who it concerns
Players
Personal data
Experience points (XP) you earn from activities in the app, such as uploading a clip, gaining a follower or being viewed by a scout. One history row per point-earning event with amount, event type and what caused it. Level and level tier calculated from the points. Achievements you have unlocked. Streak, meaning how many consecutive days you have been active.
Legal basis
Performance of a contract (Art. 6(1)(b))
Legal basis, ages 13–17
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Giving the young person feedback on their own development, which is one of the features the account was created for.
Recipients
Level, level tier and total points are shown to other users on your profile. The history behind the points is shown only to you.
Retention
Retained for as long as the account exists.
Responsibility
Breakout is the controller

C2Public leaderboard

Purpose
Show a leaderboard of the hundred users with the most experience points.
Who it concerns
Players on the leaderboard
Personal data
First name, last name, profile picture, total points, level and level tier.
Legal basis
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Encouraging activity in the app through a visible leaderboard.
Recipients
All signed-in users.
Retention
The leaderboard is calculated on each request and is not stored separately.
Responsibility
Breakout is the controller

C3Reminders to complete your profile

Purpose
Remind you to complete your profile, and award points once it is complete.
Who it concerns
Players with an incomplete profile
Personal data
Which fields are missing, the time of the last reminder, the number of reminders, and whether points for a completed profile have been awarded.
Legal basis
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Helping you get a profile that works for its purpose, with a cap on how often we remind you.
Recipients
None. The reminder goes to you.
Retention
Retained for as long as the account exists.
Responsibility
Breakout is the controller

C4Referral codes

Purpose
Handle referral codes so that whoever invited you can be credited for it.
Who it concerns
Users who invite or are invited
Personal data
Your own referral code, the code you entered at registration, and the link between the inviter and the person who registered.
Legal basis
Performance of a contract (Art. 6(1)(b))
Legal basis, ages 13–17
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Being able to credit a referral to the right person.
Recipients
The person who invited you sees that the referral went through.
Retention
Retained for as long as the account exists.
Responsibility
Breakout is the controller

C5Training plans

Purpose
Let you create training plans and share them via a link if you want to.
Who it concerns
Users who create training plans
Personal data
The plan’s content, a share code, whether the plan is public, and likes on it.
Legal basis
Performance of a contract (Art. 6(1)(b))
Legal basis, ages 13–17
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Providing the planning feature the user chose to use.
Recipients
Other users if you make the plan public or share its code.
Retention
Retained until you remove the plan or delete the account.
Responsibility
Breakout is the controller

C6Daily wellness check-in (health data)

Purpose
Let the player rate each morning how their body feels, and derive a daily figure and a personal baseline to compare against — so the player can see their own patterns over time.
Who it concerns
Players who switch the feature on themselves, and in some cases their guardians filling it in for them
Personal data
Hours of sleep, plus ratings on a five-point scale of sleep quality, fatigue, muscle soreness, mood and stress. An optional note about the day. Whether the player marked themselves available to train. Date, time zone and the time the answer was given, plus the time consent was given. Derived and stored: a daily figure calculated from the ratings, which formula version was used, a baseline calculated from the player’s own earlier answers, and the deviation from it. Every row records both who the answer is about and who submitted it, so a guardian can fill it in for a younger child. The ratings and the note are data concerning health.
Legal basis
Consent (Art. 6(1)(a))Explicit consent under Art. 9(2)(a). The feature is off until the player switches it on, the consent is logged with a timestamp on every row, and it is withdrawn by switching the feature off. No other part of the app requires it — had it done so, the consent would not be freely given.
Recipients
Nobody but the player, unless the player expressly shares with their team — see E8. A guardian with an approved link sees the summary for children under 16, and the individual answers and the note only for children under 13.
Retention
Three clocks, the shortest for the most sensitive. The player’s own note is deleted after three months — it is the one field where someone can write something we never asked for, such as a diagnosis or a family situation, and no purpose needs it three months later. The ratings are emptied after twelve months while the row remains with its date and its daily figure, because that is what a personal development curve is made of. The row itself is deleted after three years. Everything is deleted the moment the account is deleted.
Responsibility
Breakout is the controller
If you are 13–17
Most people using the feature are aged 13–17. Age governs what a guardian may see: under 13 the guardian sees everything including the note, from 13 to 15 only the summary, and from 16 nothing unless the young person shares it themselves. The line exists so that a 15-year-old can write the truth about how they feel without it reaching home — a check-in the parent reads is a check-in nobody fills in honestly.

C7Training log and load

Purpose
Let the player log how long and how hard each session was, and derive the week’s total load and how it compares with the weeks before.
Who it concerns
Players who log their sessions, and in some cases guardians logging for them
Personal data
The session’s date, time zone and type, which sport it was, its length in minutes and an exertion rating on a ten-point scale. An optional note about the session. Whether the session was logged after the fact. Which of the team’s events the session belonged to, where it did. Derived and stored: the session’s load as length times exertion, and weekly totals calculated from the rows.
Legal basis
Performance of a contract (Art. 6(1)(b))
Legal basis, ages 13–17
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Giving the young person a picture of their own training volume over time, and the coach a basis for planning the week without adding more work than the body has kept up with.
Recipients
The player sees everything. A coach of a team the player belongs to sees the weekly total per player and how much of it came from the team’s own sessions — never the individual sessions, their type, their dates or the note. A session logged outside the team therefore appears only as part of a weekly total. Load is never presented as a risk or a warning.
Retention
The note on a session is deleted after three months, on the same clock as the check-in note: "knee has hurt since Tuesday" is a sentence about a body whichever table it is written in, and the table it landed in must not decide how long we keep it. The rest of the session is performance data of the same kind as attendance and lives as long as the season it belongs to — the whole point of a development curve is that it outlives the weeks it was measured in. Everything is deleted when the account is deleted.
Responsibility
Breakout is the controller
If you are 13–17
A guardian can log a session for a younger child, and the row then records both who the session is about and who wrote it.

C8Tactics boards

Purpose
Let a coach draw up drills and moves and save them for the next session.
Who it concerns
Coaches who create tactics boards
Personal data
The board’s name, which sport it is for, and the drawing itself: the positions of the pieces, arrows, lines and colours. Each piece may carry a label of at most three characters — a shirt number or a pair of initials — which is not room for a name or a message, and is why the board does not need to be screened as content.
Legal basis
Performance of a contract (Art. 6(1)(b))
Legal basis, ages 13–17
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Providing the drawing feature the coach chose to use.
Recipients
Nobody. A board is visible only to whoever created it — the server refuses every attempt to read someone else’s.
Retention
Retained until the coach removes the board or deletes the account.
Responsibility
Breakout is the controller

§6. Discovery and scouting

This is the core of Breakout: players being seen by trainers, scouts and clubs. It is also where your choices matter most. Verified trainers and scouts differ from ordinary users in that we have manually reviewed their identity and credentials, and in that they have search and monitoring tools others do not. What they can see is governed by your settings.

Show all 8 processing operations in detail

D1Visibility to trainers and scouts

Purpose
Make your profile and clips available to verified trainers, scouts and clubs, so that you can be discovered.
Who it concerns
Players
Personal data
Name, profile picture, age, gender, nationality, height, weight, the entire sports profile, your clips, and counters for followers, likes and number of clips.
Legal basis
Performance of a contract (Art. 6(1)(b))
Legal basis, ages 13–17
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Offering the exposure to trainers and scouts that is the whole point of the young person creating the account, limited by the safeguards for minors.
Recipients
Verified trainers, scouts and club accounts. What sets them apart from other users is that these accounts have been manually reviewed by us and have access to search and scouting features that ordinary player accounts do not.
Retention
Retained for as long as the account exists.
Responsibility
Breakout is the controller
If you are 13–17
Accounts for 13–17-year-olds are private by default, and the settings Visible to scouts and Visible to trainers are OFF by default. A minor is therefore not visible to trainers and scouts until they actively switch it on themselves in settings. The default is applied the first time a date of birth is entered.

D2Player search and filtering

Purpose
Let verified trainers and scouts search for players and filter on the details the player entered themselves.
Who it concerns
Players
Personal data
Age, gender, nationality, city and region, position, preferred foot, height, weight, league and club. In the clip search also the clip’s own tags: type of clip, what happens in it, game format, camera angle, opposition level, the attribute words you wrote yourself, whether the clip points out a player by shirt number, and when it was filmed — both as a range and as a most-recently-filmed sort. No searchable detail concerns health.
Legal basis
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Letting trainers and scouts find players matching what they are looking for, with an age floor of 13.
Recipients
Verified trainers, scouts and club accounts.
Retention
The search itself is not stored, other than when the scout actively saves it (see D4).
Responsibility
Breakout is the controller
If you are 13–17
Players under 13 never appear in search results, and a specified age range cannot be set lower than 13.

D3Automated player suggestions and weekly list

Purpose
Give scouts automatically generated suggestions of players who are active and getting attention right now, plus a weekly list curated by our team.
Who it concerns
Players
Personal data
Number of profile views from trainers and scouts over the last seven days, likes on the sports profile, and views on clips. The player is shown with name, age, position, club, nationality, followers, likes and number of clips.
Legal basis
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Highlighting players who are active — the feature scouts pay for and which gives players exposure.
Recipients
Verified scouts.
Retention
The lists are calculated continuously and are not stored.
Responsibility
Breakout is the controller
Automated processing
The suggestions are generated automatically from attention over the last seven days. The weekly list combines the same data with a manual selection by our team. Appearing in a list is no promise of contact, scouting or recruitment.
If you are 13–17
Minors and private players are filtered out of the suggestions, with an age floor of 13.

D4Saved searches with notifications

Purpose
Let a scout save a search and be notified when new players match it.
Who it concerns
Players matching the search
Personal data
The search filters, whether notifications are on, the time of the last notification, and the number of matches at the last run.
Legal basis
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Preserving the scout’s work and notifying them when new players match the criteria the scout chose.
Recipients
The scout who created the search.
Retention
Retained until the scout removes the search or deletes the account.
Responsibility
Breakout is the controller
If you are 13–17
Minors and private players are filtered out of the weekly notifications, with an age floor of 13.

D5Scouts’ own notes and watchlists

Purpose
Let a scout or trainer keep their own notes on players, collect them in a watchlist and compare them with each other.
Who it concerns
Players
Personal data
Which player was added, a free-text note written by the scout, and which players are set against each other in a comparison.
Legal basis
Legitimate interests (Art. 6(1)(f))The scout, trainer or club is the controller for their own notes and determines the purpose and legal basis. Breakout processes the data on their instruction under a data processing agreement.
Our legitimate interest
The scout’s or club’s interest in documenting their own assessment work.
Recipients
Only the scout, trainer or club who created the note. The fact that a player is on someone’s watchlist is never shown to the player and is not included in the player’s data export, because that information primarily reveals the scout’s work.
Retention
Retained until the scout removes the entry, or until either account is deleted.
Responsibility
Breakout is the processor

D6Player ratings

Purpose
Let verified trainers and scouts rate a player’s attributes on five scales, and show the player an average.
Who it concerns
Players
Personal data
Ratings for defence, passing, strength, shooting and technique, who gave the rating, and in some cases a free-text comment. Generated: an average rating that is calculated and shown on the sports profile.
Legal basis
Legitimate interests (Art. 6(1)(f))The trainer, scout or club is the controller for their own assessment. Breakout is the controller for the average we calculate and display.
Our legitimate interest
The trainer’s or scout’s interest in documenting their assessment, and the player’s interest in receiving feedback on their development.
Recipients
The player sees ratings they have received. Other trainers and scouts see ratings on player profiles. Other players never see ratings.
Retention
Retained until either account is deleted. You can switch off future ratings in settings; ratings already given can be hidden from the profile but remain in the system.
Responsibility
Breakout is the processor

D7Who viewed your profile

Purpose
Show you which trainers, scouts and clubs have visited your profile.
Who it concerns
Players and the trainers/scouts who visit profiles
Personal data
One row per visit with who visited, who was visited, sport and timestamp.
Legal basis
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Giving the player insight into who is showing interest, which at the same time makes scouts’ activity transparent to the person they are looking at.
Recipients
The player themselves, provided they have an active subscription. Aggregated statistics are also used in feed ranking and in player suggestions.
Retention
Individual visit rows are deleted after 12 months. The number of visits per day lives on in your statistics summary (B8), without any record of who visited.
Responsibility
Breakout is the controller

D8Contact requests

Purpose
Let a verified trainer, scout or club send a contact request with a message to a player.
Who it concerns
Players and the sending trainers/scouts
Personal data
Sender, recipient, message text, status and when the response was seen.
Legal basis
Performance of a contract (Art. 6(1)(b))
Legal basis, ages 13–17
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Enabling the contact that is the purpose of the service, inside the app where it can be moderated rather than outside it.
Recipients
The player and the sender.
Retention
Retained until either account is deleted.
Responsibility
Breakout is the controller

§7. Teams, events and tryouts

In this section the club or trainer is the controller and Breakout the processor, unless stated otherwise. The club is responsible, among other things, for informing people whose names are added to rosters without them holding an account.

There is exactly one place in the whole of Breakout where data concerning health may occur: when reporting an absence you may choose to give Sick or Injured as the reason. It is entirely voluntary, it is done on your explicit consent (Art. 9(2)(a)), and you tick a box stating who will see it before the reason is sent. You can remove it at any time by answering again and skipping the reason. An absence can always be reported without one. The details are in E7 below.

Show all 9 processing operations in detail

E1Team administration

Purpose
Let a trainer or club create teams, invite players and keep the team roster up to date.
Who it concerns
Players in the team and the team’s trainers
Personal data
Team name, description, team image, who owns the team, memberships with role and join date, and invitations with status.
Legal basis
Performance of a contract (Art. 6(1)(b)) and Legitimate interests (Art. 6(1)(f))The club or trainer is the controller and determines the legal basis — usually the membership agreement or the association’s legitimate interest. Breakout processes the data on their instruction.
Our legitimate interest
The club’s interest in administering its teams.
Recipients
The team’s members and the trainer or club administering the team. A club account additionally sees the teams created by trainers on the club’s active trainer roster, because the club pays for those seats — read-only, and not teams the owner has marked private. The visibility is derived from the roster each time and never stored as a grant, so it ends the moment the trainer leaves the club.
Retention
Retained for as long as the team exists. If the team owner deletes their account, ownership is transferred so the team can continue.
Responsibility
Breakout is the processor

E2Players without an account on the roster

Purpose
Let a trainer add the names of players who do not yet have an account, so the roster and squad selections are complete.
Who it concerns
People who have no Breakout account, usually children in the trainer’s team
Personal data
First and last name as free text, and position. If the person has been selected for a match, the coach may additionally record minutes played, goals and assists against the name — see E9, where that data is dealt with separately. It counts towards the team’s total playing time, because a total that leaves them out makes everyone else’s share too high.
Legal basis
Legitimate interests (Art. 6(1)(f))The club or trainer is the controller. Breakout processes the data on their instruction.
Our legitimate interest
The trainer’s interest in a complete roster and accurate squad selections.
Recipients
The team’s members and trainers.
Retention
Retained until the trainer removes the entry or the team is deleted.
Responsibility
Breakout is the processor

E3Events, attendance and squad selection

Purpose
Let a trainer create training sessions and matches, collect attendance responses and make squad selections.
Who it concerns
Players in the team and their guardians
Personal data
The event’s title, type, location, date and times, opponent and recurrence pattern, whether the event was cancelled, players’ attendance responses, and who was selected. Every response records both who the answer is about and who submitted it, so that a guardian can answer for their child — the trainer then sees the child’s name with a note of who answered. From those responses a per-player summary is derived for a chosen period: how many attended, how many were absent and how many did not answer. Where a player has voluntarily given a reason for an absence, that reason is included in the summary too — see E7, where the reason is dealt with separately. The summary can be narrowed to training sessions only or matches only, because they answer different questions. Where the event is a match, the coach may additionally record the result and playing time — see E9.
Legal basis
Legitimate interests (Art. 6(1)(f))The club or trainer is the controller.
Our legitimate interest
The club’s interest in planning and running the team’s activities.
Recipients
The team’s members and trainers, and guardians of players in the team. A club account sees the events of the teams the club has visibility into under E1 — which since August 2026 also covers teams created by the club’s own trainers and not marked private — but never the per-player summary. Club accounts are additionally refused event chat, realtime updates and answering attendance, each separately in the code.
Retention
Retained for as long as the team and the event exist.
Responsibility
Breakout is the processor

E4Event chat

Purpose
Let the team communicate in a chat attached to an event.
Who it concerns
Players in the team and the team’s trainers
Personal data
Message text, the sender’s name and ID, timestamp, and which messages have been read.
Legal basis
Legitimate interests (Art. 6(1)(f))The club or trainer is the controller.
Our legitimate interest
The club’s interest in being able to communicate with the team about a session or match.
Recipients
The team’s members. Our real-time messaging provider (EU) delivers the messages and in doing so processes the message text and the sender’s name.
Retention
Retained for as long as the team and the event exist.
Responsibility
Breakout is the processor

E5Tryouts and guardian approval

Purpose
Let clubs advertise tryouts and players apply, requiring guardian approval for the youngest.
Who it concerns
Players who apply and their guardians
Personal data
The tryout’s details (club, contact person, coach, address, city, gender, division, number of places, age range, deadline and date), the application’s status and notes, and which guardian approved it and when.
Legal basis
Performance of a contract (Art. 6(1)(b))
Legal basis, ages 13–17
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Connecting tryouts with players seeking them, with guardian approval as a safeguard for the youngest.
Recipients
The advertising club. Where an approval was required, the club also sees the guardian’s name and email address.
Retention
Retained until the account is deleted.
Responsibility
Joint controllership
If you are 13–17
For players under 15 an approved guardian link is required and the guardian must approve the application. After approval there is a 24-hour delay before the club sees the application, so the approval can still be withdrawn.

E6Calendar subscription

Purpose
Let someone follow their own team events in an ordinary calendar app instead of in Breakout, through a subscription link.
Who it concerns
Players, trainers, guardians and club accounts who have created a link themselves
Personal data
A random, secret string tied to the account, plus the events the account already has access to: title, type, location, date, times and whether the event was cancelled.
Legal basis
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
That someone who wants to see their training sessions alongside the rest of their life should be able to. The link is created only at the user’s own request and can be replaced at any time, which immediately renders the old one useless.
Recipients
Nobody except whoever holds the link. Calendar clients cannot carry a login, so the link is itself the key — anyone who obtains it can read the schedule without signing in. It should therefore be treated like a password, and it can be replaced in settings.
Retention
The link exists until the user replaces it or deletes their account. The feed shows events from the last two months onwards.
Responsibility
Breakout is the controller

E7Reason for an absence (health data)

Purpose
Let whoever reports an absence voluntarily say why, so the coach can plan the session and take an illness or injury into account.
Who it concerns
Players in the team who choose — themselves or through their guardian — to give a reason
Personal data
One of the options Sick, Injured or Other, an optional message of up to 200 characters, and the time the consent was given. Sick and Injured are data concerning health. The message is free text and may contain whatever the person writing it chooses to write. The reasons are also totalled per player in the coach’s season overview: how many were sick, injured, other, or gave no reason.
Legal basis
Consent (Art. 6(1)(a))Explicit consent under Art. 9(2)(a) for the health data. Consent is given in the app, in a box that must be ticked before the reason can be sent, and is withdrawn by answering again without a reason — which deletes the reason, the message and the record of the consent. The club or coach is the controller; the consent is obtained in the app on their behalf.
Recipients
The team’s coaches. Expressly not the club: a club account never receives these fields, not even for teams the club itself owns. Nor do the other players and guardians in the team.
Retention
The reason, the message and the record of the consent are deleted six months after the date of the event, while the absence report itself remains — a coach plans around next week’s absences, not around who had a cold two seasons ago. They are also deleted the moment the answer is changed without a reason, and when the event, the team or the account is deleted. Giving a reason is never required — an absence can always be reported without one.
Responsibility
Breakout is the processor
If you are 13–17
Most people giving a reason are aged 13–17. The reason may be given by the player themselves or by a guardian answering for their child, and either of them can remove it again. No reason is required in order to report an absence, and skipping it has no consequences.

E8Wellness shared with the coach (health data)

Purpose
Let a player who wants to show their coach how their body feels, so the coach can adapt the session to how the squad actually arrived.
Who it concerns
Players who choose to share their wellness with a particular team
Personal data
What the coach sees is governed by the level the player chose. At the lower level: a colour band saying whether today’s figure is near or below the player’s own baseline, and whether the player has answered today. At the higher level, additionally: the daily figure as a number, the baseline, the deviation, the individual ratings of sleep, fatigue, soreness, mood and stress, and the player’s own note about the day. The choice itself is stored as a row with a timestamp each time it changes.
Legal basis
Consent (Art. 6(1)(a))Explicit consent under Art. 9(2)(a), given per team and per level. The default is that nothing is shared. Consent is withdrawn by turning the sharing off, and the coach loses access immediately. Not sharing has no consequences for the player’s place in the team.
Recipients
The coaches of the team the player chose, and nobody else. Expressly not the club, not teammates and not guardians — the latter is governed by the age rules in C6 and is unaffected by this sharing. A team trend is shown only when at least three players in the team share, because an average over one or two players is those players.
Retention
The choice is stored as a history where the latest row applies, so it can be shown when sharing was turned on or off. The data itself is not stored a second time but read from the player’s own rows, and is therefore pruned on the clocks in C6 — a note older than three months cannot be shown to the coach either. Everything is deleted when the account or the team is deleted.
Responsibility
Breakout is the controller
If you are 13–17
Most people sharing are aged 13–17. The decision is the young person’s own and does not require a guardian’s involvement; sharing with the coach and sharing with home are two separate choices that do not affect each other.

E9Match results and playing time

Purpose
Let a coach record how the match ended and how long each player was on the pitch, so the squad and the player themselves can see how playing time was distributed over the season.
Who it concerns
Players in the team, and people without an account listed on the roster — see E2
Personal data
About the match: home or away, type of match, the score for and against, and the match’s actual playing time in minutes. Per player: whether they started, came on, sat unused on the bench or were not there, minutes played, goals and assists, and who recorded the entry. Derived from this: the player’s share of the time they could have played, share of the team’s total playing time, number of starts, and goals or assists per ninety minutes.
Legal basis
Legitimate interests (Art. 6(1)(f))The club or coach is the controller. The data is performance data of the same kind as attendance — it says what a person did, not what their body is — and is therefore not covered by Art. 9.
Our legitimate interest
The club’s interest in following and showing how playing time is distributed, which is the question players and guardians ask most often, and the player’s own interest in seeing their season.
Recipients
The score is seen by the whole team, and by the club if the team belongs to the club under E1 — everyone present saw it. The distribution of minutes between players is seen only by the team’s coaches. The player themselves sees their own minutes, goals and assists and their share of the team’s total playing time, never a teammate’s row. That share is an aggregate and identifies nobody.
Retention
Retained for as long as the event and the team exist. That the data outlives the season is the intention — a development curve across three seasons is the whole point — and there is no free text here that would require a shorter period. The data is deleted when the account is deleted.
Responsibility
Breakout is the processor
If you are 13–17
The entry is written by an adult about a child, and the child sees it themselves in the app. That is deliberate: a figure about a young person that the young person cannot see is worse than no figure at all, and it therefore appears in the player’s own statistics the moment the coach saves it.

§8. Safety and moderation

Measures to prevent inappropriate content and protect minors in particular.

Show all 5 processing operations in detail

F1Automated content screening

Purpose
Screen every uploaded video and profile picture automatically, to prevent sexual, violent or otherwise inappropriate content from being published — above all to protect children.
Who it concerns
Everyone who uploads content, and people appearing in that content
Personal data
Six still frames from each video are sent for analysis. Generated and stored by us: which categories were flagged, the confidence per category and frame, the screening status, and the number of screening attempts.
Legal basis
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Protecting children and other users from inappropriate content. The interest weighs particularly heavily because the service is directed at minors and hosts user-uploaded video.
Recipients
Our automated content-screening provider (EU, Stockholm — named in section 13). Breakout’s moderators.
Retention
The screening result is retained for as long as the clip exists.
Responsibility
Breakout is the controller
Automated processing
The screening is fully automated. The frames are analysed by our screening provider in Stockholm and no copy is retained by the provider. Flagged content is hidden and then reviewed by a human. You may request one re-review, and on repeated flagging the case is always escalated to manual assessment. The decision has no legal effect on you.

F2Reports and manual moderation

Purpose
Receive and handle reports of content, comments and users.
Who it concerns
Reporters and reported users
Personal data
Who reported, what was reported, the stated reason, the case status, and who decided it and when. Generated: a counter of rejected clips.
Legal basis
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Maintaining a safe service for minor users and being able to act on what other users report.
Recipients
Breakout’s moderators.
Retention
Retained for as long as the account exists and deleted with the account. Suspended accounts are not deleted while the suspension needs to be enforced.
Responsibility
Breakout is the controller

F3Automatic down-ranking on multiple reports

Purpose
Hide a user’s content in the feed once enough distinct users have reported that person, pending review.
Who it concerns
Reported users
Personal data
The number of distinct users who have reported a person.
Legal basis
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Being able to quickly limit the spread of content many users experience as harmful, before a human has had time to review it.
Recipients
None.
Retention
The assessment is made on each request and is not stored.
Responsibility
Breakout is the controller
Automated processing
The measure is applied automatically once the number of reports exceeds a threshold. The decision has no legal effect and the account otherwise works as normal.

F4Account suspension

Purpose
Suspend accounts that breach the terms of service.
Who it concerns
Suspended users
Personal data
Whether the account is suspended, when it was suspended, the stated reason, and which administrator decided.
Legal basis
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Being able to enforce the terms of service and protect other users, especially minors.
Recipients
Breakout’s administrators.
Retention
The data is retained for as long as the suspension needs to be enforced.
Responsibility
Breakout is the controller

F5Screening of place names

Purpose
Screen the city names users enter themselves, so the shared list is not filled with inappropriate or made-up names.
Who it concerns
Users who submit or report place names
Personal data
The submitted name, who submitted it, the number of uses, the number of reports, and the reporter’s ID.
Legal basis
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Keeping the shared place-name list usable and free of inappropriate words.
Recipients
All users see approved place names in the pickers.
Retention
The place names are retained as a shared list. Reports are deleted with the reporter’s account.
Responsibility
Breakout is the controller
Automated processing
Names are checked automatically against a blocklist and simple plausibility rules, and are hidden automatically if enough users report them.

§9. Child protection and guardians

Breakout may be used from age 13. Player accounts for people under 13 are not permitted: registration is stopped when the date of birth indicates an age below 13, and if we discover such an account afterwards we delete it. Age is based on the date of birth you provide — we do not require identification, because a heavier check would process more data about every child than it protects. Once entered, the date of birth can only be changed with our approval.

We want to be honest about one limitation: at registration there is currently no technical check that a guardian has approved the account. Users aged 13–17 are expected to use the app with their guardian’s knowledge. The protection instead rests on the defaults below, on a guardian being able to link a guardian account with control over the child’s account at any time, and on guardians always being able to request deletion via dataskydd@breakoutsports.se. A verified approval mechanism is under development.

Show all 4 processing operations in detail

G1Linking a guardian to a child

Purpose
Link a guardian’s account to a child’s account, after one of them requested the link and the other approved it.
Who it concerns
Children and their guardians
Personal data
Which two accounts are linked, who requested the link, the status, and when it was answered. The link is made using the accounts’ internal IDs, and the two accounts must have different email addresses.
Legal basis
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Giving guardians a real ability to exercise their responsibility for the child’s account — one of the safeguards that carries the balancing test for 13–17-year-olds.
Recipients
The two linked accounts.
Retention
Retained until either party removes the link or deletes their account.
Responsibility
Breakout is the controller

G2Parental controls

Purpose
Let a linked guardian temporarily freeze the child’s account, request its deletion, and approve or decline tryouts.
Who it concerns
Children with a linked guardian
Personal data
Until when the account is frozen and who froze it, and whether and when deletion was requested and by whom.
Legal basis
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Enabling the guardian to intervene to protect the child without having to contact us.
Recipients
The guardian. The child is notified when the account is frozen.
Retention
Retained for as long as the account exists.
Responsibility
Breakout is the controller

G3Age assessment

Purpose
Determine whether you are at least 13 and whether you are under 18, because age governs which safeguards apply to the account.
Who it concerns
All users who provide a date of birth
Personal data
Exact date of birth, which you provide yourself. Derived: your age.
Legal basis
Legal obligation (Art. 6(1)(c)) and Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Being able to apply the minimum age of 13 and the stricter safeguards for minors. We need an exact date of birth because both the 13 and the 18 threshold must be determined reliably; an age bracket would not suffice. The information is not verified against any document — a heavier age check would mean processing more data about every child than it would protect.
Recipients
None. The age is used internally and shown on the profile according to your visibility settings.
Retention
Retained for as long as the account exists.
Responsibility
Breakout is the controller
If you are 13–17
Player accounts for people under 13 are not permitted. Once a date of birth has been entered you cannot change it yourself — a change must be requested and approved by us, which gives traceability.

G4Protective default settings for minors

Purpose
Set accounts for players under 18 to private from the outset and switch off visibility to scouts and trainers, so the child does not have to activate the protection themselves.
Who it concerns
Players aged 13–17
Personal data
The private-account, visible-to-scouts and visible-to-trainers settings, and your derived age.
Legal basis
Legal obligation (Art. 6(1)(c)) and Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Meeting the data-protection-by-default requirement in Art. 25 when the service is directed at children.
Recipients
None.
Retention
Retained for as long as the account exists.
Responsibility
Breakout is the controller
If you are 13–17
The settings are applied the first time a date of birth is entered. You can change them yourself in settings, and a banner in the app explains that the account is private. Accounts created before the rules were introduced have not been changed retroactively.

Beyond the cards above, for everyone under 18: clips from private accounts never appear in the public feeds for anyone but approved followers; minors and private players are filtered out of scouts’ search results, automated suggestions and saved searches; share links outside the app do not work for minors’ clips; and we never use minors’ data for advertising or ad profiling — the app contains no advertising at all.

§10. Communication

Email, push notifications and in-app notifications.

Show all 4 processing operations in detail

H1Transactional email

Purpose
Send the emails required for the account to work: verification code, password reset, deletion confirmation and your data copy.
Who it concerns
All users
Personal data
Email address and the message content. The language is chosen from your language preference.
Legal basis
Performance of a contract (Art. 6(1)(b))
Legal basis, ages 13–17
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Being able to reach the account holder on matters concerning the account’s function and security.
Recipients
Our email provider (named in section 13).
Retention
We do not store the messages. The email provider processes them under its own terms.
Responsibility
Breakout is the controller

H2Push notifications

Purpose
Send notifications to your device about activity concerning you.
Who it concerns
Users who enabled notifications
Personal data
Device token, device type, and when the token was last updated. Your notification settings: whether you want reminders before training sessions and matches and how far in advance they should arrive, whether you want to know when an event is moved or cancelled, and whether you want to receive messages from the club. The settings are included in the data export.
Legal basis
Consent (Art. 6(1)(a))Notifications are never enabled automatically. You give consent in the dialog shown by the operating system, and can withdraw it at any time in your phone settings.
Recipients
Our push relay and Apple’s and Google’s notification services (named in section 13).
Retention
The token is retained until you turn off notifications, change device or delete the account. Invalid tokens are removed automatically.
Responsibility
Breakout is the controller

H3In-app notifications

Purpose
Show in-app notifications about followers, comments, ratings, tryouts and challenges.
Who it concerns
All users
Personal data
Notification type, title, body, associated data, and when the notification was read.
Legal basis
Performance of a contract (Art. 6(1)(b))
Legal basis, ages 13–17
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Informing you about what happens on your account.
Recipients
You.
Retention
Deleted after 30 days.
Responsibility
Breakout is the controller

H4Messages from a club to its teams

Purpose
Let a club account send one and the same message to several of its own teams at once — for example about an annual meeting or the office being closed.
Who it concerns
Players, guardians and trainers in the teams the club selected
Personal data
The message’s subject and text, which teams and which recipient groups the club selected, how many were reached and when it was sent. The club sees the number of recipients, never a list of names. The content is written by the club and may contain whatever the club chooses to write.
Legal basis
Legitimate interests (Art. 6(1)(f))The club is the controller for the content of the message; we deliver it.
Our legitimate interest
The club’s interest in reaching the families in its teams with information about its activities. A recipient can switch these messages off in settings without losing notice that a match has been cancelled, and a club may send at most five messages per 24 hours.
Recipients
The selected recipients in the selected teams, and our push notification provider — named in section 13.
Retention
The message in the recipient’s notification list is pruned after 30 days. The club’s own send log — subject, text, selected teams and recipient count — is retained for as long as the club account exists, as a record of what the club actually sent.
Responsibility
Breakout is the processor

§11. Subscriptions and competitions

Show all 4 processing operations in detail

I1Subscriptions and purchases

Purpose
Handle purchases and subscriptions and give you access to the features your tier includes.
Who it concerns
Subscribers
Personal data
Subscription tier, validity period, product ID, a RevenueCat customer ID corresponding to your internal user ID, and receipt and event data from the store. We never store card details.
Legal basis
Performance of a contract (Art. 6(1)(b))The purchase is made in Apple’s or Google’s store and is subject to their age and payment rules. For minors, Swedish law normally requires the guardian’s approval for the purchase itself.
Recipients
Our subscription provider (named in section 13) plus the Apple App Store and Google Play.
Retention
Subscription history is retained for as long as the account exists.
Responsibility
Breakout is the controller

I2Accounting

Purpose
Meet the statutory bookkeeping obligation for the revenue the service generates.
Who it concerns
Subscribers
Personal data
The records required under the Swedish Bookkeeping Act. The records come from Apple and Google and are handled in our bookkeeping, not in the app.
Legal basis
Legal obligation (Art. 6(1)(c))
Recipients
Our bookkeeping and, where required, the Swedish Tax Agency.
Retention
Seven years under the Swedish Bookkeeping Act.
Responsibility
Breakout is the controller

I3Challenges and prizes

Purpose
Run time-limited competitions, rank the entries and award prizes.
Who it concerns
Players taking part in a challenge
Personal data
Your entry in the form of a video, the answers you give in the challenge form, and the likes, comments and views the score is based on. Generated: score, placement, whether you won, and a competition tier shown as a badge on your profile.
Legal basis
Performance of a contract (Art. 6(1)(b))
Legal basis, ages 13–17
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Being able to run the competition and award the prize to the right person.
Recipients
All users see the challenge leaderboard. Where there is a prize we may need to contact you in order to deliver it.
Retention
Retained for as long as the account exists.
Responsibility
Breakout is the controller
Automated processing
The score is calculated automatically from likes, likes from trainers and scouts, the number of distinct commenters, and views. In some challenges our team sets the score manually instead.
If you are 13–17
Uploading to a challenge requires a public account. A minor with a private account therefore cannot take part without first making the account public — a deliberate choice we have identified as a residual risk.

I4Marketing using your content

Purpose
Use a clip you uploaded in our own marketing, for example on social media or on our website.
Who it concerns
Players whose clips are used
Personal data
The clip and your name to the extent you approved.
Legal basis
Consent (Art. 6(1)(a))We always ask first, by email, and publish nothing before you say yes. You can withdraw your consent at any time.
Recipients
The channels where the material is published.
Retention
For as long as the consent applies. Material already published externally cannot always be retracted.
Responsibility
Breakout is the controller
If you are 13–17
If a player under 18 appears in the material, the guardian’s express approval is required before we publish anything — the child’s own yes is not sufficient for commercial use of their name and image.

Prizes in challenges are sometimes given as gift cards tied to a named store or chain, with a value that does not exceed the Swedish Tax Agency’s threshold for tax-free competition prizes (SEK 1,800 per prize occasion; applies for 2025 and 2026). The gift cards cannot be redeemed for cash. The prize is therefore tax-free for the recipient, and we do not need to collect personal identity numbers or report the prize to the Tax Agency. Should the value of a prize ever exceed the threshold, we contact the winner — and for a minor winner their guardian, in the same way as for tryout approvals — before the prize is handed over, since we may then need to process a personal identity number in order to file a statement with the Tax Agency.

§12. Operations, support and accountability

What is required for the service to work, to help you, and to demonstrate that we comply.

Show all 9 processing operations in detail

J1Error monitoring

Purpose
Detect and fix technical errors and crashes in the app and on the website.
Who it concerns
Users affected by an error
Personal data
Error message and stack trace, app version, device type and operating system, and which request failed.
Legal basis
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Keeping the service stable and fixing errors that affect users.
Recipients
Our error-monitoring provider (named in section 13).
Retention
Sentry processes error reports under its own terms. We do not send your identity to Sentry.
Responsibility
Breakout is the controller

J2Time of last activity

Purpose
Record when you were last active, so a club can see whether the trainer licences it pays for are being used and so we can assess whether an account is abandoned.
Who it concerns
All users, and club-affiliated trainers in particular
Personal data
Time of last activity. For club-affiliated trainers also the number of sign-ins.
Legal basis
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
The club’s interest in seeing whether assigned trainer licences are used, and our interest in being able to assess inactive accounts.
Recipients
The club account sees this for its own trainers.
Retention
The timestamp is overwritten on each new activity and is deleted with the account.
Responsibility
Breakout is the controller

J3Support and feedback

Purpose
Handle your support cases and the feedback you submit.
Who it concerns
Users who contact support
Personal data
The case content, the messages in the thread, who wrote them, and any attachments such as screenshots.
Legal basis
Performance of a contract (Art. 6(1)(b))
Legal basis, ages 13–17
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Being able to answer and resolve your case.
Recipients
Breakout’s support team.
Retention
Retained until the account is deleted.
Responsibility
Breakout is the controller

J4Administration of the service

Purpose
Let our administrators review verifications, handle reports, correct inaccurate data and manage accounts.
Who it concerns
All users
Personal data
All account data is accessible to authorised administrators. The administrator’s own sign-in time and IP address are recorded.
Legal basis
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Being able to operate and moderate the service and meet the obligations we have as a service provider.
Recipients
Authorised administrators at Breakout.
Retention
The data is deleted with the account.
Responsibility
Breakout is the controller

J5Handling your rights requests

Purpose
Receive and handle your requests for a data copy, erasure, rectification and changes to date of birth or club affiliation.
Who it concerns
Users exercising their rights
Personal data
Your email address, your request and stated reason, the IP address when the request is made via the web form, the handling status, and who decided the case.
Legal basis
Legal obligation (Art. 6(1)(c))
Recipients
Our data protection function. Our email provider when we reply.
Retention
Closed or rejected cases are deleted after 12 months. Pending cases are retained.
Responsibility
Breakout is the controller

J6Deletion and pruning

Purpose
Carry out account deletions and prune data that is no longer needed.
Who it concerns
Users deleting their account
Personal data
The scheduled deletion time and who requested it.
Legal basis
Legal obligation (Art. 6(1)(c))
Recipients
The files are also removed from our file-storage provider. The confirmation is sent via our email provider to the address the account had.
Retention
The account is deleted 30 days after the request. During the grace period the account is frozen, and you can change your mind by signing in again.
Responsibility
Breakout is the controller

J7Security and abuse prevention

Purpose
Protect the service and its users against unauthorised access, fraud and abuse.
Who it concerns
All users and visitors
Personal data
IP address and user agent at sign-in, registration and when logging terms acceptance, plus counters used to limit the number of attempts.
Legal basis
Legitimate interests (Art. 6(1)(f)) and Legal obligation (Art. 6(1)(c))
Our legitimate interest
Protecting accounts and the service against attacks, account takeover and abuse.
Recipients
Our hosting and web providers (server logs) — named in section 13.
Retention
IP address and user agent in the terms-acceptance log are anonymised after 12 months. Server logs are handled by the respective provider.
Responsibility
Breakout is the controller

J8Log of staff actions

Purpose
To be able to show afterwards which member of our staff opened, changed or downloaded data about an individual, so that improper internal access can be detected and investigated — and so that you can be told if you ask.
Who it concerns
Our staff with access to the administration tool. The data concerns their actions; the users the actions related to appear only as an internal ID number.
Personal data
Timestamp, which member of staff acted, their email address and permission role, which action it was, which internal ID it concerned, whether it succeeded or was refused, IP address, browser signature, and any search filters used. The content of what was displayed is never stored — the log records that a record was opened, not what it said.
Legal basis
Legitimate interests (Art. 6(1)(f)) and Legal obligation (Art. 6(1)(c))
Our legitimate interest
Being able to detect and investigate improper internal access to data about children. Without such a log there is no way to answer the question "who has looked at my child’s data" — and the Article 32 obligation to protect the data cannot be demonstrated.
Recipients
Nobody outside Breakout. The log can only be read by administrators — expressly not by support staff, since one of its purposes is to hold them accountable. In the event of an incident, its contents may be provided to the Swedish Authority for Privacy Protection.
Retention
Kept for 24 months and then pruned automatically. Longer than our other logs, because improper internal access is usually discovered long after the fact — normally because someone gets in touch. If you delete your account the entries are not removed: they describe staff actions, and your ID then points at nobody.
Responsibility
Breakout is the controller

J10Interest enquiries from clubs and coaches

Purpose
To be able to reply to someone who got in touch through the form on the website’s club, coach and scout pages, and to follow the conversation up from there. The free-text answer about what the club wants solved is also used as input when we decide what to build next — that is the whole point of asking.
Who it concerns
Representatives of sports clubs, coaches and scouts who filled in the form themselves. They have no account with us — clubs and coaches cannot register themselves — so the record is not linked to any user.
Personal data
What the person writes: the club’s name, the contact person’s name, email address, and optionally a phone number, their role at the club and the number of teams. In addition the free text about what they want solved and an optional further message. Automatically stored: which of the three pages the enquiry came from, the language the page was shown in, the sender’s IP address, and the case status with our own notes.
Legal basis
Legitimate interests (Art. 6(1)(f))
Our legitimate interest
Being able to reply to someone who asked. The person made contact themselves and provided the data for exactly that purpose, the data concerns them as a club representative rather than their private life, and a reply is precisely what they expect. Any contract that follows is entered into with the club as a legal person, not with whoever filled in the form — which is why this rests on legitimate interests rather than on contract. Against the processing stands the fact that the data remains for a time after the conversation ends; that is offset by the retention period being fixed and enforced by a job, by the IP address being there only as a guard against abuse of an open form, and by anyone who wants earlier erasure being able to ask for it.
Recipients
Nobody outside Breakout. The enquiry is sent as email to our contact address and stored in our database, where only administrators can read it in the administration tool. The person who filled in the form receives a receipt at the address they gave.
Retention
The enquiry is automatically deleted 24 months after it was received. An enquiry we have marked as spam is deleted after 30 days. If you want it removed sooner, just get in touch.
Responsibility
Breakout is the controller

§13. Recipients and transfers outside the EU/EEA

We never sell personal data, and only share it with the processors needed to run the service, with other users according to your settings, and with authorities where the law requires. Every processor is bound by a data processing agreement and may only process data on our instructions. Apple and Google are independent controllers for payments in their stores.

ServiceWhat it doesWhere
Laravel CloudHosting, API and databaseEU (Frankfurt)
Cloudflare R2Videos, images and documentsEU endpoint; SCC/DPF
AWS RekognitionAutomated content screeningEU (Stockholm)
ResendTransactional emailUSA; SCC/DPF
Laravel ReverbReal-time chatEU via Laravel Cloud
SentryError and crash monitoringUSA; SCC/DPF
RevenueCatSubscription statusUSA; DPF
Expo Push / APNs / FCMPush notificationsUSA; SCC/DPF
VercelThe breakoutsports.se websiteUS company, EU region; SCC/DPF
Payload CMS (Railway)Challenge content — normally no player dataUSA; SCC/DPF

All core data — the database and your files — is stored within the EU/EEA. Some processors are US-based; transfers to them are protected by the EU Commission’s Standard Contractual Clauses (SCC) or the EU–US Data Privacy Framework (DPF). You can obtain a copy of the safeguards via dataskydd@breakoutsports.se.

§14. Your rights

You always have the right to lodge a complaint with the Swedish Authority for Privacy Protection (IMY) if you believe we process your data incorrectly: imy.se, +46 8 657 61 00. You do not need to contact us first — but we hope you will, so we get the chance to put it right: dataskydd@breakoutsports.se.

RightHow to use it
Access and copy (Art. 15)“Export my data” in the app settings, or email us
Rectification (Art. 16)Edit directly in the profile; date of birth via a change request
Erasure (Art. 17)“Delete account” in the app — everything is erased after a 30-day grace period
Restriction (Art. 18)Email dataskydd@breakoutsports.se
Portability (Art. 20)The export is delivered in a machine-readable format
Objection (Art. 21)Against processing based on legitimate interests — email us; for visibility, the app toggles also apply
Withdraw consent (Art. 7)Push notifications: your phone settings. Marketing: reply to the request or email us

We respond within one month (Art. 12(3)). The export covers all personal data we hold about you. Other people’s data is included only in the form you already see it in the app — for example the names of your followers, but not which scouts have you on their watchlists, since that is primarily information about the scout’s work. Withdrawing consent does not affect the lawfulness of processing already carried out.

§15. Automated processing and profiling

We make no decisions with legal or similarly significant effects solely by automated means (Art. 22). Three automated features do affect what is shown: content screening (section 8), which is always followed by human review before an action stands and where you can request reassessment; feed ranking (section 4), which orders content by popularity — not by a profile of you as a person; and scouts’ automated suggestions (section 6), which are based on activity over the last seven days and never include minors or private accounts. No profiling is carried out for advertising purposes, for any user.

§16. Cookies and local storage

The website sets no cookies and we use no analytics or marketing tools — which is why we show no cookie banner. The only things stored in your browser are three strictly necessary entries for sign-in and registration. A complete list with lifetimes is at breakoutsports.se/cookies. Should we ever introduce analytics or marketing tools, we will update that page and ask for your consent before anything is activated.

§17. Changes to this policy

For material changes we notify you by email or in the app at least 14 days before the change takes effect. The version number at the top changes with every material revision, and previous versions can be requested via dataskydd@breakoutsports.se.