Subprocessors

Robovue uses the third parties below to provide the service. Before adding a new one, we’ll give at least 30 days’ notice by updating this page and emailing workspace Admins. A customer can object as described in section 7 of our Data Processing Agreement.

Hosting and infrastructure

• Amazon Web Services EMEA SARL, London, UK (eu-west-2).
  • Purpose: hosting the application, the database, file storage for run attachments, sign-in, outbound email, secrets and logs.
  • Data: all customer and account data.
• Cloudflare, Inc., global edge network.
  • Purpose: DNS, TLS, DDoS protection and content delivery in front of the app, and hosting this website.
  • Data: all traffic to the app and this site passes through it, including IP addresses.

Service providers

• Stripe, including Link, its reseller service.
  • Purpose: subscriptions, checkout and the billing portal. Link is the seller of record for each payment, and handles VAT and sales tax.
  • Data: billing contact details, billing address and payment details, which Link collects directly (Robovue never sees card numbers), plus your workspace ID.
• Functional Software, Inc. (Sentry), EU (Germany).
  • Purpose: tracking application errors.
  • Data: error reports, meaning stack traces and request metadata. We don’t send it personal details by default.
• Zoho Corporation B.V., EU.
  • Purpose: the mailboxes for our robovue.co.uk addresses, such as contact@ and security@.
  • Data: emails you send us, including feedback submitted in the app and security reports.

Connections you set up to your own systems (a UiPath Orchestrator, an Automation Anywhere Control Room, or Power Automate) aren’t subprocessors. They’re your systems, and Robovue connects to them because you tell it to.

Alert channels you add (a Slack channel, a Microsoft Teams channel or chat, or an outgoing webhook) aren’t subprocessors either. You create them in your own Slack workspace, Microsoft 365 tenant or system, under your own agreement with that provider, and Robovue sends alerts to them because you tell it to. Each alert carries a bot’s name, its status and a failure summary.

UptimeRobot checks that Robovue is up and runs the public status page. It receives no data, so it isn’t a subprocessor either.

Healthchecks.io checks that Robovue’s background jobs, such as the one that spots overdue bots, are still running. Robovue sends it a bare signal that a job ran, with no data, so it isn’t a subprocessor either.

Last updated: 2026-10-23.