# DevLab Privacy Notice

This DevLab Privacy Notice ("Notice") explains how Neurologyca Technologies Ltd. ("Neurologyca", "we", "us") processes personal data about the people who use DevLab: Organization Admins, Authorized Users and anyone who contacts us about DevLab. It is information for you to read; you are not asked to accept it, and it is not part of any contract. Capitalized terms not defined here have the meaning given in the [Neurologyca DevLab Terms of Service](/legal/terms).

## 1. Who is responsible

The controller of the personal data described in this Notice is Neurologyca Technologies Ltd., 960 Market St. Unit 1209, San Francisco, CA 94102, United States.

For any question about this Notice or about your personal data, and to exercise your rights, write to info@neurologyca.com. For technical support with DevLab, write to support@neurologyca.com.

## 2. Scope of this Notice

This Notice covers the personal data that Neurologyca processes for its own purposes when you use DevLab: your account, your sign-ins, your activity in the console, the acceptance of the Terms, the emails we send you, the Assistant and the Playground.

It does not cover the data of End Users that a Customer captures through its own application with the SDKs and sends to Engine, the Hosted Processor or the Interpretation. For that data the Customer decides why and how it is processed, and Neurologyca acts on the Customer's behalf under the [Data Processing Addendum](/legal/dpa). End Users should read the privacy notice of the Customer whose application they use.

DevLab runs in preview environments, where Neurologyca makes new versions of DevLab available before they reach production, and in a production environment. This Notice applies to all of them; where something differs between them, this Notice says so.

DevLab is a professional service. It is not offered to consumers and is not intended for anyone under 18 (see section 13).

## 3. What we process and why

### 3.1 Your account

When your organization invites you, we receive your email address, the team you belong to and your role (developer or Organization Admin). When you activate the account, you choose a password; we store only a salted hash of it (scrypt), never the password itself. We also keep the account status, its creation date and the version of the privacy notice you were shown. We use this data to create and run your account, to let you use the Services and to tell you about them.

Where Neurologyca offers Trial Accounts under Section 7.4 of the [Neurologyca DevLab Terms of Service](/legal/terms), you create the account yourself instead of being invited, and we receive the same data, except the team and the role if the account has none. Any permission to receive commercial communications is asked for separately and is never preselected; if you give it, we keep it with its date until you withdraw it.

### 3.2 Signing in and sessions

When you sign in, DevLab sets one cookie, `devlab_session`, holding a random session identifier. We store only a SHA-256 hash of that identifier, with the times the session was created, last used and expires. A session ends after 7 days without use and in any case 30 days after sign-in, or when you sign out.

To protect accounts against password guessing, each failed sign-in is recorded with the email address and IP address used. After 5 failures in 15 minutes from the same IP address for the same email address, sign-in is paused for that pair. Failed sign-in records are deleted after one day.

Invitation links (valid for 72 hours) and password reset links (valid for one hour) are stored only as a hash and are deleted once used or expired.

### 3.3 Activity record

DevLab keeps a record of what happens in each account and team, with the minimum detail needed to operate the service, keep it secure and show your team its progress:

- sign-ins, failed sign-ins, lockouts, account activation and password resets, with the IP address;
- reveals of an API Key, downloads of a starter with an API Key included and reveals or regeneration of Hosted Processor credentials, with the IP address; downloads of a starter without a key;
- invitations sent by an Organization Admin and actions taken by Neurologyca administrators;
- your team's integration milestones (for example, the first call to Engine or the first capture);
- the Playground consent and the use of the Assistant, as described in sections 4 and 5.

The activity record never contains request bodies, API Keys or End User data. It is kept for 12 months and then deleted, except team milestones, which are kept per team without saying who triggered them. When an account is deleted, its activity is detached from it and its IP addresses are removed.

### 3.4 Acceptance of the Terms

When you accept the Terms, and when an Organization Admin accepts them on behalf of the Customer, we keep a record that proves the acceptance: your email address and account identifier, your team, the Customer's organization (its identifier in DevLab and its name), your role, the capacity in which you accepted (for yourself or for the organization), the version of the document set, each document shown with its language and SHA-256 fingerprint, a fingerprint of the text of the acceptance controls, the language, a fingerprint of your session identifier, what prompted the acceptance (for example, activation or a new version), the time, and your IP address and browser user agent. When you accept on behalf of the Customer, the other Organization Admins of the same Customer can see in DevLab that you did so, with your email address and the date.

