Privacy Policy for my projects where no data is collected
Last updated: September 12, 2026
This policy applies to Sensor Stream for Android (com.sensorsensei), developed by Priyankar Kumar.
Sensor Stream turns your phone into a sensor source for a server that you choose. Depending on the switches you enable and permissions you grant, the app accesses and transmits device sensor readings (such as motion, magnetic field, light, proximity and step count), camera images, microphone audio, location coordinates, timestamps and optional text that you enter.
Camera, microphone, location and activity permissions are requested when needed. You can decline them and continue using streams that do not require those permissions. You can revoke permissions in Android settings.
Streams go to the server address you enter. The developer does not operate a mandatory collection server, receive a copy of your streams, sell your data, or use it for advertising. The app does not include advertising or analytics SDKs. Your server receives the connection’s network address and the streams you enable. If you choose a server operated by someone else, that operator controls how received information is used and retained.
The app uses data to provide the streaming functions you request. It does not require an account. Sensor and location messages can include your optional text; do not enter information you do not want sent to the selected server.
Turn a stream off or use Stop all streams to stop sending and release capture resources. Streaming stops when the app leaves the foreground. Stream data is handled transiently rather than saved as a recording by the app. Android camera processing may create temporary image/cache files, which you can remove by clearing the app’s storage or uninstalling it.
Your server may save received data, including recordings and logs. Delete those files on your server or ask its operator to delete them. Clearing or uninstalling the phone app does not delete data already received by a server.
A ws:// connection is unencrypted. Use it only on a trusted network. Use a properly configured wss:// server when you need transport encryption. Only connect to a server you trust, and control access to that server and its saved data.
For privacy questions or requests, contact Priyankar Kumar at priyankar.kumar98@gmail.com. Changes to this policy will be published on this page with an updated date.