Privacy Policy
Effective date: 2026-07-29
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, mission performance, wake history, settings, and subscription status
- Providing advertising to free users 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, mission type and target count, alarm label, alarm sound URI, volume and vibration settings; wake time, completed count, normal or emergency dismissal, difficulty; seal time and count; current and highest difficulty; 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 runs a clap mission or ear-calibration test. No recording file is created, and the raw audio is not stored or transmitted |
| Accelerometer | Device acceleration values used to detect jumps | Analyzed in real time on the device while a jump mission is running. Raw sensor values are not stored or transmitted |
| 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 mission 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 that period.
- 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 and accelerometer input: Discarded immediately after real-time detection and not retained separately.
- 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.
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.
| 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 and raw sensor values processed during a mission are handled entirely on the device and are never transferred overseas.
If you do not want your information transferred overseas for advertising purposes, you can limit it through the ad privacy settings in the app or by resetting or deleting your device's advertising ID. 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.
- 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.
7. Personal Information of Children Under 14
The website and Owlarm do not accept registration from children under 14 and do not collect age or date of birth. Owlarm does not verify a user's age or distinguish ad requests by age. If the Company becomes aware that a child under 14 has sent personal information through an email inquiry, the child's legal representative may request access or deletion, and the Company will take the necessary action without delay after verification.
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.
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 and accelerometer input are 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 mission features.
- Data transmitted by the Google Mobile Ads SDK is encrypted in transit, per Google's guidance.
- No separate crash-reporting or user-behavior analytics SDK is used. However, the Google Mobile Ads SDK processes app/SDK diagnostic information and product interactions in the course of serving ads.
10. Privacy Officer and Contact
- Privacy officer: CEO, StrikeLab
- Email: contact@strikelabkr.com
- Address: 충청남도 천안시 서북구 성성8로 2-15, 201-505호
11. 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.
Date of announcement and effective date: 2026-07-29