PulseSync · Privacy

Your information.
Your choices.

A clear account of what PulseSync stores, when information can leave your device, and how to manage access.

Effective November 16, 2026.

This policy covers the PulseSync iPhone and Apple Watch apps and support correspondence about PulseSync. It explains the optional export and Companion MCP paths. Services you separately choose have their own privacy policies. This is not a general privacy policy for every Velastrae Labs product.

Who provides PulseSync

PulseSync is provided by Lindsay Allen, operating as Velastrae Labs in Ontario, Canada. Contact velastraelabs@gmail.com for privacy questions or requests concerning information you sent to support.

Local use

PulseSync does not require a PulseSync account. Its core features keep app records and calculations locally on your device. These can include profile choices, condition and cycle context you choose to enter, emotions and intensity, energy or spoon check-ins, daily demands, hydration entries, cached Health information and derived observations.

The paired Watch and iPhone exchange information needed for companion features. Your device’s operating-system backup and security settings can affect copies of app data. PulseSync does not provide a separate private cloud backup service.

Apple Health permissions

With your permission, PulseSync reads relevant Apple Health information. Depending on availability and permissions, categories include heart rate, resting heart rate, heart-rate variability and heartbeat series, oxygen saturation, sleeping wrist temperature, respiratory rate, steps, activity and energy, exercise and stand time, workouts, sleep, mindful sessions and activity summaries. Menstrual-flow data is requested when cycle tracking is enabled.

You choose permissions through Apple’s controls and can change them later. Revoking permission stops permitted future access; it does not automatically erase previously cached records or copies already exported.

Optional on-device reflections

On supported devices, you can request a reflection using Apple Intelligence. PulseSync uses the on-device Foundation Models framework to select relevant evidence from local observations. This feature does not use a remote model service operated by PulseSync. Local tracking and insights remain available when the system model is unavailable.

Optional export

When you configure an export endpoint and token in Settings, the app sends supported Health samples and app check-ins to that endpoint, along with derived Body Reserve information, timestamps, source information and an installation identifier. Export can continue during updates after setup; it is not limited to a single transfer.

The reference endpoint runs in a Cloudflare account you control. Cloudflare processes information as your hosting provider. The endpoint operator controls its storage and credentials. We do not receive a copy through the reference architecture merely because you use PulseSync. If you configure someone else’s endpoint, that operator can receive the exported information.

Optional Companion MCP and personal AI

The public Companion MCP is separate software that lets compatible assistants read exported data using a separate read credential. Its tools do not write to the export database. A read credential can expose the records available to that endpoint; it is not a per-question or per-record consent control.

Your chosen assistant or AI provider may receive, process and retain information returned by its tools. Review that provider’s privacy practices and client permissions before connecting. Removing a connection or rotating a credential can prevent future access, but cannot remove information already returned to an assistant or copied by another service.

Advertising and tracking

PulseSync does not include advertising or cross-app tracking functionality. A separately chosen export endpoint or AI service may have different practices; consult that service’s policy before sharing information with it.

Support correspondence

If you email support, we receive your email address and the information you send through our email provider. Please avoid including health records or secrets. We use support messages to respond to your request. You can email us to request deletion of support correspondence.

We delete resolved support correspondence 90 days after the issue is resolved, unless it is needed for an ongoing issue or a legal requirement.

Managing access

You can change Health access in Apple’s controls and adjust tracking choices in PulseSync. To disable subsequent export attempts, clear the configured endpoint and token in Settings and save; verify the app reports export is off. An export already in progress may finish. Revoke or rotate the endpoint credential if you need to block further acceptance by the server. Manage or rotate credentials if a previously configured Watch or another client could still have access.

Local retention and deletion

The main check-in history keeps up to 1,000 entries, and insight history keeps up to 30 daily snapshots. Additional copies may remain in local sample caches or pending export batches. These history limits do not constitute deletion from every storage location. Imported Health sample caches are pruned using a rolling 180-day window when an import occurs. Other local records, including saved observations and preferences, may persist. These limits do not automatically apply to exported records or copies held by another service.

The current app has no general in-app delete-all control. Removing the app is distinct from offloading it; operating-system backups and independently exported records may remain. Deletion from your export database and chosen AI service must be handled in those services. Revoking access does not delete their existing copies. Contact support if you need help identifying which data locations to manage.

Changes to this policy

We will update this page and its effective date when PulseSync’s data practices change.