AnLock Privacy Policy
Hwang Juhye, the operator of AnLock (“Operator,” “we,” or “us”), processes personal data as described below when providing the AnLock app and website (together, the “Service”). This Policy is based on the data flows identified in the current implementation. Additional rights or requirements under mandatory law in your location remain unaffected.
- Accessibility Service is used to identify the package name of the foreground app during a lock. It is not used to collect screen text, passwords, keystrokes, or web-browsing content.
- The package name and display name of an Allowed App, plus derived statistics such as launch count and use time during a session, may be synchronized to provide lock records.
- Google Play processes payments. We do not collect raw card or bank-account numbers.
- The current web client does not initialize or use Firebase Analytics or Firebase Storage.
1. Controller
- Service: AnLock
- Operator and privacy contact: Hwang Juhye
- Address: 208 Misagangbyeon Jungang-ro, Hanam-si, Gyeonggi-do, Republic of Korea
- Email: support@anlock.app
- Website: https://www.anlock.app
2. Personal data, purposes, and collection methods
- Required data: UID, email and authentication information, country and language, registration and consent records, and settings, device data, and lock records needed for the account and Service
- Purposes: identify and sign in a Member, synchronize locks and records, secure the account, verify purchases, and provide support
- Retention: until account deletion or completion of the purpose, unless a longer period is required by law
- You may decline, but we cannot create an account or provide sign-in-based core functions without this required processing.
Marketing email, marketing app push, and night-time marketing app push are optional and separate. Declining them does not affect the core Service. Android permissions, including Accessibility Service, are disclosed and requested separately immediately before the related feature is used.
| Category | Data | Purpose | Collection |
|---|---|---|---|
| Account and authentication | Firebase UID, email, email-verification status, sign-in provider, account creation and recent sign-in information, and IP address and browser/user-agent data processed during authentication | Registration, sign-in, email verification, account recovery, abuse prevention, and identity verification for deletion | Email registration/sign-in or Google Sign-In; generated by Firebase Authentication |
| Profile and settings | Country code, language, theme, Membership tier, registration and recent-activity time, time zone, consent status, document version, consent/withdrawal time, and notification settings | Personalization, country/language documents, entitlements, consent records, and aggregate statistics | User input or selection and automatic generation during use |
| Device and notifications | Android-ID-based device identifier, registered-device list and recent sign-in time, OS and app version, manufacturer and model when included in a support request, FCM token, and push-delivery history | Device management, compatibility and issue resolution, service and marketing notifications, and duplicate prevention | Generated by the app or operating system, or submitted with a support request |
| Lock and usage records | Lock type; start, scheduled-end, and actual-end time; duration; completion, voluntary termination, or technical-failure status; active-lock state; CFF conditions; interruption attempts; idle time; templates and schedules; selected Allowed App package/display names, launches, and use time; optional Give Up reason; and daily/monthly statistics and focus patterns | Provide locks, cross-device synchronization, records, statistics and insights, support, and lock recovery | Generated from user settings and Lock Sessions |
| Payment and purchases | Google Play product ID, purchase token and token hash, order ID, catalog amount, currency and displayed price, purchase purpose (Membership, CFF, or Development Support), payment/verification/refund status and time, and cumulative purchase, support, and CFF amounts. On account deletion, only the minimum transaction evidence is separately retained, excluding UID, email, purchase token, token hash, and cumulative amounts. | Purchase verification, Membership entitlement, CFF confirmation, restoration, refunds and disputes, and revenue statistics | Google Play Billing and Google Play Developer API |
| Support | UID, email, category, title, content, response, status and time; manufacturer, model, and OS version for in-app inquiries; PIN-recovery request and verification; and support-unlock reason and record. On account deletion, only the minimum inquiry/response evidence needed for dispute handling is separately retained, excluding structured UID, email, and operator identifiers. | Answer inquiries, resolve failures, verify identity, recover locks, and handle disputes | App or web inquiries and support actions |
| Development Support messages | Email, support product and amount, purchase token, optional message, optional attachment name/content (up to 20 MB), and email-delivery status | Verify the purchase, deliver the message or attachment to the Operator, and prevent duplicates | User submission and Google Play purchase data |
| Account and data deletion | During processing only: UID, email, request, identity-verification and processing status/time, and error information. After completion: a minimum audit record of request route, verification method, processing times, counts, and result, excluding UID, email, authentication token, and raw error content | Verify the requester, perform staged deletion and retry failures, and retain minimum completion evidence | App or web deletion request and Firebase email-link verification |
| Advertising and automatically generated data | Advertising ID, IP address, device and app information, approximate location, ad impressions/clicks/interactions, access logs, and error/security logs | Ads for Free or guest users, frequency capping, ad performance and fraud measurement, security, and issue resolution | Google Mobile Ads SDK (AdMob), Firebase, servers, and networks |
Passwords are handled through Firebase Authentication and are not available to the Operator in plain text. Google Play directly handles payment-method data such as card and bank-account numbers.
3. Sensitive system permissions and on-device processing
3.1 Accessibility Service
- Purpose: determine whether the foreground app is allowed during a Lock Session and restore the lock screen when a disallowed app opens.
- Accessed information: window-state change events and the associated app package name. Although the service configuration declares the capability to retrieve window content, the current implementation makes lock decisions from the event package name.
- Not collected for this purpose: screen text or images, keystrokes, passwords, message contents, and web-browsing content.
- Server synchronization: raw accessibility events are not stored as such. Derived lock records may include selected Allowed App information, session launch count and use time, and attempts to leave for disallowed apps.
3.2 Other permissions
- Usage Access: assist foreground-app detection and calculate Allowed App usage statistics
- Display over other apps: show the lock screen
- Exact alarms, boot completed, and foreground service: execute and recover timer and scheduled locks
- Notifications: deliver schedule, lock, payment, notice, and consented marketing push messages
- Device administrator: optional lock-assistance function activated by the user
- Advertising ID: AdMob delivery, measurement, and fraud prevention
You may revoke permissions in Android system settings. The related feature may then be limited, but revoking a permission does not itself trigger a CFF charge.
4. Legal bases
The legal basis depends on your location and the specific processing. Where applicable, we rely on:
- Performance of a contract and steps you request: accounts, locks, registered devices, support, and purchase verification
- Compliance with legal obligations: legally required transaction records and dispute handling
- Legitimate interests: security, abuse prevention, Service stability, and minimum operational statistics, unless overridden by your rights and interests
- Consent: promotional email, marketing app push, and night-time marketing app push
- Providing a requested function: essential cookies, local storage, and authentication tokens used for sign-in, security, and deletion requests
5. Retention
| Data | Retention period |
|---|---|
| Account, settings, device, and lock records/statistics | Until account deletion or completion of the purpose. Once deletion is confirmed, we remove the Firebase Authentication account, user document, device and notification information, all user subcollections, and lock records and progress. We remove UID, email, purchase token, token hash, and cumulative amounts from the Service’s original purchase ledger; only the minimum transaction evidence is separately retained as described below. |
| Customer inquiries, responses, and dispute-handling records | They are retained while the account is active to provide support. On account deletion, we remove original inquiries and structured account/operator identifiers. We separately retain only the minimum handling evidence—such as category, title, inquiry and response content, processing times, and related order ID—for three years from closure. Because user-written inquiry and response content may itself contain Personal Data, a retained record containing that content is used only for dispute handling or legal retention and is access restricted. |
| Marketing consent, withdrawal, and delivery history | Until withdrawal or account deletion. A minimum consent record may be retained where required by law or necessary to handle a dispute. |
| Account-deletion job and audit record | The resumable job may contain UID, email, and processing-error information only while processing and is deleted after completion. A minimum audit record containing request route, verification method, processing times, deletion/retention counts, and result—but no UID, email, authentication token, or raw error content—is separately retained for three years. |
| E-commerce records | On account deletion, minimum transaction evidence—such as product ID, order ID, stored amount/currency, status, payment/refund time, and refund reason—is retained separately from the original record for five years from transaction completion or the relevant retention event. Consumer complaint and dispute records are retained for three years as described above. Display, advertising, and other mandatory records may be retained for the period required by applicable law. |
| Access and security logs | For the minimum period needed for security and troubleshooting, or the period set by the relevant infrastructure provider. |
Separated transaction, dispute, and deletion-audit records are not used to restore a deleted account, resume Service access, or market to you, and are not accessible directly by users. They are designated for automated deletion after the retention period, although technical processing may not occur at the exact moment the period ends. Google may independently retain Google Play transactions, Google Account information, and advertising data under its policies and legal obligations. Data retained to meet a legal obligation is not used for an unrelated purpose.
6. Processors and external services
| Provider and service | Function | Relevant data |
|---|---|---|
| Google LLC — Firebase Authentication, Cloud Firestore, Cloud Functions, Cloud Messaging, and Remote Config | Authentication, storage and synchronization, server functions, push delivery, and app configuration | Account, device, lock, consent, inquiry and deletion-request data, FCM token, IP address, and technical logs |
| Google LLC — Google Sign-In, Google Play Billing and Developer API | Google sign-in, in-app payment, verification, and refund notification | Google account identifiers and product, order, purchase-token and payment-status data; Google handles raw payment-method data |
| Google LLC — Google Mobile Ads (AdMob) | Ad delivery, measurement, frequency capping, and fraud prevention | Advertising ID, IP address, device/app and approximate-location data, and ad interactions |
| Zoho Corporation group services | Send and receive support, PIN-recovery, and Development Support emails | Email, inquiry content, device information, support message, and optional attachment |
7. International processing and transfers
The Service is operated from the Republic of Korea and may process personal data in other countries as described below. Data is transmitted over encrypted network connections when the relevant function is used.
| Recipient and contact | Country, timing, and method | Data and purpose | Retention |
|---|---|---|---|
| Google LLC Firebase Privacy | United States. Firebase Authentication is processed in the United States. Cloud Functions currently runs in Iowa (us-central1). Global services such as FCM and Remote Config may process data in Google facilities, including the United States. Network transfer during Service use. | Account/authentication, server requests, push, device, purchase-verification data, and IP address described in Section 2; authentication, server functions, messaging, and security | Until account deletion, end of processing services, or completion of the purpose, subject to Google service-log and mandatory retention requirements |
| Google LLC — Google Play and AdMob Google Privacy Policy | United States and countries where Google operates infrastructure; network transfer when purchase or advertising functions are used | Purchase, order and refund data; Advertising ID, IP address, device data, and ad interactions; payment, verification, ad delivery, measurement, and security | Under Google’s policies and applicable law |
| Zoho Corporation group Zoho Privacy Policy | Countries where Zoho operates infrastructure, including the United States and India; network transfer when email is sent or received | Email, inquiry, recovery and Development Support messages, and optional attachments; support email processing | Until the email purpose is complete or the relevant account/contract ends, subject to legal and backup-retention requirements |
Cloud Firestore, which stores core user data, currently uses the Seoul region (asia-northeast3). Authentication, server functions, push, advertising, and payment nevertheless involve the international processing above. If you do not want these transfers, contact support or delete your account; core authentication, server, and payment functions may then be unavailable. Where applicable law requires a transfer mechanism or additional consent, we will use that mechanism or obtain that consent.
8. Disclosure to third parties
We process personal data only for the purposes in this Policy and do not sell or disclose it to an independent third party without consent or another lawful basis. We may disclose only what is necessary in response to a legally valid government request, to address an imminent threat to life or physical safety, or in another situation permitted by law.
9. Deletion
- Personal data is deleted without undue delay when its retention period expires or its purpose is complete.
- Electronic records are deleted using methods intended to prevent practical recovery. Legally retained data is separated or access-restricted.
- The account-deletion process first disables the authentication account, separates only the minimum transaction and dispute evidence from original records, and then removes the user document, all user subcollections, original inquiries, authentication and deletion-verification data, the original Service purchase ledger, and account-linked auxiliary records in stages. The temporary job may contain UID and email only while needed to retry a failure and is deleted after completion. Only a minimum audit record without UID, email, authentication token, or raw error content is retained for three years.
- Statistics converted into non-identifying aggregate values may continue to be used as Service metrics.
10. Your rights
Depending on your location, you may have rights to access, correct, delete, restrict or object to processing, withdraw consent, receive portable data, or complain to a data-protection authority.
- Review or change country, consent, and notification settings in the app or website account/settings area.
- When signed in, request account withdrawal and personal-data deletion directly through the app or website after recent-sign-in verification. If you cannot sign in, use the website deletion-request process; we process it after identity verification, such as email-link verification.
- For another request, email support@anlock.app. We may verify your identity or the authority of a representative.
- Withdrawing marketing consent does not prevent necessary service, security, payment, or legal-change communications.
You may also complain to the data-protection or consumer authority in your place of residence. Korean users may contact the Personal Information Infringement Report Center (118), the Personal Information Dispute Mediation Committee (+82-1833-6972), or the Korean National Police Agency (182).
11. Children’s Privacy
Our Service does not address anyone under the age of 14 (“Children”) and does not currently provide a parental-consent flow. We do not knowingly collect Personal Data from anyone under the age of 14. If you are a parent or legal guardian and become aware that your child has provided us with Personal Data, please contact us at support@anlock.app. If we become aware that we have collected Personal Data from a child without legally valid parental authorization, we will immediately take steps to disable the account and remove that information from our systems. Where the law in your location sets a higher minimum age or requires additional parental authorization, that rule applies.
12. Security measures
- Account-level access controls using Firebase Authentication and security rules
- Administrator authorization checks, server-side purchase verification, staged deletion/support operations, and blocked client access to separated retention records
- HTTPS encryption in transit, no plain-text password storage by the Operator, and hash-based purchase-token ledger identification
- Access limited to the minimum people and functions needed, with monitoring for errors and abuse
13. Cookies and local storage
The website may use cookies, browser local storage, and authentication tokens to maintain Firebase sign-in, remember language, and process an account-deletion email link. The deletion email and language information used for the link flow are designed to be removed when confirmation is complete. You may clear browser storage, but sign-in and deletion confirmation may then be limited.
14. Contact
Send privacy questions or rights requests to Hwang Juhye, AnLock’s privacy contact, at support@anlock.app.
15. Changes to this Policy
We will announce additions, removals, or changes through the app or website before they take effect. Material changes affecting your rights will be clearly announced with reasonable notice, and separate consent will be requested where required.