Moonmic Privacy Policy

First Published: October 22, 2026 · This Revision Published: October 22, 2026

CodeSand Co., Ltd. (the "Company") handles the personal information of Moonmic (the "Service") users with care and complies with the Personal Information Protection Act of Korea and other applicable laws. This policy is written so that users can see what information the Company collects, when, where it is sent, what it is used for, and when it is deleted.

1. Personal Information Collected

General: the Company does not collect your name, email address (except when you send an inquiry email yourself), phone number, precise location (GPS), contacts, photos, call or message logs, health information, payment-instrument information such as credit card numbers, or unique government identifiers such as resident registration numbers. The permissions the app requests are Microphone (for night recording — you can still use bedtime sounds without it) and Notifications (Android — for the persistent notification shown while recording; recording works even if you decline). On iOS a separate prompt asks whether to allow tracking for ad personalization (Section 7). The app does not request location, contacts, photo, storage, or camera permissions. Because the Service has no accounts, it does not collect names, passwords, or social-account information.

(a) Microphone input — only the moments with sound are saved on your phone, as clips

While a night started with "Start recording" is in progress, the Service keeps the microphone open. For about 30 seconds after the start it measures the room's background noise (the baseline), and then saves only a few seconds before and after each moment that is louder than the baseline by a set margin, as a short clip (up to 3 minutes per clip). The full night's audio is never stored; the audio used for the baseline and the audio between events is discarded without being saved.

