1. Controller and contact
Yürü ve Öğren is developed by Enis Atakan Çağırıcı under the Machine Nexus brand. Contact enisatakann@gmail.com for privacy and data requests.
2. Data stored on your device
- Raw GPS points, detailed routes, heading, and walking-session history.
- Learned and unlocked cards, repetitions, XP, diamonds, and achievements.
- Language, speech, daily-goal, appearance, and sharing preferences.
- A background-location buffer while a user-started walk is active.
This information is kept in the app’s local storage. It can be removed by resetting progress or uninstalling the app, subject to operating-system backup behavior.
3. Online profile and leaderboards
Firebase Authentication creates a persistent anonymous player ID. After onboarding, your display name, region name, avatar seed, and weekly/lifetime totals for steps, distance, sessions, streak, words heard, repetitions, new words, territory, and score are sent to Cloud Firestore to provide profiles and leaderboards.
Other players can see your display name, region name, rank, and leaderboard statistics. Your individual card collection and raw route are not made public.
4. Location, background walking, and conquest
Location is used only after you start a walk to provide route, distance, speed, heading, and conquest. If you grant permission, location tracking and spoken learning continue while the phone is locked until you finish the walk.
Raw GPS routes are not uploaded. When conquest is enabled, the identifier of the approximately 50-metre gameplay cell you visit, visit time, ownership, encounter, and quiz outcome are processed by Firebase Functions and Firestore. Turning off territory-map sharing hides your cell map from the public map but does not stop the conquest server from processing cell identifiers for ownership and conflict rules.
During an active walk, the gameplay-cell identifier derived from precise background location may be used to detect entry into rival territory. If you allow notifications, the device may show a local conquest-quiz notification while the phone is locked. The notification is created on the device; no push-notification token is stored or sent to a server for this feature. Notification permission is optional, and declining it does not prevent walking or spoken learning.
5. Information visible to other players
- Display name, region name, weekly/overall rank, and aggregate progress.
- Captured gameplay-cell boundaries when map sharing is enabled.
- The owner’s display and region names when another player enters a rival cell.
6. Region-name moderation and community safety
Region names are user-created virtual game labels. A submitted name is cleaned and normalized on a trusted server and checked for personal information and community-safety risks. It may be approved, rejected, or held for human review. We may process the cleaned and normalized name, decision and risk flags, status, and change/audit records for moderation.
When you report a name, Firebase stores the report category, the optional short note available only for “Other,” the reporting and reported anonymous player IDs, and timestamps. Reports do not include precise GPS coordinates, a home address, or a raw walking route; moderators receive only an approximate gameplay cell when location context is needed.
Hide-name and block-user choices may be stored on your device and in your private Firebase preference data. They do not alter territory ownership and are not disclosed to the blocked player. A name reported by three distinct players in a short period may be hidden temporarily; a human moderator makes the final enforcement decision.
7. Quiz and learning data
Conquest answers are checked locally. The server receives the challenge ID, question total, score, pass/fail status, language pair, and conquest outcome; the selected-answer sequence is not sent in the current flow. Spoken words use the device operating system’s text-to-speech service.
8. Providers and technical data
Online features use Google Firebase Authentication, Cloud Firestore, and Cloud Functions. These services may process the player ID, function name, IP address, and device/OS request metadata in security logs. Map rendering may use Apple Maps on iOS and Google Maps on Android.
The app contains no third-party advertising, advertising identifier, cross-app tracking, or separate app analytics SDK. We do not sell personal data.
9. Purposes and international processing
Data is processed to provide walking and learning, operate leaderboard and conquest rules, prevent abuse, secure the service, and meet legal obligations. Firebase providers may process data outside Türkiye under applicable service-provider agreements and transfer safeguards.
10. Retention and deletion
Local data remains until you reset it or uninstall the app. Online profile, leaderboard, conquest, and open moderation records remain while your account is active and they are needed for service or security. Delete account and online data in Settings removes app-controlled profiles, historical leaderboard entries, conquest and challenge records, region-name claims, reports, private hide/block preferences, and the anonymous account; reporter identifiers remaining in another record are removed or anonymized. Provider security logs and backups may remain for their required retention cycles.
11. Your choices and rights
You can change Location, Motion & Fitness, and notification permissions in system settings, disable public territory-map sharing in the app, and delete your account and online data in Settings. Send access, correction, deletion, or other privacy requests to enisatakann@gmail.com with your player name and, where available, player ID.
12. Children, security, and updates
The app is not specifically directed to children. Platform permissions, Firebase security rules, and authenticated server operations are used to protect data. We will update this policy when features or processing change and provide notice of material changes in the app.