Skip to the document
Contact
// Platform legal

Blindsight Data Processing Agreement

Version 1.0 · Effective 19 November 2026

blindsight.io/platform/legal/dpa

This document covers the Blindsight platform (the console, the desktop apps and the APIs). The blindsight.io website has its own privacy policy.


1. Parties, scope and precedence

1.1 This Data Processing Agreement (the "DPA") is made between Blindsight Technologies AG, Rennweg 57, 8001 Zurich, Switzerland, UID CHE-484.046.837 ("Blindsight"), and the Customer named in, or accepting, the Blindsight Endpoint Licence Agreement (the "EULA").

1.2 The DPA forms part of the EULA (EULA clause 10.1) and of the Service Terms (as defined in the EULA). It applies to all personal data that Blindsight processes on behalf of the Customer in providing the Service ("Customer Personal Data"). It does not apply to the contact, account, sign-in, licensing and billing data of the Customer's administrators, other users of the Blindsight console and contacts, which Blindsight processes as a controller as described in its privacy notice at https://blindsight.io/platform/legal/privacy (EULA clause 10.2). Customer Personal Data does not include that data.

1.3 The Customer is the controller of Customer Personal Data or, where the Customer processes it for its own controller, a processor. Blindsight is the processor or, respectively, the sub-processor. Where the Customer is a processor, it confirms that its own controller has authorised the instructions it gives under this DPA and the engagement of Blindsight and of the sub-processors in Annex 3, and the Customer passes on to Blindsight any instruction of that controller that is relevant.

1.4 The Software processes data on the Customer's devices (for example detection and redaction of personal data in traffic to AI services). That processing is the Customer's own processing, carried out with the Customer's installation of the Software, and is not processing by Blindsight. Blindsight is a processor for the data that reaches the Service, as described in Annex 1.

1.5 If this DPA conflicts with the EULA or the Service Terms, this DPA prevails for the processing of personal data, in accordance with EULA clause 20.1(c). An addendum under EULA clause 17 prevails over this DPA. Clause 13 (liability) and clause 14 (law and courts) of this DPA follow the EULA as stated there.

1.6 This DPA forms part of the EULA (EULA clause 10.1), and the Customer accepts it when it accepts the EULA in any of the ways set out in EULA clause 1.2, or when it signs an order form or other agreement that refers to this DPA. The console records the version and the hash of the DPA accepted. Signed copies are available on request.

2. Definitions

2.1 "GDPR" means Regulation (EU) 2016/679. "FADP" means the Swiss Federal Act on Data Protection of 25 September 2020 (SR 235.1) and its ordinances. "Applicable Data Protection Law" means the GDPR, the FADP and any other law on the protection of personal data that applies to the processing of Customer Personal Data under this DPA.

2.2 "Controller", "processor", "personal data", "processing", "data subject", "personal data breach", "supervisory authority" and "special categories of personal data" have the meanings given in the GDPR. Under the FADP they include the corresponding terms ("controller", "processor", "personal data", "processing", "data subject", "breach of data security", "sensitive personal data") and the Federal Data Protection and Information Commissioner ("FDPIC").

2.3 "Sub-processor" means a third party that Blindsight engages to process Customer Personal Data.

2.4 "Restricted Transfer" means a transfer of Customer Personal Data (a) from Switzerland to a country outside Switzerland that is not recognised as providing adequate protection under the FADP, or (b) from the EEA to a country outside the EEA that is not recognised as providing adequate protection under the GDPR, in each case including onward transfer.

2.5 "Authorised Users", "Customer Data", "Service", "Software" and "Documentation" have the meanings given in the EULA.

3. Roles and instructions

3.1 Blindsight processes Customer Personal Data only on the Customer's documented instructions (GDPR Art. 28(3)(a); FADP Art. 9), including as to transfers. The EULA, the Service Terms, this DPA, the Customer's order, the Customer's configuration of the Service and the Documentation are the Customer's complete documented instructions at the date of acceptance. The Customer may give further instructions in writing (including by e-mail or through settings in the console) that are consistent with the Service. If a further instruction requires work or cost beyond the Service, the parties will agree it first.

3.2 The Customer's configuration of the Service is an instruction. This includes whether text may leave devices, whether text is kept, how identities are shown, retention periods, the AI services inspected, policy import and topic rules (which use a hosted language model service in Ireland only), and the integrations and alert destinations that the Customer connects.