Sounds of people sleeping next to you. Any sound near the phone may be recorded even if it is not yours (a partner's snoring or talking, pets, and so on). The Company does not receive those sounds, but it is your responsibility to inform anyone else present in the space where you record and to comply with applicable law (Terms of Service, Section 4(e)). The app reminds you of this during first-run onboarding.

(b) Information that stays on the device and is not collected by the Company

This information is recorded only in the device's internal storage and there is no path by which it is sent to a Company server. However, bucketed or categorical values of some of it (the duration and detection-count buckets, end reason, bedtime sound number, the kind of label correction, and so on) are sent as the "App interactions" item in (c) below while usage statistics are on — the times at which sounds occurred, dB values, tags, and the clips themselves are never sent. Deleting the app deletes the information on the device.

Exporting clips. On the Clips screen you can export a clip you recorded as a file. The file is copied on the device and handed to the app you choose in the operating system's share sheet (mail, messenger, cloud storage, and so on); it does not pass through a Company server. The exported file's name contains the date and time the clip started (for example Moonmic_20261019_031805.m4a), so the recipient can see that time. What happens after the hand-off is the responsibility of the app you chose and the recipient. The bedtime sounds bundled with the app (noise, nature sounds, music) cannot be exported.

(c) Information the Company collects — by store-declared type

The information below is sent over the network (HTTPS) directly to the systems of the external providers named, not to the Company, at the moment the relevant function runs; the Company views aggregated results and individual error records through those providers' consoles. The Company does not separately gather this information on its own servers. The outsourcees and their work are set out in Section 5 and the details of overseas transfer in Section 6.

App interactionsApp activity · can be turned off in Settings
Items
① usage events defined by the Company (the app does not send any event or value outside a fixed, predefined list): screen view (screen type only), onboarding completed, night start (bedtime sound number, timer minutes, play mode, whether the baseline was measured, start delay minutes), whether playback handed over to recording, night end (end reason, the recording-duration bucket (e.g. "6–8 hours"), the detection-count bucket (e.g. "11–30"), whether the clip cap was reached, the interruption-count bucket), microphone error stage and type, clip relabel (the kind of label before and after), the fact that a clip was exported, the path by which the Unlock screen was opened, the kind of purchase result (purchased, restored, cancelled, error, pending), how the code-entry screen was opened, the response to the battery hint, and the fact that usage statistics were turned off ② a user property — whether Unlock all features is owned ③ basic events the analytics tool collects automatically (first open, session start, app update, completion of an app-store in-app purchase, and the like) and the basic information attached to them (device model, OS version, app version, device language and country) ④ basic information sent when fetching the remote configuration values that determine the price-notice wording on the purchase screen (app instance ID, app version, OS, device language and country)
When
when the app is launched and when the relevant action occurs
Sent to / kept by
Google LLC (Google Analytics for Firebase · Firebase Remote Config, Google data centers in the United States and elsewhere)
Purpose
improving the Service, analyzing usage statistics (where overnight recording breaks off, which features are used), analyzing paid conversion, displaying the price notice on the purchase screen

Events never include recordings, clips, file names, file paths, the times at which sounds occurred, sound levels (dB), tags, or text you enter. Recording duration and detection counts are sent only as buckets, never as exact values. Only fixed screen names chosen by the Company are sent, and the operating system's automatic screen reporting is off. The analytics tool's advertising-ID collection is off, and the analytics tool is not linked to the ad SDK. Turning off Settings → Privacy → "Send usage statistics and error reports" (on by default) sends one final "statistics turned off" event and then stops all collection by the analytics tool and stops fetching remote configuration; the setting persists across launches. Deletion of data already sent before you turned it off follows the procedure in Section 8.

Purchase historywhen a paid product is purchased
Items
the kind of purchase/restore result for Unlock all features and ownership status, the fact that an app-store in-app purchase was completed, and the transaction amount and currency the analytics tool records automatically
When
when a paid product purchase or restore completes (only while usage statistics are on)
Sent to / kept by
Google LLC (Google Analytics for Firebase)
Purpose
analyzing paid conversion, usage statistics by ownership status

The payment itself is processed by the Apple App Store or Google Play; the Company receives no payment-instrument or app-store account information. When you unlock with an offer code or promo code, the code value is not sent. Turning off usage statistics stops this item too.

DiagnosticsApp info and performance
Items
① Error reports — the type and message of the error or crash and the stack trace (the execution path through the app's code), time of occurrence, app version, build number and release identifier, device model and OS version, a marker for the action in which the error occurred (e.g. "night.mic_stream" — only predefined fixed strings), whether the error was handled, the app's state at the time (whether the app was in the foreground), and a per-installation identifier the error-collection tool issues at random for each installation ② App sessions — the start and end times of one run of the app (a session) and whether it ended normally, with an error, or with a crash; app version, build number and release identifier; device model and OS version; the same per-installation identifier as in ① ③ the ad SDK's performance and diagnostic information such as ad request and loading status, app-launch and ad-loading times, and errors
When
① when an error or crash occurs in a release build that has an error-collection address (DSN) configured ② when the app is launched and when it returns from the background — sent even when no error occurs (① and ② only while "Send usage statistics and error reports" is on) ③ when an ad is requested or shown
Sent to / kept by
①② Functional Software, Inc. (Sentry, EU region in Germany) ③ Google LLC
Purpose
analyzing the cause of errors and securing the stability of the Service (in particular, finding out why overnight recording stops midway), calculating per-version stability metrics (the share of runs that ended without a crash), checking ad serving status

Error reports do not include screenshots, screen recordings (session replay), or app-speed tracking (performance data); the Company sets no user identifier (the user field is cleared before sending); and automatic attachment of basic personal data such as email or IP address is turned off. If an error message, exception string, or action log (breadcrumb) contains a file path or clip file name, it is removed leaving only the extension before sending (because clip paths contain the night and clip number), and navigation history showing which screens were opened and development logs are not sent as breadcrumbs. The connecting IP address may be observed during receipt, but the tool is configured not to store it as the user's IP in the error record. Native crashes on Android and iOS are sent directly by the error-collection tool's native SDK through a separate path; no code places user data in those messages, but they may contain the per-installation identifier and device/app diagnostic information. There is no path at all by which recordings, clips, tags, or sound-level values are sent. Turning off "Send usage statistics and error reports" shuts down the error-collection tool itself immediately, so nothing is sent from then on — not error reports, not app sessions (②), and not native crashes. If the app is started with the switch off, the error-collection tool is not started at all; turning it back on resumes sending from the next error and session onward.

Advertising datawhen ads are requested, shown, or consent is processed
Items
records of interaction with ads such as requests, impressions, and clicks; device/OS information and the connecting IP that the ad SDK collects itself to serve ads and measure performance; the ad-consent choice made by users in the European Economic Area, the United Kingdom, and Switzerland; and the iOS tracking-permission status
When
when the banner ad at the bottom of the History screen or the Morning summary screen is requested or shown, when you interact with an ad, and when the ad-consent flow runs
Sent to / kept by
Google LLC (AdMob · User Messaging Platform)
Purpose
serving, personalizing, and measuring ads; analyzing ad statistics; preventing invalid traffic (click fraud); managing ad consent

Ad placements are only the two bottom banners on the Morning summary screen and the History screen; there are no ads on the onboarding, Tonight, sound picker, Night (recording), Clips, Settings, or purchase screens. The ad SDK starts when the History screen's banner placement first becomes visible, not at app launch; before that there are no ad requests and no consent or tracking prompts. While Unlock all features is owned, the ad SDK is not started, so this item is not collected. If you purchase during use, the banner is removed immediately and new ad requests stop, but an ad SDK that has already started remains in memory until the app is relaunched.

Device or other IDsstatistics · ads · error diagnostics
Items
① the app instance ID the analytics tool issues at random for each installation and, on iOS, the identifier for vendors (IDFV) the analytics tool may read by default. The Android advertising ID is configured not to be collected by the analytics tool ② the Android advertising ID and Android app set ID used by the ad SDK, the iOS advertising identifier (IDFA — only if you allowed tracking in the App Tracking Transparency prompt) and app/developer-scoped identifiers, and device/OS information ③ the per-installation identifier the error-collection tool issues at random for each installation
When
① when the app is launched (if usage statistics are on) ② when an ad is requested or shown (if Unlock all features is not owned) ③ when an error occurs and when an app session is sent
Sent to / kept by
① ② Google LLC (United States and elsewhere) ③ Functional Software, Inc. (Sentry)
Purpose
① distinguishing the same installation in statistics ② serving and personalizing ads, controlling frequency, preventing invalid traffic ③ de-duplicating error reports and counting sessions per installation

These identifiers are not linked to your identity (account, name, contact details) and are not hardware serial numbers. The app instance ID and the per-installation identifier are issued anew when the app is deleted and reinstalled (this app is excluded from OS backups, so previous values are not restored). On iOS, if you do not allow tracking, the advertising identifier (IDFA) is not used and non-personalized ads are shown. On Android you can reset the advertising ID or turn off ad personalization in device settings. Your choices are described in Section 7.

Coarse locationcountry / region / city level
Items
location at country, region, or city level inferred from the connecting IP address, during ① processing of statistics events, remote configuration fetches, and ad requests ② receipt of error reports and app sessions
When
① when the app is launched (if usage statistics are on) and when an ad is requested or shown ② when an error occurs and when an app session is sent
Sent to / kept by
① Google LLC ② Functional Software, Inc. (Sentry)
Purpose
regional usage statistics, serving region-appropriate ads and determining consent regions, understanding the environment in which errors occur

The app does not request location permission, does not collect precise location such as GPS, and stores no coordinates in night records. Error reports do not store the IP address itself, only the country/region/city inferred from it.

Inquiry content and email addressonly when you send an email
Items
the content of your inquiry, the sender's email address, the app name, app version (build number), and operating-system name and version the app pre-fills in the subject line and at the end of the body (you can delete them before sending), and any information you add yourself (device model, app-store receipt number for refund inquiries, and so on)
When
when you send an email yourself to the address in Section 11. The app has no inquiry-sending feature and never sends anything on its own
Sent to / kept by
email is received by Mailgun (United States) and forwarded to the Company's mailbox system (server in Seoul, Republic of Korea), where it is kept in the Company's mailbox
Purpose
replying to and handling inquiries, reproducing and fixing reported problems, handling consumer complaints and disputes such as refunds

Settings → Privacy → Contact us in the app only opens your mail app with the recipient address, a subject line (app name and version), and the app version and operating-system information at the end of the body pre-filled; writing and sending the email happens in your mail app. Everything pre-filled is visible and can be deleted before you send, and if no mail app is available the app only copies the address for you. Recordings, clips, night records, tags, and device identifiers are never sent automatically with an inquiry — the app has no path to send them unless you attach them yourself. Reply emails from the Company are also sent through Mailgun. The outsourced work is set out in Section 5, the details of the overseas transfer in Section 6, and retention in Section 3(c).

2. Purpose of Use of Personal Information

The Company uses collected personal information only for the following purposes, and if a purpose changes it gives advance notice and obtains any required consent.

The Company does not use your recordings, clips, night records, or tags for advertising or marketing. That information is never delivered to the Company in the first place. The Service only records and logs sound; it does not provide any medical judgment about your sleep or health (Terms of Service, Section 4(a)).

3. Retention and Use Period, and Destruction

(a) Information stored on the device

Night records, clips, tags, and app settings exist only on your device; because the Company does not hold them, there is nothing for the Company to destroy and no destruction procedure on its side.

Because the Service has no accounts, there is no membership-withdrawal procedure.

(b) Items with a defined period

(c) Items kept as required by law

Payment and refund records for paid products are kept by the sellers, the Apple App Store and Google Play, under their own policies and applicable law; the Company does not hold them.

(d) Method of destruction

Information whose retention period has expired or whose purpose has been achieved is permanently deleted from electronic files by a method that prevents recovery or reproduction.

4. Provision of Personal Information to Third Parties

The Company does not provide users' personal information to third parties, except in the following cases.

Where the recipient of a clip you exported and sent yourself can see its contents, that is disclosure by your own choice, not provision to a third party by the Company. The transmission of information to external providers for usage statistics, ad serving, error diagnostics, and receiving inquiry emails and sending replies is outsourcing of processing under Section 5, and its details are set out in Sections 5 and 6.

5. Outsourcing of Personal Information Processing

The Company outsources the processing of personal information to the following providers to provide the Service. If an outsourcee or the outsourced work changes, the Company discloses it through this policy.

Google LLCPrivacy Policy
Outsourced work
collecting and analyzing usage statistics (Google Analytics for Firebase), providing the price-notice configuration for the purchase screen (Firebase Remote Config), serving and measuring AdMob ads, managing ad consent for users in the European Economic Area, the United Kingdom, and Switzerland (User Messaging Platform), processing Google Play in-app purchases
Processing location
United States and elsewhere
Apple Inc.Privacy Policy
Outsourced work
processing App Store in-app purchases
Processing location
United States
Functional Software, Inc. (Sentry)Privacy Policy
Outsourced work
collecting and analyzing error diagnostics and app session information
Processing location
Germany (Sentry EU region)
Mailgun Technologies, Inc.Privacy Policy
Outsourced work
receiving and forwarding inquiry emails and sending reply emails
Processing location
United States
The Constant Company, LLC (Vultr)Privacy Policy
Outsourced work
operation of the Company's web service servers that receive inquiry emails (Seoul region, Republic of Korea)
Processing location
Seoul region, Republic of Korea

The sellers of paid products are the Apple App Store and Google Play, which process payments under their own terms and privacy policies. The Company does not collect or store payment-instrument information; it records only the fact that a purchase was completed, on the device, to determine whether Unlock all features applies. Details of transfers to providers located overseas are set out in Section 6. Email inquiries are received by Mailgun (United States) and forwarded to the Company's mailbox system (server in Seoul, Republic of Korea), where they are kept in the Company's mailbox. Reply emails from the Company are also sent through Mailgun.

6. Overseas Transfer of Personal Information

In providing the Service, the Company transfers personal information overseas as follows. These transfers constitute outsourcing and storage for the conclusion and performance of a contract with the data subject under Article 28-8(1)(3) of the Personal Information Protection Act of Korea, and disclosure of the matters below through this policy serves as the required notice.

Time and method of transfer (common to all providers below): sent over the network (HTTPS) as needed at the moment you use the relevant function. Usage statistics are sent when the app is launched or the action occurs, error reports when an error occurs, app session information when the app is launched or returns from the background, ad information when an ad is requested or shown, and inquiry emails when you send an inquiry or the Company replies. Each provider's contact details are available through its privacy policy link.

Google LLCPrivacy Policy
Destination country
United States and elsewhere (countries where Google data centers are located)
Items transferred
usage-statistics events and user properties (Section 1(c) "App interactions" and "Purchase history"), app instance ID and iOS identifier for vendors, device model, OS version, app version, device language and country, basic information sent with remote-configuration requests, advertising identifiers (Android advertising ID and app set ID; on iOS the IDFA only if tracking is allowed), IP address and the country/region inferred from it, ad interaction records such as impressions and clicks, ad consent status, the ad SDK's diagnostic information, Google Play in-app purchase transaction information (by Google account — the Company cannot access payment-instrument information)
Purpose
analyzing usage statistics and improving the Service, displaying the price notice, serving, personalizing, and measuring ads, analyzing ad statistics, preventing invalid traffic, managing ad consent, processing Google Play payments
Retention period
usage statistics for the period in Section 3(b); otherwise until the outsourcing contract ends or the purpose is achieved. The Company does not hold the data itself; actual retention follows Google's privacy policy.
How to refuse, and the effect
turning off Settings → Privacy → "Send usage statistics and error reports" stops usage statistics and remote-configuration requests (the purchase screen then shows the price only, without a notice). Transfers for advertising purposes do not occur once you purchase Unlock all features. Recording, history, and playback remain fully available whichever you refuse.
Apple Inc.Privacy Policy
Destination country
United States
Items transferred
App Store in-app purchase transaction information (by Apple account — the Company cannot access payment-instrument information)
Purpose
processing App Store payments
Retention period
until the outsourcing contract ends or the purpose is achieved
How to refuse, and the effect
no transfer occurs unless you purchase a paid product. Free features remain available.
Functional Software, Inc. (Sentry)Privacy Policy
Destination country
Germany (Sentry EU region). The recipient is a US corporation.
Items transferred
error type, message, and stack trace (with file paths and clip file names removed), time of occurrence, app version, build number and release identifier, device model and OS version, the fixed marker for where the error occurred, per-installation identifier, country/region/city inferred from the connecting IP, and app session start/end times and end status (normal, error, crash)
Purpose
analyzing the cause of errors and securing the stability of the Service, calculating per-version stability metrics
Retention period
error reports for the period in Section 3(b); app session information under the provider's retention policy
How to refuse, and the effect
turning off Settings → Privacy → "Send usage statistics and error reports" shuts down the error-collection tool itself, so neither error reports nor app session information is sent. Recording, history, and playback remain available.
Mailgun Technologies, Inc.Privacy Policy
Recipient
Mailgun Technologies, Inc. (United States; data protection officer contact dpo@sinch.com)
Destination country
United States
Time and method of transfer
sent over the network when you send an inquiry email or when the Company replies
Items transferred
email address, subject and body of the email, attachments
Purpose of transfer
receiving and forwarding inquiry emails and sending replies
Retention and use period
The message body is not stored with Mailgun but only in the Company's mailbox (server in Seoul, Republic of Korea). Processing records (sender and recipient addresses, subject, time, and processing result) may remain with Mailgun for up to 30 days under Mailgun's retention policy. The email is kept in the Company's mailbox for the inquiry retention period in this policy (Section 3(c))
How to refuse, and the disadvantage
if you do not want this overseas transfer, you may choose not to send an email inquiry; every feature of the app remains available regardless of inquiries. Email inquiries cannot be handled without this transfer

If you do not want your personal information transferred overseas, in addition to the settings and purchase above you may express your refusal to the data protection officer in Section 11.

7. Advertising Identifiers, Personalized Advertising, and Ad Consent

The Service is provided free of charge and funded by advertising. Users who have not purchased Unlock all features see Google AdMob banner ads at the bottom of the Morning summary screen and the History screen. There are no ads while recording, while bedtime sounds play, or during onboarding, and no interstitial, rewarded, or app-open ads are used.

For details, see the Google Privacy Policy and the Google Ads Controller Terms.

8. User Rights and How to Exercise Them

You may at any time request access to, correction of, deletion of, or suspension of processing of your personal information, and withdraw consent, by the following means.

Because the Service has no accounts and does not send recordings or records to a server, the Company holds no per-user information. Usage statistics and error records carry no user identifier set by the Company, so it may be difficult to single out a particular user's records; they are destroyed automatically after the periods in Section 3(b). Where there are legitimate grounds to limit a request, the Company explains them.

The legal guardian of a child under 14 may exercise the above rights on the child's behalf.

9. Measures to Secure Personal Information

The Company implements the following measures.

10. Personal Information of Children under 14

The Service is not directed at children under 14 and does not knowingly collect their personal information. If the Company learns that personal information of a child under 14 has been collected, it destroys that information without delay.

11. Data Protection Officer and Remedies for Infringement of Rights

The Company has designated a data protection officer, and users' inquiries, complaints, requests for remedy, and access requests regarding the handling of personal information are processed by the department below.

To obtain remedy for infringement of personal information, you may apply for dispute resolution or consultation with the following bodies in Korea.

12. Changes to This Policy

Effective Date: October 22, 2026 (first effective October 22, 2026)
The contents of this policy may be added to, deleted, or amended in response to changes in laws, policies, or the Service, and when it changes, the reason and the effective date are stated and the change is posted on the Service website.


© 2026 CodeSand Co., Ltd. Business Registration No. 368-87-03020.