SaaS Ranking
Menu

Franchise Dynamics

franchisedynamics.net · Franchise management · checked 2026-09-03

Not enough data: 5 of 12 criteria measured, so no transparency score

We measured 5 of 12 criteria for Franchise Dynamics on 2026-09-03. We found 0 with a source and did not find 5 at the addresses we checked; 7 we could not measure at all. Below our threshold there is no score and no rank, and that is a statement about our measurement.

Overview

Transparency labelsaas-ranking.com

Franchise Dynamics

franchisedynamics.net · Franchise management

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
Not enough data5 of 12 measured, no score

Published commitments0 of 4 found, 5 not measured

Measured behaviour0 of 1 found, 2 not measured

Checked 2026-09-03. 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.

We do not issue badges: a badge is the first step towards a paid placement, and there is none here. The SVG is a document with the date in it, for your own files.

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. We could measure 5 of 12 criteria, which is below our threshold, so there is no rank. That is a statement about our measurement, not about Franchise Dynamics.

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 Franchise Dynamics has no such document.

Gaps, heaviest first

✗

HTTPS enforced with HSTS

weight 2 of 3

No enforced HTTPS with HSTS found.

Checked 2 addresses on 2026-09-03.

Show the 2 addresses we checked
  1. http://franchisedynamics.net/ – HTTP 200, no redirect to HTTPS
  2. https://franchisedynamics.net/ – no HSTS header

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-03.

Show the 8 addresses we checked
  1. https://franchisedynamics.net/legal/subprocessors – Could not be fetched: fetch failed.
  2. https://franchisedynamics.net/subprocessors – reached, no match (HTTP 200)
  3. https://franchisedynamics.net/sub-processors – reached, no match (HTTP 200)
  4. https://franchisedynamics.net/legal/dpa – reached, no match (HTTP 200)
  5. https://franchisedynamics.net/dpa – reached, no match (HTTP 200)
  6. https://franchisedynamics.net/legal/data-processing-agreement – reached, no match (HTTP 200)
  7. https://franchisedynamics.net/trust/subprocessors – reached, no match (HTTP 200)
  8. https://franchisedynamics.net/legal/sub-processors – reached, no match (HTTP 200)

Is this wrong? Send us the URL

✗

Certifications named

weight 1 of 3

No named certification found.

Checked 6 addresses on 2026-09-03.

Show the 6 addresses we checked
  1. https://franchisedynamics.net/security – No answer within 10 seconds.
  2. https://franchisedynamics.net/trust – reached, no match (HTTP 200)
  3. https://franchisedynamics.net/trust-center – reached, no match (HTTP 200)
  4. https://franchisedynamics.net/compliance – reached, no match (HTTP 200)
  5. https://franchisedynamics.net/legal/security – reached, no match (HTTP 200)
  6. https://trust.franchisedynamics.net/ – Could not be fetched: fetch failed.

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-03.

Show the 6 addresses we checked
  1. https://franchisedynamics.net/legal/sla – No answer within 10 seconds.
  2. https://franchisedynamics.net/sla – No answer within 10 seconds.
  3. https://franchisedynamics.net/legal/service-level-agreement – reached, no match (HTTP 200)
  4. https://franchisedynamics.net/trust/sla – reached, no match (HTTP 200)
  5. https://franchisedynamics.net/uptime – reached, no match (HTTP 200)
  6. https://franchisedynamics.net/legal/uptime-sla – reached, no match (HTTP 200)

Is this wrong? Send us the URL

✗

Named privacy contact

weight 1 of 3

No named privacy contact found.

Checked 7 addresses on 2026-09-03.

Show the 7 addresses we checked
  1. https://franchisedynamics.net/legal/privacy – reached, no match (HTTP 200)
  2. https://franchisedynamics.net/privacy – reached, no match (HTTP 200)
  3. https://franchisedynamics.net/privacy-policy – reached, no match (HTTP 200)
  4. https://franchisedynamics.net/legal/privacy-policy – reached, no match (HTTP 200)
  5. https://franchisedynamics.net/legal/privacy-notice – reached, no match (HTTP 200)
  6. https://franchisedynamics.net/trust/privacy – reached, no match (HTTP 200)
  7. https://franchisedynamics.net/datenschutz – reached, no match (HTTP 200)

