Privacy Policy
For KeyLock Suite V4.0 - Lockscreen Style (Package Name: com.keylock.suite)
Table of Contents
Overview & Commitment to Privacy
Welcome to KeyLock Suite V4.0 - Lockscreen Style ("KeyLock Suite", "we", "our", or "us"). We recognize that your smartphone's lock screen and wallpapers contain sensitive personal interactions. Our core philosophy is built upon privacy-by-design and local data isolation.
This Privacy Policy informs you about how KeyLock Suite collects, uses, protects, and discloses information when you use our Android mobile application distributed via the Google Play Store.
The Zero-Trust Privacy Principle: What Stays on Your Device
Unlike many third-party customization apps that upload your personal data to remote advertising databases, KeyLock Suite processes all lock interactions locally on your device:
- Personal Wallpapers & Photos: Photos or anime images you slice for the Dynamic Puzzle Lock or import for custom felt billiard tables are processed and cropped strictly on your device. We NEVER upload, view, or transmit your private gallery photos to our servers.
- PINs, Patterns & Biometrics: Your fallback unlock PIN and Pattern credentials are never sent to any network endpoint. They are encrypted using AES-256 GCM on your phone. Biometric fingerprint and face authentication are mediated entirely by Android’s native
BiometricPrompthardware security enclave. - Touch Vectors & Lock Solves: Your swipe gestures, billiard drag angles, and puzzle snap actions are calculated entirely in-memory and discarded upon unlocking.
Information We Collect & How It Is Used
We collect only the minimum information necessary to ensure software stability, restore in-app purchases, and deliver custom lock functionality:
A. Authentication & Account ID (Optional)
When signing in with Google via the Android Credential Manager, we generate an obfuscated, pseudonymous Supabase User UUID. We do NOT store your Google password. This identifier is solely used to link and restore your Google Play purchase entitlements.
B. Lock Screen Notifications (Local Processing Only)
If you enable notification badges or card views on the lock screen overlay, our NotificationListenerService reads system notifications to present them visually. In Privacy Mode (HIDE_CONTENT), notification contents are masked. Notification data is never stored in persistent databases or sent over the Internet.
C. Technical & Diagnostic Logs
To prevent crashes on various OEM device models (such as Xiaomi/HyperOS, Samsung OneUI, and Oppo), anonymous crash traces may be logged via Firebase Crashlytics. These traces contain hardware metadata (e.g. GPU chipset type, Android OS version) without identifying individual users.
Android System Permissions & Technical Justifications
KeyLock Suite requests specific Android runtime permissions to function as a reliable, production-grade lock screen replacement:
| Permission | Technical Reason | Data Policy |
|---|---|---|
| ROLE_HOME | Registers KeyLock Suite as an alternative launcher to stop unauthorized bypass of lock screen via Home gesture. | System-level role, no data collected. |
| SYSTEM_ALERT_WINDOW | Allows drawing the secure lock overlay window immediately when screen turns on. | Visual display only, no keylogger activity. |
| READ_PHONE_STATE | Monitors incoming cellular calls so KeyLock Suite can immediately yield and defer overlay without trapping emergency calls. | Call state only (RINGING/IDLE). Does NOT record audio or contacts. |
| POST_NOTIFICATIONS | Required by Android 13+ to maintain the Foreground Service (FGS) status bar notification. | Local status indicator only. |
| NOTIFICATION_LISTENER | Optional: renders incoming notifications on the lock screen card stack. | Temporary in-memory cache, never uploaded. |
| SCHEDULE_EXACT_ALARM | Coordinates exact intervals for the 4-split canvas live wallpaper rotation engine. | Internal timing loop only. |
Dual-Storage (DE/CE) Architecture & Encryption
KeyLock Suite enforces strict cryptographic boundaries using Android’s native dual-storage architecture:
- Device Protected Storage (DE): Holds only non-sensitive boot status flags and local cache metadata. This allows the lock service to awaken during Direct Boot (
LOCKED_BOOT_COMPLETED) so your device stays shielded before first unlock. - Credential Encrypted Storage (CE): Houses sensitive user settings, PIN/Pattern hashes, and authorization tokens, sealed behind hardware-backed AES-256 GCM encryption via Android KeyStore MasterKey.
Third-Party Services & Advertising
KeyLock Suite utilizes reputable third-party services that adhere to rigorous privacy standards:
- Google Play Services & Billing: Manages purchases, licensing, and updates. Governed by Google's Privacy Policy.
- Supabase Cloud: Provides server-side purchase entitlement verification (
verify-purchaseedge function) with zero-trust token signing. - Google AdMob: For users of the free edition, non-personalized banner or rewarded video ads may appear during wallpaper browsing. All ads are 100% suppressed for Premium Lifetime users.
In-App Purchases & Financial Data Protection
All financial transactions for KeyLock Suite Premium are processed exclusively by Google Play Billing. We never see, collect, or store your credit card numbers, billing addresses, or payment instruments.
User Rights (GDPR & CCPA Compliance)
Regardless of your country of residence, you retain total authority over your data:
- Data Deletion: You can wipe all local lock settings, cached images, and custom puzzle slices at any moment by clearing the application's storage in Android Settings or uninstalling the app.
- Account Unlinking: If you linked your account via Google Sign-In, you can request total deletion of your obfuscated UUID from our backend entitlement table by contacting [email protected].
Children's Online Privacy Protection (COPPA)
KeyLock Suite is not directed to individuals under the age of 13. We do not knowingly solicit or collect personally identifiable information from children under 13 years of age.
Contact Us & Community Support
If you have questions, feedback, or inquiries regarding this Privacy Policy or your data, please reach out to our engineering support team: