This Privacy Policy explains how data is accessed, used, stored, and shared when using the Android applications Switchly, Switchly Lite, and Switchly Launcher, developed by Andi Schreiner.
This policy applies to users of the Android applications:
Switchly, Switchly Lite, and Switchly Launcher may use the Android AccessibilityService API for the app blocking feature. When enabled by the user, this service can detect when a selected app is opened so the app can immediately block access and enforce limits, schedules, profiles, and related blocking rules configured by the user.
While enabled, Android may allow the app to observe app and window changes needed to detect blocked apps. This access is used only for app blocking and enforcement of the blocking rules configured by the user. It is not used to read passwords or keystrokes for advertising.
Accessibility access is optional, must be enabled manually by the user in Android Accessibility settings, and can be revoked by the user at any time.
The apps may request App Usage Access to read Android usage statistics. This is used to provide screen-time summaries, daily app limits, usage-based blocking, and related in-app statistics.
If the user enables notification-related features, the apps may request Notification Listener access to identify notifications from apps that are currently blocked by the active profile and suppress them on the device.
Without this access, notification blocking features will not function.
If the user enables NFC-based actions, the apps may read NFC tag data to trigger user-configured actions. If paired-tag features are used, NFC tag identifiers and related metadata may be stored locally on the device so the apps can recognize authorized tags and apply configured actions, limits, or cooldowns.
If the user enables QR-based features, the apps may request Camera permission to scan QR codes. Camera access is used only for scanning QR content needed for the selected feature.
The apps may request notification permission so they can show reminders, status updates, and feature-related notifications to the user.
If the user chooses to sign in and use optional cloud features, the apps may use services such as Google Sign-In, Firebase Authentication, and Firebase Firestore to authenticate the account and store or restore backup data.
Optional cloud backup data may include app settings, profiles, schedules, blocked-app selections, NFC-related configuration, and related usage or blocking statistics needed to restore the user’s app state across installs or devices.
Cloud backup and restore are optional and user-initiated. If the user does not use these features, most app data remains stored locally on the device.
The apps may use crash reporting tools such as Firebase Crashlytics to collect technical diagnostics needed to detect errors, investigate crashes, and improve app stability.
The apps store configuration and runtime data locally on the device as needed for core functionality. This may include profiles, schedules, blocked-app selections, app usage statistics, blocking statistics, NFC-related data, and other settings created by the user.
Local app data is retained for as long as necessary to provide app functionality or until the user clears app data, uninstalls the app, or deletes relevant content. If the user uses optional cloud features, cloud-stored data is retained until it is deleted by the user or no longer needed to provide the service.
If the user has enabled optional account and cloud features, account-related cloud data can be deleted using the deletion options provided in the app, where available. Users may also contact us to request deletion support.
Under applicable data protection laws, including the GDPR where applicable, users may have the right to request access to, correction of, or deletion of their data. Requests can be made via email: info@saltyy.at
Andi Schreiner
Vienna, Austria
Email: info@saltyy.at