After each acceptance we send you a confirmation email with what you accepted and links to that exact version. Your own history is available in DevLab under Your account › My agreements.

This record cannot be edited by the application. We keep it for the life of the account and for 10 years after the account is closed, so that we can prove the contract and defend or bring legal claims. The IP address and user agent are cleared 12 months after the acceptance.

### 3.5 Emails from DevLab

We send you transactional emails: your invitation, password resets, notices about your account, your team or its API Keys, and the confirmation of each acceptance of the Terms.

From time to time a Neurologyca administrator may also send "DevLab updates" by email, in English, to active accounts, to people Neurologyca has added to a recipient list and to addresses entered for a single send. For each send we keep the address of every recipient and whether the email was sent, failed or was skipped. Every update email carries an unsubscribe link; we store a hash of its token next to the address it was sent to. If you unsubscribe, we keep your address on an unsubscribe list so that we do not email you updates again; you still see the updates inside DevLab. This data is kept for as long as DevLab sends updates by email.

### 3.6 Calls to Engine through DevLab

When you use the console or the Playground, DevLab forwards your calls to Engine and adds your team's credentials on the server, so that API Keys never reach your browser. To keep each team inside its own data, DevLab remembers for 24 hours which End User identifiers and enrollments your team has reached through DevLab. It never stores request or response bodies.

### 3.7 Hosted Processor credentials

If your organization enables the Hosted Processor, DevLab keeps the organization's processor key and webhook secret encrypted (AES-256-GCM) and sends the Hosted Processor the secret and only a hash of the key. Each reveal, regeneration or download that includes them is recorded in the activity record with the IP address.

### 3.8 Support and correspondence

When you write to info@neurologyca.com or support@neurologyca.com, we process your name, email address and what you tell us, to answer you and to keep a record of the request.

### 3.9 Technical security data

Our servers process the IP address, browser user agent and request details of every request in order to deliver DevLab, limit abuse and investigate incidents. In the preview environments, database backups are made every 24 hours and each backup is kept for 14 days. In production, database backups are managed within the production hosting; you can ask us at info@neurologyca.com how often they are made and how long they are kept.

## 4. The Assistant

Where DevLab offers the Assistant, you can ask it questions about the Documentation. The Assistant is a large language model provided by Google LLC through the Gemini API, used under Google's paid-service terms.

**What is sent to Google.** Your questions, the latest turns of the conversation in your browser tab, the language of the answer, the page you ask from and the Documentation pages the Assistant reads to answer. Of a docs page, its text goes; of a DevLab screen, its name and, if «Where everything is» describes it, that description; you can remove the page before asking. With each question, DevLab also sends your role (developer, organization admin or Neurologyca admin), the state of your team (no team, inactive or active) and whether this DevLab offers invitations and hosted processing: values with no names or identifiers, so that the answer fits your situation. Invitations and hosted processing are a setting of the DevLab you use, not data about you. No name, email address, team, organization or account identifier is sent. Before sending, DevLab removes Engine and Google API keys in their known format, tokens shaped like JWTs, email addresses and the internal addresses of Engine; any other secret you paste is sent as written, so do not paste secrets.

**What Google does with it.** DevLab asks Google not to store the interaction. 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 to improve its products. DevLab cannot delete what has already been sent to Google.

**What DevLab keeps.** DevLab never stores the text of a question or an answer, in its database or in its logs. It records in the activity record, for 12 months: that you asked, when, from which page and in which language, which Documentation pages the answer cited, whether the answer came from the Documentation, the destination it proposed, whether something was redacted, how the turn ended, the model, the work involved (rounds, characters read, timings, tokens and an estimated cost) and your rating and its reason from a fixed list. It also records when you acknowledge the Assistant's notice. The conversation itself stays only in your browser tab.

The Assistant's answers are informational and do not bind Neurologyca.

## 5. The Playground

