Privacy Policy

1. Information stored by the app

To play audio and restore your settings, the app stores the following in its storage on your device:

• Copies of audio you choose to import, with related information such as audio names;
• Saved mix names, sound combinations, track volumes, and the master volume;
• Favorites, recently used mixes, the current selection, and sleep timer settings;
• Whether you have completed the introduction, a random identifier and membership information cached by the purchase SDK, and limited analytics events awaiting upload.

This information supports playback, editing, and restoring your choices. The app has no sign-in account, developer-operated audio cloud sync, or remote audio upload feature. It does not send specific sound selections, mix recipes, or imported audio to RevenueCat or Growth. Section 3 describes purchase processing; section 4 describes automatic feature analytics and advertising attribution.

2. Imports, exports, and system features

Importing files.After you select an audio or mix file in the system file picker, the app reads the selected file and copies the audio it needs into app storage. The file name may become the imported sound’s name. If you select a file from iCloud Drive or another file service, that service handles the file under its own rules and your settings.

Sharing mixes.An exported .cwnmix file contains recipe information, including the mix name, tracks, and volumes. If the mix uses personally imported audio, the export also includes the full file contents of that audio; built-in sounds are stored as references. Before sharing, check that the contents are suitable for the recipient. Your chosen sharing service and the recipient handle their copies under their own rules.

Widgets and Siri.The app uses Apple’s App Group storage to share sound and mix lists, titles, favorites, playback state, and timer state between the main app and extensions such as widgets. This enables quick selection and controls. Siri and Shortcuts operate under Apple’s rules and your system settings.

System playback screens.Now Playing, CarPlay, and similar system interfaces may display sound or mix names. When naming personal audio or mixes, consider that those names may appear on a lock screen or vehicle display.

Permissions and backups.The app does not record audio or access your location, photos, or contacts. Whether app data is included in system backups depends on your device and system settings. We do not run an app cloud sync service and cannot control your system backups or third-party services. See Apple’s Privacy Policy for Apple’s practices.

3. VIP purchases and RevenueCat

The app uses Apple’s in-app purchase system and RevenueCat, Inc.’s SDK and service to offer VIP purchases, check access, and restore purchases. The SDK may contact RevenueCat when the app starts or checks membership, as well as when you purchase or restore; opening a purchase screen is not the only time this occurs.

• Purchase information: products, transaction or receipt information, and subscription or purchase status, including trial, renewal, expiry, and refund information.
• Random app identifier: RevenueCat generates and caches a random identifier to associate the app installation with membership records. Yantu does not supply a custom sign-in ID, name, email address, or advertising identifier (IDFA) to RevenueCat.
• Technical information: device type, operating system, locale and currency, and the last time the app contacted the service. This supports the purchase service and its records; it does not include your audio recordings or sound selections.

This information supports purchase verification, trial eligibility checks, membership access, restoration, and fraud prevention. Purchase records also support subscription analytics, such as purchase history and revenue or renewal statistics in RevenueCat’s dashboard. We use the same random identifier to connect membership records with the feature analytics and Yantu promotion measurement described in section 4. The app displays no ads and does not integrate a third-party ad display SDK.

Apple handles payment details. Neither this app nor its RevenueCat integration receives your payment card number. We do not send imported audio, audio file names, mix contents, or saved listening selections to RevenueCat. See RevenueCat’s Privacy Policy for its service practices and Apple’s Privacy Policy for Apple’s processing.

4. Automatic usage analytics and promotion measurement

Yantu uses Yuuglow Growth, an analytics service we operate. When the service configuration, app identity, and runtime environment are ready, the app automatically records the information below. A VIP purchase is not required, and there is no in-app usage analytics switch. We use this information to understand feature use, improve the product, and measure our promotion of Yantu.

• Usage events: launches and sessions, introduction completion, membership screen openings and closures, product loading, purchase or restoration outcomes, and successful playback starts, sound journeys, mix saves, and imports. These record feature and outcome categories, not sound names, a list of tracks you listen to, mix recipes, or personal audio.
• Identifiers and context: the random RevenueCat App User ID, event and session identifiers, event time, app version and build, operating system version, language, storefront region, and limited fields such as the selected membership product, plan, and trial eligibility.
• Apple Ads attribution: in the production environment, the app obtains an attribution token through Apple AdServices. Our service uses it to ask Apple whether the download came from an Apple Ads campaign for Yantu. Returned information may include campaign, ad group, and keyword identifiers, the campaign’s country or region, and conversion type. The token is used for that query and is not retained as a long-term user identifier.
• Purchases and revenue: RevenueCat server purchase notifications can provide our analytics service with product, transaction, trial, renewal, refund, and revenue information for reconciliation and promotion measurement. Client purchase outcome events contain no payment amount; revenue is based on server notifications.

