짝짝(ClapClap) 개인정보처리방침

ClapClap is an alarm clock you turn off by clapping. There is no account, no login and no server, and your alarms and settings are stored only on this device. The microphone turns on only while the alarm screen is open and reads only changes in loudness. It never keeps a recording or sends sound off your device. One Google AdMob banner appears at the bottom of the alarm list, and the internet is used only for that ad. There are no ads on the alarm screen (section 5).

From version 1.1.0, the app is available in English and Korean and follows your device's language settings. On Korean devices it is called 짝짝. The information it handles is the same in both languages. The Korean policy above and this English policy describe the same practices.

1. Information we process and why

ClapClap does not collect information that identifies you, such as your name, email address, phone number or location. While you use the app, the values below are stored only on this device or held briefly in memory. For each one we list the purpose, where it is kept and for how long. None of them are passed to the ads SDK. The information the Google ads SDK handles to show ads, such as the advertising ID, is described separately in section 5.

• Alarm list (alarm number, time, label, repeat days, sound, clap to stop on or off, vibrate on or off, alarm on or off) · Purpose: rings each alarm on time and shows it in the list · Stored in: the app's private storage on this device · Kept until: you delete the alarm or the app. Labels are text you type yourself, and they never leave the device.
• App settings (clap sensitivity, default vibration for new alarms, whether you have already seen the permission guide) · Purpose: keeps your sensitivity and defaults, and avoids showing the permission guide again · Stored in: this device · Kept until: you delete the app.
• Next alarm number (a single number) · Purpose: gives each new alarm a number that is not already in use · Stored in: this device · Kept until: you delete the app. It is a counter with no other content.
• Snooze count for each alarm · Purpose: shows how many times you snoozed on the result screen after you stop the alarm · Stored in: this device · Kept until: you stop or delete that alarm, at which point its count is removed right away.
• Microphone sound · Purpose: detects claps while an alarm is ringing · Processed in: device memory · Kept: never. While the alarm screen is open (only for alarms with clap to stop turned on), the app receives a 16 kHz mono PCM audio stream, turns it into loudness values for short time windows and discards the raw audio at once. Nothing is written to a file, and the microphone is stopped and released as soon as the screen closes.
• How the alarm was stopped and how long it rang · Purpose: shows the result screen right after you stop an alarm · Processed in: device memory · Kept until: you close the result screen.

Alarm notifications (title, text and the Stop button) are created on the device in your screen language. If you change your device language while the app is running, alarms that are on are rescheduled on the device so their notifications use the new language. Nothing new is stored or sent anywhere when this happens.

2. Permissions

When you save your first alarm, a guide sheet explains each permission and then asks for the microphone, exact alarms, notifications and the battery exemption, one at a time. You can skip them and the alarm is still saved. Below are the permissions the app actually requests or declares, and what each one is for. Permission prompts follow your device language (English or Korean).

• Microphone (Android RECORD_AUDIO, iOS microphone) · Turned on only while the alarm screen is open, to detect claps. It stays off while the app waits. The app checks again when an alarm rings, and if you deny access, you can stop or snooze with the Tap instead button on the screen. The iOS permission text on English devices reads: “ClapClap uses the microphone only while an alarm is ringing, to hear your claps. Sound is processed on your device and never saved.”
• Exact alarms (Android SCHEDULE_EXACT_ALARM, USE_EXACT_ALARM) · A core alarm clock feature that lets alarms ring right on time. The in-app explanation reads “Needed to ring right on time.”
• Notifications (Android POST_NOTIFICATIONS, iOS notifications) · Shows a notification with a Stop button when an alarm rings. The notification shows only the alarm's label (or “ClapClap alarm”), a one-line reminder of how to stop it and the Stop button. On iOS, if the app is fully closed, the device also shows a local notification warning that alarms may not ring.
• Full-screen alerts (Android USE_FULL_SCREEN_INTENT) · Shows the alarm screen over your lock screen. There is no system dialog for this, so the app only points you to its settings page.
• Battery exemption request (Android REQUEST_IGNORE_BATTERY_OPTIMIZATIONS) · Strict battery saving can delay or block alarms, so the app asks to be exempted. It is used only to ring on time.
• Wake and vibrate (Android WAKE_LOCK, VIBRATE) · Turns on the screen and vibrates when an alarm rings. These are normal permissions that never show a prompt.
• Permissions added by the alarm plugin (Android RECEIVE_BOOT_COMPLETED, FOREGROUND_SERVICE, FOREGROUND_SERVICE_MEDIA_PLAYBACK, ACCESS_NOTIFICATION_POLICY) · Used to restore scheduled alarms after your device restarts and to keep the service that plays the sound running while an alarm rings. They never show a prompt.
• iOS background modes (audio, fetch) · Let the alarm sound play on time while the app is in the background. They are not used to listen or record.
• Internet (Android INTERNET, ACCESS_NETWORK_STATE, AD_ID) · Not declared by the app's own code. These normal permissions are added by the Google ads SDK at build time and are used only to load the banner on the alarm list. Every alarm feature works without the internet. They never show a prompt.
• Permissions we do not request · ClapClap does not declare storage (photos and files), location, camera, contacts or calendar permissions. Alarm sounds come only from files built into the app.

