RanjitAtWork
  • Home
  • QR Code Generator
  • My Projects
    • QR Code Generator

    • Mouse Driver
    • VideoMaps
    • Code Scanner
    • Bluetooth Keyboard
    • NetStats
    • PingMe
    • BatteryNtfy
    • NfcTags
    • DualCam Director
    • Quick SMS Wear
    • Aarti Sangraha
  1. Home
  2. Quick SMS Wear
  3. Privacy Policy
Privacy Policy Terms & Conditions
Official Google Play Policy Wear OS & Companion App

Privacy Policy for Quick SMS Wear

Application: Quick SMS Wear (work.ranjit.quicksmswear) • Developer: Ranjit Bhonsale • Effective Date: October 22, 2026

Privacy Commitment: Quick SMS Wear is engineered with a strict local-first and privacy-by-design architecture. We do not collect, harvest, monitor, sell, or sync your private contacts, telephone numbers, or SMS messages to any external cloud database.
In this Privacy Policy
§ 1. Introduction & Service Overview
§ 2. Sensitive Permissions & SMS Handling
§ 3. Information Collection & Local Storage
§ 4. Wearable Data Layer & Companion Relay
§ 5. Diagnostic Logging (Optional)
§ 6. Third-Party Services
§ 7. Data Retention & User Deletion Rights
§ 8. Children’s Privacy
§ 9. Security Safeguards
§ 10. Policy Updates & Contact Information

1 Introduction & Service Overview

This Privacy Policy governs the use of the Quick SMS Wear application (Package identifier: work.ranjit.quicksmswear), including its Wear OS smartwatch client and paired Android companion application, developed and published by Ranjit Bhonsale (“Developer”, “we”, “us”, or “our”), hosted on ranjit.work.

Quick SMS Wear is a speed-dial and quick-dispatch SMS utility created to allow smartwatch users to send predefined and custom SMS text messages rapidly from their wrist. This service is provided at no cost as an ad-free utility and is intended for use “AS IS”.

2 Sensitive Permissions & SMS Transmission Policy

In strict compliance with Google Play’s Permissions and APIs that Access Sensitive Information (including SMS and Call Log policies), Quick SMS Wear requests only the minimum permissions necessary to deliver core wearable messaging functionality:

android.permission.SEND_SMS Send SMS Messages

Purpose & Trigger: This permission is requested exclusively to send SMS text messages initiated directly and intentionally by the user. Quick SMS Wear never sends unsolicited, silent, or background automated SMS messages without affirmative user action.

User Confirmation Safeguard: The application incorporates an explicit confirmation interface featuring a 3-second countdown timer and manual “Send Now” / “Cancel” actions to ensure no message is ever sent accidentally.

Transmission Paths:

  • LTE Standalone Smartwatches: When operating with an active cellular eSIM on your Wear OS watch, messages are sent directly via Android’s standard SmsManager.sendTextMessage() API through your watch carrier network.
  • Bluetooth-Paired Smartwatches: When operating on a Bluetooth-only watch, the message payload is relayed locally to your paired Android smartphone via Google Play Services Wearable Data Layer, and the phone companion service dispatches the SMS via the phone’s carrier SIM.
android.permission.READ_CONTACTS Read Device Contacts

Purpose: Used strictly on your local device to display your phonebook so you can select favorite contacts (e.g., Mom, Spouse, Work) and pin them as 1-tap quick action chips on your watch screen. Contact data is queried in real time, filtered in memory, and stored exclusively in your device’s private sandboxed storage. Contacts are never sent over the Internet, uploaded to external servers, or transferred to third parties.

android.permission.READ_PHONE_STATE Read Phone / Telephony State

Purpose: Used solely to check cellular radio readiness, carrier SIM connectivity, and multi-SIM state to determine whether the watch can transmit directly or needs to route through the paired phone companion. We do not access phone call logs or monitor incoming/outgoing calls.

android.permission.VIBRATE Haptic Feedback

Purpose: Provides physical tactile buzzes on your wrist during confirmation countdowns, successful SMS transmission, or network failure alerts.

android.permission.INTERNET Network Access

Purpose: Used for secure local Google Play Services Wearable Data Layer communications between the watch and phone, optional web QR configuration sync, and user-initiated diagnostic log upload (if technical support is explicitly requested by the user).

3 Information Collection & Local Storage Architecture

