Last updated: July 7, 2026
ScenarioSplice is a classroom authoring tool. We do not collect any personally identifiable information from learners. A learner opens an assigned link, plays the scenario anonymously, and is never asked to sign in or provide a name, email, or any identifier. The only accounts on ScenarioSplice belong to authors — the educators and trainers who build scenarios — who sign in with Google.
When you (an author) sign in with Google, we receive and store your name, email address, and Google account ID. We store the scenarios you create, edit, and assign. That is the extent of it.
Nothing that identifies them. When a learner plays an assigned scenario, we record anonymous, aggregate interaction events — which choices were selected and whether the scenario was completed — so the author can see how a class performed in aggregate. These events are not tied to a name, email, login, or persistent device identifier. No learner account is ever created.
Scenarios are private to their author by default. A scenario becomes reachable only when you click Assign, which produces an unlisted link — playable by anyone who has the link, but never listed in a public library and marked noindex so search engines do not index it. You can revoke an assign link at any time.
We are building an optional per-learner gradebook. It is off by default and not yet available. When it ships it will be opt-in on a per-scenario basis: an author who wants per-learner results will explicitly enable it for a specific scenario, and only then will learners be asked to enter a name (or be matched against a roster the author provides). Before that feature is released we will publish, and honor, the specifics — a stated retention window after which learner-entered names are deleted, an author-facing delete control, and a per-scenario "don't collect names" toggle so fully anonymous play always remains available.
Because we collect no personal information from learners today, ScenarioSplice operates as a classroom tool that does not create student records, and we do not knowingly collect data from children. When the opt-in gradebook and roster features arrive — and for anything closer to FERPA-grade handling such as student accounts or grade passback into a school's LMS — we intend to deliver that through an LTI integration that layers on top of your school's existing LMS, so student records remain governed by your institution's own privacy controls and data-processing agreements rather than being duplicated here. Until those features exist and are documented, no learner PII is collected, so there is no student record for us to hold or mishandle.
Authors can request deletion of their account and all associated scenarios and data by contacting us. Because we store no learner-identifying data, there is nothing learner-identifying to delete today.
For privacy questions or data-deletion requests, email info@threadlimit.co.