Privacy Policy

1. Publisher and scope

Meloop is an Android music practice journal published by Võ Trần Minh Trí under the Moss Studio brand. Võ Trần Minh Trí is responsible for the processing of personal data for Meloop. “We” means the publisher and team members assigned to support Meloop.

This policy covers the app, the policy website and user support. The first release is for people aged 13 and over in Vietnam and the United States. There are no in-app accounts. Free may display Google AdMob ads; Pro removes ads. Contact: meloop.app.support@gmail.com.

2. Journal data on your device

Instrument profiles, session names, dates, duration, practice notes, difficulties, next-session notes, mood and focus ratings are stored in the app’s private storage on your device. Unfinished sessions, weekly goals, language and reminder settings are also stored there.

Meloop uses these records to display your journal, calculate statistics and provide practice reminders. Mood and focus are optional ratings you enter; they are not used for health diagnosis.

Meloop does not automatically upload journal entries or audio to the team, RevenueCat, Firebase or AdMob. The team cannot read or recover your on-device journal. Data leaves the app when you choose to export a file or send content through another service.

3. Microphone and notifications

The app requests microphone access when you record audio or check pitch. Pitch is analysed on your device; that audio is not saved as a recording. Recordings you create, their names, duration and timestamps are stored in the app’s private storage. Meloop does not identify you by your voice.

The microphone stops when you stop or leave the tool, put the app in the background or encounter an audio interruption. You can refuse or revoke microphone access in Android and still use the journal.

Practice reminders are scheduled on your device; your schedule is not sent to a server. On Android versions requiring notification permission, the app asks when you enable reminders. Notifications may appear on the lock screen; you can disable them or change their display in Android.

4. Purchasing and restoring Pro

Google Play processes payments. Meloop does not receive your card number, payment password or Google account password.

RevenueCat helps verify transactions, grant and restore Pro, reconcile purchase status and aggregate transactions. Data includes an SDK-generated user ID, product IDs, purchase evidence such as purchase tokens, transaction times and status, currency, store region or language, and technical app or device information. The service may process connection IP addresses and the last connection time.

The SDK ID is not an instrument profile name and does not make the data fully anonymous. Necessary data may be exchanged when the Pro system starts or updates, even before you purchase. We do not add journal entries, profile names, audio, email addresses or advertising IDs to RevenueCat customer attributes.

Restoring Pro restores a purchase entitlement, not your journal or audio. The app explains the processing before you use the feature and requests separate consent when required by law.

5. Advertising and consent choices

The Free plan may display Google AdMob ads in enabled placements. Verified Meloop Pro access removes the app’s ads. Alpha builds use sample ads; release builds may use live ads.

The Google Mobile Ads SDK may collect and share IP addresses (to estimate a general area), Android advertising IDs or other device identifiers, ad interactions and diagnostic/performance information to serve and measure ads and prevent fraud. This advertising processing is separate from the Crashlytics reporting switch. Disabling crash reporting does not disable AdMob processing. Meloop does not send journal entries, notes, mood, profile names or audio for advertising, and does not request GPS location to display ads.

The app uses Google’s User Messaging Platform (UMP) to update consent status and present forms when required. Ads are requested only when UMP permits them. Depending on your region and choices, Google may serve personalized, non-personalized or limited ads; non-personalized ads may still require technical data processing.

When required by UMP, “Ad privacy choices” in Settings lets you revisit your choices. You can also manage advertising IDs in Android. Purchasing Pro does not replace required consent or erase advertising data already processed.

6. Optional crash reporting

Meloop uses Firebase Crashlytics to diagnose errors. “Send crash reports to improve the app” is off by default. Only reports from permitted app launches can be sent at a later launch. If you allow it in Settings, Google/Firebase receives error details and times, app and Android versions, device type, connection information, installation identifiers, a random crash support ID and technical session information to assess stability.

The crash ID is not an account and is not linked to the RevenueCat ID. Reports do not include journal entries, session names, mood, focus, audio, email addresses or purchase evidence. Meloop does not use Firebase Analytics to track your practice.

You can disable reporting and keep using practice features. Disabling takes full effect at the next app launch; the app explains when a restart is needed. The SDK may store temporary crash information locally, but reports generated without your permission are not automatically sent if you later opt in. Reports already queued for sending cannot be recalled by this switch. Disabling does not delete reports already sent; you can contact support to request action.

7. Contacting support

“Contact support” opens a draft in your email app for you to review, edit and decide whether to send. Meloop does not send email automatically. Technical information is added only if you choose it; journal entries, audio and purchase tokens are not automatically attached.

When you email meloop.app.support@gmail.com, you provide your address, message and selected attachments. We process them through Google’s Gmail to respond, handle requests or verify purchase issues. Sending a support email does not subscribe you to advertising.

Send only the information needed. You do not need to provide passwords, card details or identity documents for an ordinary bug report. Check images and files before sending to avoid disclosing your own or another person’s private information.

8. Backups and file exports

A backup includes profiles, saved sessions, ratings, goals and journal settings. It excludes unfinished sessions, audio, recording metadata, Pro entitlements, purchase IDs, crash reports, permissions and consent choices. Audio is exported separately.

Meloop does not encrypt the JSON backup. You choose where to save it or which app receives it; a cloud service applies its own policy. Restoring replaces the current journal and settings and deletes existing local recordings after you confirm a warning. Invalid files or cancellation before completion do not remove your existing data.

