Privacy Policy of Bhajan App

Privacy Policy for Bhajan

Effective date: April 06, 2024

Tims & AD ("us", "we", or "our") operates the Bhajan mobile application (hereinafter referred to as the "Service").

This page informs you of our policies regarding the collection, use, and disclosure of personal data when you use our Service and the choices you have associated with that data.

The Service is a free app for playing religious songs, including safe YouTube videos, audio, and their lyrics. It is designed to provide a positive experience without collecting any personal data from its users.

Information Collection And Use

We do not collect any personal data with our Service.

Types of Data Collected

Personal Data

While using our Service, we do not ask you to provide us with any personally identifiable information.

Usage Data

We do not collect information on how the Service is accessed and used ("Usage Data").

Tracking & Cookies Data

We do not use cookies or similar tracking technologies to track the activity on our Service.

Use of Data

Tims & AD uses the collected data for various purposes:

  • To provide and maintain the Service
  • To notify you about changes to our Service
  • To provide customer care and support
  • To provide analysis or valuable information so that we can improve the Service
  • To monitor the usage of the Service
  • To detect, prevent, and address technical issues

Transfer Of Data

Your information, including Personal Data, is not collected, and therefore not stored or transferred to any third party.

Disclosure Of Data

Legal Requirements

Tims & AD will not disclose your Personal Data since we do not collect it.

Security of Data

The security of your data is important to us, but remember that no method of transmission over the internet or method of electronic storage is used.

Comments

Post a Comment

Popular posts from this blog

ADB Cheat Sheet

Take screenshot of the only emulator/device, and copy the screenshot to clipboard(so we can paste it directly somewhere) adb exec-out screencap -p > screen.png && osascript -e 'set the clipboard to POSIX file "'$(pwd)'/screen.png"' If you want to add it as an alias, in ~/.zprofile file(or whichever file it is for you), add these lines: function ss() { adb exec-out screencap -p > screen.png && osascript -e "set the clipboard to POSIX file \"$(pwd)/screen.png\"" } Lists all settings adb shell settings list global enables "show taps" on the UI adb shell settings put system show_touches 1 To set animation duration to 10x adb shell settings put global animator_duration_scale 10 adb shell settings put global window_animation_scale 10 adb shell settings put global transition_animation_scale 10 set the battery state as unplugged adb shell dumpsys battery unplug To set the battery percentage adb shell dumpsys batter
Read more

Capturing Screen of Android Device using ADB

 Make sure the android device is connected. adb devices Run the following command and start performing actions on your emulator or physical device. adb shell screenrecord /sdcard/example.mp4  Once you are done, press [Ctrl] + [C] to stop the recording. Pull the video from the device to your computer using: adb pull /sdcard/example.mp4 If you want to convert the mp4 to gif, run this command: ffmpeg -i example.mp4 example.gif
Read more

Debugging Android app with ADB command

Image
1. First find the emulators that are active. adb devices 2. You can specify the device ID or serial number to start debugging in a particular emulator/device, but I am considering you have only one emulator. Close other emulators or disconnect other devices if you have any extra. 3. Find the packages installed on the emulator so you can get the package name: adb shell pm list packages Use grep command to find the exact package name. 4. Set the app to debug at startup: adb shell am set-debug-app -w com.sulav.carowner Start the app on the emulator by clicking on the launcher icon. You will get a popup saying it's waiting for a debugger to be attached. In the Android studio, go to Run -> Attach Debugger to Android Process and select the particular process. Now if you have kept breakpoint on the code, it will stop at that point.
Read more