SaaS Ranking
Menu

Q2

q2.com · Lending and mortgage software · checked 2026-09-05

30/100EBand E

Rank 7 of 32 in Lending and mortgage software, where the median is 13.5.

We measured 12 of 12 criteria for Q2 on 2026-09-05. We found 4 with a source and did not find 8 at the addresses we checked. That is a transparency score of 30 out of 100, band E.

Overview

Transparency labelsaas-ranking.com

Q2

q2.com · Lending and mortgage software

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
E 30of 100 Rank 7 of 32

Published commitments2 of 9 found

Measured behaviour2 of 3 found

Checked 2026-09-05. Every line links the page we found it on. A cross means we found nothing at the addresses we checked, not that the vendor has no such document. A transparency score, not a product rating.

The evidence pack carries every criterion with its source, the addresses we checked, the date and the data snapshot id – the four things a procurement file needs and a screenshot loses. We do not issue badges: a badge is the first step towards a paid placement, and there is none here.

The label is the whole measurement in one object: every criterion with its weight, the band, and the date. Public transparency score, not a product or security rating.

Every line in it links the page we found the result on, or lists the addresses we checked. A cross means we found nothing there, not that Q2 has no such document.

What they state

The exact figures and names we read off the pages linked below, with the sentence they stand in. This is what they publish, not what we verified about their systems.

Gaps, heaviest first

✗

Data processing agreement

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-05.

Show the 8 addresses we checked
  1. https://q2.com/legal/dpa – reached, no match (HTTP 404)
  2. https://q2.com/dpa – reached, no match (HTTP 404)
  3. https://q2.com/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://q2.com/data-processing-agreement – reached, no match (HTTP 404)
  5. https://q2.com/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://q2.com/legal/gdpr – reached, no match (HTTP 404)
  7. https://q2.com/trust/dpa – reached, no match (HTTP 404)
  8. https://q2.com/privacy/dpa – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Subprocessor list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-09-05.

Show the 7 addresses we checked
  1. https://q2.com/legal/subprocessors – reached, no match (HTTP 404)
  2. https://q2.com/subprocessors – reached, no match (HTTP 404)
  3. https://q2.com/sub-processors – reached, no match (HTTP 404)
  4. https://q2.com/legal/sub-processors – reached, no match (HTTP 404)
  5. https://q2.com/trust/subprocessors – reached, no match (HTTP 404)
  6. https://q2.com/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://q2.com/legal/subprocessor-list – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Status page with history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-09-05.

Show the 3 addresses we checked
  1. https://status.q2.com/ – The name "status.q2.com" could not be resolved.
  2. https://q2.com/status – reached, no match (HTTP 404)
  3. https://q2.com.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

✗

Public pricing

weight 2 of 3

No public pricing with figures found.

Checked 5 addresses on 2026-09-05.

Show the 5 addresses we checked
  1. https://q2.com/pricing – reached, no match (HTTP 404)
  2. https://q2.com/pricing/ – reached, no match (HTTP 404)
  3. https://q2.com/plans – reached, no match (HTTP 404)
  4. https://q2.com/en/pricing – reached, no match (HTTP 404)
  5. https://q2.com/pricing-plans – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

No third-party tracking before consent

weight 2 of 3

No consent-free first load found.

Checked 1 address on 2026-09-05.

Show the 1 address we checked
  1. https://q2.com/ – third-party requests before any interaction: app.hubspot.com, browser.sentry-cdn.com, cdn.cookielaw.org, distillery.wistia.com, embed-cloudfront.wistia.com, fast.wistia.com, fast.wistia.net, fonts.googleapis.com, fonts.gstatic.com, geolocation.onetrust.com, js.hs-analytics.net, js.hs-banner.com, js.hubspot.com, pipedream.wistia.com, www.googletagmanager.com

Is this wrong? Send us the URL

✗

Notice before subprocessors change

weight 2 of 3

No commitment to give notice before subprocessors change found.

Checked 8 addresses on 2026-09-05.

Show the 8 addresses we checked
  1. https://q2.com/legal/subprocessors – reached, no match (HTTP 404)
  2. https://q2.com/subprocessors – reached, no match (HTTP 404)
  3. https://q2.com/sub-processors – reached, no match (HTTP 404)
  4. https://q2.com/legal/dpa – reached, no match (HTTP 404)
  5. https://q2.com/dpa – reached, no match (HTTP 404)
  6. https://q2.com/legal/data-processing-agreement – reached, no match (HTTP 404)
  7. https://q2.com/trust/subprocessors – reached, no match (HTTP 404)
  8. https://q2.com/legal/sub-processors – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Certifications named

weight 1 of 3

No named certification found.

Checked 6 addresses on 2026-09-05.

Show the 6 addresses we checked
  1. https://q2.com/security – reached, no match (HTTP 404)
  2. https://q2.com/trust – reached, no match (HTTP 404)
  3. https://q2.com/trust-center – reached, no match (HTTP 404)
  4. https://q2.com/compliance – reached, no match (HTTP 404)
  5. https://q2.com/legal/security – reached, no match (HTTP 404)
  6. https://trust.q2.com/ – The name "trust.q2.com" could not be resolved.

Is this wrong? Send us the URL

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-09-05.

Show the 6 addresses we checked
  1. https://q2.com/legal/sla – reached, no match (HTTP 404)
  2. https://q2.com/sla – reached, no match (HTTP 404)
  3. https://q2.com/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://q2.com/trust/sla – reached, no match (HTTP 404)
  5. https://q2.com/uptime – reached, no match (HTTP 404)
  6. https://q2.com/legal/uptime-sla – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Evidence

The full source lists sit behind these two groups, so that the answer above stays readable.

Published, with a source 4
✓

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

  • Locations named next to the hosting wording European Union, United States.
    Show the 2 exact wordings

    r of Information Q2 engages third party service providers which host our customer data and maintain servers and systems in the United States. Our European Union affiliates and customers may transfer p...

    Read at https://www.q2.com/privacy-policy

    r of Information Q2 engages third party service providers which host our customer data and maintain servers and systems in the United States.

    Read at https://www.q2.com/privacy-policy

Source: https://www.q2.com/privacy-policy · checked 2026-09-05

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

  • HSTS max-age 31536000 seconds (365 days).
    Show the exact wording

    max-age=31536000; includeSubDomains; preload

    Read at https://q2.com/
  • HSTS options includeSubDomains, preload.
    Show the 2 exact wordings

    max-age=31536000; includeSubDomains; preload

    Read at https://q2.com/

    max-age=31536000; includeSubDomains; preload

    Read at https://q2.com/

Source: https://q2.com/ · checked 2026-09-05

✓

security.txt (RFC 9116)

weight 1 of 3

Served at /.well-known/security.txt.

Source: https://security.q2.com/.well-known/security.txt · checked 2026-09-05

✓

Named privacy contact

weight 1 of 3

A data protection officer or a dedicated privacy address is named.

Source: https://www.q2.com/privacy-policy · checked 2026-09-05

History

Not enough completed runs yet to draw a line. The next runs fill this in.

Compare

A shortlist holds up to six vendors across categories and lives entirely in the address of its page: share the link, bookmark it, put it in a ticket. Nothing is stored, so we do not know it exists.