Pixel & Pulse Simulation LLC ("Pixel & Pulse", "we", "us") Review date: November 19, 2026 · Version 1.0
This draft covers the hosted Portal, SimReactive, SimReactive OB and SimReactive CALM.
1. Who is responsible
Two roles, depending on the information:
- Account and billing information: we decide how it is used, so we are responsible for it (a "controller" or "business").
- Information inside a customer's account (simulated patients, sessions, transcripts, learner speech): the customer, usually a school, college or health system, decides how it is used, and we process it on the customer's behalf under our Data Processing Addendum.
If you are a learner, your institution is your first point of contact for questions about your information.
2. The most important points
- Every patient in SimReactive is fictional. Real patient information must never be entered or spoken. See our No Real Patient Information Policy.
- During live voice sessions our AI provider processes microphone audio to understand the learner and generate the simulated patient’s response.
- The Service can save encounter transcripts, debriefs and associated artifacts. What a user can reopen depends on the app, organization and subscription.
- We do not sell personal information, use it for targeted advertising, or use it to train AI models.
- The intended launch market is the United States. Contact us about specific data residency requirements.
3. What we collect
3.1 Account information
- Email address and password.
- The password is handled by our authentication provider (Supabase), which stores it in hashed form.
- Our servers pass it through at sign-in and sign-up, and never store or log it.
- Organization record. We maintain the organization associated with your account.
- Membership. This includes invitations, role, confirmed email status, organization and plan entitlements.
- Account events. Account creation, sign-in and account-management events. The proposed acceptance flow would also record which document version a person accepted, when and in what capacity.
3.2 Billing information (when billing opens)
- When paid sales open, planned records include billing contact, tax information, orders, credits, cancellations and invoices. Live payments are off.
- Card details: handled entirely by our payment processor (Stripe). We never receive or store full card numbers.
3.3 Content you create in the Service
- Simulated patient profiles and library.
- What they contain: names, ages, scenarios, histories and speech styles of fictional people, plus the portrait and voice chosen for them.
- Hosted libraries are scoped to the organization. Instructors choose a voice from the plan’s library. SimReactive OB uses a maternal roster.
- Generator requests. The text supplied to generate a fictional profile is processed by our AI provider. A saved profile becomes part of the organization library.
- Cue text and acting directions. Simulation inputs can be included in the AI request to shape the patient response.
3.4 Live session information
- Learner speech.
- Our AI provider processes learner audio for live conversation. This differs from saving a transcript or a generated patient or debrief audio artifact.
- We do not create voiceprints or use voice to identify anyone.
- Patient voice. The live system uses the native voice library. The hosted apps do not offer customer-designed voices.
- Transcripts and recovery. A transcript may appear in the app, persist in browser or hosted encounter storage, and be used to recover an interrupted session.
- Encounter history. The plan, app and user’s organization govern access to saved encounters. Disabling access to a feature does not by itself erase prior records.
- Debriefs and reviews.
- The Service can send conversation turns and scenario context to the AI provider for formative debriefs. CALM can also review an ongoing conversation to support the simulation.
- Saved artifacts can include transcript, debrief text and generated patient or debrief audio where supported. An instructor may export or print a separate copy.
3.5 Usage and technical information
- Usage. The Portal meters eligible live session time against the organization’s shared allowance and tracks eligible additional hours.
- Diagnostic reports. For example, a voice failing to start: the event, a short reason, and timings. No conversation content.
- Security reports. Pages that triggered a browser security policy.
- Hosting logs.
- Our hosting provider records IP address, time, page or endpoint requested, and browser type for each request.
- The hosting log retention period is under review.
- Web fonts. Some pages load fonts from Google, which receives your IP address and browser information.
3.6 Support communications
We process support email and questions submitted to the text-only Portal Support Assistant. The assistant uses an AI provider to answer questions. Keep learner identifiers, patient information and credentials out of both channels.
4. Cookies and browser storage
The Portal uses cookies for authentication and session operation. See the Cookie Notice.
| Cookie | Purpose | Lifetime |
|---|---|---|
simreactive_at |
Keeps you signed in (access token) | Until the browser closes |
simreactive_rt |
Renews your sign-in (refresh token) | 30 days |
simreactive_session |
Links your browser to its live session on our server | Until the browser closes |
simreactive_gate |
Remembers a valid access code, where one is used | Under review |
Browsers can keep settings and working session data. Ending a session or signing out does not remove an organization’s saved encounter records, downloaded files or printed copies.
5. How we use information
| Purpose | Information | Basis (US; and for future EU/UK use, the GDPR lawful basis) |
|---|---|---|
| Create and secure accounts; approve access | Account information | Performing our contract with you |
| Provide the simulation: patients, voices, transcription, debriefs | Content, live session information | Performing the contract; as processor for the customer |
| Meter hours and bill | Usage events, billing information | Performing the contract; legal obligation (tax records) |
| Keep the Service secure and working; prevent abuse | Technical information, logs, diagnostics | Legitimate interests in security and reliability |
| Support | Support communications | Performing the contract; legitimate interests |
| Improve the Service | Aggregated or de-identified usage information only | Legitimate interests |
| Comply with law and enforce our terms | As needed | Legal obligation; legitimate interests |
We do not use personal information for automated decisions that have legal or similarly significant effects on anyone. Debriefs are formative feedback for instructors, not grades.
6. Who we share information with
- Service providers (sub-processors) that run the Service for us: AI providers, database and authentication, hosting, payments and email. They are listed, with what each receives, on our Sub-processor List. They may use the information only to provide their services to us.
- Your organization. Authorized users can access organization resources according to role and plan, including eligible saved encounters.
- Legal and safety. When required by law, or to protect rights, safety and security.
- Business transfers. A successor in a merger or acquisition, bound by this policy.
We do not sell personal information or share it for cross-context behavioral advertising.
7. How long we keep information
| Information | Kept for |
|---|---|
| Account and library | During service. Proposed post-term export and deletion window is 30 days, subject to verified operations, backup rotation, signed terms and legal holds. |
| Demo accounts | A 14-day post-demo deletion target is proposed. |
| Saved encounters and associated artifacts | Retention periods for saved transcripts, debriefs, recovery records, generated audio and backups are under review. |
| Hosting logs | Retention period under review. |
| Billing and accounting records | Applicable tax and accounting retention requirements when paid sales begin. |
| Support and acceptance records | The proposed retention schedule covers support, evidence of assent where applicable, and legal obligations. Periods are under review. |
8. Security
Our safeguards include:
- encrypted connections (TLS);
- database rules that keep each organization's patient library separate, enforced by the database itself;
- authenticated organization membership and plan-based access controls;
- secret keys kept on our servers, never sent to browsers;
- short-lived session credentials for voice connections;
- browser security headers;
- review and minimization of operational logs.
No system is perfectly secure; we will notify affected customers of a breach as the law and our Data Processing Addendum require.
9. Your choices and rights
- Access, correction, deletion, export. Email contact@pixelandpulsesimulation.com. If your information is in an institution's account, we will work with that institution, which decides on the request.
- Depending on where you live, you may have further rights (for example under the Texas Data Privacy and Security Act or other state laws): to confirm processing, to obtain a copy, to correct, to delete, and to appeal a decision. We will respond within 45 days. We do not discriminate against anyone for exercising privacy rights.
- Appeals. If we decline a request, you may appeal by replying to our decision; we will respond within 60 days.
10. Children
The Service is for postsecondary and professional education. It is not directed to children under 13, and we do not knowingly collect their information. Learners under 18 may use it only within a supervised institutional program that has obtained any consent the law requires.
11. Location
The intended launch market is the United States. Hosting, backup and AI processing locations are subject to the arrangements identified in the Sub-processor List.
12. Changes
We will post updates here and, for material changes, notify account holders at least 30 days before they take effect.
13. Contact
Pixel & Pulse Simulation LLC · contact@pixelandpulsesimulation.com