Is this wrong? Send us the URL

Evidence

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

Not measured by us 7
–

Data processing agreement

weight 3 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 8 addresses we checked
  1. https://franchisedynamics.net/legal/dpa – No answer within 10 seconds.
  2. https://franchisedynamics.net/dpa – No answer within 10 seconds.
  3. https://franchisedynamics.net/legal/data-processing-agreement – No answer within 10 seconds.
  4. https://franchisedynamics.net/data-processing-agreement – No answer within 10 seconds.
  5. https://franchisedynamics.net/legal/data-processing-addendum – No answer within 10 seconds.
  6. https://franchisedynamics.net/legal/gdpr – No answer within 10 seconds.
  7. https://franchisedynamics.net/trust/dpa – Could not be fetched: fetch failed.
  8. https://franchisedynamics.net/privacy/dpa – No answer within 10 seconds.

Is this wrong? Send us the URL

–

Subprocessor list

weight 3 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 7 addresses we checked
  1. https://franchisedynamics.net/legal/subprocessors – Could not be fetched: fetch failed.
  2. https://franchisedynamics.net/subprocessors – Could not be fetched: fetch failed.
  3. https://franchisedynamics.net/sub-processors – No answer within 10 seconds.
  4. https://franchisedynamics.net/legal/sub-processors – No answer within 10 seconds.
  5. https://franchisedynamics.net/trust/subprocessors – No answer within 10 seconds.
  6. https://franchisedynamics.net/privacy/subprocessors – No answer within 10 seconds.
  7. https://franchisedynamics.net/legal/subprocessor-list – No answer within 10 seconds.

Is this wrong? Send us the URL

–

Data location stated

weight 3 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 7 addresses we checked
  1. https://franchisedynamics.net/security – No answer within 10 seconds.
  2. https://franchisedynamics.net/trust – No answer within 10 seconds.
  3. https://franchisedynamics.net/legal/privacy – No answer within 10 seconds.
  4. https://franchisedynamics.net/privacy – No answer within 10 seconds.
  5. https://franchisedynamics.net/privacy-policy – No answer within 10 seconds.
  6. https://franchisedynamics.net/compliance – Could not be fetched: fetch failed.
  7. https://franchisedynamics.net/legal/privacy-policy – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

–

Status page with history

weight 2 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 3 addresses we checked
  1. https://status.franchisedynamics.net/ – No answer within 10 seconds.
  2. https://franchisedynamics.net/status – No answer within 10 seconds.
  3. https://franchisedynamics.net.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

–

Public pricing

weight 2 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 5 addresses we checked
  1. https://franchisedynamics.net/pricing – Could not be fetched: fetch failed.
  2. https://franchisedynamics.net/pricing/ – No answer within 10 seconds.
  3. https://franchisedynamics.net/plans – browser: page.goto: Timeout 20000ms exceeded. Call log: - navigating to "https://franchisedynamics.net/plans", waiting until "domcontentloaded"
  4. https://franchisedynamics.net/en/pricing – No answer within 10 seconds.
  5. https://franchisedynamics.net/pricing-plans – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

–

No third-party tracking before consent

weight 2 of 3

Not measured. The page could not be loaded in a browser, so this was not measured.

Show the 1 address we checked
  1. https://franchisedynamics.net/ – page.goto: Timeout 20000ms exceeded. Call log: - navigating to "https://franchisedynamics.net/", waiting until "domcontentloaded"

Is this wrong? Send us the URL

–

security.txt (RFC 9116)

weight 1 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 1 address we checked
  1. https://franchisedynamics.net/.well-known/security.txt – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

History

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

Compare