Version 1.0 · Last updated: 11 November 2026
This policy explains which personal data we process when you use the Tribündeyiz app ("App"), why, who we share it with, how long we keep it and what your rights are. Users in Türkiye can also read the KVKK Information Notice. If you live in the European Economic Area (EEA) or the United Kingdom, section 12 applies to you as well.
1. CONTROLLER
Tribündeyiz is provided by its developer, Mervan Yuşa Torlak, a natural person; "we" in this policy refers to him.
- Name: Mervan Yuşa Torlak
- E-mail (privacy requests and support): info@tribundeyiz.com
- EU representative (GDPR Art. 27): will be appointed and named here when the service is offered to people in the European Union, if the GDPR requires it.
2. IN SHORT
- We only use your location while the App is open and never track it in the background. For "I'm at the stadium", the proof photo, nearby matches, distances and nearby photos and plans in the Feed your precise location is sent to our server; when the App opens it is also read on your phone for your dot on the map. We only store your home city as its centre coordinate (an approximate location).
- We only use the camera for the live proof photo and for scanning QR codes; QR codes are read on your phone and the image is not sent. Location and device data (EXIF/GPS) are removed from photos before upload.
- From your contacts, only hashes (SHA-256) of the e-mail addresses, computed on your phone, are sent to our server. Names and phone numbers never leave your phone, the hashes are not stored, and no text messages are sent. Letting others find you by your e-mail is optional and off by default.
- Your account is private by default: only your friends see your visits, photos, statistics, city and friend list. Your username, profile photo, place on the leaderboards and number of proven stadiums are visible to everyone. If you turn on "Public account" in Settings › Privacy, everyone in the App sees your account the way a friend does: your club, national team and city, your statistics, badges, stadium collection and match list, all your approved visits and photos (your live proof photos and your archive), your season and year summaries and your friend list; you are listed on the pages of the stadiums where you took proof photos, and your "I'm going" plans for matches that have not kicked off can appear in the feed of people who are not your friends. Your "I'm at the stadium" check-ins stay visible to your friends only, even with a public account. You see who liked your photos and feed posts, with their username and profile photo; when you like someone's photo or post, they see you the same way.
- We do not sell your data or use it for advertising.
- When you delete your account, your data is deleted.
3. DATA WE PROCESS
Account: your e-mail address, your password (stored only as an irreversible hash that we cannot see), e-mail confirmation and sign-in records, your username and your invite code. If you choose Sign in with Google or, on iPhone, Sign in with Apple, the identifier and e-mail address of that account. With Sign in with Google, the name and the link to the profile picture that Google shares (the address of the picture at Google, not the picture itself) are also written automatically into the account record of our authentication infrastructure (Supabase Auth) and stay there while your account is open; the App does not use them or show them to anyone (you choose your username and profile photo yourself).
Profile: your profile photo, the club you support, your national team, your home city and country (the city's centre coordinate, not your home address), your language and time zone.
Location: your device's location (latitude, longitude, accuracy), only while the App is open and only if you have given the location permission. We do not get your location in the background.
- When the App opens, your location is read on your phone: for your dot on the Stadiums map and for distances. This reading is not sent to our server at that moment; it is kept in your phone's memory for a few minutes and used for the actions below.
- For "I'm at the stadium" and the proof photo, your device's precise location (GPS) is sent to our server. The server checks whether you are within about 1 km of the stadium and within the match window (from 3 hours before kick-off to 2 hours after the final whistle). A record of each attempt (precise location, accuracy, distance to the stadium, stadium and match, result, server time) is kept. For a failed attempt (e.g. too far from the stadium, no match) the location is deleted after 1 day; the location of an attempt linked to a visit or an "I'm at the stadium" check-in is kept as long as that record exists (section 7).
- When you open Matches or a stadium's page, the location your phone found is sent to our server without rounding, that is as a precise location, to show nearby matches and distances such as "12 km from you". The server only uses it to measure the distance; the location sent for this is not stored in the database.
- When you open or refresh the Feed, the location your phone found is sent to our server in the same way, as a precise location, to show public photos taken at stadiums near you and public accounts' plans for upcoming matches at those stadiums. The server only uses it to find the nearby stadiums; the location sent for this is not stored in the database either.
- Without the location permission, or if no location is found, distances are measured from your home city, and the nearby photos and plans in the Feed are picked around your home city. Your home city is an approximate location: we store only the city's centre coordinate, not your home address.
Photos: your live proof photo and its thumbnail, gallery photos you add to archive visits, your profile photo; the results of automated moderation (labels and scores) and moderator decisions. Other people may appear in your photos.
Visits and activity: your 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 you want to visit, stadium ratings, missing-stadium reports, badges, missions, statistics (including your season and year summaries) and leaderboard position.
Friends and community: friend requests and friendships, people you block, reports you make and reports about you (reason and a note of up to 500 characters), additions through invite links and QR codes.
Contact matching: if you use "Find from contacts", the e-mail addresses in your contacts are lower-cased and hashed with SHA-256 on your phone. Only these hashes are sent to our server and compared with the hashes of users who have confirmed their e-mail address and chose to be found by it. The hashes are not stored after the comparison; to prevent abuse we only keep the number of hashes you sent, for 2 days.
Being found by your e-mail: this is optional and off by default; only if you tick "Let people find me by my email" when setting up your profile or turn it on in Settings › Privacy do users who have your e-mail address in their contacts see your username and profile photo in "Find from contacts", and you can turn it off at any time with the same setting.
Public account: this is optional and off by default; all new and existing accounts start private. We store this setting and, while it is on, since when it has been on. Section 5 explains who sees what if you turn it on; you can turn it off at any time in Settings › Privacy.
Notifications: your device's push token (FCM token), platform (iOS or Android), App version, notification preferences and in-app notification history.
Technical and security data: server logs such as IP address, request time, device and App information, session data and abuse counters (e.g. attempts per hour).
Crash reports: if the App crashes or hits an unexpected error, the technical details of the error, the App version, phone model, operating system and a random installation identifier. Your username, e-mail and location are not added to the report.
QR code scanning: the camera image is processed on your phone and is not sent anywhere. On Android the scanner is Google ML Kit; for diagnostics and usage analytics ML Kit sends Google usage and performance metrics of the scanner (device and App information, performance metrics such as latency, event types, error codes and a random installation identifier). On iPhone, scanning uses Apple's on-device Vision framework.
We do not aim to collect special categories of personal data (such as health, religion, political opinions or biometric data). Photos are not used for face recognition or biometric identification; automated moderation only checks whether the content follows the rules and, for archive photos, whether the photo is related to the match (an archive photo clearly unrelated to the match, for example a car or a meal on its own, is not published automatically; the match stays in your archive). Photos with political banners or signs are not published under our rules.
4. PURPOSES AND LEGAL BASES
- Creating your account and providing the App (collection, feed and likes, friends, leaderboards, badges, season and year summaries, support): conclusion and performance of a contract (KVKK Art. 5/2-c; GDPR Art. 6/1-b).
- Public account (only if you turn it on, showing your account to everyone in the App the way a friend sees it: your club, national team and city, statistics, badges, stadium collection, approved visits and photos, season and year summaries and friend list; listing you on the pages of the stadiums where you took proof photos; showing your plans for matches that have not kicked off in the feed of people who are not your friends and letting them join those plans; suggesting public photos and plans of people who are not your friends to you in the feed): performance of a contract (KVKK Art. 5/2-c; GDPR Art. 6/1-b). You can turn the setting off at any time.
- Verifying proven visits and preventing cheating (location, server time, live camera): performance of a contract and our legitimate interest (KVKK Art. 5/2-c and f; GDPR Art. 6/1-b and f).
- Moderating photos, reviewing reports and protecting the community: our legitimate interest and legal obligations (KVKK Art. 5/2-f and ç; GDPR Art. 6/1-f and c).
- Sending notifications (friends' activity, match reminders, likes, badges, your season or year summary being ready): performance of a contract (KVKK Art. 5/2-c; GDPR Art. 6/1-b). You manage the permission in your phone's settings and the topics in the App's Settings.
- Finding friends from your contacts (at your request): legitimate interest (KVKK Art. 5/2-f; GDPR Art. 6/1-f). Your contacts' data is only used as hashes and is not stored.
- Security, abuse prevention and debugging: legitimate interest (KVKK Art. 5/2-f; GDPR Art. 6/1-f).
- Legal obligations, requests from authorities and legal disputes: legal obligation and the establishment, exercise or defence of a right (KVKK Art. 5/2-ç and e; GDPR Art. 6/1-c and f).
We do not send marketing messages or build advertising profiles.
5. WHAT OTHER USERS SEE
- Everyone: your username, profile photo, your place on the leaderboards and your number of proven stadiums. Once you have finished setting up your profile, you are listed on the leaderboards even with 0 proven stadiums: on the World leaderboard (users of all countries), on the leaderboards of your country (e.g. Türkiye) and of your club's fans, and on your friends' Friends leaderboard. Appearing on the country and club leaderboards also indirectly shows your country and which club you support.
- Everyone, if your account is public: if you turn on "Public account" in Settings › Privacy, everyone in the App, that is every signed-in user who has finished setting up their profile and has not blocked you or been blocked by you, sees your account the way a friend you accepted sees it, even if they are not your friend: the club you support, your national team and your home 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, that is your live proof photos as well as the matches you added to your archive and your archive photos; your season summary and your year summary; and your friend list, with your friends' usernames and profile photos. When you turn it on, all of this becomes visible, including what you added earlier. Your live proof photos are also shown, with their stadium, match and like count, in the feed of people who are not your friends, in the photo gallery and 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 at that stadium, with the date of the latest). A photo you take during a match can be shown straight away to other users going to the same match that day and on that stadium's "Who's been here" list, so it can reveal that you are at that stadium right now.
- Your plans, with a public account: your "I'm going" plans for matches that have not kicked off can also be shown in the feed of people who are not your friends, next to public photos; so people who are not your friends can see which match you plan to go to, and therefore where you intend to be on that match day. People who are not your friends can like such a plan and tap "I'm coming too"; "I'm coming too" gives that person their own plan for the match. Your plan is shown to people who are not your friends only until the match kicks off. You get no notification for their likes of your plans or for their joining; you see who liked your plan in its list of likes. People who joined your plan and are not your friends are shown to you and to others only as a number, not by name; everyone sees only their own friends by name among the people who joined.
- What people who are not your friends can do, with a public account: they can like your live proof photos and your plans, tap "I'm coming too" on your plans, and report any visit they can see (archive visits included) and you; they cannot comment or send you messages. Their likes of your photos are not notified to you one by one but in at most one summary notification a day, without the names of the people who liked them; you see who liked a photo in that photo's list of likes, with their usernames and profile photos.
- What is not opened to everyone, even with a public account: your "I'm at the stadium" check-ins (the records and notifications that say you are at a stadium right now), your friends' comparison with you and the matches you went to together stay visible to your friends only. 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.
- If you make your account private again, none of this (the details on your profile, your statistics, stadium collection, visits and photos, summaries, plans and friend list) is shown to people who are not your friends from then on. People who already saw it may still have it cached on their phone or may have taken a screenshot, and a photo link someone obtained earlier can keep opening until you delete that photo; we cannot undo that. People who tapped "I'm coming too" on your plan earlier keep their own plans.
- Your friends: in addition, your club, national team, city, approved visits and photos, your match list, plans, "I'm at the stadium" check-ins, feed activity, badges, all your statistics, your season and year summaries and your friend list. A friend can compare their own collection with yours and see the matches you both went to. Your city's coordinate is not shown to anyone.
- Other people's friend lists: 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 everyone in the App if their account is public; this applies even if your own account is private.
- The owner of a photo or post you like: 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, and can open your profile from there; if your account is private, they only see on it what everyone can see. 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. Nobody but the owner sees this list; others only see the number of likes. If you take your like back, you leave the list. In the same way, you see who liked your own photos and posts: your friends, and people who are not your friends who liked your public photos or plans.
- If you join the plan of someone who is not your friend: when you tap "I'm coming too" on the plan of someone with a public account, 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 among the people who joined that plan. This applies even if your own account is private.
- People you block and people who block you do not see each other in search, profiles, the feed, leaderboards, friend lists, lists of likes or notifications.
- If you share your story card, season summary or year summary in an app such as Instagram or WhatsApp, whoever can see that post there can see it; it is subject to that app's rules.
6. SERVICE PROVIDERS AND INTERNATIONAL TRANSFERS
We only share your data with the following service providers (processors), bound by contracts, to provide the service:
- Supabase, Inc. (USA): database, authentication and server functions. Data is hosted in Germany (Frankfurt, AWS eu-central-1).
- Cloudflare, Inc. (USA): photo storage (R2) and delivery. Cloudflare automatically chooses the data centre where the photos are stored. Published photos may be cached temporarily on Cloudflare's servers worldwide for fast delivery.
- Amazon Web Services EMEA SARL (Luxembourg) / Amazon Web Services, Inc. (USA): automated photo moderation with Amazon Rekognition in the Ireland (eu-west-1) region. 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.
- Google LLC (USA): push notifications with Firebase Cloud Messaging, crash reports with Firebase Crashlytics and, on Android, usage and performance metrics of the QR code scanner (Google ML Kit). On iOS devices, notifications are delivered through Apple Inc.'s (USA) Apple Push Notification service.
- Resend, Inc. (USA): sending confirmation and password reset e-mails (your e-mail address and the content of the e-mail).
- Google LLC and Apple Inc. (USA): authentication, if you choose Sign in with Google or, on iPhone, Sign in with Apple.
Match data comes from API-Football; none of your personal data is sent to that provider.
The maps in Stadiums and Matches are loaded from OpenFreeMap's (openfreemap.org) map servers. Your phone connects to these servers directly, so your IP address and the area shown on the map reach that service. Your location is not sent to it; the location dot on the map is drawn on your phone only.
Because some of these providers are outside Türkiye (Germany, Ireland, the USA and other countries where Cloudflare has servers), your data is transferred abroad. These regular transfers from Türkiye rely on the standard contracts announced by the Turkish Personal Data Protection Board under KVKK Art. 9. Transfers from the EEA rely on the European Commission's standard contractual clauses or the EU-U.S. Data Privacy Framework.
Apart from this we only disclose your data to authorised public bodies and courts, as far as the law requires. If the App is transferred to another person or company, data may pass to the acquirer, provided it keeps to this policy; we will tell you in advance.
7. HOW LONG WE KEEP DATA
- Account, profile, visit, photo, friendship and activity data is kept while your account is open. If you delete a visit, the visit, its photos and the feed entries, likes and notifications attached to it are deleted.
- If you delete your account, your account and all data linked to it are deleted. Photos are removed from storage immediately, or within a few days at the latest through the clean-up queue. Reports you made may be kept with the link to you removed. Copies in backups are deleted when the backups expire, within 7 days at the latest.
- The visit record of a rejected photo is kept for 7 days so you can see the reason, then deleted.
- Unfinished uploads are kept for 2 days; moderation records of rejected or failed uploads for 30 days.
- Location attempts not linked to a visit or check-in are kept for 90 days; linked ones as long as that record exists. For a failed attempt (e.g. too far from the stadium, no match) the location itself is deleted after 1 day; the rest of the attempt (accuracy, distance to the stadium, outcome, time) stays for that period.
- In-app notifications are kept for 180 days, push delivery records for 14 days.
- Contact matching and abuse counters are kept for 2 days.
- Your push token (FCM token) is deleted when you sign out or when it becomes invalid.
- Crash reports are kept in Firebase Crashlytics for 90 days.
- Server logs (such as IP address and request time) are kept in our infrastructure provider's logging system for 7 days at most.
- Data we are legally required to keep is kept for the period required.
8. SECURITY
Connections are encrypted (TLS). Every database table is protected by row-level access rules. Photos are not published before moderation, and raw moderation scores are hidden from users. Passwords are only stored as hashes. Only the people needed to run and moderate the App can access data, and only as far as needed. No system is completely secure; if a data breach happens we will notify the authority and you as the law requires.
9. PERMISSIONS
- Location (while using the App): "I'm at the stadium", the proof photo, nearby matches, distances, nearby photos and plans in the Feed and your dot on the map.
- Camera: the live proof photo and scanning QR codes (the QR image is processed on your phone).
- Photos: picking archive and profile photos (only the photo you pick is read).
- Contacts: "Find from contacts" (only e-mail hashes are sent to our server, and they are not stored).
- Notifications: push notifications.
You can turn off any permission at any time in your phone's settings; the related feature then stops working.
10. CHILDREN
The App is not meant for children under 13. If you are under 18 and the law where you live requires it, you should use the App with the knowledge of a parent or guardian. If we learn that we process data of someone under 13, we delete the account and the data.
11. YOUR RIGHTS
You have the right to learn whether your personal data is processed, to ask for information and a copy, to have it corrected or deleted or its processing restricted, to object, to receive your data in a portable format and to complain. Details are in the KVKK Information Notice.
- You can change most of your information in the App's Settings and delete your account and data in Settings > Delete account.
- For other requests, write to info@tribundeyiz.com. We answer within 30 days at the latest, as a rule free of charge.
- You can ask for a human review of a photo rejected by automated moderation.
- You can complain to the Turkish Personal Data Protection Board, or, if you live in the EEA or the UK, to the data protection authority of your country.
12. USERS IN THE EEA AND THE UK
Under the EU General Data Protection Regulation (GDPR) and the UK GDPR we rely on the legal bases above. You have the rights of access, rectification, erasure, restriction, portability and to object to processing based on legitimate interests. Where we ask for consent, you can withdraw it at any time. When the service is offered to people in the European Union, we will appoint an EU representative if GDPR Art. 27 requires it and name them in this policy.
13. CHANGES
We may update this policy. We will announce material changes in advance in the App or by e-mail. The current version is always available in the App and at tribundeyiz.com.
14. CONTACT
Mervan Yuşa Torlak, info@tribundeyiz.com