SaaS Ranking
Menu

Bit: what they publish

bit.ai · Document collaboration · checked 2026-10-14

Not enough data: 3 of 12 criteria measured, so no transparency score

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

3 days since the newest dated result, 3 since the oldest. 3 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

Bit

bit.ai · Document collaboration

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
Not enough data3 of 12 measured, no score

Published commitments0 of 2 found, 7 not measured

Measured behaviour0 of 1 found, 2 not measured

Checked 2026-10-14. 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. We could measure 3 of 12 criteria, which is below our threshold, so there is no rank. That is a statement about our measurement, not about Bit.

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

What Bit 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

✗

Status page with incident history

weight 2 of 3

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

Seen at https://status.bit.ai/auth/login?returnTo=%2F · checked 2026-10-14

Show the 3 addresses we checked
  1. https://status.bit.ai/ – found, but behind a sign-in
  2. https://bit.ai/status – Could not be fetched: fetch failed.
  3. https://bit.ai.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Across the market: Status page with history in Document collaboration: 7 of 40 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 9 cloudflare.com, cloudfront.net, embedly.com, firstpromoter.com, googleapis.com, gstatic.com, vimeo.com, vimeocdn.com, website-files.com.
    Show the 9 exact wordings

    cdnjs.cloudflare.com

    Read at https://bit.ai/

    d3e54v103j8qbb.cloudfront.net

    Read at https://bit.ai/

    cdn.embedly.com

    Read at https://bit.ai/

    cdn.firstpromoter.com

    Read at https://bit.ai/

    ajax.googleapis.com, fonts.googleapis.com

    Read at https://bit.ai/

    fonts.gstatic.com

    Read at https://bit.ai/

    arclight.vimeo.com, player.vimeo.com, vimeo.com

    Read at https://bit.ai/

    f.vimeocdn.com, i.vimeocdn.com, vod-adaptive-ak.vimeocdn.com

    Read at https://bit.ai/

    cdn.prod.website-files.com

    Read at https://bit.ai/

Checked 1 address on 2026-10-14.

Show the 1 address we checked
  1. https://bit.ai/ – third-party requests before any interaction: ajax.googleapis.com, arclight.vimeo.com, cdn.embedly.com, cdn.firstpromoter.com, cdn.prod.website-files.com, cdnjs.cloudflare.com, d3e54v103j8qbb.cloudfront.net, f.vimeocdn.com, fonts.googleapis.com, fonts.gstatic.com, i.vimeocdn.com, player.vimeo.com, vimeo.com, vod-adaptive-ak.vimeocdn.com

Is this wrong? Send us the URL

Across the market: No third-party tracking before consent in Document collaboration: 6 of 41 companies

✗

Certifications named (SOC 2, ISO 27001)

weight 1 of 3

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

Seen at https://trust.bit.ai/auth/login?returnTo=%2F · checked 2026-10-14

Show the 6 addresses we checked
  1. https://bit.ai/security – Could not be fetched: fetch failed.
  2. https://bit.ai/trust – Could not be fetched: fetch failed.
  3. https://bit.ai/trust-center – Could not be fetched: fetch failed.
  4. https://bit.ai/compliance – Could not be fetched: fetch failed.
  5. https://bit.ai/legal/security – Could not be fetched: fetch failed.
  6. https://trust.bit.ai/ – found, but behind a sign-in

Is this wrong? Send us the URL

Across the market: Certifications named in Document collaboration: 18 of 40 companies

Evidence

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

Not measured by us 9
–

Data processing agreement (DPA)

weight 3 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 8 addresses we checked
  1. https://bit.ai/legal/dpa – Could not be fetched: fetch failed.
  2. https://bit.ai/dpa – Could not be fetched: fetch failed.
  3. https://bit.ai/legal/data-processing-agreement – Could not be fetched: fetch failed.
  4. https://bit.ai/data-processing-agreement – Could not be fetched: fetch failed.
  5. https://bit.ai/legal/data-processing-addendum – Could not be fetched: fetch failed.
  6. https://bit.ai/legal/gdpr – Could not be fetched: fetch failed.
  7. https://bit.ai/trust/dpa – Could not be fetched: fetch failed.
  8. https://bit.ai/privacy/dpa – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Across the market: Data processing agreement in Document collaboration: 6 of 37 companies

–

Subprocessors: the published list

weight 3 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 7 addresses we checked
  1. https://bit.ai/legal/subprocessors – Could not be fetched: fetch failed.
  2. https://bit.ai/subprocessors – Could not be fetched: fetch failed.
  3. https://bit.ai/sub-processors – Could not be fetched: fetch failed.
  4. https://bit.ai/legal/sub-processors – Could not be fetched: fetch failed.
  5. https://bit.ai/trust/subprocessors – Could not be fetched: fetch failed.
  6. https://bit.ai/privacy/subprocessors – Could not be fetched: fetch failed.
  7. https://bit.ai/legal/subprocessor-list – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Across the market: Subprocessor list in Document collaboration: 4 of 37 companies

