The short version: LOOHA does not know who you are, does not want to, and has not built anything that could find out.
Last updated 4 October 2026
No accounts. No cookies. No advertising. No trackers from other companies. No profile of you exists. Nothing about you is sold or shared with anyone.
LOOHA will never carry advertising from betting or gambling companies. That is a decision about what this project is for, not a limit imposed on it.
To know whether anyone is reading, LOOHA keeps a small set of counters. When a page is opened, one number goes up by one. The counter is filed under:
That is the entire record. There is no row per visit: if two people in Casablanca open the same player page on the same day, the count reads 2, and nothing anywhere says which two people. No IP address is stored. No cookie is set. No identifier is generated, on your device or on the server. There is no session token, no profile and no history.
When you tap the star beside a player, one number changes: the count of how many times that player's star has been pressed. It moves up by one, and back down by one if you un-tap it. His page shows that number once it is large enough to mean anything.
That is all that is sent. Not your country, not your device, not your language, not the site you came from — none of the things the page counter above records. A player's id and the number one. The list of players you follow is not sent and is not stored here. It stays in your browser, which is why following someone needs no sign-up and why your list does not appear on your other phone.
So the site can say this player has been followed 1,284 times, and cannot say who followed him, or how many separate people that is — somebody with a phone and a laptop counts twice. We would need to identify you to know the difference, and we would rather have the vaguer number.
When the summary page is opened or its text copied, and when the card page is opened or a card saved, one counter goes up. It is filed under which of those four things happened, the period or card size, the language, and — for a card — the handle typed onto it, which is the name the card is made to be posted under. Nothing about the person pressing the button is sent.
Knowing how much is read is not the same as knowing how many people read it, and that second question has an honest answer and a dishonest one. The dishonest one is to give every reader a number — a cookie, or a fingerprint built from your address and your browser — and follow it around. LOOHA does not do that.
Instead your browser keeps two yes-or-no answers, and sends only the answers:
Neither is a number that identifies you. Neither can be read by any other site. Neither can be turned back into a person, by us or by anyone who obtained the database. What comes out of it is a count of visits — so one reader on a phone and a laptop is two, and clearing your browser data makes you new again. That is the price of not tracking you, and it is worth paying.
Because the count is reported by a small script in the page, search engines and AI crawlers are not counted either. They do not run it.
When you leave a page, one more counter goes up: the seconds it was open, and how far down it was scrolled, in quarters. It is filed under the day and the kind of page — a matchday, a player — and nothing else. Not which player. Not your country, your device or your language. There is nothing in that row to join it back to anything.
Anything under two seconds is thrown away, and a tab left open is counted as thirty minutes at most. What this answers is whether people read the pages or bounce off the top of them, which is a fair question to ask about a website and needs no knowledge of who you are.
A city is more than a country, and we should say so plainly rather than bury it. The network already works out an approximate city from where your request entered — every website is told this, and it is how weather sites know roughly where you are without asking.
LOOHA records it once per visit, in a table of its own that holds three things: the date, the country and the city. No device, no language, no page, no returning flag. That separation is the whole safeguard: a city sitting beside four other details can single out one reader in a small town, and a city sitting alone cannot.
A town seen only once in the period is not named in the read-out; those are added together as "elsewhere". If you would rather not be counted at all, any browser setting or extension that blocks the request works, and nothing on the site depends on it.
Five things, and all of them are small:
None of them is an identifier, none is shared with anyone, and the language is never sent to us at all. Clearing your browser data removes all four.
LOOHA runs on Vercel (hosting) with a database at Neon, and the domain is served through Cloudflare. Like any web host, these process the technical request needed to deliver a page — including your IP address in transit — under their own privacy terms. LOOHA does not store that address or receive it in any usable form; the country and city above arrive already reduced to two letters and a name, and the address itself never reaches the code that does the counting.
Typefaces are loaded from Google Fonts, which means your browser contacts Google to fetch them. Match data comes from API-Football; that is a request LOOHA makes on its own servers, not something your browser does.
LOOHA publishes its own posts — match cards and videos — to its own accounts on Telegram, Instagram, Facebook, Threads, TikTok and YouTube, through each platform's official API. Only LOOHA's own accounts are ever connected. The access keys those platforms issue are kept on LOOHA's server, are never shown on any page, and are used for one thing: publishing LOOHA's posts and reading back the link to each post. No data about the people who see, like or comment on those posts is collected, stored or used by LOOHA.
Publishing to YouTube uses the YouTube API Services. By watching LOOHA on YouTube you are also covered by the YouTube Terms of Service and the Google Privacy Policy. The only Google account LOOHA connects is its own; its access can be withdrawn at any time from that account's security settings, and the key LOOHA keeps for it is deleted within seven days of being withdrawn.
Under the GDPR you have the right to access, correct or delete personal data held about you. LOOHA holds none, so there is nothing to retrieve and nothing to erase — that is not a refusal, it is the honest answer. If you believe otherwise, write and it will be looked into properly.
LOOHA publishes the professional match records of footballers who have represented Morocco: appearances, minutes, goals, assists, cards and the clubs they play for. This is information about their public professional activity, already published by the competitions they play in. Nothing private is collected, and nothing about anyone's personal life appears here. If you are a player listed on LOOHA and something is wrong, write and it will be corrected.
If this policy changes, the date at the top changes with it. If a change ever means collecting something new, it will be said plainly here first.