Quick SMS Wear is designed around the principle of data minimization:

  • No User Account or Registration: You do not need an account, password, email address, or profile to use Quick SMS Wear.
  • Local-First Storage: Any favorite contacts, speed-dial slots, recipient phone numbers, and custom SMS templates you create are saved exclusively in your device’s private sandboxed SharedPreferences storage (quick_sms_wear_prefs).
  • No Remote Central Database: We do not operate any backend server that receives, archives, or indexes your personal messages, contact lists, or communication history.
  • No Advertising or Tracking SDKs: Quick SMS Wear contains zero ad networks, zero tracking pixels, and zero behavioral telemetry SDKs.

4 Wearable Data Layer & Companion Relay

When sending an SMS from a Bluetooth-connected Wear OS watch without active eSIM cellular service, Quick SMS Wear communicates with its paired Android companion app using the Google Play Services Wearable Data Layer API (Wearable.getMessageClient):

  • The payload (containing the recipient phone number, message text, and timestamp) is transmitted over an encrypted local Bluetooth/Wi-Fi connection managed by Google Play Services between your authenticated devices.
  • The companion app dispatches the message via your phone’s cellular provider SIM and reports the transmission status (Sent / Delivered / Failure) back to the watch.
  • This communication occurs strictly peer-to-peer between your own paired hardware devices; no intermediary servers or third-party relays are involved.

5 Diagnostic Logging (Optional & User-Initiated Only)

Quick SMS Wear includes an optional in-app debug log viewer for technical diagnostics (e.g., verifying Bluetooth DataLayer connectivity or carrier transmission codes).

If and only if you explicitly tap the “Upload / Share Logs” button to report an issue, an event log containing technical runtime diagnostics (e.g., app version, Android OS version, connectivity timestamps, and error codes) is transmitted securely via HTTPS to an ephemeral paste service (dpaste.org) configured with an automatic 24-hour expiration. Personal SMS message bodies and your address book are never included in public diagnostic logs.

6 Third-Party Services

The application relies on core system libraries provided by Google LLC for Wear OS and Android integration:

  • Google Play Services & Wear OS APIs: Facilitates application installation, runtime license verification, and secure local watch-to-phone Wearable Data Layer communication. Review the Google Privacy Policy.

We do not sell, rent, monetize, or disclose your personal data to any third-party advertisers, data brokers, or marketing partners.

7 Data Retention & User Deletion Rights

Because all user configurations and favorite contacts are stored strictly on your local device:

  • Retention Period: Data remains stored in the app’s local private directory for as long as you have the app installed.
  • In-App Deletion: You can delete any saved contact or reset any SMS template at any time directly through the app’s “Manage Contacts” and “Templates” screens.
  • Complete Data Erasure: You can instantly and permanently purge 100% of the app’s stored data at any time by going to your Android device’s Settings → Apps → Quick SMS Wear → Storage → Clear Storage / Clear Data, or by uninstalling the application.
  • Developer Assistance: For any questions, data access inquiries, or deletion verification, you can contact the developer directly at ranjit.bhonsale@gmail.com.

8 Children’s Privacy (COPPA & GDPR Compliance)

Quick SMS Wear is a general-purpose utility and is not directed towards children under the age of 13 (or under 16 in the European Economic Area). We do not knowingly solicit or collect personally identifiable information from children. If you become aware that a child has provided us with personal data, please notify us immediately at ranjit.bhonsale@gmail.com, and we will take immediate corrective action.

9 Security Safeguards

We take data security seriously. Quick SMS Wear utilizes Android’s sandboxed operating system environment, preventing other applications from accessing Quick SMS Wear’s private data files. Inter-device watch-to-phone data synchronization utilizes Google Play Services’ encrypted IPC channels. However, please note that no method of electronic storage or wireless transmission is completely infallible, and you are advised to keep your smartwatch and smartphone operating systems up to date.

10 Policy Updates & Contact Information

We may revise this Privacy Policy periodically to reflect app updates, new Wear OS features, or evolving regulatory requirements. Any updates will be posted directly to this public URL (https://ranjit.work/quicksmswear/privacy) with an updated Effective Date. Continued use of Quick SMS Wear following any changes constitutes acceptance of the updated policy.

Developer & Data Protection Contact
Developer: Ranjit Bhonsale
Website: https://ranjit.work
Email: ranjit.bhonsale@gmail.com
Package: work.ranjit.quicksmswear
RanjitAtWork | Project Showcase Hub
Home QR Code Generator Contact © 2026