3.3 Blindsight will inform the Customer immediately if, in its opinion, an instruction infringes Applicable Data Protection Law (GDPR Art. 28(3), final subparagraph). Blindsight may suspend carrying out that instruction until the Customer confirms or changes it.

3.4 Blindsight will not process Customer Personal Data for its own purposes. In line with EULA clause 10.3, Blindsight does not use the text of prompts, replies or files processed for the Customer to train models or for any other purpose of its own. Blindsight may use technical operating data and aggregated information that does not identify the Customer, any Authorised User or any other person, as EULA clause 10.3 provides. Where EU, Member State or Swiss law to which Blindsight is subject requires Blindsight to process Customer Personal Data otherwise, Blindsight will tell the Customer of that legal requirement before the processing, unless that law forbids it on important grounds of public interest (GDPR Art. 28(3)(a)).

3.5 The Customer is responsible for the matters in EULA clause 8.2, in particular for having a lawful basis, for informing Authorised Users and others concerned, for consulting works councils and staff representatives where required, and for its own policy settings. The Customer warrants that its instructions and its use of the Service comply with Applicable Data Protection Law.

3.6 Annex 1 describes the processing and is part of the Customer's instructions.

4. Confidentiality of personnel

4.1 Blindsight ensures that the persons it authorises to process Customer Personal Data are bound by a duty of confidentiality, by contract or by law, that continues after their engagement ends (GDPR Art. 28(3)(b)).

4.2 Blindsight gives its personnel access to Customer Personal Data only to the extent needed to provide, secure and support the Service. Blindsight staff access Customer Personal Data only from Switzerland and the European Economic Area. Privileged administrative access to the hosting environment is limited to authorised Blindsight personnel who need it for their role, and to automated deployment processes. Blindsight manages the encryption keys of the Service, so personnel with privileged administrative access can technically access Customer Personal Data; they may do so only as this clause allows. Support access to Customer Personal Data held in the Service takes place only on the Customer's request or with its permission, or where needed to resolve a security incident or a fault in the Service.

4.3 Banking and professional secrecy.

(a) Where the Customer is bound by a statutory duty of professional secrecy, in particular banking secrecy under Art. 47 of the Swiss Banking Act, Blindsight acknowledges that Customer Data may contain information protected by that duty. This includes information about the Customer's clients, whether they are natural persons or legal entities, and whether or not that information is personal data.

(b) Blindsight undertakes, for itself and its personnel, to keep that information secret, to use it only to provide the Service, and not to disclose it except as this DPA allows or as paragraph (c) provides. Blindsight requires each Sub-processor, by contract, to keep Customer Data confidential. The duty of a Sub-processor is the confidentiality duty in its contract with Blindsight; Blindsight does not promise that a Sub-processor owes the Customer the same duty of secrecy as the Customer's own.

(c) Blindsight will disclose that information to an authority or court only where Swiss law, or a binding order recognised in Switzerland, requires it, and only to the extent required. Where the law allows, Blindsight will tell the Customer before it discloses, so that the Customer can respond. This paragraph prevails over clause 3.4 and over EULA clause 11.2 for that information.

(d) This undertaking has no time limit. It continues after this DPA and the EULA end, and the five-year limit in EULA clause 11.3 does not apply to it.

5. Security

5.1 Blindsight implements the technical and organisational measures in Annex 2, taking into account the state of the art, the costs, the nature, scope, context and purposes of the processing and the risks to data subjects (GDPR Arts. 28(3)(c) and 32; FADP Art. 8; Arts. 1 to 3 of the Data Protection Ordinance, SR 235.11, and its Arts. 4 and 5 where their conditions are met). Blindsight may change those measures if the change does not lower the overall level of protection, and will update Annex 2 for material changes.

5.2 The Customer is responsible for the security of its own devices, networks, identities and console accounts, for the roles and permissions it grants in the console, and for using the controls in Annex 2, part 9, appropriately for the data it handles.

5.3 Blindsight provides information about its security assessments and any certifications on request (clause 11.2).

6. Sub-processors

6.1 The Customer gives Blindsight a general authorisation to engage Sub-processors (GDPR Art. 28(2); FADP Art. 9(3) and Art. 7 of the Data Protection Ordinance), on the conditions in this clause. The Sub-processors engaged at the date of this DPA are in Annex 3. The current list is published at https://blindsight.io/platform/legal/subprocessors.

