✗
Data processing agreement (DPA)
weight 3 of 3
No data processing agreement found.
Checked 8 addresses on 2026-10-16.
Show the 8 addresses we checked
https://reco.ai/legal/dpa – reached, no match (HTTP 404)https://reco.ai/dpa – reached, no match (HTTP 404)https://reco.ai/legal/data-processing-agreement – reached, no match (HTTP 404)https://reco.ai/data-processing-agreement – reached, no match (HTTP 404)https://reco.ai/legal/data-processing-addendum – reached, no match (HTTP 404)https://reco.ai/legal/gdpr – reached, no match (HTTP 404)https://reco.ai/trust/dpa – reached, no match (HTTP 404)https://reco.ai/privacy/dpa – reached, no match (HTTP 404)
Is this wrong? Send us the URL
Across the market: Data processing agreement in Telecom and SaaS expense management: 4 of 22 companies
✗
Subprocessors: the published list
weight 3 of 3
No subprocessor list found.
Checked 7 addresses on 2026-10-16.
Show the 7 addresses we checked
https://reco.ai/legal/subprocessors – reached, no match (HTTP 404)https://reco.ai/subprocessors – reached, no match (HTTP 404)https://reco.ai/sub-processors – reached, no match (HTTP 404)https://reco.ai/legal/sub-processors – reached, no match (HTTP 404)https://reco.ai/trust/subprocessors – reached, no match (HTTP 404)https://reco.ai/privacy/subprocessors – reached, no match (HTTP 404)https://reco.ai/legal/subprocessor-list – reached, no match (HTTP 404)
Is this wrong? Send us the URL
Across the market: Subprocessor list in Telecom and SaaS expense management: 3 of 22 companies
✗
Data location: where they say data is hosted
weight 3 of 3
No statement about data location found.
Checked 7 addresses on 2026-10-16.
Show the 7 addresses we checked
https://reco.ai/security – reached, no match (HTTP 404)https://reco.ai/trust – reached, no match (HTTP 404)https://reco.ai/legal/privacy – reached, no match (HTTP 404)https://reco.ai/privacy – reached, no match (HTTP 404)https://reco.ai/privacy-policy – reached, no match (HTTP 200)https://reco.ai/compliance – reached, no match (HTTP 404)https://reco.ai/legal/privacy-policy – reached, no match (HTTP 404)
Is this wrong? Send us the URL
Across the market: Data location stated in Telecom and SaaS expense management: 8 of 22 companies
✗
Public pricing with figures
weight 2 of 3
No public pricing with figures found.
Checked 5 addresses on 2026-10-16.
Show the 5 addresses we checked
https://reco.ai/pricing – reached, no match (HTTP 404)https://reco.ai/pricing/ – reached, no match (HTTP 404)https://reco.ai/plans – reached, no match (HTTP 404)https://reco.ai/en/pricing – reached, no match (HTTP 404)https://reco.ai/pricing-plans – reached, no match (HTTP 404)
Is this wrong? Send us the URL
Across the market: Public pricing in Telecom and SaaS expense management: 7 of 22 companies
✗
No third-party tracking before consent
weight 2 of 3
Third-party requests seen on the first load, before any interaction.
- Third-party hosts we saw on the first load 39 6sc.co, 6sense.com, adnxs.com, amazonaws.com, bidr.io, bing.com, clarity.ms, claydar.com, cloudflare.com, cloudfront.net, doubleclick.net, facebook.com, facebook.net, factors.ai, g2.com, g2crowd.com, google.com, google.de, googleapis.com, googletagmanager.com, gstatic.com, hs-analytics.net, hs-banner.com, hs-scripts.com, hsadspixel.net, hsforms.com, hsforms.net, hubapi.com, hubspot.com, iubenda.com, jscloud.net, knock-ai.com, lfeeder.com, licdn.com, linkedin.com, on.aws, trendemon.com, unifyintent.com, website-files.com.
Show the 39 exact wordings
b.6sc.co, c.6sc.co, ipv6.6sc.co, j.6sc.co
Read at https://reco.ai/
epsilon.6sense.com
Read at https://reco.ai/
secure.adnxs.com
Read at https://reco.ai/
s3-us-west-2.amazonaws.com
Read at https://reco.ai/
cnv.event.prod.bidr.io
Read at https://reco.ai/
c.bing.com
Read at https://reco.ai/
c.clarity.ms, q.clarity.ms, scripts.clarity.ms, www.clarity.ms
Read at https://reco.ai/
api.claydar.com, cdn.claydar.com, static.claydar.com
Read at https://reco.ai/
cdnjs.cloudflare.com
Read at https://reco.ai/
d3e54v103j8qbb.cloudfront.net
Read at https://reco.ai/
ad.doubleclick.net, googleads.g.doubleclick.net, stats.g.doubleclick.net
Read at https://reco.ai/
www.facebook.com
Read at https://reco.ai/
connect.facebook.net
Read at https://reco.ai/
api.factors.ai, app.factors.ai
Read at https://reco.ai/
tracking-api.g2.com
Read at https://reco.ai/
tracking.g2crowd.com
Read at https://reco.ai/
region1.analytics.google.com, www.google.com
Read at https://reco.ai/
www.google.de
Read at https://reco.ai/
ajax.googleapis.com, fonts.googleapis.com
Read at https://reco.ai/
www.googletagmanager.com
Read at https://reco.ai/
fonts.gstatic.com
Read at https://reco.ai/
js.hs-analytics.net
Read at https://reco.ai/
js.hs-banner.com
Read at https://reco.ai/
js.hs-scripts.com
Read at https://reco.ai/
js.hsadspixel.net
Read at https://reco.ai/
forms-na1.hsforms.com, forms.hsforms.com, perf-na1.hsforms.com
Read at https://reco.ai/
js.hsforms.net
Read at https://reco.ai/
api.hubapi.com
Read at https://reco.ai/
cta-service-cms2.hubspot.com, js.hubspot.com, track.hubspot.com
Read at https://reco.ai/
cdn.iubenda.com, embeds.iubenda.com
Read at https://reco.ai/
jscloud.net
Read at https://reco.ai/
ca.knock-ai.com, js.knock-ai.com
Read at https://reco.ai/
sc.lfeeder.com, tr-rc.lfeeder.com
Read at https://reco.ai/
snap.licdn.com
Read at https://reco.ai/
px.ads.linkedin.com
Read at https://reco.ai/
sl-11a463aaedf44600a99367660fd6fa70.ecs.us-east-1.on.aws
Read at https://reco.ai/
assets.trendemon.com, trackingapi.trendemon.com
Read at https://reco.ai/
api.unifyintent.com, tag.unifyintent.com
Read at https://reco.ai/
cdn.prod.website-files.com
Read at https://reco.ai/
Checked 1 address on 2026-10-16.
Show the 1 address we checked
https://reco.ai/ – third-party requests before any interaction: ad.doubleclick.net, ajax.googleapis.com, api.claydar.com, api.factors.ai, api.hubapi.com, api.unifyintent.com, app.factors.ai, assets.trendemon.com, b.6sc.co, c.6sc.co, c.bing.com, c.clarity.ms, ca.knock-ai.com, cdn.claydar.com, cdn.iubenda.com, cdn.prod.website-files.com, cdnjs.cloudflare.com, cnv.event.prod.bidr.io, connect.facebook.net, cta-service-cms2.hubspot.com, d3e54v103j8qbb.cloudfront.net, embeds.iubenda.com, epsilon.6sense.com, fonts.googleapis.com, fonts.gstatic.com, forms-na1.hsforms.com, forms.hsforms.com, googleads.g.doubleclick.net, ipv6.6sc.co, j.6sc.co, js.hs-analytics.net, js.hs-banner.com, js.hs-scripts.com, js.hsadspixel.net, js.hsforms.net, js.hubspot.com, js.knock-ai.com, jscloud.net, perf-na1.hsforms.com, px.ads.linkedin.com, q.clarity.ms, region1.analytics.google.com, s3-us-west-2.amazonaws.com, sc.lfeeder.com, scripts.clarity.ms, secure.adnxs.com, sl-11a463aaedf44600a99367660fd6fa70.ecs.us-east-1.on.aws, snap.licdn.com, static.claydar.com, stats.g.doubleclick.net, tag.unifyintent.com, tr-rc.lfeeder.com, track.hubspot.com, tracking-api.g2.com, tracking.g2crowd.com, trackingapi.trendemon.com, www.clarity.ms, www.facebook.com, www.google.com, www.google.de, www.googletagmanager.com
Is this wrong? Send us the URL
Across the market: No third-party tracking before consent in Telecom and SaaS expense management: 1 of 22 companies
✗
Notice before subprocessors change
weight 2 of 3
No commitment to give notice before subprocessors change found.
Checked 8 addresses on 2026-10-16.
Show the 8 addresses we checked
https://reco.ai/legal/subprocessors – reached, no match (HTTP 404)https://reco.ai/subprocessors – reached, no match (HTTP 404)https://reco.ai/sub-processors – reached, no match (HTTP 404)https://reco.ai/legal/dpa – reached, no match (HTTP 404)https://reco.ai/dpa – reached, no match (HTTP 404)https://reco.ai/legal/data-processing-agreement – reached, no match (HTTP 404)https://reco.ai/trust/subprocessors – reached, no match (HTTP 404)https://reco.ai/legal/sub-processors – reached, no match (HTTP 404)
Is this wrong? Send us the URL
Across the market: Notice before subprocessors change in Telecom and SaaS expense management: 4 of 22 companies
✗
Uptime SLA with a figure
weight 1 of 3
No uptime figure found.
Checked 6 addresses on 2026-10-16.
Show the 6 addresses we checked
https://reco.ai/legal/sla – reached, no match (HTTP 404)https://reco.ai/sla – reached, no match (HTTP 404)https://reco.ai/legal/service-level-agreement – reached, no match (HTTP 404)https://reco.ai/trust/sla – reached, no match (HTTP 404)https://reco.ai/uptime – reached, no match (HTTP 404)https://reco.ai/legal/uptime-sla – reached, no match (HTTP 404)
Is this wrong? Send us the URL
Across the market: Uptime SLA with a figure in Telecom and SaaS expense management: 0 of 22 companies