PulsePlay · Android · Privacy Policy

This Privacy Policy explains how the PulsePlay Android and Wear OS apps handle information when you record a session, connect your devices, share with a nearby partner, create an image, or make a purchase.

PulsePlay does not require a PulsePlay account and does not operate a server for storing your heart rate recordings. Information is processed on participating devices, through the platform services described below, and by apps or people you choose to share with.

1. Information PulsePlay handles

Depending on the features you use, PulsePlay handles:

• Heart rate and session information: heart rate readings and their timing, recording duration, connection and recording status, calculated baselines, statistics, and sound or vibration alert events. A compatible watch obtains heart rate through Wear OS Health Services. The phone app does not measure or generate heart rate.
• Information you enter: a display name, optional age, maximum heart rate or reference heart rate, temporary wearer settings, moment markers and notes, and private tags. These support session setup, calculations, history, and filtering. Temporary wearer settings are separate from the device owner's profile.
• Connection and app information: app-generated owner, device, session, and operation identifiers; pairing credentials; sharing choices; language and feedback settings; and synchronization, delivery, and deletion status. These help devices recognize authorized connections, save changes, avoid duplicate operations, and respect local deletions.
• Purchase information: Google Play product identifiers, purchase tokens, signed purchase records, payment status, and acknowledgment status used to verify and restore access. PulsePlay does not receive your full payment card details or Google account password.
• Messages you send us: if you contact support, we receive the email address, message, and attachments you choose to provide. Do not send heart rate recordings, private notes, or other sensitive information unless needed for your request.

PulsePlay does not include advertising or third-party advertising or analytics SDKs. We do not sell your personal or health information or use it for targeted advertising.

2. How information is used

PulsePlay uses information to record and display sessions, calculate heart rate changes and statistics, provide optional sound and vibration feedback, save history, apply your settings, synchronize participating devices, and carry out sharing choices. Purchase information is used to check access, acknowledge purchases, and restore an existing purchase. Support messages are used to respond to your request.

Optional age can be used locally to calculate a maximum heart rate when you have not entered one. Calculated values and alerts are general informational features, not medical assessments.

3. Your devices and nearby sharing

Your phone and watch. When you link your own devices, PulsePlay uses Google Play services' Wearable Data Layer to exchange setup information, session controls, recordings, and access status needed for the features you use. Each device keeps its own saved copy of data it records or actually receives. Private tags stay on the device where they are created. Purchase tokens and signed purchase records are not transferred through PulsePlay's device synchronization.

A nearby partner. Pairing alone is not agreement to share heart rate. The sharing flow explains the data exchange and lets each participant choose whether to share and receive or only receive. Pairing exchanges the display name and technical information needed to identify and authenticate devices. When you choose to send heart rate, the shared session can include heart rate readings, their timing, your session display name, the maximum heart rate and baseline parameters used for that session, and shared moment markers and their notes. Your age, private tags, and unused personal reference values are not sent to your partner. A calculated maximum heart rate may still reveal something about the settings used to calculate it.

Your partner can save received information and synchronize the shared recording to their own linked phone. A receive-only participant does not start their own heart rate recording for that session. Sharing is designed for nearby participants, not remote monitoring.

Ending a shared session stops new recording for that session; information recorded before its end and necessary control messages may still synchronize afterward. It does not recall information already received. Removing a local record does not delete a partner's copy or your other device's copy. Shared marker edits and deletions reach other devices only when synchronization succeeds. Pair and share only with people you trust, and obtain the wearer's agreement before using another person's information.

4. Images you save or share

PulsePlay can create a PNG image from a saved recording. The image omits names, calendar dates, private tags, and note text, but can contain heart rate curves, duration, peaks, and selected moment markers. Review the preview and sharing options before exporting. Removing names does not guarantee that an image cannot be associated with you or your partner from its contents or context.

Saving places an image in your device's media library. Sharing creates a cached image and gives the app you select temporary read access through Android's system share interface. That app or its recipients may retain, upload, or redistribute the image under their own practices. PulsePlay does not track the sharing destination or confirm that a social post was published. Deleting the recording does not delete exported images or copies held by recipients.

5. Permissions and background activity

PulsePlay requests heart rate or body sensor permission on the watch to record heart rate, Bluetooth permissions for nearby discovery and connection, and notification permission where applicable for session information and controls. Nearby scanning is used to connect devices, not to determine your location. PulsePlay does not request location, contacts, microphone, or camera access.

An active watch session can keep recording through a foreground service while the screen is off or you leave the page. Closing an ordinary page or pausing sound and vibration does not end recording. Use the session's end control to stop it. You can review or revoke permissions in Android or Wear OS settings; revoking required permissions can prevent or interrupt a feature. Permission changes do not automatically delete previously saved data.

6. Storage, retention, and deletion

Recordings and settings are stored in each app's local storage. PulsePlay disables Android's automatic app backup for its app data. Images saved to your media library may separately be backed up by a photo service you enable. There is no PulsePlay cloud recording archive from which we can restore a lost record.

Saved recordings remain until you delete them on that device or remove the app's local data. Use the history and record controls to delete a saved record; private tags can also be managed locally. A local deletion does not end an active session, remove another device's copy, or reset trial or purchase access. PulsePlay retains deletion status and the technical, trial, purchase, and session-control information needed to prevent deleted records from reappearing, maintain access, and complete necessary end notifications. Necessary end notifications do not contain the deleted record's heart rate readings or notes.

Deleting a moment marker is a logical deletion used for synchronization; it is not a promise to immediately erase every underlying copy or revision. Clearing app storage or uninstalling removes that installation's local app data, but does not remove data on other devices, Google Play transaction records, or exported images. Stop active sessions first and review each device separately. PulsePlay cannot remotely access or delete recordings held only on your or your partner's devices.

Cached sharing images can remain until app cache is cleared or later cleanup runs. PulsePlay attempts to remove sharing images older than one day when another sharing image is created; this is not a guaranteed deletion timer. Support correspondence is retained only as needed to handle the request and meet applicable recordkeeping obligations. You may contact us about correspondence you have sent.

7. Platform services and security

PulsePlay uses Wear OS Health Services, Google Play services for communication between your own devices, and Google Play Billing for purchases. Google may process information under its own Privacy Policy. A Google Play purchase can require a Google account even though PulsePlay itself has no account system. We do not receive your heart rate recordings through the purchase flow. Your operating system, device provider, and any app you choose for sharing may have their own data practices.

PulsePlay uses Android app storage protections and authenticated, encrypted communication for its direct partner connection. These measures do not guarantee absolute security or prevent a recipient from keeping or sharing data they receive. Protect your devices and review pairing requests before confirming them.

8. Choices, questions, and updates

You can choose whether to enter optional profile information, start a recording, share with a partner, export an image, or grant permissions. You can edit available profile settings and manage saved records within the app. Contact us with privacy questions or requests concerning information you have sent to us. Any rights available to you under applicable privacy law remain unaffected; the information we can act on depends on what we actually hold.

We may update this policy as the app or its data practices change. The current version will show its last updated date. Where required, material changes will be disclosed and any required permission or consent obtained before the changed processing begins.

Privacy contact: [email protected]

See also the PulsePlay Terms of Use.