Is signNow HIPAA compliant?
Yes, on signNow's corporate plans once you have asked support to sign the business associate agreement: HIPAA features are off by default on every account until that happens.
Applies to signNow. Last reviewed .
Researched and maintained by the CompyMax editorial team to our published standards.
What you must do
- Be on a corporate plan. signNow's own guide states HIPAA compliance 'is only available on SignNow's corporate plans', though it never names the tiers: get the specific plan confirmed in writing when you sign.
- Contact airSlate SignNow support to request and execute the agreement. Their wording: 'HIPAA compliance is disabled by default for your airSlate SignNow account. To enable it, please contact airSlate SignNow support to sign a BAA.'
- Wait for activation. HIPAA-compliant features are switched on by the vendor after the agreement is signed: the sequence is agreement first, features second, patient documents last.
- Keep the executed copy; the published pages describe the process but are not themselves the agreement.
Does signNow sign a business associate agreement?
Yes. airSlate offers one. A corporate plan: signNow does not publicly name which tiers qualify. Contact airSlate SignNow support (or sales) to sign the agreement; the vendor then activates HIPAA features on the account.
What this means in practice
signNow's mechanic is worth understanding because it protects you from a half-configured state: HIPAA compliance is disabled by default on every account, and only the vendor switches it on, after the agreement is signed. There is no toggle to find in settings. That means an account sending patient consent forms before support has confirmed activation is simply not covered, whatever plan it is on.
The plan language is the vaguest part. signNow says HIPAA compliance is available only on its corporate plans and never names the tiers, so the tier question belongs in the same conversation as the agreement, in writing, before purchase. Do not infer eligibility from a plan's price or its name.
Feature-level scope is unpublished too. Nothing signNow posts says whether any features are excluded under the executed agreement, which cuts both ways: no known carve-outs, and no public promise either. The executed agreement is the only document that defines it, so read it rather than the marketing page.
How organizations get this wrong
- Sending patient documents after signing the agreement but before signNow confirms HIPAA features are activated on the account: the sequence is agreement, activation, then patients.
- Buying a plan because it sounds corporate, when signNow never publicly names which tiers qualify.
- Assuming the airSlate document-automation products around signNow are covered by the same agreement without asking.
- Treating the marketing page's security certifications as the agreement, which the off-by-default mechanic makes exactly wrong.
What the agreement does not cover
- Every account in its default state: signNow is explicit that HIPAA compliance is disabled until the agreement is signed and the vendor activates it.
- Non-corporate plans, whatever their price.
- Scope beyond that is unpublished: no signNow page fetched for this entry lists feature-level exclusions, so settle them in the agreement itself.
Alternatives
Where you want the plan requirement and covered features stated publicly
The incumbent most healthcare counterparties already have an account with
If documents need proposals and payment collection alongside the signature
Keep a record of your signNow agreement
Sources
- HIPAA Compliance | airSlate SignNow: airSlate. Read August 30, 2026.
- How to Achieve HIPAA Compliance with SignNow eSignature: airSlate. Read August 30, 2026.
airSlate can change these terms at any time. If something here no longer matches what airSlate tells you, tell us.