Last updated: October 18, 2026
This Privacy Policy explains what information we collect, why we collect it, and how we use and store it.
Please be aware that this is a student project and changes to the service and data policy are likely to happen frequently!
Information we collect
Cookie for consent decision: We store a cookie (or session/local storage flag) recording whether you accepted or declined session data storage. Tutorial status: We store a cookie (or session/local storage flag) recording whether you completed the tutorial. User input: Commands you type into the game are sent to our server to run the game and are kept in the memory of your game session. Submitted stories: If you submit a story, its text, its category and the time of submission are stored on our server. Please do not include personal information in your story. Abuse protection: To limit the number of submissions, your IP address is kept in the server's memory for about one hour. It is not written to disk.
How we use the information
Consent cookie: used only to remember your privacy decision for the current session or across visits (depending on cookie type). User input: processed to run the game, respond to requests, and maintain game state. Submitted stories: we review every story before it is published. Only approved stories appear on the Stories page; we may decline or delete any submission.
Storage and retention
Game input and submitted stories are kept only in the server's working memory, not in a database or file. A game session ends when you close it or after a period of inactivity. Submitted stories, approved or not, are deleted whenever the server restarts. If too many stories are waiting for review, the oldest unreviewed ones are discarded. The consent cookie/session flag is retained according to its type (session storage cleared at end of session; persistent cookie kept until expiration).
Sharing and publication
Approved stories are published on the site. Once published, they are viewable by other users and may be indexed by search engines. We do not sell your personal data. We do not share user inputs or stories with third parties except as required to operate the service (e.g., backend providers) or when required by law.
Data protection and security
We implement reasonable administrative, technical, and physical safeguards to protect data from unauthorized access and disclosure. Access to stored inputs is limited to authorized personnel and systems necessary to operate and maintain the service.
Your choices
You can accept or decline the consent cookie when prompted. If you decline, input functionality may be limited until consent is given. You may request removal of your submitted story by contacting us (see Contact below). Removal requests will be processed in accordance with our policies and technical constraints.
Changes to this policy
We may update this Privacy Policy. The “Last updated” date at the top will show when changes were made. Continued use after changes constitutes acceptance of the revised policy.
For questions, data removal requests, or other privacy concerns, contact us: contact