Blindsight Sub-processors
blindsight.io/platform/legal/subprocessors
This document covers the Blindsight platform (the console, the desktop apps and the APIs). The blindsight.io website has its own privacy policy.
1. About this list
Blindsight Technologies AG, Rennweg 57, 8001 Zurich, Switzerland (UID CHE-484.046.837) ("Blindsight") provides a desktop agent and a hosted platform. When a customer ("Customer") uses the product, Blindsight processes Customer Personal Data on the Customer's behalf and acts as processor under the data processing agreement at https://blindsight.io/platform/legal/dpa (the "DPA"; clause 10.1 of the Blindsight Endpoint Licence Agreement). To do so, Blindsight uses the providers listed in Table A. These are the sub-processors under the DPA, and Annex 3 of the DPA lists the same providers.
This page also lists, for transparency, services a Customer may choose to connect (Table B), providers that support the product but do not receive Customer Personal Data (Table C), and providers Blindsight uses as controller for its own business (section 5), which are described in the privacy notice at https://blindsight.io/platform/legal/privacy.
Notice of changes. Blindsight will tell the Customer's administrators by e-mail, and will update this page, at least 30 days before a new sub-processor starts to process Customer Personal Data, or before an existing one is given a materially wider scope or a new location (DPA clause 6.2). The Customer may object within that period as DPA clause 6.3 provides.
2. Table A: Sub-processors for Customer Personal Data
These providers receive Customer Personal Data in the product. "Always" means the provider is part of the standard service. "Only if" means the provider receives data only when the stated feature is switched on for the Customer's workspace.
| Provider (legal entity) | Service and purpose | Categories of data | Location of processing | Transfer mechanism | When used |
|---|---|---|---|---|---|
| Amazon Web Services EMEA SARL (Luxembourg) | Hosting of the platform: compute, database, cache, file and object storage, encryption keys, logs, network and web-application firewall | All data held in a workspace: administrator and user accounts, device and fleet data, prompt and file inspection records (including redacted prompt, reply and file text, kept by default), audit records, uploaded documents and datasets | Ireland | None needed: inside the EEA, which Switzerland recognises as adequate | Always |
| Amazon Web Services EMEA SARL (as above), Amazon Simple Email Service | Sends product e-mails (invitations, password and sign-in links, alert e-mails to addresses the Customer configures, in-app help and bug reports to Blindsight support) | Recipient and sender e-mail addresses, names, message content and attachments of those e-mails | Ireland | None needed (as above) | Always (default sending method) |
| Amazon Web Services EMEA SARL (as above), Amazon Bedrock, with a hosted language model served by AWS | Reads a written AI policy that an administrator uploads and turns it into rules (policy import); judges, for topic rules, whether a short excerpt of the redacted prompt breaks a rule the Customer wrote; writes example sentences for a topic rule from the rule and the examples the Customer's administrators give | Policy import: the text of the uploaded policy document, kept only for the import run. Topic rules: a short excerpt of the redacted prompt text, not stored by Blindsight after the decision; topic rule text and examples. The text can still contain personal data that redaction did not catch | Ireland only, so no workspace can use another region | None needed: inside the EEA | Only for a workspace that imports a policy document or defines topic rules |
| Microsoft Ireland Operations Limited (Microsoft 365 mailboxes) | Hosting the Blindsight mailboxes (support@, info@, legal@, security@), which receive Customer Personal Data when a console user submits in-app help or a bug report, or a Customer writes to Blindsight | The report or e-mail, the sender's name and e-mail address (unless the workspace hides identities), and attachments, which can contain Customer Personal Data | European Union and EFTA, under Microsoft's EU Data Boundary; under Microsoft's product terms certain inactive data is stored in Portugal | Data stored in the EU and EFTA under the EU Data Boundary; transfers outside the EU that the EU Data Boundary still allows are governed by Microsoft's data protection terms | When Customer Personal Data reaches Blindsight through support e-mails, attachments and bug reports |
Sub-processor staff and Blindsight staff: Blindsight's own personnel access the platform only as described in the DPA and the technical and organisational measures, and only from Switzerland and the European Economic Area.
3. Table B: Services the Customer chooses to connect
These are not Blindsight sub-processors. Data goes to them only because the Customer, or an administrator acting for the Customer, connects them or configures them as a destination. The Customer's own agreement with each provider applies to that data. Each integration is off until the Customer sets it up.
| Service the Customer connects | What it is used for | Data that goes there, on the Customer's instruction |
|---|---|---|
| Microsoft Entra ID, Microsoft Graph, Microsoft Intune, Microsoft 365 (activity records of Microsoft's AI assistant) | Single sign-on, directory synchronisation, reading device inventory, deploying the agent app, reading AI assistant activity | Sign-in tokens and group membership; user and group records read from the Customer's tenant; device inventory read; the agent package pushed to the Customer's tenant |
| Google sign-in (OpenID Connect) | Single sign-on for the Customer's users | Sign-in tokens and identity claims |
| Okta and other identity providers using SCIM or OpenID Connect | Provisioning and sign-in | User and group records the Customer's provider sends to the platform; sign-in tokens |
| Alert destinations: webhook, Slack, Microsoft Teams, e-mail, syslog, Splunk HTTP Event Collector, Microsoft Sentinel | Delivery of alerts and exports to the Customer's own security tooling | Alert content as configured, which can include user names unless the workspace hides identities |
| Managed service provider (MSP) integrations: the same destinations, plus ticketing | A Customer that is an MSP routes its clients' alerts to its own tools | Alert content for the MSP's clients, to the MSP's own endpoints. The MSP is a separate party for its clients |
| AI providers the Customer already uses (for example when the Customer routes its own AI traffic through the platform's inspection proxy) | The Customer's own calls to the AI providers it chose, inspected on the way | The Customer's own requests, forwarded to the provider the Customer named. Blindsight does not choose or contract this provider |
| Public dataset sites | Importing a public dataset by reference into the data-security scanner, when an administrator requests it | The dataset reference and the access token the administrator supplies |
| The Customer's own document stores read for retrieval-augmented generation scanning | Scanning the Customer's own corpora | Documents read from the Customer's store, under credentials the Customer provides |
4. Table C: Other providers that do not receive Customer Personal Data
| Provider | Role | Why it is not a sub-processor for Customer Personal Data |
|---|---|---|
| Keygen | Licence validation and issuing | The platform sends Keygen only the workspace's licence key and aggregate usage counters. No names, e-mail addresses, prompts, device or user data. Keygen also holds the billing contact for Blindsight's own licensing, which is Blindsight's controller data (section 5). Keygen states that its main servers are in the United States. |
| Amazon Web Services' content delivery network, operated by Blindsight as downloads.blindsight.io | Distribution of installers, update manifests and model files to devices | Files and manifests only; the download network holds no Customer Personal Data. A device that fetches an update connects to that network, so its IP address reaches AWS there, as in any web download, under the AWS data processing terms; no other customer data does |
| Public internet sources (for example public domain registration records) | Classification of web hosts that are not yet known | Only a host name or domain is sent, never a workspace, device or person |
| Publishers of public network reference data | The desktop agent downloads public reference data that it needs to operate | A plain download initiated by the device. No Customer Personal Data is sent beyond the device's IP address, which any web request reveals |
5. Providers used by Blindsight as controller
These providers process personal data for Blindsight's own purposes (billing, licensing and support). They are described in the Blindsight privacy notice, not here. One line each:
- Stripe (Stripe Payments Europe, Ltd. and Stripe, Inc.): card and invoice payments for self-serve subscriptions, through a separate licence console; Stripe collects payer name, billing address, tax identifier and payment details at checkout, and acts as a separate controller for payment processing under its own terms.
- Keygen, United States: licence records, including the Customer's billing contact name and e-mail address where Blindsight creates a Keygen user for the account. Safeguard: the European Commission's Standard Contractual Clauses (Implementing Decision (EU) 2021/914), which Keygen's terms incorporate (https://keygen.sh/terms/, section 12).
- Amazon Web Services EMEA SARL, Ireland: hosting of the licence console, its database and backups.
- Fonts: the platform console and the licence console serve their fonts from Blindsight's own servers, so no font request goes to a third party.
- Providers used for the blindsight.io website (hosting, forms, analytics, consent and mail) are listed in the website's own privacy notice at https://blindsight.io/privacy.