The Playground lets you try Engine with your own face, voice or a sample video. It is for evaluation and integration only, with yourself or colleagues who agree, never with candidates, assessed employees, customers or End Users. Before the first run, the Playground asks for its own consent (version `2026-11-17.1`), separate from the Terms. We record the consent version, the language and a fingerprint of the text you were shown; the consent expires with the activity record after 12 months, and the Playground then asks again.

**Real-time capture.** Your browser computes 478 facial landmarks, 52 expression coefficients and the head pose from the camera; only those numbers leave your device, never images, video or audio. If you turn on "Transcribe", the browser also opens the microphone and transcribes on the device what is said while a voice step is open, including what other people near you say; only the text leaves your device, never the audio. With the sample video, the Playground transcribes the video's audio and does not open your microphone. The numbers and any text go through DevLab to Engine, in your team's organization, linked to a test person that DevLab creates for the run with a random identifier. Engine computes the Indicators. Where the protocol has an Interpretation, Engine sends the Indicators and any transcript to a large language model that writes it (Google Gemini, in the United States). Some of these signals, and the inferences drawn from them, may be biometric data or data concerning health under some laws.

**Recording (deferred).** If you record, the video and the audio are recorded: with your camera, the microphone always opens too; with the sample video, its picture and sound are recorded and neither your camera nor your microphone opens. With the recording goes its manifest (the times of each step and technical data of the recording and the device), which includes your browser's full user agent: the browser, its version and the operating system. The recording is uploaded to DevLab and then processed by the Hosted Processor. Only if transcription is on for that recording, the Hosted Processor transcribes on the server the whole audio of the recording, including what is said between steps or by other people nearby, and only the text of the voice steps reaches Engine, which sends it with the Indicators to a large language model for the Interpretation (Google Gemini, in the United States). The Hosted Processor computes no Indicators: Engine computes them, as in real time, and, where the protocol has an Interpretation, sends them to the same model.

**Retention of a recording.** The recording stays in your browser until it is uploaded; if the upload fails or you cancel, DevLab deletes that copy from your browser. If you close the page before the upload ends, the copy stays in your browser until you clear this site's data or, once 72 hours have passed, until the next time you record on this site. It is uploaded in parts to DevLab's server and kept there only until it is processed. When processing ends, the video, the audio and any transcript are deleted from DevLab's server and from the Hosted Processor, and the manifest from DevLab's server. In any case, DevLab deletes the video when the job is handed to interpretation or completes, when it finally fails, or after 24 hours at most; an upload that is never completed is deleted after 72 hours. A marker with no content remains on DevLab's server for 7 days, so that the same recording cannot be uploaded twice. The Hosted Processor keeps a technical record of the job for 30 days (its step manifest, with your browser's user agent, and the download address, which no longer works once the video is deleted), with no video or audio. DevLab keeps in its database a record of the job, with no video, audio or text: internal identifiers of the session and of its enrolment, your account and your team, its state and any error code, the attempts, the result of the interpretation as a closed value (such as ready or failed), technical data of the wait for the interpretation, counts of frames per step, its times (when it was created, sent and finished, and when the video was deleted) and, if it has them, the parameters it was sent with (the context, the spoken language and the steps that are transcribed). DevLab deletes that record when it deletes the test person or, if the video had not yet been deleted, normally within an hour after deleting the video.

**Sessions and deletion.** DevLab deletes the test person and all its data in Engine 24 hours after creating it, or earlier when you press "Delete now". So that you can go back to a session of those 24 hours, live or recorded, DevLab's server keeps for each one only fixed values and numbers: when it was enrolled, the audience it was enrolled with and the one Engine applied, the way (SDK or HTTP API), the number of steps, the duration, whether the interpretation arrived and the state of the baseline and, if you record, the context, the spoken language and whether it is transcribed; never text or the transcript. These values are deleted with the test person; if deleting the test person in Engine fails, DevLab keeps them until a later attempt succeeds. After that, each session remains only as a count with its date, its protocol and its mode (live or recorded), with no audience, no outcome and no context or language. That count stays linked to your account and your team, with no set period; if your account is deleted, it is detached from the account and remains linked only to the team. The calls you see stay in your tab; DevLab keeps their metadata (route, status and timing) in memory for 30 minutes, never their content.

