Advertising & Third-Party Notice

1. Recording files in the Service are, as a principle, stored locally on the user's device.
2. The Company does not store recording files on its own servers.
3. Recording files are transmitted to third-party services only when the user directly selects Google Drive save, file sharing, or export features.
4. Certain technical information, identifiers, or purchase information required for ad/payment/subscription management may be processed by external services listed below.

The Company may use the Google Mobile Ads SDK (AdMob) to provide in-app ads. According to Google's official data disclosure documentation, Google Mobile Ads SDK may process device IP address, user interaction information (for example, app launches, taps, video views), diagnostic information, app performance information, device or other identifiers, and ad-related data depending on implementation and settings.

Choices regarding ad-related personal information may vary by region and platform. In the EEA, UK, and Switzerland, Google requires notice and consent for collection/sharing/use of personal information for cookies or other local storage and personalized ads where legally required, and provides User Messaging Platform (UMP) SDK for this purpose. If ad identifier use corresponding to tracking is needed on iOS, Apple's App Tracking Transparency (ATT) permission may be required. Google also states that ad requests may still be made when ATT is denied, but IDFA is not included in ad requests. Therefore, actual ad behavior may differ between personalized and non-personalized ads depending on user region, consent status, device settings, and SDK configuration.

The Company does not provide the content of users' recording files to AdMob and does not use recording content or voice itself for ad targeting.

The Company may use RevenueCat for operation of paid features such as ad removal, premium features, subscription status checks, and purchase restoration. According to RevenueCat documentation, the Purchases SDK integrates with Apple or Google purchase flows to implement purchases/subscriptions and can sync purchase tokens with RevenueCat servers. RevenueCat also indicates that it generally creates an anonymous App User ID to identify customers.

According to RevenueCat's Google Play Data Safety guidance, purchase history is the required disclosure item when using RevenueCat, and the same guidance states that RevenueCat does not collect audio files, files/documents, contacts, app activity, or diagnostic information by default. Accordingly, the Company treats only purchase-related information required for paid feature management as processing targets and does not send recording files themselves to RevenueCat.

If the Service uses RevenueCat's anonymous App User ID model in a structure without separate account registration/login, subscription status may not automatically sync across apps or platforms. RevenueCat explains that anonymous App User ID is suitable for single-platform apps without authentication. Therefore, after device replacement, reinstall, or platform change, purchase restoration based on the same store account may be required.

Actual payments for paid features may be made through Apple App Store or Google Play payment systems. Apple requires subscription purchase screens to provide a way for existing subscribers to restore subscriptions and guides easy subscription management/auto-renewal cancellation. Google Play also explains that users can cancel subscriptions at any time in Play Store and view/manage subscriptions within Play Store.

Accordingly, subscription cancellation, refunds, re-subscription, purchase restoration, and payment error handling may vary depending on each store's policies, user store account status, and technical limits of each platform. The Company may provide related functions in-app, but part of final payment and subscription management procedures is handled by each app marketplace.

Google Drive save/export features operate only when directly selected by the user. In such cases, recording files chosen by the user and basic metadata required for storage (such as file name) may be transferred to Google Drive. Google Drive API documentation indicates uploads can process file data together with metadata.

Google API Services User Data Policy requires that use of Google user data be limited to disclosed Privacy Policy scope and disclosed purposes, and that notice/consent be updated if new methods or new purposes arise. In accordance with these principles, the Company limits Google Drive access scope to what users can understand and what is minimally required to provide the feature.

Files saved to Google Drive are managed in the user's Google account and Google Drive environment. Users can review or remove app access permissions in Google account third-party app connection management and can directly delete uploaded files in Drive. The Company does not centrally control retention/deletion of files stored in Google Drive on behalf of users.

1. Ad-related choices Users may adjust ad-related choices, where available, through in-app privacy option screens, consent screens, operating system settings, or platform permission settings. Google's UMP documentation states user consent status can be updated when the app launches and a privacy options entry point can be provided where required, and Apple requires ATT permission for data used for tracking in-app.

2. Purchase and subscription management Users can check and manage paid feature status through App Store or Google Play account settings and in-app purchase restoration features (if provided).

3. Google Drive usage choice Users may choose not to use Google Drive storage features and may directly delete already saved files in their Google Drive or revoke app access permissions in Google account settings.

If iCloud storage or other external services are added in the future, the Company may revise this notice before release or at release timing. This notice will also be updated if advertising SDKs, payment services, or external storage methods are changed.

This notice explains third-party service use related to advertising, payments, purchase restoration, and optional external storage features. More detailed matters such as processing items, retention periods, cross-border transfer, and methods for exercising data subject rights are governed by the separate Privacy Policy.