Overview
SniperPulse is a precision sports stability trainer for Android, Wear OS, iOS, and Apple Watch. It uses your device's motion sensors to measure hold stability, detect shots, and track improvement over time. On the watch it also reads your heart rate during a training session.
By default, all training data stays on your device. Session recordings, shot events, stability scores, and heart-rate readings are stored locally and are not transmitted to our servers.
SniperPulse does not require an account, a sign-in, or any personal information to use. It does not collect your name, email address, phone number, contacts, or precise location, and it uses no advertising SDK.
Two things can send limited data off your device: (1) an optional, anonymous device sensor-performance report to our own servers, sent only after you accept the in-app consent dialog; and (2) user-initiated bug reports, sent only when you shake your device and choose to submit one. Production Android builds contain no third-party analytics SDK. Each channel is described in detail below.
Data Collection
By default: stays on your device
These items are read and stored on your device only. Nothing is transmitted unless you explicitly opt in.
- Motion sensor readings (accelerometer, gyroscope, rotation vector) - Measure hold stability, wobble, and shot detection during training sessions. Raw sensor streams never leave your device.
- Heart rate (Wear OS / Apple Watch) - Read from the watch's body sensor during a training session; shown live and in the session summary so you can relate physical state to hold stability. Stored locally and synced only to your own paired phone; never uploaded to our servers or shared with third parties. SniperPulse does not use Health Connect.
- Training session data - Shot events, stability scores (MOA), wobble traces, steadiness score, drift detection, session duration, and heart-rate summary - stored locally with your training history.
- Mounting profiles - User-created calibration profiles (orientation baseline, threshold settings). Local only.
Opt-in: uploaded only with your consent
These items are transmitted only if you enable the corresponding feature. Opting out prevents future uploads.
- Anonymous device sensor-performance profile - After you accept the in-app consent dialog, the app sends a technical profile of your device's sensors to our own servers (lincinnovations.com): device manufacturer, model, and hardware; OS / SDK version; sensor fusion availability; and aggregate sensor-quality statistics (gravity mean/standard deviation, requested vs. actual sample rate and jitter, per-axis noise), plus the app version. It contains no name, email, location, advertising ID, or per-install identifier, and no sensor recordings. We use it to tune sensor accuracy across device models. Turn it off any time in Settings - Data Collection.
Bug reports only
These items are included only when you manually submit a bug report or feedback from within the app.
- User-typed bug-report description (optional) - When you shake the device to file a bug report, you can type a description and pick a category. The text is uploaded with the report. We ask that you not include personal identifiers; the field is sent verbatim.
- Screenshot of the current screen (optional) - When you submit a bug report, a screenshot of the screen you were on is captured and uploaded so we can reproduce the issue. SniperPulse screens do not display personal identifiers, but the screenshot captures whatever was visible.
- Recent app logs (optional) - When you submit a bug report, the most recent in-session log lines are attached to help us diagnose the issue. Logs are written without personal identifiers.
- Bug-report device & diagnostic context (optional) - Each bug report you submit also includes technical context: device manufacturer/model, OS version, app version and build channel, locale, time zone, screen size/density, free and total memory, battery level and charging state, network-connection type, a session identifier, an anonymous Firebase Authentication UID, and an anonymous device identifier derived by one-way hashing a system device ID (Android SSAID / iOS IDFV). This hashed identifier lets us group multiple reports from the same device; note that, unlike an uninstall-reset ID, it does NOT reset on reinstall. It is not linked to your name or any account.
Opt-In Features
The following features transmit data only if you explicitly enable them. They are off by default.
Anonymous device sensor-performance report
When enabled via the in-app consent dialog, SniperPulse sends the anonymous device sensor-performance profile described above to our own servers. No sensor recordings, no free text, no location, no advertising ID, no per-install ID. Disable it any time in Settings - Data Collection; toggling off stops all further uploads.
Bug reports
Shake your device to open the bug-report form. If you choose to submit, it sends what you typed, a screenshot of the current screen, recent in-session logs, the category you picked, and the device/diagnostic context described above. Reports go to LINC's Firebase project (linc-xraykit-prod) and our internal Slack, and are used solely to diagnose and fix issues.
Third-Party Services
SniperPulse interacts with the following third-party services. It uses no advertising SDKs, no analytics trackers, and no social media integrations.
- Firebase (Google) - project linc-xraykit-prod - Backend for user-initiated bug reports submitted through XrayKit. Report contents (description, screenshot, logs, device/diagnostic context, anonymous UIDs) are uploaded to Firebase Storage and Firestore in this project. Google processes this data as our service provider, on our behalf, not for its own purposes.
When used: Only when you submit a bug report · Privacy policy - Slack - When a bug report is submitted, a notification containing the report content (including the device/diagnostic context above) is posted to LINC's internal Slack channel for triage. Slack processes this as our service provider.
When used: Only when you submit a bug report · Privacy policy
Data Retention
- Local data: Until you uninstall the app or clear storage. Uninstalling SniperPulse permanently deletes all local training data, sessions, heart-rate history, and calibration profiles.
- Uploaded data: The anonymous device sensor-performance profile is kept to help us improve sensor accuracy across device models. Because it contains no name, account, location, or per-install or device identifier, it cannot be traced back to you or your device - there is nothing personal to delete, and we retain it as anonymous device-behaviour data. You can stop sending new profiles any time in Settings - Data Collection.
- Bug reports: Bug-report attachments (screenshots, logs) and the report record (description, category, device/diagnostic context, anonymous UIDs) are automatically deleted 90 days after submission. To request earlier deletion of a report you submitted, contact hello@lincinnovations.com with the date and category.
Children's Privacy
SniperPulse is not directed at children under 13. It is designed for adult precision sports training and is gated by an in-app age-confirmation step on first launch. We do not knowingly collect data from children under 13. If you believe a child has used the app, contact us at hello@lincinnovations.com and we will investigate and delete any associated records.
Your Rights
Residents of California (CCPA), the European Union (GDPR), and similar jurisdictions have the right to access, correct, or delete personal data held about them, and to opt out of certain data uses. Because SniperPulse does not collect personal identifiers tied to individuals, some of these rights may not apply as usually framed. Contact us at hello@lincinnovations.com to exercise any rights under applicable law.
Changes to This Policy
We may update this policy as SniperPulse evolves. Changes will be reflected in the “Last updated” date at the top of this page. Material changes will be announced in-app when possible.