**Third-party downloads.** To capture, your browser downloads the face-tracking software (MediaPipe) from cdn.jsdelivr.net and its model from storage.googleapis.com and, with transcription, the speech software from cdn.jsdelivr.net and its model from huggingface.co and *.hf.co. With the SDK way and the camera or the sample video, entering Measure downloads the face-tracking software and model (about 13.5 MB) without you pressing anything, even before you accept the Playground consent. With "Transcribe" on, it also downloads speech (about 160 MB) the same way, but only on a good connection, without data saver and on a wide screen; otherwise, when you press Measure or "Download now". Those servers see your IP address and your browser, but receive nothing captured.

You can withdraw your consent at any time by not starting new runs and pressing "Delete now"; withdrawal does not affect processing already carried out.

## 6. Legal bases

Where the GDPR, the UK GDPR or the Swiss Federal Act on Data Protection apply, we rely on these legal bases:

| Processing | Legal basis |
| --- | --- |
| Account, sign-in, sessions, calls to Engine, Hosted Processor credentials, transactional emails | Performance of the contract with you or with the Customer you act for |
| Acceptance records and confirmation emails | Performance of the contract; our legitimate interest in proving the contract and in establishing, exercising or defending legal claims; compliance with legal obligations to keep evidence |
| Activity record, failed sign-in records, technical security data, backups | Our legitimate interest in operating DevLab securely, preventing abuse and showing teams their progress |
| DevLab updates by email | Our legitimate interest in informing professional users about the service they use; you can unsubscribe at any time |
| The Assistant | Our legitimate interest in helping you use the Documentation; you choose whether to use it |
| The Playground | Your consent, which you can withdraw at any time; for data that may be biometric or concerning health, your explicit consent |
| Downloads of the capture software when you enter Measure in the Playground, before you accept its consent | Our legitimate interest in having the capture ready when you start; you can avoid them by not entering Measure, or by choosing the HTTP API way or the synthetic sample before entering Measure |
| Support and correspondence | Performance of the contract, or our legitimate interest in answering you |
| Responding to authorities and keeping records required by law | Compliance with legal obligations |

Where we rely on legitimate interest, we have weighed it against your rights, and you can object (see section 11).

## 7. Recipients and subprocessors

We do not sell your personal data and do not share it for advertising. We disclose it only to:

- the service providers that host and operate DevLab for us, listed with their purpose and location in [Subprocessors](/legal/subprocessors): OVH (hosting of DevLab, its database and the Hosted Processor queue in the preview environments, France) and Google (Google Cloud for DevLab, its database and the Hosted Processor queue in production and for Engine and the Hosted Processor, United States; the Gemini API for the Assistant and the Interpretation, United States; and Google Workspace for email, United States and European Union);
- the Organization Admin and Neurologyca administrators, who can see the people, activity and acceptances of the Customer's teams as described in the Documentation;
- professional advisers, auditors and insurers, under confidentiality;
- authorities, courts or other parties where required by law or to establish, exercise or defend legal claims;
- a successor in a merger, acquisition or sale of assets, subject to this Notice.

## 8. International transfers

Neurologyca is established in the United States. In the preview environments, DevLab and its database are hosted in France; in production, they are hosted in the United States, so that the account data of those who use DevLab in production, and the other data described in section 3, are stored there. Engine, the Hosted Processor and the Gemini API are operated in the United States; our email, in the United States and the European Union; and members of our staff located in Spain may access the data to operate and support DevLab.

When personal data from the European Economic Area, the United Kingdom or Switzerland is transferred to a country without an adequacy decision, we use the Standard Contractual Clauses approved by the European Commission, the UK International Data Transfer Addendum and the adaptations required by Swiss law, or another mechanism recognized by the applicable law, such as a recipient's certification under the EU-U.S. Data Privacy Framework and its UK and Swiss extensions. You can ask for a copy of the relevant safeguards at info@neurologyca.com.

## 9. Retention

