← Back to mSync mSync · Android App

Privacy Policy

Effective Date: April 23, 2026 · Last Updated: October 4, 2026

Trei ("we", "us", "the developer") built mSync as an Android application for synchronized music listening with friends. This privacy policy explains how the app handles your data.

Data You Provide

Account - email via Google Sign-In or Apple Sign-In.
Display name and profile photo - shown to friends you invite to sync sessions.
Session data - rooms you create, friends you invite, tracks you play within a sync session (transmitted to our real-time backend so co-listeners stay in sync).

How Your Data Is Used

To identify you to friends you invite to sync sessions.
To keep co-listeners in sync via our real-time backend at api.trei.dev.
We do not log or retain the full listening history; session state is transient.

Permissions

INTERNET / ACCESS_NETWORK_STATE - Required for real-time sync.
POST_NOTIFICATIONS - Friend invites, session notifications.
FOREGROUND_SERVICE / MEDIA_PLAYBACK - Keep sync active while you listen.

Third-Party Services

Firebase Authentication + Firestore / Realtime Database - auth and sync state. Firebase Privacy.
Google AdMob - Free tier ads. Google Privacy.
Meta Audience Network - ad mediation fallback. Meta Privacy.
RevenueCat - subscription management. RevenueCat Privacy.

Children's Privacy

mSync is not directed at children under 13. We do not knowingly collect data from children.

Data Retention and Deletion

You can delete your account from Settings. Account deletion removes profile data from our servers within 30 days. Backups may retain data for up to 90 additional days.

Data Security

All data is transmitted over HTTPS. Authentication is handled by Firebase.

Changes to This Policy

We may update this policy when new features are added. Any changes will be posted here with an updated "Last Updated" date.

Google Play Data Safety Summary

The Android app and the services it uses collect the following. This matches the Data safety section shown on Google Play.

Device or other IDs. An app-install or device identifier is sent to api.trei.dev once a day to count active devices, and the ad networks may read your advertising ID to show and measure ads.
User IDs. If you sign in, your account ID is used to keep your data with your account.
App interactions. Events such as opening the app or a screen are sent to Firebase Analytics and to api.trei.dev to understand usage.
Crash logs and diagnostics. Crash and performance data is collected to find and fix problems.
Purchase history. Google Play and RevenueCat process Premium purchases and tell the app whether Premium is active.
Approximate location. The ad networks (Google AdMob and its partners) may estimate your region from your IP address to show and measure ads. The app does not use this for anything else.

This data is encrypted in transit. Ad, analytics and crash data is shared with the providers named in this policy for advertising, analytics and fraud prevention. We do not sell it.

Contact

Trei
Email: contact@trei.dev
Phone: +91 85500 77767
Website: trei.dev · Contact form