Solution · Data residency

Keep your iPhones under your control — and know where the data goes

With HelmSwarm's Your Own Device package, the iPhones stay physically on your premises, attached to your own Mac running the HelmSwarm agent, which only makes outbound encrypted connections. Control traffic — screen frames, commands and results — is relayed through HelmSwarm's servers, and the hosted panel stores scenarios, run results and screenshots. Here is exactly what goes where.

What goes where

Location of devices and data with the hosted HelmSwarm panel
ItemYour Own DeviceRental iPhone (± eSIM)
The iPhone itselfOn your premises, attached to your MacHosted by HelmSwarm
Apps and data on the iPhoneOn the device, on your premisesOn the device, hosted by HelmSwarm
Live screen frames and commandsRelayed through HelmSwarm's servers to your browser, encrypted in transitRelayed through HelmSwarm's servers to your browser, encrypted in transit
Scenarios, run results, screenshots, recordingsStored by the HelmSwarm panelStored by the HelmSwarm panel
Secrets used in scenariosEncrypted vault in the panelEncrypted vault in the panel
App builds installed from the panelPass through HelmSwarm to the devicePass through HelmSwarm to the device

Patterns for data-sensitive teams

Keep devices on-site

Use the Your Own Device package: the iPhones, their apps and their local data stay in your building. The agent only dials out, so your firewall doesn't need inbound rules.

Use test data, not production data

Point the app under test at a staging backend with synthetic accounts. Keep test credentials in the encrypted vault and reference them by name, so they don't appear in scenarios or exports.

Install sensitive builds yourself

If a build must not leave your network, install it on your own devices with your existing tooling, and use HelmSwarm for control, automation and reporting.

Need the panel in your own environment?

Standard plans use the hosted panel. A self-hosted deployment is available on the Enterprise plan — contact sales with your requirements and we'll tell you honestly whether it fits.

Who this is for

Fintech, health, public-sector and EU or Türkiye-based teams working under GDPR or KVKK, and anyone whose security review asks where devices, builds and screenshots end up. Compliance is a legal determination for your whole setup; this page describes HelmSwarm's part of it.

Data residency questions

Does my test data leave my network with HelmSwarm?

Yes, some of it. With your own devices, the iPhones stay physically on your premises, attached to your own Mac. Screen frames, commands and their results are relayed through HelmSwarm's servers over an encrypted connection so you can use the devices in the browser, and scenarios, run results, screenshots and recordings are stored by HelmSwarm.

Do I have to upload my app build to HelmSwarm?

Builds installed through the panel pass through HelmSwarm on their way to the device. If your builds must not leave your network, install them on your own devices with your existing tooling and use HelmSwarm for control and automation.

Can HelmSwarm be self-hosted?

Only on the Enterprise plan. Standard plans use the hosted (cloud) panel described on this page. A self-hosted deployment is available on Enterprise — contact sales with your requirements.

Is HelmSwarm GDPR or KVKK compliant?

Our Privacy Policy explains how HelmSwarm processes personal data under GDPR and KVKK where they apply. Whether your overall test setup is compliant depends on your data and configuration — this page is guidance, not legal advice.

Your devices. Clear answers.

Tell us what may and may not leave your network, and we'll tell you honestly whether HelmSwarm fits.