EBLElite Basketball League

Privacy policy

Privacy policy

Updated 17 November 2026

This is the privacy policy of EBL, the Elite Basketball League’s app, on phones and on the web. The app is the league’s. OverPowered Electronix builds it for the league and publishes it on the App Store and Google Play. “We” here means the league and OverPowered Electronix.

Questions about your privacy, and requests to see or delete what you sent: hello@opinternational.dev.

In short

  • No account and no sign-in for anyone watching the league. The league’s staff sign in with the league’s invitation, never a password.
  • No advertising, no tracking across other apps or sites, nothing sold, and no analytics or advertising company receives anything.
  • No location, contacts or microphone. The camera and your photos open only when you choose: a photo of your own for a graphic, which stays on your phone unless you give it to the league; for the league’s staff, a team’s stat sheet after a game. Nothing else is read from your photos, and the app adds to them only what you save.
  • Notifications only if you switch a reminder on, and only the game nights and results you chose (for a signed-in player or coach, their own page’s daily notice, if they switch it on): never advertising or offers.

Kept only on your phone

The screens you open, so they open again with no signal; the reels you liked and have seen, and how often you watch each player and team, to order the Reels for you; the comments you wrote that are waiting to be read, the comments and photos you reported, the people whose comments or photos you blocked, and that you accepted the rules for comments; which reminders you switched on. None of this is sent anywhere, apart from the reminders, as below. Uninstalling the app, or clearing its data (in a browser, the site’s data), removes all of it.

Sent to the league’s server, and why

  • Reading the league’s record. The app asks for games, teams, players and statistics. Nothing about you is part of the question. The server reads the address a request comes from only to stop any one phone sending too much, holds it in memory, and never writes it down.
  • The Reels. To order the Reels and show the league what is watched, the app makes a random id on your phone (never your name, number or address) and sends it with what happens to each reel: shown, watched through, played again, swiped past, shared. The server counts these for each reel and keeps no id with them: the id is read only to stop one phone sending too many. A like is kept with the id, so that it counts once and can be taken back.
  • Sharing. A link you share from the app carries the name of the place you shared it to, such as WhatsApp or Instagram. When you send or save a file, and when someone opens the link, the server adds one to a count for that reel or game, that place and that day. No id is sent and none is kept.
  • Following. Following a player or a team needs no account. The app sends the league’s server the list of players and teams this phone follows, with the same random id, as you tap Follow and again when you open the app, at most once a day. The server keeps one row for each player or team a phone follows, so each page can show how many follow it, counting each phone once. It never shows who follows anyone. A follow taken back is deleted at once; a phone that has not opened the app for 270 days has its follows deleted, so the counts are of phones still following.
  • Opening a player’s or team’s page. The app adds one to a count for that page and that day, once a day on this phone. No id is sent and none is kept. A player, or a team’s coach, signed in with the league’s code, sees these counts for their own page.
  • Comments. A comment is sent with the name you type and the same id. Every comment is read by the league before it is shown; only an approved comment appears, with the name you gave, for everyone who opens that reel. The league can remove any comment. A report of a comment is sent with the same id and the reason you chose, and so is a block, which counts as a report. Each comment shown carries a code for its writer, made from their id so that the id itself is never shown, so you can block them. The league can block a phone that posts abusive comments: it can no longer comment, and none of its comments is shown.
  • A photo you give the league. A graphic you make with your own photo is drawn on your phone and the photo never leaves it. Only if you choose Give this photo to the league, and tick its words, is the photo sent: with the same id, the name you type for the credit if you give one, and what it is of (the game, the team and the player of the page you made it on). Before it leaves, your phone draws the photo again, which leaves behind where and when it was taken and on what; the league’s server takes any of that out again. No one but the league’s media officer and admin sees it until it is approved. An approved photo appears in the app on the player’s, the game’s and the team’s pages, with the name you gave, and may be used in the league’s graphics and posts. The words you tick say what a photo must not show (anything offensive, sexual, violent or hateful, or anyone’s private details), and the league takes down any photo that breaks them. You can take it down at any time, in Make a graphic under Your photos. A photo shown carries Report and Block, as a comment does: a report is sent with the same id and the reason you chose, and hides the photo on your phone; a block hides every photo and comment of that fan on your phone and counts as a report. Each photo shown carries the same code for its giver as their comments, never the id itself. The league can block a phone that gives abusive photos: it can give no more, and comment no more.
  • Game night reminders, in the Android and iPhone apps. Nothing is sent, and your phone is asked nothing, until you switch a reminder on: on Home, Game night reminders (30 minutes before tip-off) or Final scores; on a team’s screen, that team’s games. Your phone then asks whether EBL may send you notifications. If you allow it, the app gets a push token from Google’s Firebase Cloud Messaging: a code that lets a notification reach this app on this phone, and says nothing else about you. The app sends the league’s server that token, the same random id as the Reels, whether it is the Android or the iPhone app, and the reminders you chose; it sends them again when you open the app, at most once a day, so the server knows the phone still wants them. The server uses them for one thing: to send you the reminders you chose, half an hour before tip-off and each final score (no older than 36 hours). The website sends no notifications.
  • A player’s or coach’s own daily notice, in the apps. A player, or a team’s coach, signed in with the league’s code, can switch on a notice about their own page (a coach’s, their team’s): at most once a day, how many new followers it had and how often its page and plays were shared or saved, in numbers only, never naming anyone, and when its followers reach a round number. Switched on, the server keeps their account with this phone’s push token and the page it is for. Switching it off, deleting the account or switching every notification off deletes that.
  • The league’s staff. The league’s admin, media officer, stream operator, scorers, players, and each team’s coach, scout and analyst sign in with a code the league’s admin gives them. Their account holds the name the league’s admin entered for them; their role, with the team a coach, scout or analyst works for, or the player a player is; and the devices they are signed in on: whether each is the app or a browser and on which phone system, when each signed in, and when it was last seen. Nothing else: no password, e-mail address or telephone number. The device keeps its sign-in in the app’s own storage on that device; the server keeps only a scrambled form of it, which cannot be turned back into it. A team’s staff may keep their game plan on their accounts, read by that team’s staff alone. A staff member’s name is seen by the league’s staff only, and nothing public names them. The league keeps a record of each change to the accounts (an invitation, a role given or withdrawn, a device signed in or out, an account deleted), by the account’s number and never by a name. The address a code is tried from is held in memory to limit tries, and never written down.
  • The stat sheets. After each game the league’s admin or media officer photographs each team’s courtside stat sheet, in the app or on the website. The photograph is sent at full size to the league’s server, where the league’s reader straightens it and reads its tallies; a staff member then checks the figures and confirms them. The photograph, the straightened page and the figures are kept with the league’s record of the game, with the name of the staff member who sent it and of the one who confirmed it. A sheet shows the players’ names and numbers as the league’s table wrote them, and nothing about whoever took the picture. A demo’s sheets are seen by that demo alone and deleted with it.
  • The courtside scorer. For the league’s statisticians, by the league’s invitation. The game’s log is kept on the phone after every play, and sent to the league’s server only from a phone the league has given a seat or a key. It holds the game’s plays on the league’s own rosters, and the name a scorer signs a correction with.

