This Data Processing Addendum ("DPA") forms part of the SimReactive Terms of Service (or other agreement) between Pixel & Pulse Simulation LLC ("Processor", "we") and the Customer. It applies whenever we process Customer Personal Data on the Customer's behalf.
1. Definitions
- Customer Personal Data — personal information about Authorized Users (instructors, administrators, learners) that we process on the Customer's behalf in providing the Service: learner speech and transcripts, cue text, debrief inputs, and any personal information in Customer Content.
- Data Protection Laws — US federal and state privacy laws that apply to the processing, including FERPA where the Customer is an educational institution. When this DPA is extended under Section 12, it also includes the GDPR and the UK GDPR.
- Security Incident — a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Personal Data.
- Sub-processor — a third party we engage to process Customer Personal Data.
Other capitalized terms have the meaning given in the Terms of Service.
2. Roles and instructions
2.1 The Customer is the controller (or "business") of Customer Personal Data, and we are its processor (or "service provider").
2.2 We process Customer Personal Data only on the Customer's documented instructions. Those instructions are:
- the Terms of Service;
- the Customer's use of the Service's features; and
- any further written instructions we agree to.
We will tell the Customer if we believe an instruction breaks Data Protection Laws.
2.3 We will not:
- sell or share Customer Personal Data;
- use it for any purpose other than providing, securing and supporting the Service;
- combine it with personal information from other sources, except as the law permits for a service provider; or
- use it to train AI models.
2.4 Customer responsibilities. The Customer is responsible for:
- the lawfulness of its instructions;
- giving notice to, and obtaining any consent required from, its Authorized Users, including learners, about the processing of their speech by AI providers; and
- ensuring no real patient information (protected health information) is provided to the Service.
The Service is designed for fictional scenarios and must not receive protected health information.
3. Confidentiality of personnel
Everyone we authorize to process Customer Personal Data is bound by confidentiality obligations, and access is limited to what their role requires.
4. Security
We maintain the technical and organizational measures in Annex II. We may update them, but we will not lower the overall level of protection during the Customer's subscription term.
5. Sub-processors
5.1 The Customer authorizes the Sub-processors on our Sub-processor List (Annex III).
5.2 New Sub-processors.
- We will give at least 30 days' notice before a new Sub-processor starts processing Customer Personal Data. We give notice by updating the list and emailing account Administrators who have subscribed to notices.
- The Customer may object on reasonable data-protection grounds.
- If we cannot address the objection, the Customer may terminate the affected Service and receive a refund of prepaid fees for the remaining term.
5.3 We impose data-protection obligations on each Sub-processor that are at least as protective as this DPA, to the extent the service allows. We remain responsible for our Sub-processors.
6. Education records (FERPA)
Where the Customer is an educational agency or institution subject to the Family Educational Rights and Privacy Act (20 U.S.C. § 1232g; 34 C.F.R. Part 99):
6.1 School official. We act as a "school official" with a legitimate educational interest, performing an institutional service for which the Customer would otherwise use its own employees. We do so under the Customer's direct control with respect to the use and maintenance of education records.
6.2 Limits on use. We use education records only for the purposes of this agreement.
6.3 No redisclosure. We do not redisclose education records except:
- to our Sub-processors, to provide the Service; or
- as FERPA or other law permits or requires.
6.4 Access requests. We will help the Customer respond to requests to inspect, review or amend education records, to the extent they are held in the Service.
6.5 Education records. Hosted encounters may contain learner speech in transcript form, formative reviews, debriefs and associated generated audio. Include these in institutional access, return and deletion procedures. Institutions also control their own exports and printouts.
7. Assistance
Rights requests.
- Taking into account the nature of the processing, we will help the Customer respond to requests from individuals to exercise their rights.
- If an individual contacts us directly about Customer Personal Data, we will pass the request to the Customer and not respond ourselves, unless the law requires otherwise.
Other assistance. We will provide reasonable information the Customer needs for:
- data-protection assessments;
- security questionnaires (for example HECVAT); and
- consultations with regulators.
8. Security Incidents
We will notify the Customer without undue delay, and in any case within 72 hours after becoming aware of a Security Incident affecting Customer Personal Data.
- What the notice includes: the information reasonably available to us about the nature of the incident, the categories and approximate numbers of individuals and records affected, likely consequences, and the measures taken or proposed.
- Afterwards: we will cooperate with the Customer's investigation.
- Not an admission: notification is not an admission of fault.
9. Deletion and return
- Proposed export window. During the term and for 30 days afterward, arrange return of eligible customer data, subject to the signed agreement.
- Proposed deletion. Delete covered data after the agreed window, subject to legally required preservation. Backup timelines remain under review.
- Exceptions. We may keep information when the law requires it (for example billing records), under continued confidentiality.
- Written confirmation. On request, we will confirm deletion in writing.
10. Audits
- How we show compliance. We will make available the information reasonably necessary to demonstrate compliance with this DPA: completed security questionnaires, summaries of our safeguards, and, when available, third-party audit reports.
- Further audits. If the law requires more, the Customer may audit once a year on 30 days' notice, during business hours, at its expense, under confidentiality, and in a way that does not compromise other customers' data.
11. Liability
Each party's liability under this DPA is subject to the limitations in the Terms of Service, except where Data Protection Laws do not permit the limitation.
12. International transfers (for EU/UK expansion)
The Service is currently offered only in the United States. If we agree to provide the Service to a Customer in the European Economic Area, Switzerland or the United Kingdom:
- (a) the GDPR, UK GDPR and Swiss law become Data Protection Laws for that Customer;
- (b) the EU Standard Contractual Clauses (Commission Decision 2021/914) are incorporated. Module Two (controller to processor) applies, with Annexes I–III of this DPA completing their appendices. The UK International Data Transfer Addendum applies to UK transfers;
- (c) our obligations include those in Article 28(3) GDPR, and Sections 2–10 of this DPA are read to include them; and
- (d) we will name our EU and UK representatives under Article 27, where required.
Optional international transfer provisions remain under review.
13. Order of precedence
On a data-protection matter, this DPA prevails over the Terms of Service. If Section 12 applies, the Standard Contractual Clauses prevail over this DPA.
Annex I — Description of the processing
| Item | Description |
|---|---|
| Data subjects | The Customer's instructors, administrators and learners (students, trainees, staff). |
| Categories of personal data | Learner speech, transcripts and encounter artifacts. Staff account, organization, role and invitation data, fictional patient profiles, cues, and text supplied to generators or support. Operational data can include IP addresses and session events. |
| Sensitive data | None intended. The Service is not designed to receive health information about real people, and the Customer must not provide it. Voice audio is not used to identify anyone and no voiceprints are made. |
| Nature of processing | Authenticate users, manage invitations and org access, meter sessions, process speech, generate patient responses, conduct CALM reviews and create debriefs. Store patient libraries, eligible encounter records, and generated audio artifacts. |
| Purpose | Providing the SimReactive simulation Service to the Customer for healthcare communication training. |
| Duration | As agreed under §9, with a verified retention schedule covering saved encounters, generated audio and backups. |
| Frequency | Continuous during use. |
| Where | United States launch market. Contact us about specific data residency requirements. |
Annex II — Technical and organizational measures
The technical and organizational measures annex is under review. Institutions may request the current security information by emailing contact@pixelandpulsesimulation.com.
Annex III — Sub-processors
See the Sub-processor List.