Blindsight Privacy Notice
blindsight.io/platform/legal/privacy
This document covers the Blindsight platform (the console, the desktop apps and the APIs). The blindsight.io website has its own privacy policy.
1. Who we are and how to reach us
Controller: Blindsight Technologies AG, Rennweg 57, 8001 Zurich, Switzerland, UID CHE-484.046.837 ("Blindsight", "we", "us").
Privacy contact: legal@blindsight.io.
2. What this notice covers, and what it does not
This notice covers the Blindsight platform (the console, the desktop apps and the APIs). It covers personal data that Blindsight handles as controller, that is, for its own purposes, about:
- people who contact us or need support about the platform (section 4);
- administrators and other users of the Blindsight console, and the operators of our licence console (section 5);
- licensing and billing contacts of our customers (section 6).
Visitors to the blindsight.io website, website forms, evaluation requests and job applications are covered by the website's own privacy notice at https://blindsight.io/privacy.
Data about a customer's staff is handled for the customer
When an organisation (the "Customer") uses the Blindsight software and service, Blindsight processes data about the Customer's staff and other users on the Customer's behalf. This includes data about devices and people in the Customer's workspace, findings, audit records of actions in the workspace and, by default (the Customer can change this), the text of prompts, replies and files sent to AI services, after redaction on the device, which is kept for 90 days by default (the Customer can change the period or turn sending or keeping off). When the contract ends, the Customer can export its data for at least 30 days; Blindsight then deletes the data within 30 days after that period closes, and backups expire within 35 days. For that data the Customer (usually the employer) is the controller and Blindsight acts as its processor under the data processing agreement (DPA) at https://blindsight.io/platform/legal/dpa. This notice does not describe that processing. If you are an employee or other user of a Customer and have a question or a request about it, please contact your employer, who decides how your data is used and is responsible for informing you. If you send such a request to us, we will pass it to the Customer where we can, and we will not answer it ourselves unless the Customer instructs us to.
The sub-processors we use for Customer data are listed at https://blindsight.io/platform/legal/subprocessors.
Contact, account, sign-in, licensing and billing data of a Customer's administrators, other users of the Blindsight console and contacts is handled by Blindsight as controller, as described below (clause 10.2 of the Blindsight Endpoint Licence Agreement).
3. Overview
| Group | Main data | Main purpose | Legal basis (GDPR) | Retention |
|---|---|---|---|---|
| People who contact us | Name, e-mail, message, attachments | Answer, give support | Art. 6(1)(b) and (f) | See section 4 |
| Console users and operators | Account, sign-in, session and security data | Provide and secure the service | Art. 6(1)(b), (c), (f) | See section 5 |
| Licensing and billing contacts | Name, e-mail, workspace, plan, payment status | Issue licences, bill, comply with law | Art. 6(1)(b), (c), (f) | See section 6 |
4. People who contact us or need support
Data.
- E-mail to info@blindsight.io or legal@blindsight.io: your address, name and the content of the message.
- Support: in-app help and bug reports are stored in the platform and forwarded by e-mail to our support mailbox. They contain the reference, the submitter's name and e-mail address (unless the workspace hides identities), the workspace label, an optional contact address, attachments and the description. Those reports can contain data that belongs to the Customer; we handle that content for the Customer under the DPA (see section 2) and use it only to answer the report.
Purposes and legal basis.
- Answering e-mails and requests addressed to us: steps taken at your request before a contract, and performance of a contract, Art. 6(1)(b) GDPR; otherwise our legitimate interest in conducting our business, Art. 6(1)(f). Under the FADP the processing is proportionate and, where needed, justified by our overriding interest or by your request.
- Support: performance of the contract with the Customer, and our legitimate interest in running and improving the service, Art. 6(1)(f).
- Marketing: we send no newsletter or marketing e-mail.
Recipients (categories and verified providers).
- E-mail to us and support mailbox: Microsoft 365 hosts our mailboxes (the support@ shared mailbox for support e-mails and bug reports, info@, legal@, security@); the provider is Microsoft Ireland Operations Limited, acting as our processor for contact and support data. The mailboxes are stored in the European Union and EFTA under Microsoft's EU Data Boundary; under Microsoft's product terms certain inactive data is stored in Portugal. Support requests and bug reports go to our support mailbox (support@blindsight.io). Support e-mails are kept two years after the last message in the thread, security@ e-mails three years, and legal@ e-mails ten years (business correspondence, Art. 958f CO); after that they are deleted. The platform sends its product e-mails through Amazon Simple Email Service (Amazon Web Services EMEA SARL) in Ireland.
- Our professional advisers, and authorities where the law requires.
Retention. E-mails: support@ two years after the last message in the thread, security@ three years, legal@ ten years (as stated under Recipients above); info@ 36 months (commercial correspondence). Stored support reports and attachments: 24 months after closure.
5. Administrators and other users of the console, and our operators
This section applies to your own account data when you sign in to the Blindsight console as an administrator or user. For what the Customer's workspace holds about its staff, see section 2.
Data.
- Account: name, e-mail address, password hash, roles, status (active or deactivated), security information about your account (for example failed sign-ins, lock-outs and password changes), notification preferences, identifiers from the Customer's directory or single sign-on provider (for example tenant and subject), and department and manager link where provided.
- Two-factor authentication: your two-factor settings and the credential used to check your codes.
- Sessions: cookies that are strictly necessary to keep you signed in and to protect your session, which end when you sign out or the session expires; if you choose, a cookie that remembers a trusted device for up to one year; session records with device, browser, IP address, user agent, creation, last use and revocation.
- Security records: sign-in attempts, failed sign-ins and lock-outs, rate-limiting data, and the web and application logs of our hosting, which include IP addresses.
- Audit records of actions in a Customer's workspace (event type, the person who acted, the object concerned, IP address, user agent and time, chained with hashes so that changes can be detected) are held for the Customer under the DPA, not as our own data (section 2).
- Acceptance records for the licence agreement: version, hash, the person, e-mail, organisation entered, time, IP address.
- Help requests (section 4).
- Fonts: the console serves its fonts from our own servers, so no font request goes to a third party.
- No analytics, advertising, tag manager, error-tracking or chat tools are loaded in the console.
- Operators of our licence console (Blindsight staff): account, sign-in and security data, web access logs with IP addresses, and an audit log of their actions.
Purposes and legal basis.
- Providing the account, signing you in, applying roles and keeping the service available: performance of the contract with you, Art. 6(1)(b), or, where your access comes from the Customer's contract with us, our legitimate interest in providing the service the Customer ordered to the people it authorises, Art. 6(1)(f).
- Security (two-factor authentication, lock-out, rate limiting, detecting abuse): our legitimate interest in protecting the service, our customers and their data against unauthorised access, Art. 6(1)(f), which also serves our duty to secure data, Art. 32 GDPR and Art. 8 FADP. Under the FADP the processing is justified by our overriding private interest where it goes beyond the performance of a contract.
- Complying with law, defending legal claims: Art. 6(1)(c) and (f).
- We do not use this data for advertising.
Recipients. Hosting and e-mail: Amazon Web Services EMEA SARL (Luxembourg), in Ireland. The Customer's own administrators can see the accounts and audit records of their workspace, and the Customer is controller of what is recorded inside its workspace about its own users. Where an identity provider (Microsoft Entra, Google sign-in, Okta) is connected by the Customer, that provider and the Customer exchange sign-in data with us.
Location and transfers. The platform runs on Amazon Web Services in Ireland. Processing inside the EEA needs no transfer mechanism. Our licence console is also hosted by Amazon Web Services in Ireland. Blindsight staff access personal data in the platform only from Switzerland and the European Economic Area. Installers, update manifests and model files are delivered from downloads.blindsight.io 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 data does. The desktop agent also downloads public network reference data from its publishers, which reveals the device's IP address to them, as any web request does.
Retention.
- Account data: for as long as the account exists. Removed accounts: deleted 90 days after removal, subject to legal retention.
- Sessions: until revoked or expired; the records of ended sessions are kept one year.
- Security records (sign-in attempts, lock-outs and similar): one year. Technical logs of the platform: no more than 365 days.
- Audit records of a workspace follow the Customer's retention setting under the DPA.
- Backups: no more than 35 days, then deleted.
- Technical logs, database copies and snapshots of the licence console: no more than 90 days. Licence-console records (audit, failure and workspace records): seven years. Billing and accounting records are kept ten years, as Swiss law requires (Art. 958f CO; see section 6).
6. Licensing and billing contacts
Data.
- In the licence console: workspace name, environment, plan and licence settings, billing mode, the billing contact's name and e-mail address, internal notes, subscription status, plan, interval, currency, number of seats, paid-through and trial dates, payment state, whether a payment is disputed, and identifiers at Stripe and Keygen.
- At Keygen (our licence service): licence records and, for the billing owner or licensee, a user record with e-mail address and first and last name. The platform sends Keygen only the workspace licence key and aggregate usage counters.
- At Stripe: if you pay by card through the hosted checkout page, you type your name, billing address, business tax identifier and payment details on Stripe's page. We do not send your name, e-mail or address to Stripe and card data never reaches our systems. We receive the status of the payment and identifiers from Stripe.
- Invoices and accounting records.
Purposes and legal basis. Issuing and managing licences and subscriptions, invoicing and collecting payment: performance of the contract, Art. 6(1)(b). Tax and accounting duties: legal obligation, Art. 6(1)(c). Fraud prevention, debt collection and defence of claims: legitimate interest, Art. 6(1)(f). Under the FADP this processing is necessary for the contract or is justified by our overriding interest or by law (Art. 31).
Recipients. Stripe (Stripe Payments Europe, Ltd. and Stripe, Inc.), which processes payment data as a separate controller under its own terms; Keygen, as our processor; Amazon Web Services EMEA SARL (hosting of the licence console and its backups), our accountants, tax advisers and authorities where the law requires.
Location and transfers. The licence console and its backups are hosted by Amazon Web Services in Ireland. Keygen processes licence records in the United States; for that transfer Keygen relies on the European Commission's Standard Contractual Clauses (Implementing Decision (EU) 2021/914), which its terms incorporate (https://keygen.sh/terms/, section 12, and https://keygen.sh/privacy/, section 1.5). Stripe processes data in the EEA and the United States and states that it takes part in the EU-U.S., UK and Swiss-U.S. Data Privacy Framework.
Retention. Billing and accounting records: 10 years, the Swiss statutory period (Art. 958f of the Code of Obligations). Other licensing and contact data: for the life of the account, then 24 months unless the law requires longer.
7. Shared catalogue of AI services
Blindsight keeps one catalogue of AI services (host names, a name, vendor and category, public information about the service, an indication of how widely it is seen, and first and last day). An entry is created only when more than one independent paying workspace has reached the same public host, and it holds no customer, device or person identifier. We use it, as the licence agreement allows (clause 10.3), to recognise AI services for all customers. We do not treat it as personal data.
8. Automated decisions
We take no decision about people who contact us, console users or billing contacts that has legal effect on them or similarly significantly affects them, based solely on automated processing, including profiling (Art. 22 GDPR, Art. 21 FADP). Automated measures such as lock-out after repeated failed sign-ins protect the service and do not decide on rights or contracts. In the Customer's workspace, the software can block or redact content in prompts according to the Customer's policy. That is the Customer's processing (section 2).
9. Recipients and transfers in general
We share personal data only with the providers named above, our advisers, authorities where the law requires, and a buyer in a sale of the business (under the same protections). We do not sell personal data.
Where data goes to a country without an adequacy decision (and for Switzerland, without a listing in Annex 1 of the Data Protection Ordinance), we use the Data Privacy Framework certification of the recipient or the EU Standard Contractual Clauses with the Swiss addendum, and we assess additional safeguards where needed. You can ask us for a copy of the safeguards. Transfers between the EEA and Switzerland rely on the adequacy decisions each side has issued for the other.
10. Whether you must give us data, and where it comes from
You are not required by law to give us personal data. Some data is needed for a contract or for the service: without an e-mail address and the sign-in data in section 5 we cannot give you a console account, without the billing data in section 6 we cannot issue a paid licence, and without the content of your message we cannot answer it.
We collect most data from you directly. Some comes from others: the Customer that gives you access to the console (your name, e-mail address and role), the Customer's identity provider or directory when the Customer connects one (identifiers, department and manager link), Stripe (payment status and identifiers) and Keygen (licence records).
11. Security
We protect data with measures suited to the risk, including hosting in a European region, encryption in transit and at rest, role-based access, two-factor authentication as an option for console users, sign-in lock-out and rate limiting, hash-chained audit records, a web-application firewall, and logging and alarms. No system is completely secure. The measures for data we process for Customers are set out in Annex 2 of the DPA.
12. Your rights
Under the GDPR you have the right to access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), notification of recipients (Art. 19), data portability (Art. 20), and not to be subject to certain automated decisions (Art. 22). Where processing rests on consent you can withdraw it at any time, without affecting the processing before the withdrawal.
Right to object. Where we rely on our legitimate interest (Art. 6(1)(f) GDPR), you have the right to object at any time, on grounds relating to your particular situation (Art. 21 GDPR). We then stop the processing unless we have compelling legitimate grounds that override your interests, or need it for legal claims.
You can lodge a complaint with a supervisory authority, in particular in the EU or EEA country where you live, work or where the alleged infringement took place (Art. 77 GDPR).
Under the Swiss FADP you have the right to information about your data (Art. 25), to receive or have transmitted data you gave us (Art. 28), to have incorrect data corrected (Art. 32(1)), to request that a particular processing or a disclosure to third parties be stopped, or that data be deleted or destroyed (Art. 32(2)), and, for an automated individual decision, to state your point of view and to ask for a review by a person (Art. 21). You can report a suspected breach of data protection rules to the Federal Data Protection and Information Commissioner (FDPIC), https://www.edoeb.admin.ch.
How to exercise them. Write to legal@blindsight.io. We reply within one month under the GDPR (extendable by two months for complex requests, with notice) and within 30 days under the FADP. We may ask for proof of identity, for example confirmation from the e-mail address on file, before we release or change data. The service is free, unless the request is clearly unfounded or excessive. Under the FADP, we may ask for a contribution to costs only where answering involves disproportionate effort; it is at most CHF 300, and we tell you the amount before we answer (Art. 25(6) FADP; Art. 19 of the Data Protection Ordinance). For data a Customer controls, see section 2.
13. Children
Our software and service are for businesses and are not directed at children. We do not knowingly collect personal data from children. If you believe a child has sent us data, contact us and we will delete it.
14. Changes and effective date
We may update this notice. We publish the new version at https://blindsight.io/platform/legal/privacy with its date and, for material changes affecting Customer administrators, tell them by e-mail. Earlier versions are available on request.
This version is effective on the date of publication.