Effective date: August 12, 2026
Modesmith Launcher (“Modesmith,” “we,” “our,” or “us”) is an Android launcher published by Sriraman Balachander under the Google Play developer name Modesmith Launcher.
This Privacy Policy explains what information Modesmith accesses, how it is used, where it is stored, and the choices available to you.
For privacy questions, contact:
Sriraman Balachander
Email: sriramanb1997@gmail.com
Modesmith is designed to operate locally on your Android device.
Modesmith does not include advertising SDKs, analytics SDKs, third-party crash-reporting SDKs, cloud sync, user accounts, or developer-operated servers for launcher data. Modesmith does not sell personal or sensitive user data.
Optional features may access information already available on your device, including installed apps, app shortcuts, contacts, calendars, foreground location, paired Bluetooth devices, notifications, active media sessions, widgets, wallpapers, alarms, and launcher settings.
Unless this policy says otherwise, that information is processed locally on your device and is not transmitted to Modesmith or to developer-operated servers.
Modesmith uses Google Play services for optional Pro purchases and Play-managed app updates. Optional actions may also open third-party apps or websites, such as your browser, Google Play, or Razorpay.
Modesmith accesses information about apps and activities that Android makes available to launchers. This allows Modesmith to provide:
The Home screen
App search
The A–Z app list
Mode-based favorites
Always apps
Hidden apps
Per-mode visibility rules
App launching
App icon styles and icon packs
Work profile app support
Android app shortcuts
Universal Search actions
Browser and media-app selection
This information may include:
App names
Package names
Activity names
App icons
Android profile identifiers
Shortcut identifiers
Shortcut labels and icons
App and shortcut selections made by you
Shortcut labels supplied by another app may contain names or other information created by that app. Modesmith uses this information locally for display, search, selection, and launching.
Modesmith stores the launcher configuration you create, including mode names, colors, app assignments, schedules, smart triggers, visibility rules, hidden apps, custom app names, shortcut selections, manual override state, wallpaper preferences, widget identifiers, notification badge preferences, onboarding state, language selection, appearance settings, gesture choices, and other launcher preferences.
Modesmith does not upload your installed-app inventory, app selections, shortcut information, or launcher configuration to developer-operated servers.
If you enable Contact Search and grant Android’s Contacts permission, Modesmith reads limited contact information so matching contacts can appear in launcher search.
This may include:
Contact display names
Android contact lookup identifiers or URIs
Optional contact thumbnail photo URIs
Modesmith does not upload your contacts, sell contact information, or store your complete contact list in its local database.
Contact information is processed locally to display search results and open the selected contact using your device’s contacts app. Modesmith does not read or store contact messages or communication history.
If you disable Contact Search or revoke Contacts permission, contact search stops working.
If you enable a calendar pill, calendar widget, or Calendar Event Smart Trigger and grant Android’s Calendar permission, Modesmith reads limited calendar information needed for those features.
This may include:
Event title
Start and end time
All-day status
Calendar name
Calendar identifier
Basic event visibility, availability, and status information
Your own event-attendance status where Android provides it
Modesmith uses this information locally to:
Display an upcoming calendar event
Display calendar information in a Modesmith widget or Smart Pill
Determine whether an event matches a Calendar Event Smart Trigger
Switch modes according to rules configured by you
Modesmith does not read attendee lists, event descriptions, meeting notes, event locations, or attachments for these features.
Event titles and event history are not written to Modesmith’s persistent database or included in exported backups. Active event information may be held temporarily in memory while the calendar feature is running.
A Calendar Smart Trigger may store:
A title filter entered by you
Whether all-day events should match
A calendar display label
A one-way fingerprint representing the selected calendar
Modesmith does not upload calendar information to developer-operated servers.
If you disable the calendar feature or revoke Calendar permission, calendar access stops.
If you create or enable a Location Smart Trigger and grant Android location permission, Modesmith may access your approximate and precise device location.
Location is used only to:
Capture your current coordinates when you explicitly request it
Determine whether the device is inside or outside an area configured by you
Switch modes according to a Location Smart Trigger configured by you
Modesmith accesses location only while Modesmith is open and visible. Modesmith does not request Android background-location permission and does not access location while the app is closed or not in use.
A current location sample may include coordinates, accuracy, provider time, and related Android location metadata. Current device-location samples are processed temporarily in memory.
Modesmith does not persistently store:
Sampled device positions
Location history
Visit history
Routes
Movement history
Location-trigger transition history
A Location Smart Trigger does persistently store the location rule created by you, including:
Target latitude and longitude
Radius
A place label entered by you
The mode and trigger settings associated with that location
Saved target coordinates remain in Modesmith’s local database until you edit or delete the rule, clear app data, or uninstall Modesmith.
If you explicitly export a Modesmith JSON backup, saved Location Smart Trigger coordinates, radii, and labels are included in that backup. Sampled device positions and location history are never included.
Modesmith does not perform geocoding, address lookup, map tracking, or network-based location sharing. Modesmith does not transmit location information to the developer, advertisers, analytics services, or developer-operated servers.
If you disable Location Smart Triggers or revoke location permission, location evaluation stops.
If you enable a Connected Device Smart Pill or paired-device Smart Trigger and grant Android’s Nearby Devices or Bluetooth permission where required, Modesmith may access information about connected or already-paired Bluetooth audio devices.
This may include:
Device display name
Connection state
Device type
Battery percentage, when Android provides it
A device identifier needed to distinguish paired devices
Modesmith does not scan for new Bluetooth devices and does not use Bluetooth features to determine your location.
For a paired-device Smart Trigger, Modesmith stores the device’s display label and a SHA-256 fingerprint derived from the device identifier. Modesmith does not store the raw Bluetooth hardware address in the trigger rule.
This information is used locally to display connected-device information or switch modes according to rules configured by you.
Modesmith does not upload connected-device information to developer-operated servers.
If you enable notification badges, media controls, or Guest Mode notification protection, Modesmith may use Android Notification Listener access.
For notification badges, Modesmith uses the app package and Android profile associated with active notifications to calculate badge counts.
If you enable the Guest Mode option to hide notifications from hidden apps, Modesmith may dismiss notifications belonging to apps hidden by your Guest Mode visibility rules. Dismissed notifications may not return after Guest Mode is disabled, and Android may prevent some ongoing notifications from being dismissed.
For launcher media controls, Modesmith may access active Android media-session information, including:
Media app name and package
Track or media title
Artist, album, or subtitle
Album artwork or media artwork
Playback state
Playback position and duration
Available playback controls
Media information is used locally to display and operate launcher media controls. It may be retained temporarily in memory to keep playback controls stable, but it is not uploaded or saved as a permanent listening or viewing history.
Modesmith does not persistently store general notification titles, message text, sender names, or notification content.
Notification Listener access can be disabled at any time in Android settings.
Modesmith includes an optional Accessibility Service for launcher actions initiated by you, such as:
Locking the screen
Opening the notification panel
Opening the Quick Settings panel
Before directing you to Android Accessibility settings, Modesmith provides an in-app explanation of why the capability is requested.
Modesmith does not use its Accessibility Service to:
Read screen content
Collect text
Monitor app usage
Record user actions
Capture passwords
Capture keyboard input
Perform advertising or analytics
Transmit accessibility information
The Accessibility Service is not required for normal launcher use and can be disabled at any time in Android Accessibility settings.
Modesmith may request Android’s Camera permission solely to control the device flashlight through a launcher action.
Modesmith does not use this permission to:
Take photographs
Record video
Record audio
Read photographs
Perform facial recognition
Transmit camera information
If you do not grant Camera permission, the flashlight action will not be available.
Modesmith may request Android’s notification permission to display local timer alerts and timer controls.
Timer information is stored and processed locally. Modesmith does not transmit timer names, durations, or timer activity to developer-operated servers.
If notification permission is denied or revoked, timers may continue locally, but Android may prevent Modesmith from showing timer notifications.
If you configure a mode or launcher action to control Do Not Disturb, Modesmith may ask you to grant Android Notification Policy access.
Modesmith uses this access only to read or change Android’s current interruption-filter state when required by an action or mode configured by you.
Modesmith does not use this access to read notification message content.
You can revoke Do Not Disturb access in Android settings.
If you use an action that changes Android screen auto-rotation, Modesmith may ask you to grant permission to modify system settings.
Modesmith uses this capability only to read and change Android’s auto-rotation setting when requested by you.
Modesmith does not use this capability to change unrelated system settings.
You can revoke this access in Android settings.
Modesmith may ask Android to show a device credential prompt for:
Guest Mode Lock
Protected Modesmith settings
Protected Android Settings shortcuts opened from Modesmith
Android handles the authentication interface and verification.
Modesmith does not receive, store, or transmit your PIN, password, pattern, fingerprint, face data, or other biometric information.
If you choose a mode wallpaper image, Modesmith stores the Android content URI or reference for that image so it can display the wallpaper locally.
Modesmith uses Android’s Storage Access Framework and does not request broad access to all files on your device.
If you add an Android widget, Modesmith stores the widget ID needed to display it. Widget content is created and controlled by the widget provider’s app. Interactions with a third-party widget may be handled by that provider and are subject to that provider’s privacy practices.
Wallpaper references and widget IDs are generally device-specific and may not work after moving a backup to another device.
If you export or import a backup, Modesmith uses the file or document location selected by you through Android’s Storage Access Framework.
An exported backup is a JSON file that may include:
Modes
Mode names and colors
App package and activity identifiers
App assignments
Schedules
Smart Trigger configuration
Saved Location Smart Trigger coordinates, radii, and labels
Calendar trigger filters and labels
Bluetooth trigger labels
Hidden-app and visibility rules
Wallpaper references
Icon and appearance preferences
Launcher settings and other configuration
Exported backups do not include sampled device locations, location history, complete contact lists, calendar event content, general notification content, or raw Bluetooth hardware addresses.
Modesmith does not upload backup files to developer-operated servers. However, Android may allow you to select a third-party or cloud document provider, such as Google Drive. If you choose such a provider, that provider handles the file according to its own privacy policy.
Exported backups are not encrypted by Modesmith. Anyone who can access the exported file may be able to read the launcher configuration and saved location-rule coordinates inside it. Store backup files only in locations you trust.
Modesmith may store app keys representing recently launched apps for launcher convenience.
If you enable usage learning, Modesmith stores local launch counts so app ranking can adapt on your device.
Modesmith does not use Android Usage Access for this feature. It learns only from launches initiated through Modesmith.
This information is not uploaded or shared by Modesmith.
Modesmith may read Android’s next scheduled alarm time to display it on the launcher or in an upcoming-alarm Smart Pill.
Smart Triggers may also read limited device state, such as:
Charging state
Connected audio output
Already-paired Bluetooth connection state
Active calendar-event state
Foreground location state
Modesmith can open Android screens or other apps for actions initiated by you, including:
Android Settings
Calendar
Clock
Contacts
Notification settings
Wallpaper settings
Bluetooth settings
App information
Android’s uninstall confirmation
Dialer or messaging apps
Browsers and web links
Modesmith does not complete an app uninstall without Android’s user-controlled confirmation.
Once another app or Android system screen is opened, that app or service is governed by its own privacy practices.
Modesmith allows you to follow the Android system language or choose a supported language for Modesmith.
The selected app-language setting is stored locally using Android and AndroidX locale facilities. Changing the app language does not transmit language data to Modesmith or to developer-operated servers.
Modesmith uses Google Play Billing for optional Pro purchases and Google Play’s in-app update APIs to check for and install Play-managed updates.
Google Play may process account, device, payment, transaction, and network information according to Google’s own terms and privacy policy.
Modesmith receives limited purchase-state information needed to determine whether Pro access is active, pending, cancelled, cached, or unavailable. Modesmith stores only the local entitlement state needed to provide purchased features.
Modesmith does not receive or store your complete payment-card number, bank information, Google account password, or payment credentials.
Google’s Privacy Policy is available at:
https://policies.google.com/privacy
The optional Support Modesmith action opens a Razorpay-hosted page in your chosen browser only after you confirm the external handoff.
Modesmith does not make the payment request itself and does not receive or store:
Payment-card details
Bank details
UPI credentials
Payment account credentials
Payment authentication information
Any information you enter on the Razorpay page is handled by Razorpay, your browser, your bank, and other payment providers according to their own terms and privacy policies.
Razorpay’s privacy policy is available at:
Support payments do not unlock Modesmith Pro features.
Modesmith’s optional Web Search pill allows you to select an installed browser.
Modesmith stores the selected browser package locally and opens that browser using a normal Android web intent.
Modesmith does not:
Choose a search provider
Read your browser history
Read the search query after the browser opens
Make the web search request itself
Operate a search proxy or search server
The browser and search provider you use are governed by their own privacy practices.
Modesmith does not collect your email address through an in-app account or registration system.
If you voluntarily contact the developer by email, submit a Google Play review, or send diagnostic information, the information you provide may include your email address, message content, attachments, device details, screenshots, or other information you choose to send.
That information will be used to respond to your request, investigate a problem, maintain the app, or meet legal obligations. Do not send passwords, payment credentials, precise location, private backup files, or other sensitive information unless it is necessary and you understand the risk.
Modesmith does not transmit the following to developer-operated servers:
Your installed-app inventory
Launcher configuration
Contact list
Calendar events
Current or sampled device location
Location history
Saved location-rule coordinates, except when you independently send a backup or other information to the developer
Notification content
Media history
Bluetooth-device information
Wallpaper images
Backup files
Web browsing history
Advertising identifiers
Custom analytics events
Modesmith does not include ads, advertising SDKs, third-party analytics SDKs, third-party crash-reporting SDKs, cloud sync, or an in-app user account system.
Google Play and other external apps or services may independently process information under their own privacy policies.
Modesmith does not sell personal or sensitive user data.
Modesmith does not share personal or sensitive launcher data with advertisers, analytics providers, data brokers, or third parties for marketing or profiling.
Because Modesmith does not operate developer servers for launcher data, the developer generally cannot access information stored locally inside the app.
Information may be handled by Android system services or apps you choose to use with Modesmith, including:
Android Contacts
Android Calendar
Android location services
Android Notification Listener services
Android Accessibility services
Android Storage Access Framework
Android AppWidgetHost
Android system backup
Google Play Billing
Google Play app updates
Selected widget providers
Selected browsers
Razorpay
Apps or settings screens opened by you
Those services and apps are governed by their own privacy practices.
We may disclose information actually in our possession if required by applicable law or a valid legal request. Because Modesmith stores launcher data locally and does not operate launcher-data servers, we normally do not possess your on-device launcher data.
Depending on your Android version, device settings, and Google account settings, Android system backup or device transfer may back up eligible Modesmith preferences through Android or Google backup services.
Modesmith’s current backup rules exclude its primary launcher database and certain transient caches from automatic Android cloud backup and device transfer. Other eligible preferences may still be handled by Android’s backup system.
Android system backup is controlled by Android, your device manufacturer, and your Google account settings—not by Modesmith’s own servers.
This is separate from the explicit JSON export created when you choose Modesmith’s Backup feature.
Modesmith stores local data using Android-provided app storage, including a local database and preferences. Android app sandboxing helps prevent other apps from directly accessing this data.
Sensitive runtime permissions are requested only when needed for optional features.
Modesmith does not transmit launcher data to developer-operated servers. Google Play services and external apps may communicate with their own services according to their own privacy practices.
Exported JSON backups are not encrypted by Modesmith. Backup files containing location-rule coordinates or private launcher configuration should be stored only in trusted locations.
No storage or security system can guarantee absolute security, but Modesmith limits access and retention to what is needed for its local launcher features.
Modesmith keeps local launcher configuration until you:
Change or delete it in Modesmith
Delete the relevant mode, trigger, widget, shortcut, or rule
Clear Modesmith’s app storage in Android settings
Uninstall Modesmith
Temporary information such as current location samples, active calendar events, media metadata, notification badge state, and connected-device state is retained only as needed in memory for the corresponding feature.
You can delete Modesmith’s local data by clearing the app’s storage or uninstalling the app.
Clearing app data or uninstalling Modesmith does not delete:
JSON backup files exported by you
Information stored by Android or Google backup services
Google Play purchase records
Emails or support information you voluntarily sent
Information handled by third-party apps or services
Exported backup files must be deleted separately from the location where you saved them.
If you request deletion of information you voluntarily sent to the developer, contact sriramanb1997@gmail.com. Some records may be retained where required for security, fraud prevention, legal compliance, or legitimate support records.
You can control optional access at any time:
Disable Contact Search or revoke Contacts permission.
Disable calendar features or revoke Calendar permission.
Disable Location Smart Triggers or revoke Location permission.
Disable connected-device features or revoke Nearby Devices or Bluetooth permission.
Disable notification badges, media controls, or Guest notification dismissal, or revoke Notification Listener access.
Revoke notification permission to stop Modesmith timer notifications.
Disable the Modesmith Accessibility Service.
Revoke Camera permission to disable flashlight control.
Revoke Do Not Disturb access.
Revoke permission to modify system settings.
Remove widgets and wallpaper references.
Delete smart triggers, modes, app selections, and other configuration.
Clear Modesmith’s app storage or uninstall the app.
Delete exported backups separately.
Select Follow system or another supported Modesmith language.
Disabling an optional permission may prevent the related feature from working, but normal launcher functionality remains available where technically possible.
Modesmith is a general Android launcher utility and is not directed specifically to children.
Modesmith does not knowingly collect personal information from children through developer-operated servers. Parents or guardians can use Android permission controls and device settings to manage access to optional features.
We may update this Privacy Policy when Modesmith’s features, permissions, data practices, legal obligations, or platform requirements change.
When material changes are made, the effective date at the top of this page will be updated and the revised policy will be published at the privacy-policy URL listed for Modesmith on Google Play and linked from the app where applicable.
For privacy questions, requests, or concerns, contact:
Sriraman Balachander
Modesmith Launcher
Email: sriramanb1997@gmail.com