6.2 Blindsight will give the Customer's administrators notice by e-mail, and will update the published list, at least 30 days before (a) a new Sub-processor starts to process Customer Personal Data, or (b) an existing Sub-processor is given a materially wider scope or a new location. The Customer is responsible for keeping an administrator e-mail address current.

6.3 The Customer may object to the change on reasonable data protection grounds by written notice within that period, stating the grounds. The parties will discuss the objection in good faith. If it is not resolved within 30 days after the objection, and Blindsight does not offer a reasonable alternative (for example, not using the new Sub-processor for the Customer, or a setting that removes the Customer's data from it), the Customer may terminate the affected part of the Service by written notice. Blindsight will refund the prepaid fees for the remainder of the Subscription Term for the affected part, pro rata. Until termination takes effect, Blindsight will not use the new Sub-processor for the Customer Personal Data concerned, where the Service allows that data to be kept apart. Where the change is needed urgently for security or to meet a legal duty, Blindsight may make it earlier, will tell the Customer at once, and the Customer's rights to object and terminate continue.

6.4 Blindsight enters into a written contract with each Sub-processor that imposes data protection obligations no less protective than those in this DPA, including the technical and organisational measures appropriate to the processing, and, for Restricted Transfers, the safeguards in clause 7 (GDPR Art. 28(4)).

6.5 Blindsight remains fully liable to the Customer for the performance of its Sub-processors' obligations, subject to EULA clause 13 and clause 13 of this DPA.

6.6 Services that the Customer itself chooses to connect (for example identity providers, directory and device-management services, alert destinations such as webhook, chat, e-mail, syslog or security-information tools, and AI services the Customer uses) are not Sub-processors of Blindsight. Data sent to them is sent on the Customer's instruction and under the Customer's own agreement with each provider. The Customer is responsible for those integrations.

7. International transfers

7.1 Blindsight hosts the Service in the EEA: production data is held by Amazon Web Services in Ireland, which Switzerland recognises as providing adequate protection (Annex 1 of the Data Protection Ordinance). Blindsight is established in Switzerland, which the European Commission recognises as providing adequate protection (Decision 2000/518/EC). Customer Personal Data that Blindsight accesses or processes in Switzerland or the European Economic Area is therefore not a Restricted Transfer from the EEA. The exceptions are the Microsoft 365 mailboxes described in Annex 3 (stored in the EU and EFTA under the EU Data Boundary, with the limited transfers that it allows), the IP address of a device that fetches updates, which reaches Amazon Web Services' content delivery network, under the AWS data processing terms (Annex 1, part 10), and integrations the Customer connects (clause 7.4).

7.2 Blindsight will not carry out, and will not allow a Sub-processor to carry out, a Restricted Transfer unless one of the following applies: (a) the receiving country or recipient is covered by an adequacy decision or equivalent recognition under Applicable Data Protection Law, including the EU-U.S. Data Privacy Framework and the Swiss-U.S. Data Privacy Framework where the recipient is certified and the certification covers the data; or (b) the transfer is covered by the standard contractual clauses in Commission Implementing Decision (EU) 2021/914 (the "SCCs"), with the amendments for Switzerland required by the FDPIC (so that references to the GDPR are read as references to the FADP for transfers governed by the FADP, the term "Member State" is not interpreted so as to exclude data subjects with their habitual residence in Switzerland from bringing claims there under Clause 18(c), Swiss courts are an alternative forum for those data subjects, and the FDPIC is named in Annex I.C as the competent supervisory authority for transfers governed by the FADP); or (c) another safeguard that Applicable Data Protection Law recognises applies.

7.3 Where the SCCs apply between the parties, they are incorporated as follows: Module Two (controller to processor) or Module Three (processor to processor), as the Customer's role requires; the option in clause 7 (docking clause) applies; for clause 9 option 2 (general written authorisation) applies with the notice period in clause 6.2 of this DPA; the optional wording in clause 11 does not apply; for clause 17 option 1 applies and the governing law is the law of Ireland; for clause 18 the courts of Ireland; Annexes I to III of the SCCs are completed by Annexes 1 to 3 of this DPA. Where the SCCs apply, they prevail over this DPA, the EULA and the Service Terms if they conflict, and nothing in those documents modifies them (SCC Clauses 2(a) and 5).

7.4 The Customer's choices of integration or destination are the Customer's instruction. The hosted language model service runs in Ireland only, so a workspace cannot send data to it in another region. If the Customer connects an integration or alert destination located outside Switzerland and the EEA (clause 6.6), the transfer to it is made on the Customer's instruction under the Customer's own agreement with that provider, and the Customer is responsible for its lawfulness.

7.5 Blindsight will tell the Customer without undue delay if it can no longer comply with this clause 7, for example because a safeguard is invalidated. The Customer may then suspend the transfer concerned.

8. Assistance with data subject rights

8.1 Taking into account the nature of the processing, Blindsight will assist the Customer by appropriate technical and organisational measures, so far as possible, in answering requests from data subjects to exercise their rights under Applicable Data Protection Law (GDPR Art. 28(3)(e), Chapter III; FADP Arts. 25 to 29 and 32). The console lets the Customer's administrators export the record the Service holds about one person or one device for an access request, and erase a console user together with the records linked to that user's account. The Customer should use these functions where they meet the request. Erasing a person who has no console account, or a person named inside stored prompt text, is not a console function and is done under clause 8.3.

8.2 If a data subject contacts Blindsight about Customer Personal Data, Blindsight will, so far as it can identify the Customer, refer the person to the Customer and tell the Customer without undue delay, and will not answer the request itself except to confirm the referral, unless the Customer instructs it or the law requires.

8.3 Where the Customer cannot meet a request with the functions of the Service, Blindsight will carry it out on written instruction, in a reasonable time. If the assistance requires effort beyond the functions of the Service and routine support, Blindsight may charge for it at its then current rates, after telling the Customer.

8.4 Where the Customer has turned on pseudonymised or aggregated identity display, pseudonymised data remains personal data. In the console, a pseudonymised person is re-identified only through the reveal function, which records who asked, who approved and when.

9. Personal data breaches

9.1 Blindsight will notify the Customer without undue delay, and at the latest within 48 hours, after becoming aware of a personal data breach affecting Customer Personal Data (GDPR Art. 33(2); FADP Art. 24(3)). Notice goes to the e-mail addresses of the Customer's administrators.

9.2 The notice will contain, so far as available at that time and in stages if necessary (GDPR Art. 33(3) and (4); Art. 15(1) and (2) of the Data Protection Ordinance): (a) the nature of the breach, including where possible its time and duration and the categories and approximate number of data subjects and of records concerned; (b) the name and contact details of the contact point at Blindsight; (c) the likely consequences; (d) the measures taken or proposed to address the breach and reduce its possible adverse effects.

9.3 Blindsight will take reasonable steps to contain and investigate the breach, will keep the Customer informed, and will cooperate with the Customer in meeting its duties to notify supervisory authorities and data subjects. The Customer decides whether and how to notify them. Blindsight will not notify a supervisory authority or data subject about a breach affecting the Customer without the Customer's prior approval, unless the law requires it.

9.4 Notice of a breach is not an acknowledgement of fault or liability.

9.5 Blindsight will also tell the Customer without undue delay of any security incident or outage that materially affects the confidentiality, integrity or availability of Customer Data in the Service, even where no personal data is affected.

10. Assistance with impact assessments and prior consultation

10.1 Blindsight will, on request and taking into account the nature of the processing and the information available to it, assist the Customer with its obligations under GDPR Arts. 32 to 36 and FADP Arts. 8, 22 and 23, including data protection impact assessments and prior consultation of a supervisory authority (GDPR Art. 28(3)(f)).

10.2 The Customer acknowledges that inspecting traffic to AI services on employees' devices is likely to require a data protection impact assessment, and that carrying it out is the Customer's duty (EULA clause 8.2(d)).

10.3 To support this, Blindsight makes available the Documentation, this DPA, the list in Annex 3 and the description in Annex 1 and Annex 2. The Service also generates, for the Customer to review and adapt before use, (a) a works-council pack that describes the processing for employee representatives, and (b) an employee notice, in the languages offered in the console. These documents describe the Service's functions and the Customer's settings. They are not legal advice, and the Customer remains responsible for their content and use.

11. Audits and information

11.1 Blindsight will make available to the Customer the information necessary to demonstrate compliance with this DPA and Article 28 GDPR, and will allow for and contribute to audits, including inspections, by the Customer or an auditor it appoints (GDPR Art. 28(3)(h)).

11.2 The Customer will first use the Documentation and Blindsight's written answers to reasonable questions and questionnaires, which Blindsight will give within 30 days.

11.3 If that information is not enough to show compliance, or if a supervisory authority or Applicable Data Protection Law requires it, the Customer may carry out an audit, remotely or on site at Blindsight's premises, at most once in any twelve months (unless a personal data breach affecting the Customer or a supervisory authority's request gives a reason for more), on at least 30 days' written notice, during business hours, in a way that does not unreasonably disturb Blindsight's operations or the data of its other customers. The auditor must be bound by confidentiality and not be a competitor of Blindsight. The scope and timing will be agreed in advance. The audit is at the Customer's cost, including a reasonable charge for Blindsight's time, unless it shows a material breach of this DPA by Blindsight, in which case Blindsight bears its own costs.

