SaaS Ranking

Named privacy contact in Search and vector infrastructure

"Contact us" is not a privacy contact. A named officer or a dedicated address is.

17 of 41 companies we measured here publish it, that is 41%. Last checked 2026-10-18.

41% here against 36% across every category we measure. Search and vector infrastructure sits above the overall share for this criterion.

This page counts companies, not product entries: a company with two products in this category is one company here and two rows below.

Back to Named privacy contact across all categories, or to Search and vector infrastructure.

The evidence at a glance
  • Found17
  • Not found at checked addresses24
  • Not measured4

45 companies in total. Unmeasured companies are excluded from the published share.

Published

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

VendorWhat we found
Chroma https://www.trychroma.com/privacyChecked
Cludo https://cludo.com/legal-hub/privacy-policy/Checked
Constructor https://constructor.com/privacy-policyChecked
Coveo https://www.coveo.com/en/company/legal/privacy-and-security/privacy-noticeChecked
Dashworks https://www.dashworks.ai/legal/privacy-policyChecked
Doofinder https://www.doofinder.com/en/privacy-policyChecked
Exa https://exa.ai/privacy-policyChecked
FACT-Finder https://www.fact-finder.com/privacy-policyChecked
Glean https://www.glean.com/privacyChecked
Hebbia https://www.hebbia.com/privacyChecked
Metal https://www.metal.ai/legal/privacy-policyChecked
Pinecone https://www.pinecone.io/privacy/Checked
Sinequa https://www.sinequa.com/privacy-policy/Checked
SuperDuperDB https://superduper.io/privacyChecked
turbopuffer https://turbopuffer.com/privacy-policyChecked
Vespa https://vespa.ai/privacy-policy/Checked
Zilliz https://zilliz.com/privacy-policyChecked
No named privacy contact found.

We reached at least one address for each of these vendors and none of them carried it. That is what we found at the addresses we checked, on the date we checked them, and not a statement about what the vendor has.

VendorWhat we found
Addsearch 7 addresses checkedChecked
Epoq 7 addresses checkedChecked
Findologic 7 addresses checkedChecked
Inbenta 7 addresses checkedChecked
Jina AI 7 addresses checkedChecked
Klevu 7 addresses checkedChecked
LanceDB 7 addresses checkedChecked
Luigis Box 7 addresses checkedChecked
Marqo 7 addresses checkedChecked
Meilisearch 7 addresses checkedChecked
Nosto 7 addresses checkedChecked
Parallel 7 addresses checkedChecked
Prefixbox 7 addresses checkedChecked
SearchHub 7 addresses checkedChecked
Semknox 7 addresses checkedChecked
Site Search 360 7 addresses checkedChecked
Sooqr 7 addresses checkedChecked
Spinque Desk 7 addresses checkedChecked
Typesense 7 addresses checkedChecked
Unbxd 7 addresses checkedChecked
Valyu 7 addresses checkedChecked
Vectara 7 addresses checkedChecked
Voyage AI 7 addresses checkedChecked
Yext 7 addresses checkedChecked
Not measured

We could not look at these, or their robots.txt asks us not to. That says something about our measurement, not about them, and they are left out of the percentage above.

VendorWhat we found
Algolia The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked
Lucidworks The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked
Searchspring This vendor was not measured because our run stopped waiting for it.Checked
Tavily The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured.Checked

Other criteria in Search and vector infrastructure

Named privacy contact in related categories

Found something we missed? Tell us. A correction moves that vendor into our next nightly run. That run reads the same fixed addresses we check for every vendor, not the address you send.