–

Data location: where they say data is hosted

weight 3 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 7 addresses we checked
  1. https://bit.ai/security – Could not be fetched: fetch failed.
  2. https://bit.ai/trust – Could not be fetched: fetch failed.
  3. https://bit.ai/legal/privacy – Could not be fetched: fetch failed.
  4. https://bit.ai/privacy – Could not be fetched: fetch failed.
  5. https://bit.ai/privacy-policy – Could not be fetched: fetch failed.
  6. https://bit.ai/compliance – Could not be fetched: fetch failed.
  7. https://bit.ai/legal/privacy-policy – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Across the market: Data location stated in Document collaboration: 14 of 37 companies

–

Public pricing with figures

weight 2 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 5 addresses we checked
  1. https://bit.ai/pricing – Could not be fetched: fetch failed.
  2. https://bit.ai/pricing/ – Could not be fetched: fetch failed.
  3. https://bit.ai/plans – Could not be fetched: fetch failed.
  4. https://bit.ai/en/pricing – Could not be fetched: fetch failed.
  5. https://bit.ai/pricing-plans – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Across the market: Public pricing in Document collaboration: 26 of 37 companies

–

HTTPS enforced with HSTS

weight 2 of 3

Not measured. The HTTPS endpoint could not be reached, so this was not measured.

Show the 2 addresses we checked
  1. http://bit.ai/ – redirects to https://bit.ai/
  2. https://bit.ai/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Across the market: HTTPS enforced with HSTS in Document collaboration: 30 of 40 companies

–

Notice before subprocessors change

weight 2 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 8 addresses we checked
  1. https://bit.ai/legal/subprocessors – Could not be fetched: fetch failed.
  2. https://bit.ai/subprocessors – Could not be fetched: fetch failed.
  3. https://bit.ai/sub-processors – Could not be fetched: fetch failed.
  4. https://bit.ai/legal/dpa – Could not be fetched: fetch failed.
  5. https://bit.ai/dpa – Could not be fetched: fetch failed.
  6. https://bit.ai/legal/data-processing-agreement – Could not be fetched: fetch failed.
  7. https://bit.ai/trust/subprocessors – Could not be fetched: fetch failed.
  8. https://bit.ai/legal/sub-processors – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Across the market: Notice before subprocessors change in Document collaboration: 4 of 37 companies

–

Uptime SLA with a figure

weight 1 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 6 addresses we checked
  1. https://bit.ai/legal/sla – Could not be fetched: fetch failed.
  2. https://bit.ai/sla – Could not be fetched: fetch failed.
  3. https://bit.ai/legal/service-level-agreement – Could not be fetched: fetch failed.
  4. https://bit.ai/trust/sla – Could not be fetched: fetch failed.
  5. https://bit.ai/uptime – Could not be fetched: fetch failed.
  6. https://bit.ai/legal/uptime-sla – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Across the market: Uptime SLA with a figure in Document collaboration: 0 of 37 companies

–

security.txt (RFC 9116)

weight 1 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 1 address we checked
  1. https://bit.ai/.well-known/security.txt – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Across the market: security.txt (RFC 9116) in Document collaboration: 7 of 39 companies

–

Named privacy contact (DPO or privacy address)

weight 1 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 7 addresses we checked
  1. https://bit.ai/legal/privacy – Could not be fetched: fetch failed.
  2. https://bit.ai/privacy – Could not be fetched: fetch failed.
  3. https://bit.ai/privacy-policy – Could not be fetched: fetch failed.
  4. https://bit.ai/legal/privacy-policy – Could not be fetched: fetch failed.
  5. https://bit.ai/legal/privacy-notice – Could not be fetched: fetch failed.
  6. https://bit.ai/trust/privacy – Could not be fetched: fetch failed.
  7. https://bit.ai/datenschutz – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Across the market: Named privacy contact in Document collaboration: 12 of 37 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.

Bit

0 found · 3 not found · 9 not measured across 12 public checks.

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

Investigate 12 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. Data location stated

    Which locations apply to our primary data, backups and support access? Which region can we select for this plan?

    Inspect this check
  4. 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
  5. Public pricing

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

    Inspect this check
  6. Certifications named

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

    Inspect this check
  7. 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
  8. HTTPS enforced with HSTS

    How is HTTPS enforced on the product and sign-in domains we will use? Please distinguish those domains from the public website.

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

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

    Inspect this check
  11. 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
  12. 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.