SaaS Ranking
Menu

Cayuse: what they publish

cayuse.com · Research administration · checked 2026-10-17

35/100EBand E

Rank 3 of 27 in Research administration, where the median is 13.

Public transparency score, not a product or security rating. Latest check: 2026-10-17. 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

0 days since the newest dated result, 0 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

Cayuse

cayuse.com · Research administration

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

Published commitments3 of 9 found

Measured behaviour1 of 3 found

Checked 2026-10-17. 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 Cayuse has no such document.

Where Cayuse sits in Research administration

  1. A0 0%
  2. B0 0%
  3. C0 0%
  4. D1 4%
  5. E7 26%
  6. F19 70%
27 vendors with a score; 3 more without a score because we could measure too little. Bands have fixed thresholds, see how the score works.

The band of Cayuse 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 Cayuse 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

✗

Data processing agreement (DPA)

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-10-17.

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

Is this wrong? Send us the URL

Across the market: Data processing agreement in Research administration: 2 of 27 companies

✗

Subprocessors: the published list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-10-17.

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

Is this wrong? Send us the URL

Across the market: Subprocessor list in Research administration: 0 of 27 companies

✗

Public pricing with figures

weight 2 of 3

No public pricing with figures found.

Checked 5 addresses on 2026-10-17.

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

Is this wrong? Send us the URL

Across the market: Public pricing in Research administration: 3 of 27 companies

✗weight 2 of 3

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

  • Third-party hosts we saw on the first load 1 gaug.es.
    Show the exact wording

    secure.gaug.es

    Read at https://cayuse.com/

Checked 1 address on 2026-10-17.

Show the 1 address we checked
  1. https://cayuse.com/ – third-party requests before any interaction: secure.gaug.es

Is this wrong? Send us the URL

Across the market: No third-party tracking before consent in Research administration: 2 of 30 companies

✗

Notice before subprocessors change

weight 2 of 3

No commitment to give notice before subprocessors change found.

Checked 8 addresses on 2026-10-17.

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

Is this wrong? Send us the URL

Across the market: Notice before subprocessors change in Research administration: 0 of 27 companies

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-10-17.

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

✗

security.txt (RFC 9116)

weight 1 of 3

No security.txt found.

Checked 1 address on 2026-10-17.

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

Is this wrong? Send us the URL

Across the market: security.txt (RFC 9116) in Research administration: 1 of 25 companies

✗

Named privacy contact (DPO or privacy address)

weight 1 of 3

We found this behind a sign-in, so it is not published openly.

Seen at https://www.cayuse.com/privacy/ · checked 2026-10-17

Show the 7 addresses we checked
  1. https://cayuse.com/legal/privacy – found, but behind a sign-in
  2. https://cayuse.com/privacy – found, but behind a sign-in
  3. https://cayuse.com/privacy-policy – reached, no match (HTTP 404)
  4. https://cayuse.com/legal/privacy-policy – No answer within 10 seconds.
  5. https://cayuse.com/legal/privacy-notice – Could not be fetched: fetch failed.
  6. https://cayuse.com/trust/privacy – No answer within 10 seconds.
  7. https://cayuse.com/datenschutz – No answer within 10 seconds.

Is this wrong? Send us the URL

Across the market: Named privacy contact in Research administration: 6 of 27 companies

Evidence

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

Published, with a source 4
✓

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 Australia, United States. This does not establish the company’s headquarters.
    Show the 2 exact wordings

    A.3 For Individuals Based in Australia This section is applicable to individuals whose personal information is collected, stored, used or disclosed by an APP Entity under the Australian Privacy Princi...

    Read at https://www.cayuse.com/privacy/

    pose Information Collected by the Service Provider Data Location Amazon Web Services Infrastructure Hosting provider Limited, no PII United States (AWS) Sentree Cayuse Web Page Hosting Limited, no PII...

    Read at https://www.cayuse.com/privacy/

Source: https://www.cayuse.com/privacy/ · checked 2026-10-17

Across the market: Data location stated in Research administration: 7 of 27 companies

✓

Status page with incident history

weight 2 of 3

A public status page with incident history.

Source: https://status.cayuse.com/ · checked 2026-10-17

Across the market: Status page with history in Research administration: 5 of 27 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

    Read at https://cayuse.com/

Source: https://cayuse.com/ · checked 2026-10-17

Across the market: HTTPS enforced with HSTS in Research administration: 23 of 30 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 HITRUST CSF (unclear from the sentence), ISO/IEC 27001 (unclear from the sentence), SOC 2 (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 4 exact wordings

    SOC 2, ISO 27001 & HITRUST i1 certified Type 2 SOC 2, ISO 27001 and HITRUST i1 audited and certified security program.

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

    SOC 2, ISO 27001 & HITRUST i1 certified Type 2 SOC 2, ISO 27001 and HITRUST i1 audited and certified security progra

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

    Read now Blog Why SOC 2 Certification is the New Standard for Security in Research Administration Cayuse has earned SOC 2 c

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

    SOC 2, ISO 27001 & HITRUST i1 certified Type 2 SOC 2, ISO 27001 and HITRUST i1 audited and certified secu

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

Source: https://www.cayuse.com/security · checked 2026-10-17

Across the market: Certifications named in Research administration: 10 of 28 companies

History

100 0 2026-10-10: 35 of 1002026-10-17: 35 of 100 2026-10-10 2026-10-17
Score over the last 2 runs we measured Cayuse in: 35 (2026-10-10), 35 (2026-10-17).

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.

Cayuse

4 found · 8 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-17.

Investigate 8 open evidence questions
  1. Data processing agreement

    Please share the current data processing agreement for the product and plan we are considering, including its annexes and signing process.

    Inspect this check
  2. Subprocessor list

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

    Inspect this check
  3. Public pricing

    Please confirm the total cost for our seats and usage, including minimum commitments, add-ons, overages and renewal terms.

    Inspect this check
  4. 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
  5. 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
  6. security.txt (RFC 9116)

    Where should we report a vulnerability, and what acknowledgement and follow-up process should we expect?

    Inspect this check
  7. Notice before subprocessors change

    How will you notify us before a subprocessor changes, with how much notice, and what response options apply to our contract?

    Inspect this check
  8. Named privacy contact

    Which privacy contact handles requests for our account, and what escalation path should we use?

    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.