What your IT department will ask.
Written for the people who have to approve the software, not just use it.
Who can start a session
Only a signed-in instructor can create a room. Accounts are created by us, not by self-service sign-up. Students never sign in.
How students are identified
Students join with the session code and an identifier they type in themselves. Nothing verifies it. For graded sessions, a session can be restricted to a list of enrolled addresses.
What is stored
Whatever identifier the student types, plus their orders, trades, and positions for the session. It is kept for 30 days, and the instructor can download it for grading and research before then. We keep it longer only if the contract says so.
Where it runs
We host on Railway. The servers and the database run in its EU region, in Amsterdam, the Netherlands.
Tracking
No analytics, no advertising trackers, and no cookie banner, because there is nothing to consent to.
Availability
Rooms are recovered after a restart, so a deploy or a crash does not end a running session. We set up your first session with you and stay on hand while it runs, if you want us to. Email is answered within 24 hours.
Questionnaires and agreements
If your institution requires a data processing agreement, a security questionnaire, or an accessibility statement, write to [email protected].