11.4 The audit will not extend to the data of other customers or to Sub-processors' facilities, except as the Sub-processor contract allows. Blindsight will pass on to the Customer the audit reports that a Sub-processor makes available to it where the Sub-processor contract allows.

11.5 Nothing in this clause limits the powers of a supervisory authority, including its right to audit and inspect Blindsight under Applicable Data Protection Law, and Blindsight will cooperate with them.

11.6 If the Customer is a regulated customer within EULA clause 17, the access, information and audit rights in the addendum under that clause apply in addition to and, where they conflict, instead of this clause 11.

12. Return and deletion

12.1 During the Subscription Term, the Customer can export its Customer Data and erase records using the functions of the Service, and can set the retention periods described in Annex 1.

12.2 At the end of the provision of the Service, Blindsight will, at the Customer's choice, return Customer Personal Data and delete it, or delete it (GDPR Art. 28(3)(g)). The Customer exercises the choice to have it returned by exporting it: after the EULA ends (EULA clause 15.3), the Customer may export its Customer Data for at least 30 days after the end, in a common machine-readable format through the console. The export period is at least 30 days after the end, whether the end is automatic or follows a revocation or suspension, as EULA clause 15.3(c) provides.

12.3 Blindsight will delete the remaining Customer Personal Data, including existing copies, from the Service within 30 days after the end of the export period, or earlier at the Customer's written request after it has exported its data, and will confirm the deletion to the Customer on request. Blindsight records the date the export period closed and the date the deletion was completed.

