Privacy Policy for SilverLink Launcher
This policy applies exclusively to the SilverLink Launcher app. Your privacy is important to us. SilverLink Launcher ("the App") is a product of Golden River. This privacy policy explains how the App handles the information it can access on your device, including the analytics and crash-reporting data it collects through Google Firebase.
Information We Access
Your personal data — such as your imported contacts, SOS emergency contact, favourites, search history, and settings — stays on your device and is never collected without consent or shared. Location and contact information are accessed only with your consent and only when the corresponding feature needs them (for example, the SOS feature or viewing contacts), as explained in the "How We Handle Location and Contacts" section below. The App also collects anonymous technical and usage data (crash logs, performance data, and app-interaction statistics) through the Google Firebase SDKs strictly to keep the App stable and improve it. No account information or personal identity is sent to us or any third party.
How We Handle Location and Contacts
Your location and contact information are only collected with your explicit consent, and only when the relevant feature of the App actually needs them — never by default. The App does not access your location or contacts unless you first allow it and then use the function that requires it.
- Location is accessed only when you trigger the SOS emergency feature, so the App can include your current location in the emergency message you send to your preset contact. Location is read in real time and is not stored.
- Contacts are accessed only when you choose to import contacts so you can view and use them within the App's favourites. Contact data is saved only on your device and is never transmitted to or stored on another device or server.
- We never obtain your location or contacts without your permission and while the corresponding feature is in use — you must grant the permission in the App's settings and actively use the SOS or contacts feature for the data to be read.
Analytics and App Performance Data
To keep the App stable and improve its performance, the App integrates the Google Firebase platform. This includes Firebase Crashlytics, Firebase Analytics (which powers Remote Config and A/B testing), and the Firebase Performance SDK. These services collect only anonymous, technical data:
- Crash logs and diagnostic information — sent automatically when the App crashes, so we can find and fix bugs. Used for analysis.
- App performance data — response and load times of different screens, used for analysis.
- App-interaction statistics — how often and which pages/screens of the App are used, used for analysis.
- Information about installed apps and device — a device identifier and technical attributes of your device, used for analysis.
None of this data identifies you personally. We do not collect your account information, contacts, calls, messages, location history, or any other content you create in the App.
Data We Share With Third Parties
The only third party involved is Google via the Firebase services described above. We share the anonymous technical and usage data listed in the previous section with Google Firebase solely for the purpose of app analytics, crash reporting, and performance monitoring. We do not sell, rent, or otherwise disclose your personal data to any other company or organization.
Permissions
Used only when you choose to import existing contacts into the App's favourites list. Contact names and phone numbers are read from the device and stored locally so the App can display one-tap call shortcuts. Contact data is never sent off-device.
Allows the App to start a phone call directly when you tap a favourite contact's call shortcut. If this permission is not granted, the App automatically falls back to the system dialer for confirmation. The number dialled is the one you saved in the App.
Used to toggle the device's camera flash LED on or off as a convenience flashlight/torch. No images or camera data are accessed.
Provides haptic feedback when buttons are pressed and powers the vibration alarm for the SOS emergency feature. No vibration data is collected.
Used only when you trigger the SOS emergency feature to obtain your current location and include it in the emergency message. Location is read in real time and is not stored by the App or transmitted anywhere except in the emergency SMS you initiate.
Used only when you trigger the SOS emergency feature to send an emergency message to your preset emergency contact. The App sends messages from your device but does not read your messages or SMS history.
Features That Use Device Hardware
How We Use the Information
- Contact details you import are stored locally on the device so the App can provide one-tap call shortcuts.
- Phone permission is used strictly to trigger the system dialer with the number you selected.
- App usage frequency is cached locally to sort the home-screen app grid by how often you use each app.
- Search history is stored locally to speed up app search.
- Settings and preferences (font size, column count, display mode, voice feedback, etc.) are stored locally to remember your choices.
- SOS emergency uses your current location and sends an SMS to your preset emergency contact only when you trigger it. Location and SMS content are used in real time and are not stored.
- Analytics and performance: anonymous technical and usage data is collected through the Google Firebase SDKs (crash logs, diagnostic information, performance data, app-interaction statistics, and a device identifier) for analysis and app improvement, as described in the "Analytics and App Performance Data" section above.
- The App never shares your contacts, call data, messages, search history, location history, or any other personal or sensitive information with third parties. The only data shared with a third party is the anonymous technical and usage data we send to Google Firebase for app analytics.
Data Storage
All data created by the App — including favourite contacts, SOS emergency contact, app usage frequency, search history, settings, and preferences — is stored exclusively in the device's local storage (MMKV). Your location is read only in real time during an SOS event and is not stored. No cloud storage or remote databases are used for your personal data.
The only information sent off-device is the anonymous technical and usage data collected by the Google Firebase SDKs (crash logs, performance data, app-interaction statistics, and a device identifier). This data is processed in the aggregate and contains no personal identity.
Data Retention and Control
- You can remove contacts, apps, or any personalisation at any time from within the App.
- You can revoke any permission at any time through your device's system settings.
- Uninstalling the App deletes all locally stored data created by it.
- Anonymous analytics and performance data collected through Google Firebase (crash logs, performance data, app-interaction statistics, and device identifiers) is automatically deleted within 90 days. This retention is handled by the data-retention settings of the Firebase services and needs no action from you.
Data deletion: All data you create in the App — such as imported contacts, your SOS emergency contact, favourites, and preferences — can be deleted at any time by removing them in the App or by uninstalling it. The anonymous analytics data described above is deleted automatically within 90 days and requires no separate request. If you have any questions, contact us through the in-app feedback channel.
Children's Privacy
The App is not directed at children under the age of 13 and does not knowingly collect any personal information from children.
Changes to This Policy
We may update this policy to reflect new features or legal requirements. If we make significant changes, we will update the "Last updated" date above and, where practical, highlight the updates in the App or accompanying documentation.
Update History
Contact Us
If you have any questions about this policy or how the App handles data, please contact us through the in-app feedback channel.