Video

The league’s games and moments play from the league’s own copies, on the league’s media server, wherever it holds one; the pictures of each moment come from there too. They carry nothing about you. Where the league holds no copy, and for its live stream: on the website, YouTube’s privacy-enhanced player is loaded on the screen that shows the video; in the app, no YouTube player is loaded, and “Watch on YouTube” opens YouTube outside the app. When YouTube is reached, it receives the request under Google’s privacy policy.

Who handles it for us

  • Amazon Web Services, in the United States, hosts the league’s server, the league’s media (through Amazon CloudFront, its content delivery network) and the app’s website. It holds and carries what this page describes for us alone, under the AWS privacy notice; like any host, it may keep its own records of requests, with the address they came from, for its security and operation.
  • YouTube, Google’s, only as the Video section says.
  • Google’s Firebase Cloud Messaging, only if you switch a reminder on, delivers the reminders, through Apple’s Push Notification service on an iPhone. It receives the push token and the reminder’s words; Firebase makes the token on your phone with an installation id of its own, under Firebase’s privacy and security terms. Firebase’s analytics are switched off in the app, and it keeps no record of your use of the app for us.
  • Nobody else receives anything from the app.

How long it is kept

  • Likes and comments, and the id and the name kept with them: while the reel is in the Reels, and for one season after it leaves them; then deleted, within a day. The Reels hold the current season’s reels, and a season’s reels leave them when the next season begins, so a like or a comment is kept until the season after next begins. A report goes with the comment it is about.
  • A phone the league has blocked from commenting or from giving photos: its id, for as long as the comment it was blocked for is kept, or for this season and the next.
  • A photo you gave the league, with the id and the name: until you take it down or ask for it to be deleted; one the league did not use, or took down, is deleted 30 days after. A report goes with the photo it is about.
  • What happens to each reel, what each shared link brought and each page’s visits: only as counts, with no id.
  • A follow, with the id: until you take it back, which deletes it at once; or after 270 days in which the app was not opened on that phone.
  • A player’s or coach’s daily notice: until it is switched off, the account is deleted, or the phone’s push token is.
  • A push token, with the id and the reminders chosen: until you switch your last reminder off, which deletes it at once from the phone and the league’s server; until the app is removed from the phone (Firebase then tells the server, which deletes it with the next reminder); or after 270 days in which the app was not opened. Turned off in your phone’s settings, it is deleted the next time you open the app.
  • A staff account: until it is deleted, by the person in the app or by the league’s admin when asked.
  • The scorer’s log: it is the league’s record of the game.
  • What is kept only on your phone: until you clear the app’s data or uninstall it.

Your choices

  • Watch without following, liking or commenting: the league then keeps nothing of yours, only each reel’s and each page’s counts.
  • Take a follow back where you made it, on the player’s or team’s page, the Reels or Watch: it is deleted from the league’s server at once.
  • Switch a reminder off where you switched it on, or turn off EBL’s notifications in your phone’s settings: with the last one off, the push token is deleted from the phone and from the league’s server.
  • Clear the app’s data, or the site’s data in your browser: the id and everything kept on the phone go, and a new id is made only if you use the Reels again.
  • Ask us to delete what your phone sent, or your staff account, as below.

Deleting what you sent

The league’s staff delete their own account in the app: Staff, on the foot of Home, then Delete your account. It removes at once their name, roles, every device signed in as them and any code of theirs not yet used. The league’s record is not changed by it: a decision or label keeps the initials typed with it, and a game plan stays the team’s. The league’s admin can delete an account on request too.

For what a phone sent, write to us with its id, shown on this page on that phone (or in that browser), and we delete what it sent: its follows, its likes, its comments, its reports and its push token.

How to ask, with the app or without it: Delete your data.

Children

The app is not made for children under 13, and we do not knowingly collect anything from them.

Security

Everything the app sends and receives travels encrypted (HTTPS).

Changes

When this page changes, its date above changes with it.

Questions

Write to hello@opinternational.dev. The Support page answers the common questions.