3. What is sent to a server and how long it is kept

ClapClap has no SLOX server. The app's code makes no network requests, and none of the values in section 1 (alarms, settings, microphone sound, snooze counts) ever leave the device. Only the Google ads SDK described in section 5 uses the network. A database library that ships in our shared UI package is never set up or called in ClapClap. The app does not handle location, names, contacts or hardware device identifiers.

4. Service providers, sharing and international transfers

Because the values in section 1 never leave the device, SLOX has nothing to hand over to service providers or share with third parties. Clap detection is an on-device calculation that looks only at changes in loudness, and it does not use operating system speech recognition (Apple or Google). The only case in which a company other than SLOX handles information is the following.

• Google AdMob (in-app ads) · To show the banner on the alarm list, the Google ads SDK collects the information described in section 5 and processes it on Google's servers. Google runs servers in several countries, so this information may be processed outside your country. What is collected, why, and your choices are described in section 5.

Downloads and installs are handled by the App Store and Google Play under their own policies, and ClapClap receives no information from that process.

5. Ads

ClapClap shows one Google AdMob banner at the bottom of the alarm list. The alarm screen, the alarm editor and Settings have no ads, there are no interstitial or rewarded ads, and no new banner is requested while an alarm is ringing. To serve and measure ads, the Google Mobile Ads SDK may collect your device's advertising ID, approximate location based on your IP address (country or region level), ad views and clicks, and app performance and crash diagnostics. Microphone sound, clap detection results, and your alarms and labels are never passed to the ads SDK.

• No tracking · On iOS, ClapClap does not ask for App Tracking Transparency (ATT) permission and does not use the advertising ID to track you across other companies' apps or websites.
• Ad content rating · Ads are requested with a maximum content rating of T (Teen).
• Consent and choices · Users in the European Economic Area (EEA) and the UK see a consent form before any ad is shown and can change their choice at any time with Ad privacy settings in Settings. Elsewhere, no extra consent is needed, so the button is unavailable and shows “Not needed in your region.”
• Deletion and questions · Information collected by the ads SDK is processed by Google. SLOX does not receive it at the individual level, so it cannot be deleted from within the app. On Android, you can reset or delete your advertising ID under Ads in your device settings. For details on how Google processes this data, see Google's advertising policy.
• No analytics · ClapClap includes no usage analytics SDKs and uses the internet for nothing other than ads.

6. Children

ClapClap has no accounts and does not ask your age. It is not directed at children under 13, and in the EEA and UK it is not directed at children under 16 where local law sets that age. Because everything stays on the device, the operator receives no personal information from any user, and we do not knowingly collect personal information from children.

7. Your rights and how to delete your data

You can see, change and delete the values stored on your device directly in the app.

• Open any alarm in the list to change it, or remove it with Delete alarm. Deleting an alarm also deletes its snooze count.
• Change clap sensitivity and the default vibration for new alarms in Settings.
• There is no delete-all button in the app. To erase your alarms, settings, the next alarm number and snooze counts all at once, delete the app; they are deleted with it.
• The operator keeps no personal information on a server, so there is nothing on our side to delete. For questions about this policy, or about access, correction or deletion, email us at the address below and we will reply.
• If you are in the EEA or UK, you can also complain to your local data protection authority.

8. Security

• The app's code makes no network requests, so alarms, settings and microphone data have no way to leave the device. The network is used, over HTTPS, only when the Google ads SDK loads ads.
• Microphone sound is never written to a file. In memory it is turned into loudness values for short time windows, and the raw audio is discarded at once. When the alarm screen closes, the microphone is stopped and released.
• Alarms and settings are kept in the app's private storage, which the operating system keeps separate for each app. The app does not add its own encryption.
• The storage (photos and files) permission has been removed, and alarm sounds come only from files built into the app.

9. Privacy officer and contact

• Service provider: SLOX (ClapClap)
• Privacy officer: Seokwon Yang (양석원)
• Contact: namurobori@gmail.com

10. Changes to this policy

If this policy changes, we will post the revision date and version on this page. The app has no server and cannot announce changes inside the app, so this page is how we notify you.

• September 23, 2026 · v1.0 · First version.
• September 24, 2026 · v1.1 · Added one Google AdMob banner at the bottom of the alarm list. Section 5 became Ads, and the internet permission, service provider and international transfer text was updated.
• October 7, 2026 · v1.2 · Added the English app (English name ClapClap) and this full English policy. Sections 1, 2 and 5 now cover the language of notifications and permission prompts, and the pause on banner requests while an alarm rings. The information we handle is unchanged. Applies from app version 1.1.0.