Privacy

In one paragraph

Rehearsal Room is a practice tool offered by StableState LLC. To run a rehearsal it keeps the material you add, the words you and the cast exchange, the coaching and debrief, and the progress it works out from them, all under your account. The people running the service see counts and timings only: how many sessions, how long the cast takes to answer, how often something fails. They do not see your material, your answers, your email address or your feedback comments. You can download everything as a .rrt file and delete everything with one button.

Use mock details. Do not enter real patient, client, employer or colleague information. The cast cannot tell the difference and the service is not built to hold it.

What we keep, and where

• Your email address, to sign you in. There is no password. We also keep short sign-in records: a link that works once, the session that keeps you signed in for up to seven days, and counters that limit how often a link can be requested, kept against a scrambled form of the address.
• Your material: the text of files you add and text you paste, as text only. The original file is read once and not kept.
• Your sessions: every turn in the scene, the coaching, the debrief, the claims the cast is holding you to, and the questions carried to the next session.
• Your progress: counts of slips by kind, retries, and questions coming back.
• Your feedback: the rating and any words you add when you tap "Rate this session".
• Your topics: the saved project that groups the above, the same thing you download as a .rrt file.

All of it is stored in one place on StableState's servers in Microsoft Azure, in a journal file under your account. There is no analytics service, no advertising tag and no tracking cookie on this site.

What the operator view cannot show

The people running the service have a separate, password-protected view for keeping the service healthy. It is built on a file of events that holds only counts, timings and error classes: a session started, a turn took 1.8 seconds, a file upload was refused for size. It never contains your name, your answers, your material, file names, feedback words, or an identifier that maps back to you; in that file you are counted through a salted hash that is never shown. The same view also lists who has signed in: your email address, when you first signed in, when your last session was, how many sessions you held and finished, and your plan, taken from the sign-in records. It shows nothing you wrote or said. Small counts are hidden so a single person cannot be picked out. A test that plants a fake name, phone number and medical-looking text in answers, a file and a feedback comment, then searches the event file, the operator view and the service log, runs on every release and must find nothing.

What happens on your device

Dictation has two modes, and in neither do we receive or store audio. By default the mic uses your browser's own speech recognition, so the audio goes to the browser's maker (Apple in Safari, Google in Chrome) under that company's terms; we receive only the text you choose to send. A one-line notice says so the first time you use it on a device. If you turn on Private voice, dictation runs on your device instead: the first use downloads the speech files once (about 100 MB), your browser keeps them, and no audio leaves the device. The theme and the Private voice choice are kept in your browser. Nothing else is stored on your device.

Who else processes it

Browser dictation sends your voice to the browser's maker (Apple in Safari, Google in Chrome) under its own terms; it does not pass through us. To play the cast and the coach, each turn of the scene, together with the relevant parts of your material, is sent to the AI model provider that generates the replies, under the provider's commercial terms for API use. Under those terms the provider may not train its models on your content. The provider may keep API records under its own terms. Sign-in emails are sent through a transactional email service. Payments, where offered, are handled by a payment provider that sees your email and the payment, never the rehearsal. Each of these is a processor acting for StableState; none of them receives your data for any other purpose. The page's typefaces load from Google Fonts, so your browser sends its IP address to Google to fetch them, as it does for any site that uses that service; no other data goes with it.

How long

Your account and everything under it are kept while the account exists. Sign-in links expire in ten minutes; sign-in sessions in seven days. Event counts are kept for the life of the service in daily files with a fixed ceiling, oldest dropped first. Before a wider release StableState may clear early data; you will be told first and can download your .rrt files before that.

Your choices

• Download any topic as a .rrt file from the front page or the debrief. It is a plain file you own.
• Delete everything from Progress with "Delete all my data". It removes your material, sessions, progress, feedback, sign-in records and account from the service's store at once, by rewriting the store file without them; there is no undo, so download first. Removing a topic deletes the topic, its material and its carried-in questions and rewrites the store file the same way; the topic's sessions (your answers, the cast's words, the debrief, and the material text each session was created with) stay in History until you remove them one by one there, which rewrites the file too, or delete all your data. We do not take separate copies of the store. The hosting platform keeps a deleted storage share recoverable for 7 days; that does not include a copy of individual files or of your content.
• Sign out from the header, on this device. Sign-in links to your address stop working when the account is deleted.
• Ask anything about your data: contact@stablestateit.com.

Security

The sign-in cookie cannot be read by scripts, travels only over a secure connection, and is limited to this site. Sign-in links are single use and are stored only as a hash. The operator view uses its own password and its own cookie, separate from yours. The service runs behind a spending cap and per-person daily limits so it fails safe rather than runs away.

Contact

StableState LLC. Questions about this note or your data: contact@stablestateit.com. This note will be updated as the service changes; the date at the top of the Terms is the date of the last change to either page.