Use Capgo Cloud with EU endpoints
Route update, statistics, and channel requests through the EU host when your review allows hosted Capgo Cloud with regional data residency.
HIPAA-sensitive live updates
Capgo deployment paths for HIPAA review
Capgo helps teams keep live updates available while reducing or removing hosted telemetry paths that may not fit a HIPAA review. Use hosted Capgo Cloud with regional controls, disable statistics, self-host statistics, or move to a licensed self-hosted setup.
Default hosted data
Device-scoped telemetry, not user analytics
Capgo's updater telemetry is designed for update delivery and operational debugging. The hosted statistics payload is anonymous to the app user by default: no names, emails, credentials, user content, medical record numbers, or behavioral analytics are sent.
The only stable identifier is a random, app-scoped device_id. It is not tied to a known user unless your app
explicitly sets a custom_id. Hosted statistics can be fully disabled by setting statsUrl: ''.
app_id - Capacitor app identifier
device_id - random app-scoped device ID
platform - iOS, Android, or Electron
version_name - installed web bundle version
version_build and version_code - native app version
version_os and plugin_version
action - install, download, failure, rollback, app-ready events
is_emulator and is_prod when available
IP address for routing, abuse prevention, and CDN optimization
custom_id only if your app explicitly sets it
Do not set a custom ID for HIPAA-sensitive deployments.
setCustomId can connect updater telemetry to a user, patient, employee, or account record from your
own app. Leave it unset when the review requires device-scoped telemetry.
Need zero hosted statistics?
Set statsUrl: '' in the updater config. Capgo Cloud will stop receiving updater statistics; update
checks can still use updateUrl and channelUrl if you keep them enabled.
Control choices
Four paths for stricter review contexts
Start with the least operationally complex option your reviewer accepts. Move toward self-hosting only when hosted controls are not enough.
Disable hosted statistics
Set statsUrl to an empty string when your process allows Capgo Cloud for update delivery but not for device update statistics.
Self-host statistics
Send update statistics to your own endpoint so your team owns retention, alerting, and incident review data.
License self-hosting
Run the updater stack in your controlled environment when hosted paths are not enough for your reviewer or customer contract.
Telemetry tradeoff
What you lose if statistics stop going to Capgo
Disabling or redirecting statistics can be the right compliance decision, but it removes the hosted signal Capgo uses to explain what happened in the app after an update was checked, downloaded, installed, or rolled back.
- No Capgo failure alerts based on hosted statistics
- Less dashboard visibility into installs, failures, rollbacks, and app-ready events
- Less support context for explaining what happened inside the app after an update
- Your team must replace the missing monitoring if you still need those signals
When review needs more
We work with teams toward HIPAA compliance
Capgo works with companies going through HIPAA compliance review, including U.S. organizations that use Capgo in HIPAA-compliant programs. If the hosted service, EU data residency, disabled statistics, or self-hosted statistics endpoint is still not enough, we can help you self-host with a licensing model.
That path gives your organization control over infrastructure, logs, retention, network boundaries, and review evidence while keeping the Capgo update workflow.
Need security evidence first? Review the public trust center, then use the HIPAA technical docs to choose the deployment model for your app.