Meloop excludes journal entries, audio, purchase data and privacy choices from automatic Android backups. Operating-system or manufacturer transfer tools may behave differently. Meloop does not manage files you have exported outside the app.

9. Recipients and international processing

Recipients include Google Play for payments; RevenueCat for Pro; Google AdMob/UMP for advertising and consent choices; Google/Firebase for crash reports you allow; Gmail for support messages; Firebase Hosting for the policy website; and file services you choose. Assigned support, transaction and development team members access only the data needed for their work.

Services may process data outside Vietnam, including in the United States. Before a flow requiring consent under applicable law, the app explains the data, purpose and recipients so you can decide. Reading this policy or continuing to use the app does not replace required consent.

Meloop does not sell your journal entries or audio. Google’s advertising processing/sharing is described in section 5 and depends on configuration, region and consent choices. Data we hold may be disclosed in response to lawful requests from competent authorities within the scope permitted by law.

The policy website is hosted on Firebase Hosting. Google may process IP addresses, browser, device and access information to operate and protect its services under its privacy policy. Meloop adds no advertising, Google Analytics or tracking tools to the site. “Do Not Track” signals do not change Meloop’s processing; the choices in section 11 remain available.

10. Retention and deletion

Journal entries and audio remain on your device until you delete individual items, profiles or all local data. If file cleanup is incomplete, the app tells you and continues cleanup. Ordinary deletion does not guarantee permanent removal of every trace from device storage. Uninstalling may remove local data.

Deletion within Meloop does not remove exported files, sent emails, copies held by other services or Google Play/RevenueCat transaction data. It does not refund a payment or cancel Pro. Disabling reporting or resetting the app does not automatically delete reports already sent.

Pro data is kept as needed to maintain and restore purchases, resolve transactions and meet legal obligations. If you request deletion, we remove what can be removed and explain anything that must be retained. Google Play manages its own transaction records.

According to Firebase, Crashlytics retains crash data and related identifiers for 90 days before starting removal from live and backup systems. Other systems have their own periods. For deletion requests, we use the provider’s available mechanisms and explain scope and progress; reaching 90 days does not mean every copy has already been erased.

Support emails and files stored by the team are deleted from team-managed locations no later than 90 days after a request closes, or earlier following a valid request. Exceptions apply to transactions, disputes or legal obligations. Providers may need additional time to remove copies under their policies.

Google retains advertising data and consent choices according to its purposes, settings and policies. Deleting a journal or purchasing Pro does not automatically delete previously sent advertising data. Use Google’s available controls or contact support for a request; Meloop does not promise one deletion period for all advertising data.

11. Your privacy choices and rights

You can revisit ad privacy choices in Settings when UMP requires that entry point. Refusing or withdrawing a choice does not automatically erase data already processed by Google.

You can view, edit, export and delete journal entries; disable reporting and reminders; and revoke microphone or notification access in Android. These privacy rights do not require Pro.

To request access, correction, a copy or deletion of data held by the team or Meloop’s service providers, email meloop.app.support@gmail.com. You may also withdraw consent, request restriction, object to processing or complain to a competent authority under applicable law. We do not discriminate against you for exercising your rights.

Describe your request and the data involved. We ask only for information needed to verify the person and locate the data. The relevant purchase or crash support ID may be needed; do not send purchase tokens or passwords. If there is insufficient information to locate records, we explain the limits and available steps.

In Vietnam, we respond to valid requests under the applicable procedure within two working days, explain the steps and resolve them within the deadline for each right. We explain any lawful extension or retention, including its reason and duration. In other markets, rights and deadlines follow applicable law.

RevenueCat deletion does not erase Google Play transactions and may affect Pro verification. Using purchase or restore again may create necessary service data again. We explain this impact when handling your request.

12. Younger users

Meloop is for people aged 13 and over and is not directed to children under 13. If we learn that we received data from a child under 13 outside a legally permitted situation, we stop the relevant processing and take appropriate deletion measures. Parents or legal representatives can contact meloop.app.support@gmail.com.

In Vietnam, people aged 13–15 are still children. Their legal representatives exercise data rights as provided by law. Publishing or disclosing private-life information or personal secrets of a child aged seven or over requires valid consent from both the child and their legal representative.

Purchase, crash reporting and data-sending flows involving minors must meet applicable consent and legal-representative requirements. Meloop does not enable a flow requiring such consent before an appropriate mechanism is available. Representatives can send requests to support.

13. Security and policy updates

Meloop uses private app storage and HTTPS for service connections. Access to support, purchase and crash systems is limited to assigned people. Exported JSON files have no Meloop encryption layer; we do not promise end-to-end encryption for all data.

If a data incident occurs, we take containment and remediation measures and notify relevant parties as required by law. You can report an incident to support. Protect your device and exported files; no system is completely secure.

Each policy has a version and application date. The first policy applies when Meloop officially launches on Google Play. An offline copy is packaged with the app; the latest copy is on the policy website. We notify users in the app before significant changes take effect and request new consent when necessary. Continued use does not replace consent required by law.

14. Provider policies

Google Play, AdMob/UMP, Gmail, Google Sites and Firebase Hosting: https://policies.google.com/privacy

RevenueCat: https://www.revenuecat.com/privacy

Firebase: https://firebase.google.com/support/privacy

These sources explain provider processing. Requests about Meloop data should still be sent to the team; using external services does not replace the publisher’s responsibilities.