| Data | How long we keep it |
| --- | --- |
| Account data | For the life of the account; deleted when the account is deleted |
| Sessions | Until sign-out or expiry (7 days without use, 30 days at most); the record is deleted one day later |
| Failed sign-in records (email, IP address) | One day |
| Invitation and password reset links (hash) | Until used or expired (72 hours and one hour); then deleted |
| Activity record, including IP addresses, Playground consent and Assistant metadata | 12 months; team milestones are kept without the person who triggered them |
| Acceptance records | Life of the account plus 10 years; IP address and user agent cleared after 12 months |
| End User identifiers reached through DevLab | 24 hours |
| Playground call metadata | 30 minutes, in memory |
| Playground test person in Engine | 24 hours, or until "Delete now" |
| Playground session values (when it was enrolled, the audience, the way, the steps, the duration, whether the interpretation arrived, the state of the baseline and, for a recording, the context, the spoken language and whether it is transcribed) | Until the test person is deleted (24 hours, "Delete now" or, if deleting it in Engine fails, until a later attempt succeeds); then each session remains only as a count with its date, its protocol and its mode |
| Count of each Playground session (its date, its protocol and its mode), linked to your account and your team | No set period; if your account is deleted, it is detached from the account and remains linked only to the team |
| Playground recordings and their manifest in DevLab | Until handed to interpretation, completed or finally failed, and 24 hours at most; incomplete uploads 72 hours |
| Playground job records in DevLab (internal identifiers, account and team, state, error code, attempts, the result of the interpretation as a closed value, technical data of the wait for the interpretation, counts per step, times and parameters, with no video, audio or text) | Until the test person is deleted or, if the video had not yet been deleted, normally within an hour after the video is deleted |
| Marker of an uploaded Playground recording on DevLab's server, with no content | 7 days |
| Technical record of a Playground job in the Hosted Processor (step manifest with the browser's user agent, and the download address) | 30 days |
| Assistant questions and answers | Never stored by DevLab |
| DevLab updates: recipients, unsubscribe token hashes and unsubscribe list | For as long as DevLab sends updates by email |
| Database backups | 14 days in the preview environments; in production, as set out in section 3.9 |
| Support correspondence | For as long as needed to handle the request and any related claim |

## 10. Cookies and browser storage

DevLab uses one cookie and a few browser storage entries. All of them are strictly necessary to provide the service you ask for or remember a preference you set. DevLab uses no advertising cookies, no analytics and no third-party tracking.

| Name | Type | Purpose | Duration |
| --- | --- | --- | --- |
| `devlab_session` | Cookie (HttpOnly, SameSite=Lax) | Keeps you signed in | Until sign-out; 7 days without use, 30 days at most |
| `starlight-theme` | localStorage | Your theme choice (light, dark or automatic) | Until you clear site data |
| `devlab-lang` | localStorage | Your language choice | Until you clear site data |
| `devlab-news-seen` | localStorage | The last DevLab update you closed | Until you clear site data |
| `devlab-code-tab` | localStorage | The code language you chose in the Documentation | Until you clear site data |
| `nl-ref-lang` | localStorage | The request language you chose in the API reference | Until you clear site data |
| `devlab-pg-view` | localStorage | How the Playground shows calls | Until you clear site data |
| `devlab-pg-sources` | localStorage | The source used by each Playground run, so that baseline and measurement use the same one | Until you clear site data; pruned by the Playground |
| `devlab-assistant.target` | localStorage | The page the Assistant opened for you, to highlight it | 30 seconds |
| `kodec.stt.v4` | localStorage | Device facts for on-device transcription in the Playground (no text, no identifiers) | Until you clear site data |
| `devlab.session.anonymousAt` | sessionStorage | Remembers for 60 seconds that you are not signed in | Until the tab closes |
| `devlab-assistant.conv.v1` | sessionStorage | Your Assistant conversation | Until the tab closes |
| `devlab-assistant.open.v2` | sessionStorage | Whether the Assistant panel is open | Until the tab closes |
| `devlab-pg-run` | sessionStorage | The active Playground run of the tab | Until the tab closes |
| `devlab-baseline-ask` | sessionStorage | Whether to ask again about capturing a baseline | Until the tab closes |
| `devlab-integration-kit:<team>` | sessionStorage | The last protocol you opened in the kit | Until the tab closes |
| `devlab-legal-accepted` | sessionStorage | The version of the Terms you have just accepted, to show you once that your acceptance was recorded | Until that message is shown, or until the tab closes |
| `devlab-legal-later` | sessionStorage | The version of the Terms whose advance notice you chose to see later, so that the notice is not shown again in the tab | Until the tab closes |
| `sl-sidebar-state` | sessionStorage | The state of the Documentation sidebar | Until the tab closes |
| `kodec.stt.tab` | sessionStorage | A random identifier of the tab for on-device transcription | Until the tab closes |
| `neuro-capture-recordings` | IndexedDB | A Playground recording until it is uploaded | Until uploaded or canceled; a copy left behind when the page is closed is deleted the next time you record on this site once 72 hours have passed, or when you clear site data |
| Speech models | Cache Storage | The on-device transcription model (about 136 MB), when you use transcription | Until you clear site data |

Because these entries are necessary or record a choice you make, DevLab does not ask for cookie consent. You can delete them at any time by clearing the site data in your browser; you will then be signed out and your preferences reset.

## 11. Your rights

### 11.1 European Economic Area, United Kingdom and Switzerland

You have the right to access your personal data, to have it corrected or erased, to restrict or object to its processing, to receive it in a portable format and, where we rely on consent, to withdraw consent at any time. You can object at any time to processing based on our legitimate interest, including DevLab updates by email. DevLab makes no decisions about you based solely on automated processing that produce legal or similarly significant effects.

### 11.2 United States

If you are a California resident, the California Consumer Privacy Act, as amended by the California Privacy Rights Act, gives you the right to know what personal information we collect, use and disclose, to access it, to correct it and to have it deleted, and not to be discriminated against for exercising these rights. In the last 12 months we have collected identifiers (such as your email address and IP address), professional information (your organization, team and role), internet activity (your activity in DevLab), account login credentials and, in the Playground, information that may be biometric, all from you or your organization and for the purposes in sections 3 to 5. We use account login credentials and any sensitive personal information only for the purposes the law permits. We do not sell or share personal information, as those terms are defined in that law, and have not done so in the last 12 months. Residents of other U.S. states with comparable privacy laws have equivalent rights, which we honor in the same way.

### 11.3 Mexico

Under the Federal Law on the Protection of Personal Data Held by Private Parties, you have the rights of access, rectification, cancellation and opposition (ARCO rights), and you can revoke your consent or limit the use or disclosure of your data. Your request must include your name, a means to answer you, a document proving your identity (or that of your representative), a clear description of the data and the right you wish to exercise, and any document that helps locate the data. We will answer within the periods set by that law.

### 11.4 How to exercise your rights

Write to info@neurologyca.com from the email address of your account, or tell us how we can verify your identity. You may act through an authorized agent, who must show that you authorized them. We answer within the period set by the applicable law and, in any case, within one month, which may be extended where the law allows. Exercising your rights is free. Some data, such as acceptance records, may be kept where we need it to prove the contract or defend legal claims, and we will tell you when that is the case.

## 12. Complaints

If you think we have not handled your personal data properly, please write to info@neurologyca.com first. You also have the right to lodge a complaint with a supervisory authority: in the European Economic Area, the authority of the Member State where you live, work or where the alleged infringement took place; in the United Kingdom, the Information Commissioner's Office; in Switzerland, the Federal Data Protection and Information Commissioner; in Mexico, the competent personal data protection authority; and in the United States, the authority of your state, such as the California Privacy Protection Agency.

## 13. Children

DevLab is for professionals and is not directed to anyone under 18. We do not knowingly collect personal data from anyone under 18. If you believe that someone under 18 has given us personal data, write to info@neurologyca.com and we will delete it.

## 14. Security

We protect personal data with measures appropriate to the risk, including encryption in transit (TLS), hashed passwords, session identifiers and link tokens, encryption of API Keys and Hosted Processor credentials with AES-256-GCM, access limited to the people who need it, records of administrative actions, protection against password guessing and regular deletion of data that is no longer needed. No system is completely secure; if a personal data breach is likely to put you at risk, we will tell you as the law requires.

## 15. Changes to this Notice

We may update this Notice. We publish each version at [/legal/privacy](/legal/privacy), at its own address and with its effective date, before it takes effect, and keep earlier versions available. If a change is significant, we will tell you in DevLab before it takes effect.
