Privacy Policy
Announcement date: 2026-08-29 · Effective date: 2026-09-05
StrikeLab ("the Company") processes information only to the extent necessary to operate its website and Owlarm. Owlarm has no user registration and no company-operated user data server; app data such as alarms and wake history is stored only on the user's device. However, to provide advertising and prevent ad fraud, the Google Mobile Ads SDK processes the advertising usage information described below, and to process subscription purchases and check status, Google Play Billing communicates with Google Play.
1. Purposes of Processing Personal Information
- Receiving and responding to product, partnership, and customer inquiries through the website
- Providing Owlarm's alarm scheduling, alarm dismissal, wake history, settings, and subscription status
- Providing advertising to free users, measuring and analyzing ad performance, and preventing ad errors and fraudulent use
- Purchasing paid services through Google Play, checking subscription status, and restoring purchases
2. Items Processed and Collection Methods
| Category | Items Processed | Method and Location of Processing |
|---|---|---|
| Email inquiries | Sender's email address, the name shown in the email, the inquiry content, and any materials the user attaches | Collected when the user sends an email directly to contact@strikelabkr.com |
| Owlarm local data | Alarm time, repeat days, enabled status, dismissal method and target count, alarm label, alarm sound URI, volume and vibration settings; wake time, completed count, normal or emergency dismissal; seal time and count; onboarding completion, practice completion, and seal bypass status; subscription-active status and the time of the last subscription check | Generated from the user's input and app usage and stored in the on-device Room database and DataStore. Not transmitted to any company server |
| Microphone input | 16kHz mono audio signal used to detect claps and shouts | Analyzed in real time on the device when the user grants microphone permission and performs a clap dismissal or Strixy learning (clap recognition calibration). No recording file is created, and the raw audio is not stored or transmitted |
| Clap detection log files | The time each alarm rang and how it was dismissed; the detection score and threshold values for each clap (energy floor ratio, attack ratio, peak amplitude, classifier threshold); per-user calibration values and calibration quality; the length and strength of shouts; and impact magnitude, jerk, and stable maximum measured by the device's accelerometer | Written by the app while clap dismissal and Strixy learning are running, appended to date-named files (format: events-20260829.jsonl) in the app's private folder on the device. No other app can read them and they are not transmitted to any company server. The audio itself is not included; only the resulting detection numbers are kept |
| Advertising usage information and advertising SDK sensor information | Per the Google Mobile Ads SDK's disclosure: IP address (which may allow approximate location estimation), product interactions such as app launches and taps, app/SDK diagnostic information, and device or account identifiers such as advertising ID and app set ID. The advertising SDK may use device sensor information such as accelerometer, gyroscope, and rotation | May be processed by the Google Mobile Ads SDK to serve ads and to prevent ad fraud, an industry-standard practice, when preparing or loading a banner or rewarded ad. This sensor access is unrelated to Owlarm's dismissal detection, and the Company does not receive or store that sensor information. Ads are not shown to paid subscribers, but in the current implementation a rewarded ad may be preloaded when entering the alarm-editing screen, so the possibility of the SDK's sensor access cannot be ruled out |
| Google Play billing | Subscription product information, purchase status, and purchase token. The app stores only the subscription-active status and the time of the last subscription check locally, and does not store the purchase token | Google Play Billing communicates with Google Play to process subscription purchases and check status when the app starts, when the user returns to the app, and when the user requests a purchase or restoration. Payment is processed by Google, and the Company does not receive or store payment-method information such as card numbers |
| Website settings | Light/dark mode selection | Stored only in the browser's localStorage and not transmitted to any company server |
3. Retention and Use Period
- Email inquiries: Retained until the inquiry and any follow-up response are complete, then deleted without delay. Where retention is required by applicable law, it is kept separately for the period shown in the table below.
- Owlarm local data: Alarms can be deleted within the app. Other local data, such as wake history and settings, remains on the device until the user clears the app's data or uninstalls the app through Android.
- Raw microphone input: Discarded immediately after real-time detection and not retained separately.
- Clap detection log files: Accumulated only on the device with no automatic deletion schedule, because they are the material used to improve clap recognition. They are removed when the user clears the app's data or uninstalls the app through Android, and remain on the device until then.
- Subscription status: Kept on the device for as long as needed to provide subscription status, and deleted together when app data is cleared.
- Advertising and Google Play processing information: The Company does not keep a separate copy, and this information is processed according to Google's policies and the user's settings.
As an online retailer, the Company retains the following transaction records for the periods below, as required by Article 6 of the Act on the Consumer Protection in Electronic Commerce, Etc. These records are used to respond to subscription payment and purchase-restoration inquiries and are destroyed once the period expires.
| Type of transaction record | Retention period |
|---|---|
| Records of contracts or withdrawal of offer | 5 years |
| Records of payment and supply of goods/services | 5 years |
| Records of consumer complaints or dispute resolution | 3 years |
| Records of labeling and advertising | 6 months |
Owlarm does not allow standard Android automatic backup. However, data-transfer behavior may vary depending on the Android version and the device manufacturer's platform policy.
4. Provision to Third Parties
The Company does not sell users' personal information and, in principle, does not provide it to third parties without the user's consent. However, it may be provided to the extent necessary where the user has given prior consent or where a law specifically provides for it.
5. Outsourced Processing, External Services, and Overseas Transfers
The following external services are used to provide the service.
| Provider | Purpose of Use | Information Processed |
|---|---|---|
| Google LLC | Providing, analyzing, and preventing fraudulent use of Google Mobile Ads | IP address, product interactions, diagnostic information, device or account identifiers, and device sensor information such as accelerometer, gyroscope, and rotation that may be used for ad-fraud prevention |
| Google LLC | Google Play in-app billing, subscription status verification, and restoration | Subscription product, purchase status, purchase token, and information Google requires to process payment |
| Google Fonts, jsDelivr | Delivering web fonts for the website | IP address and browser/device communication information involved in the font request |
The specific processing and retention standards of external services follow each provider's privacy policy and the user's settings.
5-1. Transfer of Personal Information Overseas
The external services above are operated by companies located outside the Republic of Korea. Personal information is therefore transferred overseas as follows. Among these, the advertising identifiers and related data transferred to Google LLC for ad delivery are not processed by the Company itself but are outsourced to Google for the task of serving ads; publishing the table below serves as the notice required under applicable law for this outsourced processing.
| Recipient | Country | Items transferred | Time and method of transfer | Purpose | Retention period |
|---|---|---|---|---|---|
| Google LLC | United States and other countries where Google data centers are located | IP address, advertising identifier, product interaction and diagnostic information, device or account identifiers, and device sensor information that may be used to prevent ad fraud | Transmitted over the network when the app requests an ad | Serving and measuring ads, and preventing fraudulent use | In accordance with Google's privacy policy |
| Google LLC | United States and other countries where Google data centers are located | Subscription product, purchase state, purchase token | Transmitted over the network when a subscription is purchased, verified, or restored | Processing in-app payments and verifying subscription entitlement | In accordance with Google's privacy policy |
| Google LLC, jsDelivr | United States and other countries where each provider's servers are located | IP address and browser/device communication information involved in the font request | Transmitted over the network when the website is accessed | Delivering web fonts for the website | In accordance with each provider's policy |
Microphone audio processed during alarm dismissal is handled entirely on the device and is never transferred overseas.
If you do not want your information transferred overseas for advertising purposes, you can limit it by resetting or deleting your device's advertising ID. The ad privacy settings screen inside the app appears only for users in regions whose local law requires an advertising consent flow, such as the European Economic Area and the United Kingdom. Owlarm is currently distributed only in the Republic of Korea, so that item does not appear for users here, and the opt-out available to them is the advertising ID reset or deletion described above. Transfers required for in-app payments are essential to providing paid features, so refusing them will limit access to paid functionality.
6. User Rights and How to Exercise Them
- Users may request access, correction, deletion, suspension of processing, or withdrawal of consent regarding their own inquiry information held by the Company.
- Owlarm's alarms can be deleted within the app. There is currently no feature to delete individual wake-history entries; all data stored on the device can be deleted by clearing the app's data or uninstalling the app through Android settings.
- The advertising ID can be reset or deleted in Android settings, and advertising-related choices can be changed in the Google account and device settings.
- For detailed instructions on deleting on-device data and information about data the Company does not retain, see the Data Deletion Request page.
- Requests to exercise these rights can be made to contact@strikelabkr.com, and the Company will process them in accordance with applicable law after verifying identity.
6-1. Automatically Collected Information and How to Opt Out
- App: The app uses the device's advertising identifier (advertising ID) to serve ads. Users can opt out by resetting or deleting the advertising ID in device settings. The ad privacy settings item inside the app's settings appears only in regions whose local law requires an advertising consent flow, such as the European Economic Area and the United Kingdom, and does not appear for users in the Republic of Korea.
- Website: The website stores the user's light or dark display preference in browser local storage. It does not use cookies. Users can delete this value at any time through the browser's stored-data controls, and deleting it does not interfere with use of the website.
7. Personal Information of Children Under 14
Owlarm is not directed to children under 14. Its target age group on Google Play is set to ages 16 and over, it does not participate in programs directed to children or families, and its advertising is not configured for children. The Company does not intentionally collect personal information from children under 14. Because there is no user registration and Owlarm does not ask a user's age, the Company has no means to identify whether a user is a child. If the Company learns that information from a child under 14 has been collected, it will destroy that information without delay. A legal representative may contact the point of contact above to request verification and deletion.
8. Destruction Procedure and Method
The Company separates personal information whose processing purpose has been achieved from other information and deletes it in a way that makes recovery difficult. Electronic files are deleted from the relevant account and storage, and any paper documents that arise are shredded or incinerated. Alarms stored on the device can be deleted within the app, and all local data can be deleted by clearing the app's data or uninstalling the app through Android. Detailed deletion instructions are available on the Data Deletion Request page.
9. Security Measures
- No user registration or company-operated user data server is maintained, minimizing the scope of external transmission.
- Alarm, wake-history, and settings data are stored within the Android app sandbox.
- Raw microphone input is processed in real time on the device, and no storage file is created.
- Permissions are used only at the time and for the purpose necessary for alarm and dismissal features.
- Data transmitted by the Google Mobile Ads SDK is encrypted in transit, per Google's guidance.
- The Company has not added any crash-reporting or user-behavior analytics SDK of its own. However, the Google Mobile Ads SDK processes app/SDK diagnostic information and product interactions in the course of serving ads, and this processing includes ad performance measurement and analysis.
10. Privacy Officer and Contact
- Privacy officer: Privacy Protection Contact
- Affiliation: StrikeLab
- Contact: Email contact@strikelabkr.com, telephone +82-10-2194-5606
- Address: 201-505, 2-15 Seongseong 8-ro, Seobuk-gu, Cheonan-si, Chungcheongnam-do, 31078, Republic of Korea
11. Remedies for Infringement of Data Subject Rights
Data subjects may apply to the institutions below for dispute resolution or counseling to seek remedies for infringement of personal information rights. These institutions are independent of the Company and may be contacted if the Company's own response is unsatisfactory or if more detailed assistance is needed.
| Institution | Telephone | Website |
|---|---|---|
| Personal Information Dispute Mediation Committee (개인정보분쟁조정위원회) | +82-1833-6972 (domestic: 1833-6972) | www.kopico.go.kr |
| Personal Information Infringement Report Center (개인정보침해신고센터) | +82-118 (domestic: 118) | privacy.kisa.or.kr |
| Cyber Investigation Division, Supreme Prosecutors' Office (대검찰청 사이버수사과) | +82-1301 (domestic: 1301) | www.spo.go.kr |
| Cyber Bureau, Korean National Police Agency (경찰청 사이버수사국) | +82-182 (domestic: 182) | ecrm.police.go.kr |
12. Notice of Policy Changes
If this Policy is added to, deleted from, or changed, we will announce it through the website before the change takes effect. Changes that materially affect users' rights will be announced by the method and within the period set by applicable law.
Announcement date: 2026-08-29 · Effective date: 2026-09-05
Change history
- Effective 2026-09-05 (this revision): Added the clap detection log files the app leaves on the device to the list of collected items and to the retention periods. Corrected which regions actually see the in-app ad privacy settings, and stated clearly that the opt-out available to users in the Republic of Korea is resetting or deleting the device's advertising ID.
- Revised 2026-08-28: Filled in the disclosure of why advertising usage information is processed, and added the transaction-record retention periods required by law and the nature of overseas transfers. Reflected raising the target age to 16 and over. That revision was not announced separately and is included in this announcement.
- Effective 2026-08-11: Added remedies for infringement, data deletion guidance, and disclosure of automatically collected information, and updated the designation of the Privacy Officer.
- Effective 2026-07-29: First version in force.