Privacy

Last updated: 7 September 2026.

Who we are

Papapetrou Patroklos & Co (SoftConf), Egnatias 154, 54636 Thessaloniki, Greece, operates basketlens. For anything in this notice, write to [email protected].

Two different roles

This matters, because it decides who you ask about what.

For accounts, we are the controller. If you have a sign-in, we decide what we hold about you and why.

For everything a club records about its players, the club is the controller and we are its processor. Positions, heights, birth dates, wages, availability and injury notes are entered by the club, for the club's own purposes. We store and process them on the club's instructions and do not use them for anything of our own. If you are a player asking about your data, ask your club — they decide, and we act for them.

What we hold

About account holders: your email address, your name and profile picture as Google gives them to us, your club and whether you are an operator, the questions your club has asked and when, your saved answers, and for each sign-in a session record with your browser's user-agent string.

About players, on behalf of clubs: the player's name and federation registration number, which arrive in the official box scores; and where the club fills them in — position, height, birth date, monthly wage, availability, an injury note, and an expected return date. Also the dates a player joined or left a club, and coach changes, where the club records them.

Game data — box scores, fixtures, standings — comes from the federation's own published records.

Why

Accounts: to give you access to a service you asked for, and to enforce your club's question allowance. Player data: on your club's instructions, so that it can run its own squad.

Who else sees it

Google, when you sign in. We use Google sign-in and never see or store a password.

Anthropic, when the Ask feature answers a question or a match report is generated. This is the one worth reading carefully: the model is sent the data needed to answer, and for squad questions that includes player names, positions, monthly wages and availability status. Anthropic processes it in the United States and does not train on it. If your club would rather this data never left, tell us — the feature can be limited for your club.

Railway, which hosts the application and the database. Everything is stored in the European Union.

So the Anthropic call above is the only point at which any of this leaves the European Union, and it carries only what a question needs — never the whole database.

Nobody else. We do not sell anything to anybody, and there is no advertising or analytics tracking in this application.

How long

Sessions expire on their own. Everything else we keep while your club uses the service, and delete on request. A withdrawn invitation ends the person's access immediately; their account and what they wrote — saved answers, recorded transfers — are kept unless deletion is asked for, because they are part of the club's own records.

Your rights

You can ask for a copy of what we hold about you, ask us to correct it, or ask us to delete it. Write to [email protected].

For player data, ask the club. They decide; we do what they instruct. If you write to us about a player, we will pass the request to the club and tell you we have.

Published game records are kept. Names, appearances and statistics come from the federation's own published box scores, and we keep them as a record of the competition — the same way a newspaper keeps its results pages. Removing a player from a box score would not protect anybody; it would make the record of that game wrong. This does not extend to anything a club records privately: a wage, a birth date or an injury note can be cleared, and the club can do it themselves from the roster screen.

You can also complain to the Hellenic Data Protection Authority.