# 7 Healthcare Automation Vendors Compared on Data Export, Residency and Retention

Certifications tell you a vendor has controls. None of them tells you where your data lives, how long it is kept, or how it comes back. Seven vendors checked against what they actually publish, and the six questions to send in writing.

**Category:** Listicles
**Written by:** Zain Qayyum
**Last updated:** Oct 27, 2026
**Source:** https://signals.medsender.com/listicles/healthcare-vendors-data-export-residency-retention

---

## TL;DR

- Almost nobody publishes this. Data residency, retention periods and export mechanics are routinely absent from vendor security pages across this category.

- That is the finding. It means these questions cannot be answered by comparison shopping and have to be asked directly, in writing, before signature.

- Certifications are not answers. HITRUST, SOC 2, FedRAMP and PCI tell you a vendor has controls. None of them tells you where your data lives or how it comes back.

- One vendor publishes a model training position. The other six say nothing either way.

- The useful test is whether a vendor will put residency, retention, export and subprocessors in writing during evaluation. Most will when asked. Few volunteer it.

- If the export would be unusable to the next vendor, you have a backup rather than an exit.

## The Three Questions an IT Review Actually Asks

Security questionnaires are long and most of their content is boilerplate. Three questions carry the weight, and they are the three this comparison is built on.

**Where does our data live.** Country, and increasingly which provider. This matters for organizations with state contracts, for anyone with a data residency clause elsewhere in their obligations, and for a security committee that will ask regardless.

**How long do you keep it, and what happens at the end.** Retention during the relationship, and deletion after it. A vendor with no published retention position has one, it is simply undocumented, and you will inherit whatever it is.

**How do we get it back, in what form.** This is the one that decides whether you are a customer or a hostage. It is also the one that is almost never published, because publishing it invites comparison.

A fourth sits behind all three and has become more pressing. **Who else touches it.** Subprocessors, and whether your data is used to train or tune models.

These are different from the questions covered when vetting a vendor's compliance posture generally, which is treated separately in this library. Business associate agreement mechanics, trust center contents, SOC 2 report types, audit trail requirements and encryption are all covered there. This article starts after all of that is satisfactory, at the point where someone asks what happens to the data itself.

## How These Vendors Were Compared

Seven vendors across document processing, patient texting and patient outreach, assessed only against what each publishes on its own public pages, read on October 26, 2026.

No vendor was asked, and nothing here comes from a sales conversation. That is deliberate. The question this article answers is what a practice can establish before contacting anybody, and the answer turns out to be very little.

"Not stated" means it is not published. It does not mean the vendor lacks a position, and in most cases they will have one and will share it on request. The gap between having a position and publishing it is the subject of this comparison.

Where a vendor publishes a certification only as a badge image rather than as a written claim, that is noted, because an image is not a statement.

## Data Export, Residency and Retention at a Glance

| Vendor | Data residency | Retention period | Export mechanics | Subprocessors | Model training position |
| --- | --- | --- | --- | --- | --- |
| Medsender | Published: "Hosted on Google Cloud with US-based servers" | Not published, acknowledged as covered in the security review | Not published, acknowledged as covered in the security review | Not named; BAA stated as enforced with every vendor and subprocessor | Not stated |
| Artera | Not stated | Not stated | Not stated | Not stated | Published: "We do not use identifiable PHI/PII to train our models" |
| Documo | Not stated; HITRUST e1 badge references Google Cloud Platform | Not stated | Not stated | Not stated | Not stated |
| WestFax | Not stated | Not stated | Not stated | Not stated | Not stated |
| OhMD | Not stated | Not stated | Not stated | Not stated | Not stated |
| Spruce Health | Not stated | Not stated | Not stated | Not stated | Not stated |
| Phreesia | Not stated | Not stated | Not stated | Not stated | Not stated |

Five of seven publish nothing on any of the five columns. That is the comparison.

## The Vendors, One Section Each

### Medsender

The only vendor of the seven to publish data residency, and the only one to acknowledge export and retention as questions with answers.

**What is published.** Hosting is stated as "Hosted on Google Cloud with US-based servers", repeated in a deployment table as "Cloud, US-based servers". Encryption is stated as 256-bit SSL in transit and 2048-bit private key encryption at rest, with the page adding that documents are never stored or transmitted unencrypted. Access controls are stated as centralized user management, role-based permissions and inactivity timeouts, with sign-in through Microsoft SSO. An audit trail is stated to record every automated action. A BAA is included at no additional cost and is stated to be enforced with every vendor and subprocessor used.

**What is acknowledged but not published.** The page states that "Export options, retention settings, and offboarding steps are covered in the security review." It also states that "Your practice's documents remain your practice's documents", which addresses ownership rather than mechanics.

**Assessment.** The strongest published position of the seven, and notable mainly for being honest about the boundary rather than silent past it. A vendor that names residency and then says the rest is covered in a security review has told you something useful: the questions have answers and there is a defined point at which you get them. Subprocessors are not named, which is the main gap, and the retention and export detail still has to be requested.

### Artera

Publishes the most certifications of the seven and almost nothing about data handling.

**What is published.** HIPAA Compliant, SOC 2 Type 2, HITRUST Certified and FedRAMP High appear as claims. A model training position is published and it is the only one in this comparison: "We do not use identifiable PHI/PII to train our models."

**What is not.** The security page states nothing about residency, retention, export or subprocessors. SOC 2 and HITRUST appear on that page only as badge images identified by filename, with the written claims appearing elsewhere. The page directs readers to a SafeBase trust center for detail, which is the right pattern and means the information likely exists behind a request.

