PRIVACY / DATA PROCESSING

The boundary should be visible before the microphone turns on.

This page states what the public demonstration does today, what it does not prove, and the data decisions that must be fixed before a venue deployment.

PUBLIC DEMOUSE FICTIONAL DETAILSDEPLOYMENT TERMS ARE SEPARATE

01 / PUBLIC DEMO

Fictional venues. Deliberate data boundaries.

The Airport, Market and Dental Reception experiences contain synthetic fixtures. No real passenger, customer, patient, booking, inventory, clinic calendar, advertiser or venue system is connected. Model-generated results and offers are fictional even when the interface presents a complete journey.

Typed text and microphone audio are processed to generate responses, transcribe speech and support live conversation. The live demo does not request camera access or capture camera stills. The application is designed not to write demo transcripts or audio to a SimulatingMachines database, and generated text requests use a no-store setting. The current repository does not establish zero-data-retention terms for every processing path, so we do not promise that all processing is retention-free.

Do not enter real names, dates of birth, booking references, medical information, payment information or other sensitive data. Use fictional details only. Closing or resetting the demo clears the visible browser session; it does not change any retention that may apply during service processing.

02 / VENUE DEPLOYMENTS

A customer contract is necessary, but it is not the whole lawful basis.

Before any pilot collects real interaction data, the deployment must declare the service purposes, controller and processor roles, subprocessors, lawful basis, visitor notice, retention, deletion and export process, security review, incident handling and the route for data-subject requests. Raw-audio handling and sensitive-input rules must be explicit.

Customers control supplied venue-state and service data under contract. Rights in interaction and derived records are defined by contract and applicable law. Service delivery does not imply permission for internal training, cross-venue learning or external licensing; each requires a separate, explicit permission and purpose.

Recording a conversation may be technically possible and may be requested by a venue, but it is not automatically permitted. The actual design must follow the applicable law, the declared roles and purpose, and the choices communicated to the person using the service.

QUESTIONS / DATA BOUNDARY

Ask before you connect a real system.

This is a product-data boundary, not a claim that a production deployment or complete privacy programme already exists. For a pilot or a data request, contact us first.

hello@simulatingmachines.com