SaaS Ranking

Moesif

moesif.com · API management · checked 2026-09-04

65/100CBand C

Rank 1 of 27 in API management, where the median is 26.

We measured 12 of 12 criteria for Moesif on 2026-09-04. We found 7 with a source and did not find 5 at the addresses we checked. That is a transparency score of 65 out of 100, band C.

Overview

Transparency labelsaas-ranking.com

Moesif

moesif.com · API management

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

Published commitments6 of 9 found

Measured behaviour1 of 3 found

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

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 Moesif 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

Status page with history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-09-04.

Show the 3 addresses we checked
  1. https://status.moesif.com/ – reached, no match (HTTP 200)
  2. https://moesif.com/status – reached, no match (HTTP 404)
  3. https://moesif.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-04.

Show the 5 addresses we checked
  1. https://moesif.com/pricing – reached, no match (HTTP 404)
  2. https://moesif.com/pricing/ – reached, no match (HTTP 404)
  3. https://moesif.com/plans – reached, no match (HTTP 404)
  4. https://moesif.com/en/pricing – reached, no match (HTTP 404)
  5. https://moesif.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-04.

Show the 1 address we checked
  1. https://moesif.com/ – third-party requests before any interaction: api.hubspot.com, app.hubspot.com, browser-intake-datadoghq.com, connect.facebook.net, cookie-cdn.cookiepro.com, exceptions.hubspot.com, geolocation.onetrust.com, region1.analytics.google.com, static.hsappstatic.net, stats.g.doubleclick.net, www.googletagmanager.com

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

Show the 6 addresses we checked
  1. https://moesif.com/legal/sla – reached, no match (HTTP 404)
  2. https://moesif.com/sla – reached, no match (HTTP 404)
  3. https://moesif.com/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://moesif.com/trust/sla – reached, no match (HTTP 404)
  5. https://moesif.com/uptime – reached, no match (HTTP 404)
  6. https://moesif.com/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-04.

Show the 1 address we checked
  1. https://moesif.com/.well-known/security.txt – 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 7

Data processing agreement

weight 3 of 3

Published and readable without a login.

Source: https://www.moesif.com/dpa · checked 2026-09-04

Subprocessor list

weight 3 of 3

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

Source: https://www.moesif.com/subprocessors · checked 2026-09-04

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

  • Locations named next to the hosting wording United States.
    Show the exact wording

    Data Storage Location Moesif customer data at rest currently resides in the United States of America.

    Read at https://www.moesif.com/security

Source: https://www.moesif.com/security · checked 2026-09-04

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://moesif.com/
  • HSTS options includeSubDomains, preload.
    Show the 2 exact wordings

    max-age=31536000; includeSubDomains; preload

    Read at https://moesif.com/

    max-age=31536000; includeSubDomains; preload

    Read at https://moesif.com/

Source: https://moesif.com/ · checked 2026-09-04

Notice before subprocessors change

weight 2 of 3

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

Source: https://www.moesif.com/dpa · checked 2026-09-04

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page ISO/IEC 27001, ISO/IEC 27017, PCI DSS, SOC 2 Type II.
    Show the 4 exact wordings

    Data is stored only in the cloud in ISO/IEC 27001 and ISO/IEC 27017 compliant data centers in Microsoft Azure which further provides fault-tolerance

    Read at https://www.moesif.com/security

    Data is stored only in the cloud in ISO/IEC 27001 and ISO/IEC 27017 compliant data centers in Microsoft Azure which further provides fault-tolerance and strong access

    Read at https://www.moesif.com/security

    recommends either masking sensitive data such as ePHI (electronic Protected Health Information) or PCI DSS (Payment Card Industry Data Security Standard) using our SDKs mask function or leveraging Moe...

    Read at https://www.moesif.com/security

    Moesif maintains an active SOC 2 Type 2 attestation available in the Moesif Trust Center and is a big believer in zero-knowledge and

    Read at https://www.moesif.com/security

Source: https://www.moesif.com/security · checked 2026-09-04

Named privacy contact

weight 1 of 3

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

Source: https://www.moesif.com/privacy · checked 2026-09-04

History

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

Compare