Data Processing Addendum
SHA-256 53e5d501c4262f41a0b73f0eaabf1e369bca6902302f29c73e30b543b2415047
In this document
What changes from version 1.0
Gaze, where the Customer enables it, is listed among the Signals of the live mode in section 5 and in Annex 1, and Annex 1 also lists hand and body presence where the Customer enables them. A new Subprocessor and a material change to this DPA are notified by an email from support@neurologyca.com to the Organization Admin, in DevLab and under /legal. Section 15 states that Engine applies no automatic expiry and what the deletion of an End User covers, and that Neurologyca has not confirmed that this deletion reaches the records that the service generating the Interpretation may keep, about which it informs on request. Annex 3 distinguishes the preview environments, hosted by OVH in France, from production, hosted by Google Cloud in the United States.
This Data Processing Addendum ("DPA") forms part of the Agreement between Neurologyca Technologies Ltd. ("Neurologyca") and the Customer. It is incorporated into the Neurologyca DevLab Terms of Service and takes effect, without signature, when the Organization Admin accepts the Terms on behalf of the Customer. It sets out how Neurologyca processes Customer Personal Data on the Customer's behalf. Capitalized terms not defined here have the meaning given in the Terms.
1. Definitions
In this DPA:
- "Data Protection Laws" means all laws on privacy and the protection of personal data that apply to the processing under the Agreement, including, where applicable, Regulation (EU) 2016/679 ("GDPR"), the GDPR as retained in the law of the United Kingdom ("UK GDPR") and the UK Data Protection Act 2018, the Swiss Federal Act on Data Protection ("FADP"), the California Consumer Privacy Act as amended by the California Privacy Rights Act ("CCPA") and comparable laws of other U.S. states, the Illinois Biometric Information Privacy Act and other biometric privacy laws, and Mexico's Federal Law on the Protection of Personal Data Held by Private Parties ("LFPDPPP").
- "Customer Personal Data" means the personal data within Customer Data that Neurologyca processes on behalf of the Customer through Engine, the Hosted Processor and the Interpretation.
- "Account Data" means personal data about Authorized Users and Organization Admins that Neurologyca processes to provide DevLab, including account, session, activity, acceptance and support data.
- "Personal Data Incident" means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Personal Data processed by Neurologyca or its Subprocessors.
- "Subprocessor" means a third party that Neurologyca engages to process Customer Personal Data.
- "SCCs" means the standard contractual clauses approved by Commission Implementing Decision (EU) 2021/914 of 4 June 2021.
- "UK Addendum" means the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses issued by the UK Information Commissioner under s. 119A of the UK Data Protection Act 2018, version B1.0.
- "controller", "processor", "data subject", "personal data", "processing", "business", "service provider", "responsable" and "encargado" have the meanings given in the applicable Data Protection Laws.
2. Roles of the parties
The role of each party depends on the activity:
| Activity | Customer | Neurologyca |
|---|---|---|
| Engine: receiving Signals, transcripts and End User profiles, computing and storing Indicators and results | Controller (or processor on behalf of its own client) | Processor, service provider and encargado |
| Hosted Processor: receiving recordings, transcribing them where requested and replaying the capture against Engine | Controller (or processor on behalf of its own client) | Processor, service provider and encargado |
| Interpretation: generating the natural-language reading of Indicators and transcripts | Controller (or processor on behalf of its own client) | Processor, service provider and encargado |
| DevLab accounts, sessions, activity record, acceptance records and service emails (Account Data) | Not applicable | Controller |
| Usage and telemetry of the Services, in aggregated or de-identified form | Not applicable | Controller |
| The Assistant | Not applicable | Controller |
| The Playground, used by Authorized Users with themselves or consenting colleagues | Not applicable | Controller |
Neurologyca processes Account Data and the data of the Assistant and the Playground as described in the DevLab Privacy Notice. The rest of this DPA applies to Customer Personal Data.
Where the Customer acts as a processor on behalf of a third-party controller, the Customer warrants that its instructions, including the appointment of Neurologyca as a Subprocessor, have been authorized by that controller, and the Customer remains Neurologyca's sole point of contact.
3. Customer responsibilities
The Customer is responsible for the lawfulness of the processing of Customer Personal Data and for its instructions. In particular, the Customer:
- determines the purposes of the processing and the legal basis for it in every place where it uses the Services, where its End Users are and where the results are used;
- gives End Users the notices and obtains the consents required by Data Protection Laws before any capture, including written consent where biometric privacy laws require it, as further set out in the Biometric and Emotion-Inference Addendum;
- carries out any data protection or AI impact assessment required by law;
- uses opaque identifiers for End Users and keeps the link to the real person in its own systems, as recommended in the Documentation;
- keeps its API Keys on its backend and never in a browser or mobile application; and
- remains responsible for recordings, transcripts and results that it stores in its own systems, including uploads held by the SDK receiver in its own backend.
4. Processing on instructions
Neurologyca processes Customer Personal Data only on the Customer's documented instructions, unless required otherwise by law, in which case Neurologyca will inform the Customer of that requirement before processing unless the law prohibits it. The Agreement, this DPA, the configuration the Customer chooses in the Services and the calls it makes to Engine and the Hosted Processor are the Customer's complete instructions. Additional instructions require written agreement. Neurologyca will tell the Customer if, in its opinion, an instruction infringes Data Protection Laws, and may suspend the affected processing until the instruction is confirmed or changed.
Neurologyca will not sell or share Customer Personal Data, retain, use or disclose it for any purpose other than providing the Services, or combine it with personal data it receives from other sources, except as the CCPA permits a service provider to do.
5. Description of the processing
Annex 1 describes the subject matter, nature, purpose and duration of the processing, the categories of data subjects and of personal data, and the retention that applies.
The Services work in two modes:
- Live (on-device) mode. The SDKs run in the End User's browser and compute Signals there: facial landmarks, expression coefficients, head pose, gaze where the Customer enables it, audio features and pulse estimates (rPPG) and, where the Customer enables it, a transcript of speech produced on the device. No image, video or audio leaves the device; only Signals and text are sent, through the Customer's backend, to Engine.
- Deferred mode. The browser records video with audio and uploads it to the Customer's backend. The Hosted Processor downloads the recording through a signed URL, transcribes it where the Customer has enabled transcription and replays the capture against Engine, which computes the Indicators. The deferred mode is a Preview Feature.
In both modes, the Interpretation receives Indicators, any transcript, the Customer's query and the narrative preferences of the End User's profile, but not the End User's name or external identifier.
6. Confidentiality
Neurologyca ensures that every person it authorizes to process Customer Personal Data is bound by an appropriate obligation of confidentiality, receives training appropriate to their role, and accesses Customer Personal Data only as needed to provide the Services, give support the Customer requests or comply with the law.
7. Security
Neurologyca implements and maintains the technical and organizational measures described in Annex 2, appropriate to the risk of the processing and to the nature of Customer Personal Data, which may include biometric data and data concerning health. Neurologyca may update these measures provided that the overall level of protection is not reduced.
Two credentials travel in a URL by design, and the following mitigations apply:
- WebSocket session token. When the optional WebSocket channel of
@neurologyca/kodecis used, its session token is sent in the connection URL, because browsers cannot set headers on a WebSocket connection. The token is short-lived and valid only for that session and that purpose. - Hosted Processor signed URLs. The Hosted Processor downloads each recording through a signed URL issued by the Customer's backend. Each URL gives access to a single recording, expires after 24 hours by default and never later than 7 days, and stops working once the recording is deleted.
The Customer must not log these URLs and must configure its proxies so that they do not keep query strings in their logs.
8. Subprocessors
The Customer gives Neurologyca general authorization to engage Subprocessors. The current Subprocessors are listed in Annex 3 and at Subprocessors.
Neurologyca will:
- impose on each Subprocessor, by written contract, data protection obligations that are no less protective than those in this DPA;
- remain responsible to the Customer for the performance of each Subprocessor's obligations; and
- give the Customer at least 15 days' notice before a new Subprocessor begins processing Customer Personal Data, by an email sent from support@neurologyca.com to the Organization Admin, by a notice in DevLab and by publishing the updated list at Subprocessors, where each version has its own permanent address.
The Customer may object to a new Subprocessor on reasonable data protection grounds by writing to info@neurologyca.com within those 15 days. The parties will discuss the objection in good faith. If Neurologyca cannot offer a reasonable alternative within 30 days of the objection, the Customer may terminate the affected Services by written notice, without penalty, and Neurologyca will refund any fees prepaid for the period after termination. Where a Subprocessor must be replaced urgently for reasons of security or continuity of service, Neurologyca will give notice as soon as possible, by the same means, and the Customer keeps the same right to object.
9. International transfers
Neurologyca is established in the United States, and Customer Personal Data is processed in the countries listed in Annex 3. Neurologyca staff located in Spain may access Customer Personal Data to operate and support the Services. Neurologyca will transfer Customer Personal Data only in accordance with Data Protection Laws.
9.1 European Economic Area
For transfers of Customer Personal Data from the European Economic Area to a country without an adequacy decision, the SCCs are incorporated into this DPA as follows: Module Two (controller to processor) applies where the Customer is a controller, and Module Three (processor to processor) where the Customer is a processor. The Customer is the data exporter and Neurologyca the data importer. Clause 7 (docking clause) applies. In Clause 9, Option 2 (general written authorization) applies, with the notice period in section 8 of this DPA. The optional wording in Clause 11 does not apply. In Clause 13, the competent supervisory authority is the one determined under that clause. In Clauses 17 and 18, the SCCs are governed by the law of Ireland and disputes are resolved by the courts of Ireland. Annexes I, II and III of the SCCs are completed with the information in Annexes 1, 2 and 3 of this DPA.
9.2 United Kingdom
For transfers from the United Kingdom, the UK Addendum is incorporated into this DPA and amends the SCCs as set out in it. Tables 1 to 3 of the UK Addendum are completed with the information in this DPA and its Annexes, and for Table 4 either party may end the UK Addendum as allowed by its Section 19.
9.3 Switzerland
For transfers from Switzerland, the SCCs apply with these adaptations: the Federal Data Protection and Information Commissioner is the competent supervisory authority for transfers governed by the FADP; references to the GDPR are read as references to the FADP; and the term "Member State" does not prevent data subjects habitually resident in Switzerland from bringing claims there.
9.4 Other transfers
Where other Data Protection Laws require a transfer mechanism, the parties will rely on the SCCs as adapted to that law or on another mechanism that the law recognizes, and will sign any further document reasonably required.
10. United States and Mexico
10.1 CCPA and other U.S. state laws
With respect to Customer Personal Data, Neurologyca acts as a service provider or processor. The Customer discloses Customer Personal Data to Neurologyca only for the limited and specified business purpose of providing the Services. Neurologyca will comply with the obligations that the CCPA and comparable state laws impose on service providers and processors, will provide the same level of privacy protection they require, will notify the Customer if it can no longer meet those obligations, and will allow the Customer to take reasonable and appropriate steps to stop and remediate any unauthorized use. Neurologyca will not use biometric data for any purpose other than providing the Services to the Customer, and will not sell, lease, trade or otherwise profit from it.
10.2 Mexico
With respect to Customer Personal Data, Neurologyca acts as an encargado under the LFPDPPP. It will process Customer Personal Data only in accordance with the Customer's instructions and for the purposes the Customer has communicated to its data subjects in its privacy notice, will keep it confidential, will apply the security measures in Annex 2, and will delete it when the relationship ends as set out in section 15, unless the law requires its retention.
11. Personal Data Incidents
Neurologyca will notify the Customer without undue delay, and in any case within 72 hours, after becoming aware of a Personal Data Incident. The notice is sent by email to the Organization Admin and includes, as far as it is known, the nature of the incident, the categories and approximate number of data subjects and records concerned, the likely consequences and the measures taken or proposed. Where not all the information is available at once, Neurologyca will provide it in phases without undue delay. Neurologyca will take reasonable steps to contain and remedy the incident and will cooperate with the Customer in meeting its own notification duties. Notice of an incident is not an acknowledgment of fault or liability.
12. Assistance
Taking into account the nature of the processing and the information available to it, Neurologyca will assist the Customer:
- with data subject requests. The Services let the Customer delete an End User and everything Engine holds about them, block an End User and read their results, as described in the Documentation. Where the Customer cannot respond to a request with those functions, Neurologyca will provide reasonable additional help. If Neurologyca receives a request directly from a data subject of the Customer, it will redirect the data subject to the Customer and will not respond itself unless the law requires it;
- with impact assessments and prior consultations that the Customer must carry out under Data Protection Laws or AI laws, by providing the Documentation and reasonable information about the Services; and
- with supervisory authorities, by cooperating with any request that concerns the processing of Customer Personal Data. If an authority asks Neurologyca directly for Customer Personal Data, Neurologyca will notify the Customer, unless the law prohibits it, and will disclose only what it is legally compelled to disclose.
13. Audits
Neurologyca will make available to the Customer the information reasonably necessary to demonstrate compliance with this DPA. The Customer agrees that its audit rights are exercised first by reviewing the Documentation, Neurologyca's written answers to reasonable security questionnaires and any third-party audit reports or certifications that Neurologyca holds, under confidentiality.
An on-site audit may take place only where that information is not sufficient to demonstrate compliance and the audit is required by Data Protection Laws or by a supervisory authority. In that case the Customer will give at least 30 days' written notice, agree the scope and timing with Neurologyca in advance, use an auditor bound by confidentiality who is not a competitor of Neurologyca, carry out the audit during business hours without disrupting the Services or accessing other customers' data, and bear its own costs. Such an audit may not take place more than once in any 12-month period, unless a supervisory authority requires it or after a Personal Data Incident.
14. No training on Customer Personal Data
Neurologyca does not use Customer Personal Data to train, retrain or improve machine learning models, whether its own or third parties', unless the Customer agrees to it in a Written Agreement and a valid legal basis exists. Pseudonymized data is not treated as anonymous for this purpose. Neurologyca may use aggregated, de-identified data about the use of the Services, which does not identify the Customer, any End User or any other person, to operate, secure and improve the Services. Under the Gemini API Additional Terms of Service, as of November 3, 2026 (https://ai.google.dev/gemini-api/terms), Google does not use prompts or responses of paid services, such as those of the Interpretation, to improve its products.
15. Retention, return and deletion
During the Agreement, Customer Personal Data is retained as follows:
- Engine applies no automatic expiry: it keeps Customer Personal Data until the Customer deletes the End User or until it is deleted at the end of the Agreement as set out below. The Customer can delete an End User at any time with the deletion function described in the Documentation. That deletion is physical, all-or-nothing and irreversible, and covers what Engine holds about the End User: the profile, the Signals and transcripts received, the results, the Interpretations and the baseline. Engine keeps a record of each deletion, with the End User's external identifier, the API Key that requested it and the counts of what was deleted, and Engine's server logs may mention the external identifier.
- Hosted Processor. Recordings are kept only while they are processed. The video, the audio and any transcript are deleted when processing ends, and the Hosted Processor keeps afterwards only a technical record of the job without video, audio or transcript, as stated in the Documentation. Where DevLab receives a recording, it deletes the video when the job reaches interpretation or succeeds, when it finally fails, or after 24 hours at most.
- Interpretation. The Interpretation that Engine returns is stored in Engine with the results it belongs to and is deleted with them when the Customer deletes the End User. Neurologyca has not confirmed that this deletion also reaches the records that the service generating the Interpretation may keep on its side; on request, Neurologyca will tell the Customer what it knows about what that service keeps and for how long. The requests sent to the Gemini API to generate the Interpretation are processed under the paid-service terms cited in section 14.
On termination or expiry of the Agreement, the Customer may export its Customer Personal Data with the functions of the Services for 30 days. After that period, Neurologyca will delete Customer Personal Data, including copies held by Subprocessors, within a further 30 days, unless the law requires its retention, in which case Neurologyca will keep it confidential and process it only for that purpose. Data in backups is deleted as the backups expire in the normal cycle. On request, Neurologyca will confirm the deletion in writing.
16. Liability
Each party's liability arising out of or relating to this DPA is subject to the limitations and exclusions of liability in the Terms, or in a Written Agreement where one applies. Nothing in this DPA limits a party's liability to data subjects where Data Protection Laws or the SCCs do not allow it.
17. Order of precedence, duration and changes
In case of conflict, the following order applies: the SCCs and the UK Addendum, then this DPA, then the rest of the Agreement. A Written Agreement prevails over this DPA only where it expressly says so. This DPA remains in force for as long as Neurologyca processes Customer Personal Data.
Neurologyca may update this DPA following the procedure for changes in the Terms, with at least 30 days' notice of material changes, given in DevLab, under /legal and by an email sent from support@neurologyca.com to the Organization Admin. Changes required by law or by a supervisory authority may take effect sooner. An update will not reduce the overall level of protection of Customer Personal Data. The list of Subprocessors is updated as set out in section 8.
18. Contact
Notices and questions under this DPA, including objections to Subprocessors and requests for assistance, must be sent to info@neurologyca.com. Neurologyca sends notices to the Organization Admin's email address.
19. Annex 1: Description of the processing
| Item | Description |
|---|---|
| Data exporter | The Customer, as identified in its DevLab account; contact: the Organization Admin. Role: controller or processor |
| Data importer | Neurologyca Technologies Ltd., 960 Market St. Unit 1209, San Francisco, CA 94102, United States; contact: info@neurologyca.com. Role: processor |
| Subject matter | Provision of Engine, the Hosted Processor and the Interpretation to the Customer under the Agreement |
| Nature of the processing | Receipt, computation, storage, transcription (deferred mode, where enabled), replay, interpretation by a large language model, retrieval and deletion |
| Purpose | To compute Human Context Indicators from Signals, to generate the Interpretation and to return results to the Customer, as instructed by the Customer |
| Categories of data subjects | End Users of the Customer's applications; any other person whose image or voice is captured by the Customer, such as people near an End User during a recording |
| Categories of personal data, live mode | End User profile sent by the Customer (external identifier, name, role, audience, narrative preferences and time zone); Signals (facial landmarks, expression coefficients, head pose, gaze and hand and body presence where the Customer enables them, audio features and pulse estimates); transcripts produced on the device; Indicators, results, baseline and Interpretation; technical metadata of each capture |
| Categories of personal data, deferred mode | All of the above, plus video and audio recordings, transcripts produced by the Hosted Processor and the recording manifest |
| Special categories and sensitive data | Signals, including gaze, and Indicators may be biometric data, and pulse estimates and inferences of stress or affect may be data concerning health under some laws; transcripts may reveal any category of data the End User mentions. They are processed only to provide the Services, with the safeguards in Annex 2 |
| Frequency | Continuous, for as long as the Customer uses the Services |
| Retention | As set out in section 15 |
| Subprocessors | As set out in Annex 3, for the purposes stated there |
| Competent supervisory authority | The one determined under Clause 13 of the SCCs |
20. Annex 2: Security measures
Neurologyca applies the following technical and organizational measures:
- Encryption in transit. All traffic to DevLab, Engine and the Hosted Processor is protected with TLS.
- Encryption at rest. Customer Personal Data in Engine and the Hosted Processor is stored encrypted at rest by the hosting provider. API Keys and Hosted Processor credentials held by DevLab are sealed with AES-256-GCM under a master key kept apart from the database (a key vault), and each sealed value is bound to its record.
- Secrets on the backend. API Keys are used only by servers. DevLab adds team credentials on its server, so that API Keys never reach the browser, and requires the same of the Customer.
- Least privilege. Access to production systems and to Customer Personal Data is limited to authorized personnel who need it for their role, with individual accounts. API Keys can be scoped, rotated and revoked; DevLab separates teams so that each one reaches only its own End Users.
- Authentication. Passwords are stored with scrypt and a salt; session identifiers, invitation and reset links are stored only as hashes; sessions expire; repeated failed sign-ins are paused; revealing an API Key requires the password again, is rate-limited and is recorded.
- Protection against cross-site requests. State-changing requests must come from DevLab's own origin, and the session cookie is HttpOnly and SameSite.
- Audit records. Sign-ins, reveals of keys and credentials, and administrative actions are recorded, without request bodies, keys or End User data, and kept for 12 months.
- Data minimization. In live mode, images, video and audio never leave the End User's device. The Interpretation does not receive the End User's name or external identifier.
- Retention and deletion. Data is kept only for the periods in section 15; recordings are deleted automatically; the Customer can delete an End User and all their data in Engine at any time; deletions in Engine are physical and all-or-nothing.
- Backups and availability. Databases are backed up regularly, backups are kept for a limited time and access to them is restricted.
- Vulnerability management. Dependencies are reviewed and updated, and changes go through review and automated checks before deployment.
- Incident response. Neurologyca maintains a procedure to detect, contain, investigate and notify Personal Data Incidents, as set out in section 11.
- Subprocessors. Subprocessors are selected for their security practices and bound by written data protection obligations.
- Credentials in URLs. The mitigations in section 7 apply to the WebSocket session token and the Hosted Processor signed URLs.
21. Annex 3: Subprocessors
The Subprocessors authorized at the effective date of this DPA, with their purpose and location, are listed at Subprocessors, which forms part of this Annex. DevLab runs in preview environments, where Neurologyca makes new versions of DevLab available before they reach production, and in a production environment; where a Subprocessor is used only in one type of environment, the table says so:
| Subprocessor | Purpose | Location |
|---|---|---|
| OVH SAS | Hosting of DevLab, its database and the Hosted Processor queue, in the preview environments | France |
| Google LLC (Google Cloud) | Hosting of Engine and the Hosted Processor; computation of Indicators; in production, also hosting of DevLab, its database and the Hosted Processor queue | United States |
| Google LLC (Gemini API) | Generation of the Interpretation | United States |
| Google LLC (Google Workspace) | Transactional email | United States and European Union |
Changes to this list follow section 8.
Versions
| Version | In effect | What changes | SHA-256 |
|---|---|---|---|
| 1.1 current | Nov 17, 2026 | What changesGaze, where the Customer enables it, is listed among the Signals of the live mode in section 5 and in Annex 1, and Annex 1 also lists hand and body presence where the Customer enables them. A new Subprocessor and a material change to this DPA are notified by an email from support@neurologyca.com to the Organization Admin, in DevLab and under /legal. Section 15 states that Engine applies no automatic expiry and what the deletion of an End User covers, and that Neurologyca has not confirmed that this deletion reaches the records that the service generating the Interpretation may keep, about which it informs on request. Annex 3 distinguishes the preview environments, hosted by OVH in France, from production, hosted by Google Cloud in the United States. | 53e5d501c4262f41a0b73f0eaabf1e369bca6902302f29c73e30b543b2415047 |
| 1.0 | Nov 3, 2026 | 896db3c2e40c8fa13a65d9041a2a0b2370c382f910c0db1767e880f9bd20b9d0 |