CastPulse is a fishing activity tracking application for Android phones and supported wearable devices. This policy covers the CastPulse mobile app and its Wear OS companion app.
For privacy questions, contact the CastPulse team at [email protected].
Data processed by CastPulse
CastPulse processes motion sensor readings from supported wearable devices, including accelerometer and gyroscope data. These readings are used to detect fishing activity and calculate statistics such as casts, reeling activity, and fishing time. Activity recognition runs locally on your phone.
CastPulse also processes and stores:
- Trip start and end times, recorded sensor data, detected activities, and derived statistics.
- Connected wearable names and identifiers, device models, and connection or battery status where available.
- Application and activity-recognition model version information.
- Technical diagnostic information, including timestamps, errors, and recording or connection events.
This information is used to record fishing activity, display trip history, connect supported devices, and investigate technical problems.
Local storage and accounts
Core trip and sensor data is stored locally on your phone. The Wear OS companion app may also store diagnostic information locally on your watch.
CastPulse does not require an account for its core tracking functionality and does not provide its own cloud backup or account synchronization service.
However, Android system backup and device-transfer features may copy app data, depending on your device and settings. These copies are managed by your platform or backup provider. For more information, see Android’s backup documentation.
Wearable communication
CastPulse communicates with supported wearable devices to receive motion sensor readings and device status, and to exchange recording controls.
Communication with supported Bluetooth sensors uses Bluetooth. Communication between the Wear OS companion app and your phone uses Google Play services.
Depending on connectivity, Wear OS communication may travel over Bluetooth or through Google’s servers. Google states that data transferred through its cloud using the Wear OS Data Layer service is end-to-end encrypted. See Google’s Wear OS communication documentation.
Permissions and location
CastPulse uses the following permissions and system capabilities:
- Bluetooth and Nearby devices: to discover and connect to supported wearable devices.
- Location permission on Android 11 and earlier: Android requires this permission for Bluetooth discovery. CastPulse does not use it to read GPS coordinates or record fishing locations.
- Notifications: to show recording status and ongoing trip information.
- Background services and wake locks: to keep an active recording running when the screen is off or another app is open.
- Network access: to support platform communication services, including communication between the phone and watch.
CastPulse does not currently collect or store your geographic location as part of its tracking functionality.
You can manage permissions in your device settings. Disabling a required permission may prevent the associated feature from working.
Optional sharing and model improvement
CastPulse does not automatically send trip recordings or diagnostic logs to the CastPulse team.
You may choose to export or share trip recaps, diagnostic logs, or support packages through your device’s sharing interface. Support packages may include raw motion sensor recordings, trip information, derived statistics, wearable identifiers, version information, and technical diagnostics.
You choose the app or destination that receives the file. That app or service’s privacy practices apply to its handling of the shared information.
If you voluntarily send recordings or support packages to the CastPulse team during alpha testing, we use them to investigate problems and to train, test, and improve fishing activity-recognition models. Sharing is optional and is not required to use the app’s core tracking functionality.
If you contact us, we also receive the information you provide, such as your email address, message, and attachments, and use it to respond to your enquiry.
Data retention and deletion
Locally stored trip data remains on your device until the app’s stored data is cleared or the app is uninstalled. Some diagnostic logs and temporary files are automatically pruned.
You can remove local app data through your device’s application settings. Phone and watch storage are separate, so you must clear the app’s data or uninstall it on each device to remove its local data.
Clearing app data or uninstalling the app does not remove copies previously exported, shared, or backed up. Those copies must be managed through the relevant recipient, service, or backup settings.
We retain voluntarily submitted recordings, diagnostic files, and related correspondence while they are needed to investigate reported problems, respond to enquiries, or develop and evaluate activity-recognition models. We delete them when they are no longer needed for those purposes.
You can request deletion of files and correspondence you submitted to the CastPulse team by contacting [email protected].
Security
CastPulse uses Android and Wear OS application storage protections and platform communication APIs to protect data within the app.
When you export or share a file, its subsequent storage and protection depend on the recipient and the apps or services you choose.
Children
CastPulse is not specifically designed for children.
Changes to this policy
We may update this policy when CastPulse functionality or data practices change, including if accounts, cloud synchronization, or additional sharing features are introduced.
The latest version will be published on this page with an updated date.
Contact
For privacy questions or requests concerning information you have sent us, contact:
CastPulse team
Email: [email protected]