Privacy Policy for QuickBeam
Effective Date: October 15, 2026
Last Updated: October 15, 2026
Developer: Mohammad Zaki
Contact: mohdzaki407@gmail.com
1. Overview & Privacy-by-Design Philosophy
QuickBeam ("we", "our", or "the App") is developed as an offline-first, privacy-by-design application for peer-to-peer Near Field Communication (NFC) sharing, instant QR code generation and scanning, and local digital card management.
Our core principle is simple: Your data belongs exclusively to you.
QuickBeam operates with zero remote cloud backends, zero personal tracking SDKs, zero advertising networks, and zero behavioral telemetry. All your beamed payloads (contacts, Wi-Fi credentials, dynamic links, notes, and payment identifiers) are stored strictly on your local device and encrypted at rest.
2. Information We Do NOT Collect
We do not collect, transmit, sell, or rent any of the following:
- Personal Identification: Names, phone numbers, email addresses, or physical addresses (except what you choose to store locally in your personal profile on your device).
- Location Data: GPS, Wi-Fi geolocation, or cell tower location.
- Biometric or Health Data: None.
- Advertising Identifiers: Google Advertising ID (AAID) is not tracked or shared.
- Browsing or Usage Habits: We have no analytics SDKs (e.g., Firebase Analytics, Mixpanel, or Flurry) embedded in the App.
3. Information Handled Strictly on Your Device
All payload information created or received in QuickBeam remains under your complete control:
3.1 Encrypted Local Storage (SQLCipher & Room DB)
- What is stored: Saved beam records (SSIDs, Wi-Fi passwords, contact cards, web links, custom text, UPI/payment handles) and app preferences.
- How it is protected: Your data is stored in a local SQLite database encrypted with SQLCipher (AES-256 encryption). The encryption key is securely managed on-device.
3.2 NFC Host Card Emulation (HCE)
- How it works: When you choose to beam a payload, QuickBeam utilizes Android's Host Card Emulation (
HostApduService, Type 4 Tag protocol).
- Proximity: Data transmission occurs only over immediate physical proximity (typically ~4 cm or less) when your device is active and held against another NFC reader or smartphone.
- Broadcast Control: Emulation can be toggled on/off instantly via the QuickBeam NFC quick-settings sheet.
3.3 Camera & QR Code Scanning
- How it works: When you use the QR scanner, camera access is requested strictly to decode QR codes in real time using Google Play Services Code Scanner or ZXing.
- Zero Retention: Video frames are analyzed locally in memory and immediately discarded. No photos, videos, or camera recordings are ever saved, cached, or transmitted to any remote server.
4. Third-Party Services & Financial Transactions
QuickBeam integrates minimal, industry-standard services exclusively to fulfill in-app billing and subscription entitlements in compliance with Google Play Developer policies:
4.1 Google Play Billing
- Purpose: All in-app purchases and subscription transactions (QuickBeam PRO: Lifetime, Annual, and Monthly tiers) are processed directly by Google Play.
- Data Handled: Google processes your payment details, billing address, and transaction tokens in accordance with the Google Play Terms of Service and Google Privacy Policy. QuickBeam never receives or stores your credit card or bank details.
4.2 RevenueCat SDK
- Purpose: We utilize RevenueCat (
com.revenuecat.purchases) to validate purchase receipts, manage subscription states, and unlock PRO entitlements across app launches.
- Data Collected:
- Anonymous Scoped User ID: A randomly generated, non-personal device identifier (e.g.,
qb_dev_...) generated on-device. This identifier is not linked to your identity, Google account, or hardware IMEI.
- Purchase History: Anonymous transaction IDs, product IDs (e.g.,
lifetime, yearly, monthly), and subscription active/expiration timestamps.
- Network & IP: Standard HTTP request data required to communicate with RevenueCat's API over TLS/HTTPS.
- Privacy Reference: For more information on RevenueCat’s security and data handling practices, please review the RevenueCat Privacy Policy.
5. Android System Permissions
QuickBeam requests only the minimum Android permissions necessary to perform its core functions:
- android.permission.NFC - Required to transmit beam payloads via Host Card Emulation (HCE) to nearby devices.
- android.permission.CAMERA - Required for scanning QR codes in real time. Frames are never stored or uploaded.
- android.permission.INTERNET - Required exclusively to verify subscription status and purchase receipts with RevenueCat and Google Play.
- android.permission.VIBRATE - Provides subtle, tactile neo-brutalist haptic feedback upon successful beams, scans, and button presses.
6. Data Retention, Backups & Deletion
6.1 Record Deletion
You can delete any individual beam record, contact, or saved Wi-Fi network at any time directly from the Library tab. Deletion is instantaneous and permanent from the local encrypted database.
6.2 Full Data Purge ("Erase All Data")
QuickBeam includes a dedicated "Erase All Data" option in Settings. Tapping this permanently wipes all encrypted SQLite tables, clears cached preferences, and resets the app to its factory state.
6.3 Local JSON Backups
Exported backups are plain, open JSON files. QuickBeam uses the Android Storage Access Framework (SAF) system file picker, meaning backups are written only to the specific folder or drive you explicitly authorize. We do not maintain any cloud copies of your exported backups.
6.4 App Uninstallation
Uninstalling QuickBeam from your device permanently removes the app's internal sandbox, including all encrypted database files and cached credentials.
7. Security Standards
We employ industry-standard security measures to safeguard your information:
- AES-256 Encryption: Database storage is encrypted using SQLCipher.
- Encrypted Preferences: Device settings and scoped identifiers are stored using Android's
EncryptedSharedPreferences.
- Encrypted Transmission: All billing and receipt validation calls to RevenueCat and Google Play use strict TLS 1.3 / HTTPS encryption.
8. Children’s Privacy (COPPA / GDPR-K Compliance)
QuickBeam does not knowingly collect or solicit personal information from children under the age of 13 (or under 16 in the European Economic Area). Because the app does not collect personal identifiers or maintain user accounts, no children's data is retained. If you believe that a child has provided us with personal information, please contact us at mohdzaki407@gmail.com so that we can take appropriate action.
9. Changes to This Privacy Policy
We may update this Privacy Policy periodically to reflect app updates, new features, or changes in legal regulations. Any revisions will be posted with an updated "Last Updated" date at the top of this document. We encourage you to review this policy periodically.
10. Contact Us
If you have any questions, suggestions, or concerns regarding this Privacy Policy or QuickBeam's privacy practices, please contact: