Skip to content

App Store and Privacy

Eric Slutz edited this page Aug 6, 2026 · 9 revisions

App Store and Privacy

PumpSync's App Store and legal assets live in the iOS repository. Backend privacy and operational retention behavior is documented in the backend repository and summarized here.

App Store Evidence

Current App Store evidence lives in PumpSync/docs/app-store/:

  • pumpsync-subscription-review.jpg: current subscription review image for the PumpSync auto-renewable subscription in App Store Connect.
  • hosted-services-subscription-image.png: earlier hosted-service subscription image retained for reference.
  • accessibility.md: App Store accessibility label answers, common task matrix, and manual validation checklist for iPhone and iPad.

StoreKit Routing

Purpose Scheme Configuration StoreKit environment Hosted environment
Local Xcode install PumpSync Debug Sandbox Nonprod hosted API
TestFlight upload PumpSync Beta Beta archive Sandbox Nonprod hosted API
App Store release PumpSync Release archive Production Production hosted API

TestFlight and development-signed purchases use Apple's sandbox and do not charge real money. App Store release builds use the production App Store transaction environment.

Apple Capabilities

Keep HealthKit enabled for the app. StoreKit access comes from enabling the In-App Purchase capability in Apple Developer and App Store Connect; do not add an In-App Purchase entitlement key to PumpSync.entitlements.

Background task identifiers and UIBackgroundModes=processing are app configuration values in project.yml, not separate Apple entitlement keys to add for StoreKit.

Privacy Model

The Privacy Policy on the website is the canonical statement of what PumpSync handles, stores, retains, and deletes. Do not restate it here — this section covers implementation details only.

  • Credentials are held in the iOS Keychain with device-only accessibility; they are never written to backend durable storage.
  • Credential transmission is scoped to a single in-flight HTTPS sync request, whether the sync was started manually, on app open, or by the daily background task.
  • Duplicate prevention uses a local rolling HMAC external-ID ledger keyed on the sample external ID.
  • Keychain items are not synced through iCloud in v1, so each device is configured separately.

Backend Storage

The website's Backend storage section is the canonical inventory of what the hosted backend keeps. Self-host SQLite stores the same operational state in the configured self-host database.

For the full backend security model — rate limits, forwarded-header trust, transport posture, and retention — see the backend repo's docs/security-and-privacy.md.

Account and Data Deletion

Use the public website for user-facing privacy and deletion instructions:

Implementation references:

Medical Disclaimer

The medical disclaimer is published on the website and rendered on every page there. See the Privacy Policy and Terms of Use; do not maintain a copy of that wording here.

Clone this wiki locally