SaaS Ranking
Menu

Calendly: what they publish

calendly.com · Scheduling · checked 2026-10-10

65/100CBand C

Rank 2 of 33 in Scheduling, where the median is 26.

Public transparency score, not a product or security rating. Latest check: 2026-10-10. How the score works.

Evidence at a glance

Choose a check to see its source, date and scope.

Not found means not found at the addresses we checked. Not measured means we could not complete the check.

Start a vendor reviewDownload evidence (CSV)

Overview

6 days since the newest dated result, 6 since the oldest. 12 of 12 criteria have a measured result in the last 30 days. Failed checks and undated results are excluded.

Evidence freshness is a statement about our measurement and is kept apart from the transparency score, which is frozen at v1. How good our own measurement is.

Transparency labelsaas-ranking.com

Calendly

calendly.com · Scheduling

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

Published commitments6 of 9 found

Measured behaviour2 of 3 found

Checked 2026-10-10. 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.

Downloads include all checks, source URLs, dates and the snapshot ID for your procurement file. We do not issue badges.

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

Where Calendly sits in Scheduling

  1. A0 0%
  2. B1 3%
  3. C1 3%
  4. D4 12%
  5. E12 36%
  6. F15 45%
33 vendors with a score; 2 more without a score because we could measure too little. Bands have fixed thresholds, see how the score works.

The band of Calendly is marked. Vendors without a score are the ones where we could measure too few criteria to rank them – a gap on our side, counted separately.

What Calendly states

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

✗

Subprocessors: the published list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-10-10.

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

Is this wrong? Send us the URL

Across the market: Subprocessor list in Scheduling: 3 of 33 companies

✗

Status page with incident history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-10-10.

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

Is this wrong? Send us the URL

Across the market: Status page with history in Scheduling: 7 of 33 companies

✗weight 2 of 3

Third-party requests seen on the first load, before any interaction.

Checked 1 address on 2026-10-10.

Show the 1 address we checked
  1. https://calendly.com/ – third-party requests before any interaction: cdn.calendlycms.com, cdn.cookielaw.org, geolocation.onetrust.com, global.ketchcdn.com, pagead2.googlesyndication.com, prompts.maze.co, snippet.maze.co, unpkg.com, www.googletagmanager.com

Is this wrong? Send us the URL

Across the market: No third-party tracking before consent in Scheduling: 1 of 35 companies

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-10-10.

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

Is this wrong? Send us the URL

Across the market: Uptime SLA with a figure in Scheduling: 0 of 33 companies

Evidence

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

Published, with a source 8
✓

Data processing agreement (DPA)

weight 3 of 3

Published and readable without a login.

Source: https://calendly.com/legal/data-processing-addendum · checked 2026-10-10

Across the market: Data processing agreement in Scheduling: 8 of 33 companies

✓

Data location: where they say data is hosted

weight 3 of 3

The hosting location is stated on a public page.

  • Locations named next to the hosting wording United States. This does not establish the company’s headquarters.
    Show the exact wording

    luding through the use of methods such as Cookies and other web technologies) will be processed and stored in the United States or in other countries where we or our Service Providers have operations.

    Read at https://calendly.com/legal/privacy-notice

Source: https://calendly.com/legal/privacy-notice · checked 2026-10-10

Across the market: Data location stated in Scheduling: 11 of 33 companies

✓

Public pricing with figures

weight 2 of 3

Actual numbers on a public page.

Source: https://calendly.com/pricing · checked 2026-10-10

Across the market: Public pricing in Scheduling: 25 of 34 companies

✓

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

    max-age=31536000; includeSubDomains; preload

    Read at https://calendly.com/

    max-age=31536000; includeSubDomains; preload

    Read at https://calendly.com/

Source: https://calendly.com/ · checked 2026-10-10

Across the market: HTTPS enforced with HSTS in Scheduling: 26 of 35 companies

✓

Notice before subprocessors change

weight 2 of 3

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

Source: https://calendly.com/legal/data-processing-addendum · checked 2026-10-10

Across the market: Notice before subprocessors change in Scheduling: 3 of 33 companies

✓

Certifications named (SOC 2, ISO 27001)

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page CSA STAR (not counted: the sentence does not carry it), ISO/IEC 27001 (not counted: the sentence does not carry it), SOC 2 Type II (unclear from the sentence). The sentence we kept does not carry this finding on its own, so it counts in no list and no figure.
    Show the 3 exact wordings

    Review documentation SOC 2 (Type 2) SOC 3 CSA STAR PCI COMPLIANT ISO/IEC 27001 Trust center Need additional documentation?

    Read at https://calendly.com/security

    Review documentation SOC 2 (Type 2) SOC 3 CSA STAR PCI COMPLIANT ISO/IEC 27001 Trust center Need additional documentation?

    Read at https://calendly.com/security

    Review documentation SOC 2 (Type 2) SOC 3 CSA STAR PCI COMPLIANT ISO/IEC 27001 Trust center Need additional documentation?

    Read at https://calendly.com/security

Source: https://calendly.com/security · checked 2026-10-10

Across the market: Certifications named in Scheduling: 9 of 34 companies

✓

security.txt (RFC 9116)

weight 1 of 3

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

Source: https://calendly.com/.well-known/security.txt · checked 2026-10-10

Across the market: security.txt (RFC 9116) in Scheduling: 3 of 32 companies

✓

Named privacy contact (DPO or privacy address)

weight 1 of 3

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

Source: https://calendly.com/legal/privacy-notice · checked 2026-10-10

Across the market: Named privacy contact in Scheduling: 12 of 33 companies

History

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

Prepare your vendor review

A source is a starting point. Check the product, plan, legal entity and date before treating it as evidence for your purchase. These questions do not change the transparency score.

Calendly

8 found · 4 not found · 0 not measured across 12 public checks.

12 of 12 criteria have a measured result from the last 30 days. Oldest dated result: 2026-10-10.

Investigate 4 open evidence questions
  1. Subprocessor list

    Which subprocessors apply to our product, what does each process, and in which countries? Please share the current list.

    Inspect this check
  2. Status page with history

    Where can we review incident history for the service we will use, and how do we subscribe to incident updates?

    Inspect this check
  3. Uptime SLA with a figure

    Which availability commitment applies to our plan? Please include the measurement window, exclusions and credit claim process.

    Inspect this check
  4. No third-party tracking before consent

    Which third-party requests occur before a visitor makes a choice, and for what purpose? Please distinguish the public website from the product.

    Inspect this check

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.

Compared with

Each comparison lists only the criteria where the two differ, with the source for every one. All comparisons.