SaaS Ranking

Sales and marketing / Influencer marketing

Modash

What Modash publishes on modash.io, measured on 2026-09-02. Every line links the page we found it on, or lists the addresses we checked.

Transparency 70/100 BBand B

Rank 1 of 9 in Influencer marketingcategory median 13checked 2026-09-02

5 gaps found: 5 criteria not found at the addresses we checked. 7 found5 not found0 not measured

Public transparency score, not a product or security rating.

Transparency labelsaas-ranking.com

Modash

modash.io · Influencer marketing

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
B 70of 100 Rank 1 of 9

Published commitments6 of 9 found

Measured behaviour1 of 3 found

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

Show the full transparency label

Transparency labelsaas-ranking.com

Modash

modash.io · Influencer marketing

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
B 70of 100 Rank 1 of 9

Published commitments6 of 9 found

Measured behaviour1 of 3 found

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

Not found, heaviest first

Status page with history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-09-02.

Show the 3 addresses we checked
  1. https://status.modash.io/ – reached, no match (HTTP 200)
  2. https://modash.io/status – reached, no match (HTTP 404)
  3. https://modash.io.statuspage.io/ – Could not be fetched: fetch failed.

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

Show the 1 address we checked
  1. https://modash.io/ – third-party requests before any interaction: ajax.googleapis.com, apps.tooeasy.dev, assets.calendly.com, cdn.jsdelivr.net, cdn.prod.website-files.com, cdnjs.cloudflare.com, client.px-cloud.net, collector-pxebumdlwe.px-cloud.net, connect.facebook.net, d3e54v103j8qbb.cloudfront.net, ddwl4m2hdecbv.cloudfront.net, embed.typeform.com, embeds.beehiiv.com, fonts.googleapis.com, fonts.gstatic.com, get.geojs.io, ift.px-cloud.net, ipapi.co, js.hs-analytics.net, js.hs-banner.com, js.hs-scripts.com, js.hsadspixel.net, js.hscollectedforms.net, js.px-cloud.net, s3.amazonaws.com, snap.licdn.com, unpkg.com, widget.intercom.io, www.facebook.com, www.google-analytics.com, www.googletagmanager.com

Is this wrong? Send us the URL

Certifications named

weight 1 of 3

No named certification found.

Checked 6 addresses on 2026-09-02.

Show the 6 addresses we checked
  1. https://modash.io/security – reached, no match (HTTP 404)
  2. https://modash.io/trust – reached, no match (HTTP 404)
  3. https://modash.io/trust-center – reached, no match (HTTP 404)
  4. https://modash.io/compliance – reached, no match (HTTP 404)
  5. https://modash.io/legal/security – reached, no match (HTTP 404)
  6. https://trust.modash.io/ – The name "trust.modash.io" 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-02.

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

Is this wrong? Send us the URL

security.txt (RFC 9116)

weight 1 of 3

No security.txt found.

Checked 1 address on 2026-09-02.

Show the 1 address we checked
  1. https://modash.io/.well-known/security.txt – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Published evidence 7

Data processing agreement

weight 3 of 3

Published and readable without a login.

Source: https://www.modash.io/legal/data-processing-agreement · checked 2026-09-02

Subprocessor list

weight 3 of 3

The actual list is published, not just a promise to keep one.

Source: https://www.modash.io/legal/subprocessors · checked 2026-09-02

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

Source: https://www.modash.io/legal/privacy-policy · checked 2026-09-02

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://www.modash.io/pricing · checked 2026-09-02

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

Source: https://modash.io/ · checked 2026-09-02

Notice before subprocessors change

weight 2 of 3

The vendor commits publicly to giving notice before the list changes.

Source: https://www.modash.io/legal/data-processing-agreement · checked 2026-09-02

Named privacy contact

weight 1 of 3

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

Source: https://www.modash.io/legal/privacy-policy · checked 2026-09-02

Keep going