Version 1.0 · Last updated: 11 November 2026
Under Article 10 of the Turkish Personal Data Protection Law No. 6698 ("KVKK") and the Communiqué on the Procedures and Principles of the Duty to Inform, we, as the data controller, inform you about the personal data processed in the Tribündeyiz mobile application ("App").
1. DATA CONTROLLER
Tribündeyiz is provided by its developer, Mervan Yuşa Torlak, a natural person; "we" in this notice refers to him.
- Name: Mervan Yuşa Torlak
- E-mail (KVKK applications and support): info@tribundeyiz.com
- VERBİS: we are not required to register with the Data Controllers' Registry, under the Personal Data Protection Board's decision exempting data controllers whose annual number of employees and annual balance sheet total are below the thresholds set by the Board and whose main activity is not the processing of special categories of personal data.
2. PERSONAL DATA PROCESSED, PURPOSES AND LEGAL GROUNDS
2.1 Identity and account data
- Data: e-mail address, password (only as an irreversible hash), username, invite code, e-mail confirmation and sign-in records; when Sign in with Google or Apple is chosen, the identifier and e-mail address of that account; with Sign in with Google also the name and the link to the profile picture that Google shares (written automatically into the account record of the authentication infrastructure, Supabase Auth; not used in the App and not shown to anyone).
- Purposes: membership, authentication, account security, providing the App, answering support requests.
- Legal ground: being directly related to the conclusion or performance of a contract (KVKK Art. 5/2-c).
2.2 Profile data
- Data: profile photo, the club supported, national team, home city and country (only the city's centre coordinate, that is an approximate location), language and time zone.
- Purposes: creating the profile and showing it to friends and, if the user turned on "Public account", to all users, calculating leaderboards (friends, country, World and club fans) and statistics, measuring distances from the home city, notifications about your team's matches.
- Legal ground: KVKK Art. 5/2-c.
2.3 Location data
- Data: the device's location (latitude, longitude, accuracy), only while the App is open and if the location permission is given. For "I'm at the stadium" and the proof photo the precise location (GPS) is sent to the server and kept with the distance to the stadium, the stadium and match, the result of the attempt and the server time. For nearby matches, distances and, in the Feed, public photos from nearby stadiums and public accounts' plans for upcoming matches there the precise location is sent too, but not stored. When the App opens, the location is read on the device for the user's dot on the map and is not sent to the server at that moment.
- Purposes: verifying "I'm at the stadium" and proven visits (being within about 1 km of the stadium and within the match window), preventing fraud, showing nearby matches and distances, showing public photos from nearby stadiums and public accounts' plans for upcoming matches there in the Feed, showing the user's location on the map.
- Legal ground: KVKK Art. 5/2-c and the controller's legitimate interest (KVKK Art. 5/2-f). Location is not collected in the background. The location sent for distances, nearby matches and the Feed is not stored in the database. The location of a failed attempt is deleted after 1 day; the other periods are in section 7 of the Privacy Policy.
2.4 Visual data
- Data: live proof photo and its thumbnail, archive photos, profile photo; results of automated moderation and moderator decisions. EXIF/GPS data is removed from photos before upload.
- Purposes: building the collection and showing it to friends, showing approved live proof photos and archive photos to all users if the user turned on "Public account" (live proof photos also in the feed, with their stadium, match and like count), story, season summary and year summary cards, checking automatically and, when needed, by people that photos follow the rules and that archive photos are related to the match.
- Legal ground: KVKK Art. 5/2-c; for moderation KVKK Art. 5/2-f and legal obligation (KVKK Art. 5/2-ç). Photos are not processed for face recognition or biometric identification.
2.5 In-app activity data
- Data: visits (stadium, match, date, proven or archive), "I'm at the stadium" check-ins, "I'm going" plans, "I'm coming too" joins, likes, stadiums the user wants to visit, stadium ratings, missing-stadium reports, badges, missions, statistics and leaderboards.
- Purposes: providing the collection, feed, leaderboard, badge, mission, season summary and year summary features; if the user turned on "Public account", showing their approved visits, statistics, badges and season and year summaries to all users and showing their "I'm going" plans for matches that have not kicked off in the feed to people who are not their friends too; creating a plan for the match for a user who taps "I'm coming too" on the public plan of someone who is not their friend; showing a user who likes a photo or a post in the feed, with their username and profile photo, to the owner of that photo or post in its list of likes.
- Legal ground: KVKK Art. 5/2-c.
2.6 Social data
- Data: friend requests and friendships, the account privacy setting (whether "Public account" is on and, if so, since when), blocks, reports (reason and a note of up to 500 characters), additions through invite links and QR codes.
- Purposes: providing the friendship features (including showing friend lists), applying visibility rules, reviewing reports, community safety.
- Legal ground: KVKK Art. 5/2-c and f.
- Public account: this is optional and off by default, and your account stays private unless you turn it on; only if you turn it on in Settings › Privacy does your account become visible to all users the way a friend sees it (4.1), and you can turn it off at any time with the same setting.
2.7 Contact matching data
- Data: when "Find from contacts" is used, SHA-256 hashes of the e-mail addresses in the contacts, computed on the device and sent to our server.
- Purposes: finding acquaintances who use the App, at the user's request.
- Legal ground: KVKK Art. 5/2-f. Names and phone numbers in the contacts never leave the device; the hashes are not stored after matching, and only the number of hashes sent is kept for 2 days to prevent abuse.
- Being found by your e-mail: this is optional and off by default; only if you turn on "Let people find me by my email" (profile set-up or Settings › Privacy) do you appear, with your username and profile photo, in other users' contact matching, and you can turn it off at any time with the same setting.
2.8 Notification data
- Data: push token (FCM token), platform, App version, notification preferences and in-app notification history.
- Purposes: sending push and in-app notifications.
- Legal ground: KVKK Art. 5/2-c. The permission is managed in the device settings, the topics in the App's Settings.
2.9 Transaction security data
- Data: IP address, request time, device and App information, session data, abuse counters, crash reports (technical details of the error, App version, phone model, operating system and a random installation identifier; kept in Firebase Crashlytics for 90 days), the usage and performance metrics that the QR code scanner (Google ML Kit) sends Google on Android (device and App information, event types, error codes, a random installation identifier; the QR image is processed on the device and not sent).
- Purposes: information security, preventing abuse and fraud, debugging, answering requests from competent authorities.
- Legal ground: KVKK Art. 5/2-f, being expressly provided for by law and legal obligation (KVKK Art. 5/2-a and ç), the establishment, exercise or protection of a right (KVKK Art. 5/2-e).
We have no processing activity based on explicit consent.
3. METHOD OF COLLECTION
Personal data is collected electronically, by fully and partly automated means: from the information you enter in the App, from your device's location, camera, photo and contact features with your permission (location while the App is open, the others only when you start the related action), from the notification infrastructure, from server logs and from the App's crash reports. It may also be collected through other users when they send you a friend request, like your photo or a post of yours in the feed, tap "I'm coming too" on your plan, or report you. Match data comes from API-Football and contains no personal data.
4. TRANSFERS OF PERSONAL DATA
4.1 Other users
Your username, profile photo, your place on the leaderboards and your number of proven stadiums are visible to all users. Every user who has finished setting up their profile is listed, even with 0 proven stadiums, on the World (users of all countries), country and club fans leaderboards, and on their friends' Friends leaderboard; appearing on the country and club leaderboards also indirectly shows your country and which club you support. Your club, national team, city, approved visits, photos, plans, "I'm at the stadium" check-ins, badges, other statistics, season and year summaries and friend list are visible only to your friends; your friends can compare their own collection with yours and see the matches you both went to. When you become friends with someone, you appear in their friend list with your username and profile photo; their friends can see that list, and so can all users if their account is public, even if your own account is private. When you like a photo or a post in the feed, its owner sees you in the list of people who liked it, with your username and profile photo (nobody but the owner sees this list); this applies when you like a public photo or plan of someone who is not your friend too, even if your own account is private. You see who liked your own photos and posts in the same way. When you tap "I'm coming too" on the plan of someone with a public account who is not your friend, you get your own plan for that match; the owner of the plan is not notified, the owner and other users do not see your name, only the number of people who joined, while your own friends see you by name.
The only exception is "Public account", which you turn on by your own choice (it is off by default). While it is on, all users who are signed in, have finished setting up their profile and have not blocked you or been blocked by you see your account the way a friend you accepted sees it: your club, national team and city; your counts and all your statistics (your team's results at the matches you went to, the countries and cities you have been to, the scorers you saw live, the goals you saw, the kilometres you travelled); your place on the leaderboards, your badges and your league progress; your stadium collection, your visits at a stadium and your full match list; all your approved visits (your live proof photos, the matches you added to your archive and your archive photos); your season and year summaries; and your friend list, with your friends' usernames and profile photos. When you turn it on, what you added earlier becomes visible too. Your live proof photos are also shown, with their stadium, match and like count, in the feed of people who are not your friends, and you appear in the "Who's been here" list of the stadium where you took them with your username, profile photo and your number of visits and proof photos there, with the date of the latest. A photo you take during a match can be shown straight away to users going to the same match that day and on that stadium's "Who's been here" list, and can reveal that you are at that stadium right now. Your "I'm going" plans for matches that have not kicked off can be shown in the feed of people who are not your friends too, and reveal which match you plan to go to; a plan is shown to people who are not your friends only until the match kicks off.
People who are not your friends can like your live proof photos and your plans, tap "I'm coming too" on your plan (which gives that person their own plan for the match), and report any visit they can see (archive visits included) and you; they cannot comment or send messages. Their likes of your photos are notified to you in at most one summary a day, without the names of the people who liked them; you get no notification for their likes of your plans or for their joining. You see who liked your photo or plan in its list of likes, with their usernames and profile photos; people who joined your plan and are not your friends are shown to you and to others only as a number.
Your "I'm at the stadium" check-ins, your friends' comparison with you and the matches you went to together stay visible only to your friends, even with a public account; photos that are waiting for approval, in review or rejected, proven visits that are not approved or were rejected, the stadiums you want to visit and your missions are seen by nobody but you; a match you added to your archive is still shown, without the photo, while its photo is waiting for approval or after it was rejected. When you make your account private again, none of this is shown to people who are not your friends from then on; people who saw it before may still have it cached on their device or may have taken a screenshot, and a photo link someone obtained earlier can keep opening until you delete that photo.
Your city's coordinate is not shown to anyone. Blocked users do not see each other.
4.2 Recipients in Türkiye
Authorised public bodies and courts, upon request and as far as the law requires (KVKK Art. 8/2-a).
4.3 Service providers abroad
Because the App's technical infrastructure is provided by service providers (processors) abroad, your personal data is transferred, limited to the purposes above, to these recipients:
- Supabase, Inc. (USA): database, authentication and server functions; data is hosted in Germany (Frankfurt). All data categories.
- Cloudflare, Inc. (USA): photo storage (R2) and delivery; Cloudflare automatically chooses the data centre where the photos are stored, and its cache servers are worldwide. Visual data.
- Amazon Web Services EMEA SARL (Luxembourg) / Amazon Web Services, Inc. (USA): automated photo moderation with Amazon Rekognition, Ireland (eu-west-1). Visual data. AWS's AI services opt-out has been enabled since 8 October 2026; AWS does not use the moderated photos to improve its own services or store them for that purpose.
- OpenAI, L.L.C. (USA): additional automated photo moderation, if enabled. Visual data.
- Google LLC (USA) and Apple Inc. (USA): delivering push notifications (Firebase Cloud Messaging, Apple Push Notification service). Notification data and notification content.
- Google LLC (USA): collecting crash reports (Firebase Crashlytics) and, on Android, usage and performance metrics of the QR code scanner (Google ML Kit). Transaction security data (crash reports, scanner metrics).
- Resend, Inc. (USA): sending confirmation and password reset e-mails. E-mail address.
- Google LLC and Apple Inc. (USA): Sign in with Google and, on iPhone, Sign in with Apple, if the user chooses them. Identity data.
Because these transfers are regular, they rely on the standard contracts announced by the Personal Data Protection Board under KVKK Art. 9/4; the standard contracts are notified to the Personal Data Protection Authority within 5 business days of signing.
4.4 Map service
The maps in Stadiums and Matches are loaded from OpenFreeMap's (openfreemap.org) servers. For this your phone connects to these servers directly, and your IP address and the area shown on the map reach that service; your location is not sent.
5. AUTOMATED DECISIONS
Uploaded photos are first checked by automated systems. A photo found clearly against the rules may not be published automatically; when the systems are unsure, a moderator decides. Gallery photos added to archive visits are also checked automatically for whether they are related to the match: automated labels describe what the photo shows (for example a stadium, a crowd, a car or a meal), and a photo found clearly unrelated to the match (for example a car, a meal or a pet on its own) is not published automatically. The match stays in your archive, you get a notification and you can pick another photo. If you think an automated check produced a result against you, you can object under KVKK Art. 11/1-g and ask for a human review at info@tribundeyiz.com.
6. RETENTION
Personal data is kept for as long as the purposes of processing require, as a rule while your account is open, and deleted when you delete your account. Detailed periods (such as 7 days for rejected photo records, 90 days for location attempts not linked to a visit (1 day for the location of a failed attempt), 180 days for in-app notifications and 2 days for contact matching and abuse counters) are in section 7 of the Privacy Policy. Expired data is deleted or anonymised under the Regulation on the Deletion, Destruction or Anonymisation of Personal Data.
7. YOUR RIGHTS UNDER KVKK ART. 11
By applying to the data controller you have the right to:
- learn whether your personal data is processed,
- request information if it has been processed,
- learn the purpose of processing and whether it is used accordingly,
- know the third parties in Türkiye or abroad to whom it is transferred,
- ask for its correction if it is incomplete or inaccurate,
- ask for its deletion or destruction under the conditions of KVKK Art. 7,
- ask that the correction, deletion or destruction be notified to the third parties it was transferred to,
- object to a result against you arising from analysis exclusively by automated systems,
- claim compensation if you suffer damage because of unlawful processing.
8. HOW TO APPLY
Under the Communiqué on the Procedures and Principles of Applications to the Data Controller you can send your request:
- from the e-mail address registered in the App to info@tribundeyiz.com,
- signed with a secure electronic signature or mobile signature, to info@tribundeyiz.com.
Your application should state your name and surname, your username and e-mail address in the App, your request and an address for notices. We conclude applications within 30 days at the latest and, as a rule, free of charge; if the action has an additional cost, the fee in the Board's tariff may be charged. If your application is rejected, the answer is insufficient or not given in time, you can complain to the Personal Data Protection Board within 30 days of learning the answer and in any case within 60 days of your application.