Privacy Policy

The Pulse Commit app has no developer-operated server for Health data. The developer does not receive or see your Health exports. This website separately stores launch waitlist signups as described below.

1.What the app collects

The app reads selected Apple Health data on your device and writes it directly to destinations you configure. It has no developer Health-data backend, analytics, telemetry, crash reporter or advertising SDK.

2.Where your data goes

Before a Health export, Pulse Commit requires separate affirmative consent for each exact destination. The disclosure identifies your selected Health categories and the GitHub repository, branch and subdirectory or the Telegram chat and topic. A changed destination, category set or disclosure version requires consent again.

GitHub exports contain summary.json, summary.md, raw samples/*.json, workout JSON and route files when available. Repository collaborators and organization readers can access them; if the repository is public, anyone can. GitHub retains commits under the repository and account settings.

Telegram exports contain a Markdown summary and ZIP attachment. Chat members, bot operators and Telegram may process and retain them. An AI service may also process a message only when you chose an AI-backed bot or chat. Pulse Commit itself has no AI integration.

Only to destinations you set up yourself:

• The GitHub repository you connect (via api.github.com and the GitHub Device Flow endpoints https://github.com/login/device/code and https://github.com/login/oauth/access_token).
• The Telegram chat you connect (via api.telegram.org).

The app's direct export and GitHub authorization requests use these hosts:

• api.github.com
• github.com (Device Flow only)
• api.telegram.org

The website uses Cloudflare services for hosting, waitlist storage and abuse protection; these are separate from the app's Health export requests.

3.How to revoke

Disable or disconnect a destination to stop future exports to it and clear its local consent receipt. Replacing the Telegram bot token, or changing the repo, branch, subdirectory, chat, topic or selected categories, requires new consent before another export.

• In Pulse Commit, open Destinations → GitHub and sign out. This deletes the OAuth token from the iOS Keychain.
• In Telegram, talk to @BotFather and revoke (or delete) the bot you created. Then open Destinations → Telegram in Pulse Commit and clear the bot token field.
• In iOS Settings → Privacy & Security → Health → Pulse Commit, turn off any category you no longer want the app to read.

4.How to delete data

Reset all data removes local preferences, tokens, history, cursor and consent receipts. It cannot delete remote copies. Delete commits and files in GitHub, and delete Telegram messages or contact the bot operator where applicable. The developer holds no copy of your Health exports.

• To delete what was exported: delete the GitHub repository (or specific commits) and delete the Telegram chat history.
• To delete local state: open Pulse Commit → Settings → Reset all data. This wipes the history database, the export cursor, and the Keychain tokens on this device. It does not touch your GitHub repo or Telegram chat.

5.Third-party services we depend on

• Apple — HealthKit (data source), App Store (distribution and payment).
• GitHub — the repository you choose to commit to. Their privacy policy applies to your repo.
• Telegram — the chat you choose to send messages to. Their privacy policy applies to that chat.

The app embeds one open-source library: ZIPFoundation (MIT). It runs on-device only and makes no network calls.

6.No advertising / no data brokers / no analytics

The app contains no advertising SDKs, no data broker integrations, and no analytics. There is no event log to share, sell, or hand over.

7.HealthKit-specific notice

In accordance with Apple App Review Guideline 5.1.3, Pulse Commit does not use HealthKit data for advertising or for any purpose other than the export you explicitly trigger. HealthKit data is never transmitted to the developer. It is written only to the destinations you configure and authorize.

8.This website and the waitlist

If you submit the waitlist form on pulsecommit.app, our Cloudflare D1 database stores the email address you enter, a server-generated signup timestamp and your country derived by Cloudflare from the request (when available). We use this record to notify you when Pulse Commit launches.

• Email hi@pulsecommit.app to request deletion of your waitlist record.
• Cloudflare Turnstile checks form submissions for abuse before we store a signup.
• The site is hosted on Cloudflare. Cloudflare processes standard request data (such as IP address and user-agent) to serve and protect the site, and provides traffic metrics such as request and visitor counts. This site adds no separate client-side analytics or tracking script.

9.Contact

Questions or deletion requests: hi@pulsecommit.app.