**Assessment.** FedRAMP High is a serious credential and implies controls well beyond this list, which makes the absence of published residency detail more surprising rather than less. The training statement is genuinely useful and worth reading precisely: it covers identifiable PHI and personally identifiable information, which leaves de-identified and aggregated use unaddressed. That may be entirely acceptable. It should be a question you asked.

### Documo

Strong published security credentials, nothing published on data handling.

**What is published.** SOC 2 Type II, described on the security page as guaranteeing rigorous security protocols. HIPAA safeguards. A HITRUST e1 certification whose badge alt text references Documo residing at Google Cloud Platform, which is the closest thing to a residency statement but names a provider rather than a region. US-based support is stated, which describes staff rather than data location.

**What is not.** Residency as a region or country, retention, export, subprocessors, training. No BAA statement on the security page.

**Assessment.** The infrastructure reference is suggestive but it is not a residency commitment, and a buyer with a residency requirement should not treat it as one. The missing BAA statement is the more urgent gap for a healthcare buyer and should be the first question.

### WestFax

Publishes the clearest BAA language in this group and nothing on data handling.

**What is published.** "Fully HIPAA-compliant with executed BAAs", with the FAQ adding that WestFax runs in a HIPAA-secure environment and signs a BAA as standard for healthcare plans. SOC 2 described as Type II audited. Published per-page pricing, which is unrelated to this comparison but unusual enough to note.

**What is not.** Residency, retention, export, subprocessors, training.

**Assessment.** The BAA language is unambiguous and executed as standard is a better formulation than available on request. Everything in this article's subject matter is unpublished, so all four questions go into the evaluation.

### OhMD

The clearest published BAA terms of the seven, and nothing on data handling.

**What is published.** "Standard BAA included in all agreements. Custom BAA included in our Enterprise package." HIPAA and SOC 2 appear under a combined heading, with no audit detail.

**What is not.** Residency, retention, export, subprocessors, training.

**Assessment.** Distinguishing a standard BAA from a custom one by tier is more precise than most vendors manage and it tells a buyer something practical about what is negotiable. SOC 2 as a heading with no detail is thin. Everything in scope for this comparison is unpublished.

### Spruce Health

Publishes pricing and BAA terms, nothing on data handling.

**What is published.** "Every eligible Spruce organization automatically receives a HIPAA Business Associate Agreement (BAA)", included in every plan. HIPAA-compliant communications across phone, texting, faxing and telehealth. Published per-user pricing.

**What is not.** Residency, retention, export, subprocessors, training. SOC 2 appears only in logo image filenames, with no written claim.

**Assessment.** Automatic BAA inclusion for every eligible organization is the most frictionless arrangement in this list and removes a step that frequently delays small practice deployments. The word eligible is doing work and is worth asking about. SOC 2 should be treated as unverified until a written claim or report is provided.

### Phreesia

Strong certification set, nothing on data handling.

**What is published.** "HITRUST CSF, SOC 2 Type 2 and PCI Level 1 certified." Native integration with 16 or more practice management and EHR systems.

**What is not.** HIPAA is not stated on the page read, which is unusual given the certifications that are. No BAA. Residency, retention, export, subprocessors, training all unpublished.

**Assessment.** PCI Level 1 is relevant if the platform handles payment data and nobody else here publishes it. The absence of a HIPAA statement alongside HITRUST CSF is almost certainly an omission rather than a gap in posture, and it is exactly the kind of thing to confirm rather than assume.

## What No Vendor Publishes, and How to Ask For It

The pattern is consistent enough to be structural rather than accidental. Vendors publish certifications, because certifications are marketing assets. They do not publish residency, retention, export or subprocessors, because those are commitments.

That makes this a procurement exercise rather than a research exercise. Six questions, sent in writing during evaluation, produce in a week what no amount of reading produces.

Where is our data stored and processed, by country and by provider, and will that be stated in the agreement.

How long is our data retained during the relationship, and how long after termination.

What exactly does an export contain. Ask in three parts: the documents themselves, the structured data extracted from them, and the audit record of what happened to them. A yes to the first is often delivered as a yes to the question.

In what format, how is it initiated, is it self-service, and is there a fee.

Who are your subprocessors, and will you notify us when that list changes.

Is our data used to train, tune or evaluate models, in identified, de-identified or aggregated form, and does any of it leave our instance.

Two notes on how to read the responses. A vendor that answers in mechanics is describing something that exists. A vendor that answers in principles has usually not been asked before. And ask the same question twice, once of the sales contact and once in writing of whoever owns security. Divergent answers mean the position has not been settled internally, and you will be the one who discovers where it lands.

## Deciding Whether a Vendor Clears Your IT Gate

Three tests, in increasing order of what they tell you.

**Will they put it in writing.** Residency, retention, export and subprocessors, in the agreement or an addendum. Most vendors will when asked. The ones that will not have told you something.

**Can you test the export while you are still a customer.** Self-service export is better than vendor-performed export for exactly one reason: you can run it in month two rather than discovering its shape in the final month. Run it early. The first time an export process runs properly should not be during an exit.

**Would the output be usable to a competitor.** This is the uncomfortable question and the one that separates a real exit path from a formality. Documents with system-generated names, no structured fields and no audit record satisfy an export clause and leave you starting over. If what comes back could not be loaded into another system without months of work, the clause is satisfied and the exit is not real.

None of these require an adversarial conversation, and raising them during evaluation is ordinary diligence rather than distrust. How a vendor responds is itself one of the more informative things you will learn about them, regardless of what the answers turn out to be.

One final point about this comparison. Five of seven vendors publish nothing on any of these five dimensions, which means this is not a field where one vendor is hiding something the others disclose. It is a field where almost nobody discloses, the questions are legitimate, and the practices that ask them get answers. The ones that do not ask inherit whatever the defaults were.