12.4 Copies in backups and logs are not deleted individually. Database backups and snapshots are kept for no more than 35 days and then deleted, so Customer Personal Data in them is gone no later than 35 days after its deletion from the Service. Logs that can contain identifiers such as e-mail and IP addresses are kept for no more than 365 days. Blindsight will not restore Customer Personal Data from a backup or snapshot except to recover the Service, in which case it will repeat the deletion.

12.5 Audit records of the Customer's workspace (actions in the console, with the actor, IP address and user agent) are Customer Personal Data and are deleted with the workspace under clause 12.3. During the Subscription Term they follow the workspace's audit retention setting (clause 9 of Annex 1). When a person is erased, the personal fields in the hash-chained audit trail are redacted. Where EU, Member State or Swiss law requires retention, Blindsight may keep what it must, and will protect it under this DPA and process it only for that purpose.

12.6 Blindsight may keep Customer Personal Data after the end only to the extent that EU, Member State or Swiss law requires, and will tell the Customer which law, unless the law forbids it.

12.7 The Software is the Customer's installation. When the licence ends, the Software behaves as EULA clause 4.2 describes. The Customer is responsible for uninstalling it (EULA clause 15.3(b)). Data stored on the Customer's devices by the Software, for example the local event store and the pseudonymisation vault, is the Customer's data on its own devices and is outside this clause 12. The Documentation describes what the Software keeps on a device and how it is removed.

13. Liability

13.1 The liability of each party under or in connection with this DPA is subject to the exclusions and limits in clause 13 of the EULA, which apply to this DPA together with the EULA and the Service Terms (EULA clause 13.3).

13.2 Nothing in this DPA or the EULA limits or excludes either party's liability to data subjects under Article 82 GDPR or equivalent mandatory law, or any liability that cannot be limited by law (EULA clause 13.1). Between the parties, the allocation of that liability under Article 82(5) GDPR is not affected.

13.3 Each party is responsible for its own fines. A fine imposed on one party because of the other party's breach of this DPA is a loss that the other party must bear, subject to clause 13.1 and EULA clause 13.