These records are linked through a random identifier within the same app, with membership identifier relationships supplied by RevenueCat used where needed to reconcile purchases. They are pseudonymous, rather than fully anonymous records that cannot be linked to an individual’s activity. We do not combine user identities across our different apps, combine these records with user data from other companies’ apps or websites for advertising tracking, or sell or provide them to data brokers.

The app does not read IDFA, create a device fingerprint, or access device location. The advertising region describes the campaign, and the storefront region describes the store environment; neither means that we obtain your precise location. Analytics does not receive personal audio, file paths, audio or mix names, mix contents, passwords, or payment card numbers. Apple provides available attribution information according to system privacy settings; see Apple’s AdServices documentation.

Events may be queued on the device and sent in batches when connected; unavailable connections or services are retried. Production, sandbox, and development data are kept separate, and tests and previews are excluded from production analytics. The analytics endpoint processes network information needed for a connection and uses a short-lived network address digest to limit abuse; raw IP addresses are not written into product event or advertising attribution records.

5. Policy website visits and support

When you visit this website, the server receives ordinary access logs such as your IP address, the requested URL, the time, and the browser User-Agent. These help serve pages, operate the site, and protect its security. These pages set no tracking cookies and load no third-party scripts, analytics tools, or third-party fonts. Access logs are rotated daily, keeping the most recent 14 rotated logs; empty logs may not be rotated. Relevant records may be retained longer when necessary to address a security incident or meet legal requirements.

If you email us, we process your email address, message, and attachments to respond and troubleshoot. The app’s email draft includes the app version, device model identifier, system, and language; you can edit or remove them before sending. Email is sent only after you confirm. Please include only what is needed, without passwords, payment details, or personal audio. Contacting support does not automatically give us access to audio or mixes on your device.

We do not sell your personal information. Infrastructure providers may help operate website hosting and email; their processing is limited to providing those services, except for information that must be provided as required by law.

6. Retention, deletion, and security

App data remains on your device so you can continue using it. You can delete imported sounds or saved mixes and remove favorites. Deleting an imported sound also removes that track from mixes that use it; personal mixes with no remaining tracks are also deleted.

Deleting the app and its data through the system removes its local app data. This does not recall exported files or erase copies held by recipients, file services, or system backups. Manage those copies through the relevant service. Deleting Yantu does not cancel an Apple subscription and does not automatically delete purchase records held by Apple or RevenueCat.

Membership records may be retained for purchase verification, access restoration, support, refunds, and applicable recordkeeping requirements. You can request review or deletion of information processed for our membership service using the contact details below; requests are handled subject to applicable obligations and the records needed to locate and verify the purchase. Apple controls its own transaction records. To stop future renewal charges, use Apple’s subscription settings.

The analytics SDK’s local upload queue holds at most 2,000 events and discards records aged 30 days or more when adding or attempting to send events; disk cleanup is not promised to occur while the app is not running. While operating, our analytics service checks hourly and removes product events whose occurrence time is more than 180 days old. This rule does not cover attribution, purchases, user relationships, audit records, or backups. Those records are retained for analytics, reconciliation, security, and applicable recordkeeping needs and may be addressed through the request process below.

Deleting the app removes its local analytics queue but does not automatically delete records already sent. Verified deletion requests can remove related events, user relationships, attribution, and transaction records from our analytics service. This does not cancel subscriptions or stop subsequent purchase notifications from Apple or RevenueCat. Continued app use may produce new analytics records; describe any request about subsequent processing in your email.

Support correspondence is retained for the time needed to resolve the request, handle necessary follow-up, and keep necessary records. Deletion requests do not override retention required by law. We use reasonable protections such as access controls, but no storage or transmission method can guarantee absolute security.

7. Your choices and requests

You can manage relevant data and features in the app and in system settings. For support correspondence, website access information, membership records, or analytics and advertising attribution records processed for us, email support@yuuglow.com to request information, access, correction, or deletion. Describe the scope of your request. To protect information, we may need to verify your identity or ask for enough detail to locate a record.

We handle requests in accordance with applicable requirements and explain if a request cannot be fulfilled or some information must be retained. We cannot read or directly delete app files stored only on your device, or manage copies held by recipients on their behalf.

8. Updates and contact

When features or information practices change, we will update this policy and the date above. For significant changes, we will provide notice in the app or through another available channel where appropriate. If new processing requires your choice or consent, we will explain it and provide the relevant choice before it begins.

Operator: Chengdu Yuuglow Technology Co., Ltd.
Email: support@yuuglow.com