Subprocessors
The service providers that process data for Arxova
16 subprocessors
AWS
Cloud Infrastructure
United StatesProvides cloud infrastructure supporting Arxova's cryptographic signing operations for blockchain audit receipts. Signing requests contain digital fingerprints rather than underlying medical records. Arxova maintains an applicable Business Associate Agreement with AWS.
Vendor-reported attestations
- SOC 1
- SOC 2
- SOC 3
- ISO 27001
- HIPAA BAA
- PCI DSS
- FedRAMP
Anthropic
AI & Machines
United StatesProvides ARIA and other optional AI-powered features, including health summaries, insights, document interpretation, and background guidance. Depending on the feature, receives minimized health information, user-entered text, or uploaded documents and images that may contain personal identifiers. Processing requires the user's AI consent. Anthropic's commercial AI services are covered by Arxova's applicable Business Associate Agreement.
Vendor-reported attestations
- SOC 2 Type 2
- ISO 27001
- ISO 42001
- CSA Star
- HIPAA
- NIST 800-171
Apple Push Notification service (Apple Inc.)
Push notifications (iOS)
United StatesDelivers iOS push notifications. Receives device push tokens and notification payloads. Arxova's server-generated notifications are designed not to include specific health readings, medications, diagnoses, or clinic or study names.
Vendor-reported attestations
- ISO 27001
- ISO 27018
Beehiiv
email / newsletter
United StatesProvides Arxova's email newsletter service. Receives subscriber email addresses and newsletter engagement information, such as opens and clicks. The newsletter is separate from the Arxova health application and is not intentionally supplied with health records.
Vendor-reported attestations
- SOC 2 Type II
- GDPR
- CCPA
Expo (650 Industries)
App updates and push notification relay
United StatesProvides over-the-air application updates and relays mobile push notifications to Apple and Google. May receive device information, application version information, push tokens, and notification text. Server-generated notifications are designed not to include health readings, medication names, condition names, or clinic or study names.
Vendor-reported attestations
- SOC 2 Type II (Security criterion)
- EU-US DPF
Fasten Health
health records integration
United StatesFasten Health facilitates patient-directed connections to healthcare providers and electronic health record systems through FHIR-based and other supported interoperability methods. When authorized by a user, Fasten processes the information necessary to establish the connection, retrieve the user's medical records, and securely transmit those records to Arxova. These connections are initiated and authorized by the user to support access to their own health information.
Vendor-reported attestations
- SOC 2 Type 1
- SOC 2 Type 2
- HIPAA Compliant
- DiMe Seal
- CARIN-Trust-Framework
Fly.io
Cloud hosting
United StatesHosts Arxova's application servers and databases, including systems that store and process personal information and health records. Processing is governed by Arxova's infrastructure configurations, access controls, encryption safeguards, and applicable Business Associate Agreement.
Vendor-reported attestations
- SOC 2 Type 2
- HIPAA BAA
Google Firebase Cloud Messaging
Push notifications (Android)
United StatesDelivers Android push notifications. Receives device registration tokens and notification payloads. Arxova's server-generated notifications are designed not to include specific health readings, medications, diagnoses, or clinic or study names.
Vendor-reported attestations
- ISO 27001
- ISO 27017
- ISO 27018
- SOC 1
- SOC 2
- SOC 3
Google Workspace
Business productivity
United StatesProvides business email, documents, and internal collaboration services. Arxova does not intentionally use Google Workspace to store or process patient medical records. Business communications may include personal or professional contact information.
Helius
Blockchain API / RPC infrastructure
Location not statedProvides blockchain API infrastructure used to submit or retrieve Solana audit transactions. May process transaction information and technical request metadata. Current audit receipts use random references and generic event names; historical receipts may expose wallet-linked health-related event types. No individually negotiated agreement is asserted.
Irys / Bundlr
Decentralized storage upload infrastructure
Location not statedProvides infrastructure used to upload encrypted health records to the Arweave permanent storage network. May process encrypted record payloads and associated transaction metadata. Historical uploads before October 1, 2026 may include public wallet-linked record-type labels. No individually negotiated agreement is asserted.
PostHog
Product analytics
United StatesProvides product analytics for Arxova's application and website. Receives pseudonymous feature-use events that may reveal health-related interests. App analytics can be disabled in Settings, although this does not stop all server-side events.
Vendor-reported attestations
- SOC 2 Type II
- EU-US Data Privacy Framework
Privy (a Stripe company)
Authentication and embedded wallet
United StatesSupports user authentication, account-associated Solana wallets, and authorized wallet-signing operations. May process email addresses, authentication identifiers, wallet addresses, and signing requests. Arxova does not intentionally send medical records or health measurements to Privy.
Vendor-reported attestations
- SOC 2 Type II
Twilio
SMS and messaging
United StatesProvides SMS and WhatsApp delivery for Arxova Circle communications. May receive contact telephone numbers, the user's first name, message content describing health or well-being, and replies. SMS is used for United States and Canadian numbers; WhatsApp is used for supported international numbers.
Vendor-reported attestations
- SOC 2 Type I
- SOC 2 Type II
- ISO 27001
- ISO 27017
- ISO 27018
- PCI DSS Level 1
- Binding Corporate Rules
- EU-US DPF
- HIPAA BAA available
Vercel
Web hosting
United StatesHosts Arxova's public website, web application, clinic console, and research portal. May process visitor IP addresses, technical request logs, and research-related consent or review information transmitted through hosted services. Arxova's web application sends medical records directly to its application servers rather than through Vercel.
Vendor-reported attestations
- SOC 2
- ISO 27001
- HIPAA BAA
- PCI DSS
Sinch
Fax
Location not statedFaxes a person's signed records request to the doctor's office when they tap "Send it for me", at their direction and to the number they confirm. Receives records that offices fax back to Arxova. The request includes the person's name, date of birth and what they are asking for. Faxed records are medical records. Arxova has a signed Business Associate Agreement with Sinch, and Sinch's "Don't save" settings are on, so it keeps no copy once a fax is delivered.
Vendor-reported attestations
- HIPAA
- SOC 2
- GDPR
Not subprocessors
Decentralized networks
Arweave and Solana are public decentralized networks, not subprocessors. How Arxova uses them, and what that means for permanence, is described under Security practices.
Data sources you connect
Apple Health · Health data on your iPhone, connected by the user
Connects through iPhone's own Health permission screen when a user chooses to connect it. The Arxova app reads only the data types the user allows, on the phone, and sends that data to Arxova. Apple does not send data to Arxova.
Health Connect (Android, including Samsung Health) · Health data on your Android phone, connected by the user
Connects through Android's own Health Connect permission screen when a user chooses to connect it. Apps such as Samsung Health share data through Health Connect. The Arxova app reads only the data types the user allows, on the phone, and sends that data to Arxova. Google and Samsung do not send data to Arxova.
Garmin · Wearable data, connected by the user
Connects through Garmin's own sign-in and authorization page when a user chooses to connect it. Garmin sends the data the user authorizes directly to Arxova.
Oura · Wearable data, connected by the user
Connects through Oura's own sign-in and authorization page when a user chooses to connect it. Arxova receives the data the user authorizes directly from Oura.
WHOOP · Wearable data, connected by the user
Connects through WHOOP's own sign-in and authorization page when a user chooses to connect it. Arxova receives the data the user authorizes directly from WHOOP.
Withings · Health device data (scales, blood pressure, sleep), connected by the user
Connects through Withings's own sign-in and authorization page when a user chooses to connect it. Arxova receives the data the user authorizes directly from Withings.
Polar · Wearable data, connected by the user
Connects through Polar's own sign-in and authorization page when a user chooses to connect it. Arxova receives the data the user authorizes directly from Polar.
Strava · Activity data, connected by the user
Connects through Strava's own sign-in and authorization page when a user chooses to connect it. Arxova receives the data the user authorizes directly from Strava.
Sensor Bio · Wearable data, from devices provided in a study
Used when a participant receives a Sensor Bio device through a study Arxova takes part in. The device is registered to Arxova's Sensor Bio account and linked to the participant's Arxova account when they enroll, and Arxova receives that device's data directly from Sensor Bio. Participants do not connect a personal Sensor Bio account.