This policy covers the new iOS version being prepared and earlier versions that may remain installed. Availability of the new iOS version in the store depends on completion of Apple's review.
In short: Müso stores your name, username, phone number if added, status, friendships and text messages with friends on the developer's own server in Turkey. Only accepted friends see your number and status; messages can be seen only by the friend in that conversation and the developer who operates the service. Notification tokens and content pass through notification services outside Turkey. No ads, no analytics, no tracking; data is never sold. You can delete your account inside the app: Profile → Delete account.
Müso is developed by an individual, Emre Taşçı, who is the data controller. Contact: [email protected].
Optional contact matching: Starts only through Add friend → Find from contacts → Allow and find from contacts. Names and phone numbers of permitted contacts are read on your device; names and raw numbers are not sent to the server. Turkish mobile numbers are normalized and hashed using SHA-256 on the device. Hashes of up to 2,500 numbers are sent with your session to Müso's server to find matches. They are processed in memory only to answer that request, with no database, backup or log storage. Hashing does not make a phone number anonymous. Your local contact names are displayed only on your device. Becoming friends still requires a request and acceptance.
You can add friends by username or invitation without granting contact permission. Contacts are never scanned automatically or in the background; you can revoke permission in phone settings. On iPhone you may allow only selected contacts. Müso does not access location, camera, microphone or photos, and does not use an advertising ID. Your phone also keeps your session key in secure device storage, a copy of your profile and friends list (to show them while offline), your Favorites and your view preference. Home Screen widgets store friends' names, initials and status summaries on the device; session keys, phone numbers and message content are not passed to widgets.
Availability reminders and calls: With notification permission and a valid session, the server sends reminder pushes at 12:00, 18:00 and 21:00 in this phone's time zone. A different reminder is used after 48 hours without a Free/Busy selection; for someone who has never selected a status, the period starts when the account is created. The phone's reminder preference and time zone are sent to the server. You can turn reminders off for this phone in Profile → Settings. The device is excluded once sign-out or a disabled preference reaches the server, the account is deleted, or the session is no longer valid. The previous local reminder schedule is removed. Tapping “Müsait var mı?” on the widget opens the comment screen; an optional short comment is included in the notification to accepted friends only when you tap Send. Call notifications default to on; recipients can disable them in Settings or mute a friend. The Free/Busy notification actions open the app's status picker; your choice saves the status.
Updates in new versions: The new iOS version being prepared and Android 1.1.0 (7) do not use Expo EAS Update. Application and widget code and assets are embedded in the signed package; the app does not download and execute JavaScript code. Code and asset changes are distributed through a new TestFlight / App Store / Google Play version.
Installed build 16 and earlier test builds: iOS TestFlight 1.1.0 (16), earlier iOS test builds containing OTA updates, and Android 1.1.0 (4) may still use Expo EAS Update until replaced with a version without OTA updates. Build 16 offers compatible code/asset updates on the home screen; downloading and restarting are the user's choice. The service processes technical information such as installation ID, IP address, platform, application/runtime version and update channel. Müso does not use it for advertising or usage analytics. The new local preparation does not itself remove this behavior from older installations.
The account and conversation database is stored in Turkey, on the developer's own server (a Raspberry Pi). Traffic between the app and the server passes, encrypted (HTTPS), through Cloudflare, which connects the server to the internet and may process connection information such as your IP address on infrastructure outside Turkey. Cloudflare is used to transmit traffic, rather than to host the account database.
Notifications are transferred outside Turkey. Push tokens and the content needed to deliver a notification (the sender's name, free/busy status, activity and any status note, the first approximately 100 characters of a message, an availability-call question and optional comment, or a reminder message) pass through Expo Push Service (United States) to Apple Push Notification service (APNs) on iPhone or Google Firebase Cloud Messaging (FCM) on Android. These services process this data to deliver notifications to your device; storing the conversation database in Turkey does not remove this transfer. The 12:00, 18:00 and 21:00 reminders also use these push services.
Application updates in installed older test builds: In TestFlight 1.1.0 (16) and earlier OTA builds that use EAS Update, Expo EAS Update (United States) and its distribution infrastructure may process the installation and connection information above outside Turkey. The next native version being prepared will not use this update service; this change does not modify older installations. Contact hashes are not sent to update or push services; matching traffic to Müso's server also passes through HTTPS and Cloudflare.
Transfers outside Turkey are subject to KVKK article 9; the applicable transfer basis, necessary safeguards and provider agreements require a separate assessment. This notice does not represent that any particular adequacy decision, standard contract or explicit-consent mechanism has been completed. Your phone's notification permission alone is not explicit consent for an overseas transfer under KVKK. You can contact the controller for information or requests concerning these transfers.
Data is never sold, rented or shared for advertising. Google and Apple handle sign-in under their own policies (Google, Apple). The "WhatsApp" and "Call" buttons only open the corresponding app on your phone.
In Müso: Profile → Delete account → Delete my account. Your server-side profile, phone, status, friendships, requests, invite, blocks, all conversation messages, abuse reports and message copies associated with you, push tokens, notification preferences and sessions are deleted. If you signed in with Apple, the Apple authorization is revoked through Apple; Müso's data on the phone and widget content are cleared. If you cannot use the app, email [email protected] from your account's email address. Details: Account and data deletion.
Sign out clears data on that phone and widget content, and cancels the previous local reminder. Once sign-out reaches the server, the session's push token and server reminder are removed. Your account and messages that have not reached their retention limit remain on the server.
You can ask to access, correct, delete or export your data, object to processing, or ask what was shared with whom, by writing to [email protected] from your account's email; requests are answered free of charge within 30 days. You can also edit your name, username and phone in the app (Profile → Edit profile). You may complain to Turkey's Personal Data Protection Authority (KVKK) or, in the EU, to your local data protection authority.
Traffic is encrypted with HTTPS. Messaging is not end-to-end encrypted: the developer can technically access messages on the server, and notification services can access the preview delivered to them. The server listens only on a local address and is exposed to the internet only through a Cloudflare tunnel. Only hashes of session keys are stored. No system is perfect; in case of a breach, affected users (and, where required, the authority) will be notified.
Müso is not directed at children under 13 and does not knowingly collect their data. See our child safety standards.
If this policy changes, the current version is published here with its date; significant changes are also announced in the app.