14. Term, governing law and courts

14.1 This DPA starts on acceptance (clause 1.6) and continues for as long as Blindsight processes Customer Personal Data, including during the export and deletion periods in clause 12. Clauses 9, 11, 12, 13 and 14 survive until the Customer Personal Data has been deleted. Clause 4.3 continues without time limit.

14.2 This DPA is governed by Swiss law, and the courts of Zurich have jurisdiction, in accordance with EULA clause 19 (including EULA clause 19.3 where it applies), except where mandatory law or the SCCs (clause 7.3) require otherwise. Data subjects keep their rights to enforce this DPA, or the SCCs, as those instruments provide, and their rights before a supervisory authority and the courts of their place of residence.

14.3 Blindsight may update this DPA to reflect a change in Applicable Data Protection Law, in a supervisory authority's guidance, or in the Service, in accordance with EULA clause 18. An update does not reduce the protection of Customer Personal Data.

14.4 This DPA is written in English. If it is translated, the English text prevails.


Annex 1: Description of the processing

1. Subject matter. Operation of the Blindsight hosted platform and console (the "Service") for the Customer, to protect personal data and confidential information when the Customer's staff and others use AI services from devices on which the Customer has installed the Software.

2. Duration. The Subscription Term, plus the export and deletion periods in clause 12.

3. Nature of the processing. Receiving, storing, analysing, displaying, exporting, transmitting to destinations that the Customer configures, and erasing (a) data that the Software on the Customer's devices sends to the Service, (b) text that the Customer's own applications send to the Service through its programming interface or software development kit for inspection, (c) datasets, documents and document stores that the Customer uploads or connects for scanning, and (d) data that the Customer's administrators enter or synchronise. The Service analyses the text it receives for security threats (for example prompt injection), sensitive information and the Customer's own rules. Blindsight's own detection models are operated by Blindsight within its hosting environment in Ireland; the hosted language model service in Annex 3 is used only for the functions stated there. The Service shows the Customer's reviewers per-person counts of allowed, flagged, redacted and blocked requests over a period, and shows managers those counts for their own reports, unless the Customer chooses pseudonymised or aggregated identity display.

4. Purpose. To provide the Service to the Customer under the EULA and the Service Terms: enrolling and monitoring the health of devices; applying the Customer's policy; recording findings and actions; showing them to the Customer's authorised administrators; alerting; compliance reporting; support; and the security and operation of the Service. The Service is not designed to evaluate the performance or behaviour of individuals (EULA clause 8.3).

5. Data subjects.

6. Categories of personal data.

7. Special categories and criminal-offence data. The Service does not look for special categories of personal data as such, but the text of prompts, replies and files may contain them (for example health, trade-union membership, religion, biometric or criminal-conviction data), because the Customer's staff write what they write. The Customer controls this through its policy (which services are inspected and what is blocked or redacted), through whether text leaves devices and whether it is kept, and through its rules for staff. The Customer must not instruct Blindsight to process special categories except as its policy and Applicable Data Protection Law allow.

8. Frequency. Continuous while the Software is active (regular device heartbeats, event records when AI services are used, console use).

9. Retention. Every workspace has retention on by default, and the Customer controls the periods within the limits of the product. Prompt records (the event, the encrypted text, embeddings and labels), with alert deliveries and host findings, are kept for 90 days by default (the Customer can set 7 to 3,650 days). Counts, with identity reveal records and retention run records, are kept for 400 days by default (30 to 3,650 days). Audit records are kept for seven years (2,555 days) by default (365 to 3,650 days). Device timelines are kept for 30 days and diagnostic bundles for 30 days. Datasets, documents and their scan results are kept until the Customer deletes them. Imported policy documents are kept only for the import run. Support reports and attachments stored in the platform are kept for 24 months after closure. The copies that reach Blindsight's mailboxes (Annex 3) are kept two years after the last message in the thread in the support@ mailbox, three years in security@ and ten years in legal@, and are then deleted. After the end of the contract, clause 12 applies.

