1. Subprocessors
The following vendors process Customer Data on Remote Home Check's behalf in connection with providing the Services. RHC maintains DPAs with Subprocessors and, where PHI is transmitted to a Subprocessor and a BAA is available, a BAA.
1.1 PHI / Consumer Health Data Subprocessors
| Vendor | Service | Data Categories |
|---|---|---|
| Google Cloud | Hosting, storage, logs | Customer Data, health signals, platform logs |
| Snowflake Not active at launch | Data warehouse, analytics | Aggregated health data, analytics |
| Twilio | SMS/voice communications | Alert metadata (no PHI in message content) |
| ElevenLabs Not active at launch | AI voice services | Voice interaction content (no PHI in voice) |
1.2 Operational Subprocessors (Scope-Dependent)
| Vendor | Service | Data Categories |
|---|---|---|
| Tekumo Pro | Installation services | Names, addresses, device assignments |
| TechRescue | Support / escalation | Support tickets, event details |
| T-Mobile | Connectivity / carrier | PII, telecom metadata |
| Stripe | Payment processing | Billing data, payment methods |
1.3 Conditional Subprocessor
| Vendor | Service | Activation Condition |
|---|---|---|
| Clear Partners, LLC Conditional | UL-certified central station monitoring | Active only when Monitoring Center Addendum (Exhibit G) is executed |
2. Third-Party Services & Integrations
The following are third-party device and platform providers whose products are integrated with or enabled by Customer through the Services. These providers are not Subprocessors. Customer's use of each service is governed by that provider's own terms.
| Provider | Integration | Governed By |
|---|---|---|
| Apple (Watch / HealthKit) | Health metrics, movement, cardiac data | Apple Terms of Service; Apple Health privacy policy |
| HERO Health | Medication dispenser ecosystem | HERO Health Terms of Service |
| YoLink | Sensor and cloud integration | YoLink Terms of Service |
| Family1st | Driving monitoring (B2C only) | Family1st Terms of Service |
3. Non-Subprocessors (Self-Hosted Software)
The following are software tools deployed within RHC's own infrastructure. They are not third-party data processors and do not transmit Customer Data to external parties: Apache Pulsar (message streaming), Terraform (infrastructure management), Go (programming language).
4. Change Notification Process
RHC will provide at least thirty (30) days' advance notice before adding a new Subprocessor that processes Customer Data. Customers may raise objections within thirty (30) days of notice. If an objection cannot be resolved through good-faith discussion, the affected Customer may terminate the relevant portion of Services without penalty.
5. BAA / DPA Status
RHC maintains Data Processing Agreements (DPAs) with Subprocessors and, where PHI is transmitted and a BAA is available, a Business Associate Agreement (BAA). BAA/DPA status for each Subprocessor is maintained as an internal compliance record and is available for review during authorized audits.