SaaS Ranking
Menu

Timely Events: what they publish

time.ly · Event management · checked 2026-10-28

32/100EBand E

Rank 12 of 50 in Event management, where the median is 24.5.

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

1 day since the newest dated result, 1 since the oldest. 11 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

Timely Events

time.ly · Event management

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
E 32of 100 Rank 12 of 50

Published commitments1 of 9 found

Measured behaviour2 of 2 found, 1 not measured

Checked 2026-10-28. 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 Timely Events has no such document.

Where Timely Events sits in Event management

  1. A0 0%
  2. B1 2%
  3. C3 6%
  4. D6 12%
  5. E15 30%
  6. F25 50%
50 vendors with a score; 6 more without a score because we could measure too little. Bands have fixed thresholds, see how the score works.

The band of Timely Events 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 Timely Events 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-28.

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

Is this wrong? Send us the URL

Across the market: Data processing agreement in Event management: 5 of 50 companies

✗

Subprocessors: the published list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-10-28.

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

Is this wrong? Send us the URL

Across the market: Subprocessor list in Event management: 7 of 50 companies

✗

Status page with incident history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-10-28.

Show the 3 addresses we checked
  1. https://status.time.ly/ – The name "status.time.ly" could not be resolved.
  2. https://time.ly/status – reached, no match (HTTP 404)
  3. https://time.ly.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Across the market: Status page with history in Event management: 11 of 50 companies

✗

Public pricing with figures

weight 2 of 3

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

Seen at https://time.ly/pricing/ · checked 2026-10-28

Show the 5 addresses we checked
  1. https://time.ly/pricing – found, but behind a sign-in
  2. https://time.ly/pricing/ – found, but behind a sign-in
  3. https://time.ly/plans – reached, no match (HTTP 404)
  4. https://time.ly/en/pricing – found, but behind a sign-in
  5. https://time.ly/pricing-plans – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: Public pricing in Event management: 28 of 51 companies

✗

Notice before subprocessors change

weight 2 of 3

No commitment to give notice before subprocessors change found.

Checked 8 addresses on 2026-10-28.

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

Is this wrong? Send us the URL

Across the market: Notice before subprocessors change in Event management: 4 of 50 companies

✗

Certifications named (SOC 2, ISO 27001)

weight 1 of 3

No named certification found.

Checked 6 addresses on 2026-10-28.

Show the 6 addresses we checked
  1. https://time.ly/security – reached, no match (HTTP 404)
  2. https://time.ly/trust – reached, no match (HTTP 404)
  3. https://time.ly/trust-center – reached, no match (HTTP 404)
  4. https://time.ly/compliance – reached, no match (HTTP 404)
  5. https://time.ly/legal/security – reached, no match (HTTP 404)
  6. https://trust.time.ly/ – The name "trust.time.ly" could not be resolved.

Is this wrong? Send us the URL

Across the market: Certifications named in Event management: 14 of 51 companies

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-10-28.

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

Is this wrong? Send us the URL

Across the market: Uptime SLA with a figure in Event management: 1 of 50 companies

✗

Named privacy contact (DPO or privacy address)

weight 1 of 3

No named privacy contact found.

Checked 7 addresses on 2026-10-28.

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

Is this wrong? Send us the URL

Across the market: Named privacy contact in Event management: 16 of 50 companies

Evidence

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

Published, with a source 3
✓

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

    These locations may include, for example, the United States, Canada, and Germany, where our data hosting providers and service partners maintain servers and operations.

    Read at https://time.ly/legal/privacy-policy/

    These locations may include, for example, the United States, Canada, and Germany, where our data hosting providers and service partners maintain servers and operations.

    Read at https://time.ly/legal/privacy-policy/

    These locations may include, for example, the United States, Canada, and Germany, where our data hosting providers and service partners maintain servers and operations.

    Read at https://time.ly/legal/privacy-policy/

Source: https://time.ly/legal/privacy-policy/ · checked 2026-10-28

Across the market: Data location stated in Event management: 22 of 50 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://time.ly/
  • HSTS options includeSubDomains, preload.
    Show the 2 exact wordings

    max-age=31536000; includeSubDomains; preload

    Read at https://time.ly/

    max-age=31536000; includeSubDomains; preload

    Read at https://time.ly/

Source: https://time.ly/ · checked 2026-10-28

Across the market: HTTPS enforced with HSTS in Event management: 36 of 53 companies

✓weight 2 of 3

No third-party requests before any interaction.

Source: https://time.ly/ · checked 2026-10-28

Across the market: No third-party tracking before consent in Event management: 3 of 53 companies

Not measured by us 1
–

security.txt (RFC 9116)

weight 1 of 3

Not measured. The vendor’s server blocked, rate-limited or could not serve this request, so this was not measured.

Show the 1 address we checked
  1. https://time.ly/.well-known/security.txt – blocked or unavailable (HTTP 403)

Is this wrong? Send us the URL

Across the market: security.txt (RFC 9116) in Event management: 6 of 48 companies

History

100 0 2026-10-21: 32 of 1002026-10-28: 32 of 100 2026-10-21 2026-10-28
Score over the last 2 runs we measured Timely Events in: 32 (2026-10-21), 32 (2026-10-28).

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.

Timely Events

3 found · 8 not found · 1 not measured across 12 public checks.

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

Investigate 9 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. 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
  4. Public pricing

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

    Inspect this check
  5. Certifications named

    Please share the current certificate or audit report and its scope, covered legal entity, products and validity period.

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

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

    Inspect this check
  8. 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
  9. 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.