10. Hosting and locations. Amazon Web Services, Ireland. The hosted language model service, where used, runs in Ireland only. Installers, update manifests and model files are delivered through Amazon Web Services' content delivery network, under the AWS data processing terms. A device that fetches an update connects to that network, so its IP address reaches AWS there; no other Customer Personal Data does. Support e-mails and bug reports that reach Blindsight are held in Microsoft 365 mailboxes (Annex 3). Support and engineering by Blindsight personnel take place in Switzerland and the European Economic Area. Privileged administrative access is limited as described in clause 4.2. See Annex 3 for Sub-processors.


Annex 2: Technical and organisational measures

Blindsight applies the measures below.

1. On-device minimisation (done by the Software on the Customer's devices).

2. Transport.

3. Encryption at rest.

4. Access control and authentication.

5. Tenant isolation.

6. Logging and audit trail.

7. Availability and backups.

8. Vulnerability and update management.

9. Customer-configurable controls.

10. Organisational measures. Confidentiality undertakings of personnel (clause 4); Sub-processor management (clause 6); a process for personal data breaches (clause 9).


Annex 3: Sub-processors

The binding list is the one published at https://blindsight.io/platform/legal/subprocessors, which is kept in line with the table below.

Sub-processorService and purposeDataLocationTransfer mechanismWhen 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 firewallAll data held in a workspaceIrelandNone needed: inside the EEA, which Switzerland recognises as adequateAlways
Amazon Web Services EMEA SARL (as above), Amazon Simple Email ServiceProduct e-mails (invitations, sign-in and password links, alerts to addresses the Customer sets, in-app help and bug reports sent to Blindsight support)Recipient and sender addresses, names, message content and attachmentsIrelandNone needed (as above)Always (default sending method)
Amazon Web Services EMEA SARL (as above), Amazon BedrockA hosted language model that reads a policy document the Customer 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; and writes example sentences for a topic rule from the rule and the examples the Customer's administrators giveThe uploaded policy text (kept only for the import run); the redacted excerpt (not stored by Blindsight after the decision), which can still contain personal data that redaction did not catch; topic rule text and examplesIreland onlyNone needed: inside the EEAOnly 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 BlindsightThe report or e-mail, the sender's name and e-mail address (unless the workspace hides identities), and attachments, which can contain Customer Personal DataEuropean Union and EFTA, under Microsoft's EU Data Boundary; under Microsoft's product terms certain inactive data is stored in PortugalData 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 termsWhen Customer Personal Data reaches Blindsight by support e-mail, attachment or bug report

Blindsight's other providers that do not receive Customer Personal Data (for example licence validation, which receives only the workspace licence key and aggregate counters, and the download network for installers and model files), the providers Blindsight uses for its own controller data, and the services the Customer connects itself are listed on the published page for information and are not Sub-processors. Amazon Web Services' content delivery network, which delivers installers, updates and model files, receives only the IP address of a device that fetches them, under the AWS data processing terms (Annex 1, part 10).


Annex 4: Mapping of Article 28(3) GDPR and FADP requirements to this DPA

RequirementReferenceClause
Subject matter, duration, nature, purpose, data types, data subjectsGDPR Art. 28(3)Annex 1
Processing only on documented instructions, including transfersGDPR Art. 28(3)(a); FADP Art. 9(1)3, 7
Notice if an instruction infringes lawGDPR Art. 28(3), last subparagraph3.3
Confidentiality of persons authorised to processGDPR Art. 28(3)(b)4
Security measuresGDPR Arts. 28(3)(c), 32; FADP Art. 85, Annex 2
Conditions for engaging another processorGDPR Art. 28(2), (3)(d), (4); FADP Art. 9(3); Data Protection Ordinance Art. 76, Annex 3
Assistance with data subject requestsGDPR Art. 28(3)(e); FADP Arts. 25 to 29 and 328
Assistance with security, breach notification, DPIA, prior consultationGDPR Art. 28(3)(f), Arts. 32 to 36; FADP Arts. 22 to 245, 9, 10
Return or deletion at the end, at the controller's choiceGDPR Art. 28(3)(g)12
Controller's obligations and rightsGDPR Art. 28(3), first subparagraph3.5, 6.3, 11
Information and auditsGDPR Art. 28(3)(h)11
Transfers outside Switzerland and the EEAGDPR Chapter V; FADP Arts. 16, 177
Breach notification by the processorGDPR Art. 33(2); FADP Art. 24(3); Data Protection Ordinance Art. 159
Processor deciding purposes and meansGDPR Art. 28(10)3.4
Written form, including electronicGDPR Art. 28(9)1.6