Privacy Policy
This version has been superseded. Read the current Privacy Policy.
Version 2026-10-25.2. Earlier versions: 2026-10-25, 2026-10-22.
What we collect
Students join without creating an account or giving an email address. We do not ask for student rosters or grades. Classroom records include the team names entered in class and the game decisions and results, so use team names that do not identify students. For AI coach and debrief requests, we replace team names with neutral labels before sending game information to the AI provider.
- Teacher beta application (voluntary). If a teacher applies for the classroom beta, we store what the form asks: name, role, work email, school, courses and grade levels, approximate class size, sections, devices, whether the school network needs an allowlist, when they want to run the first class, and — optionally — how they heard about Informatist and a school email or staff page. Club applications also ask for a faculty advisor's name, email, or both. We do not ask for student names, student emails, rosters, or grades. The older waitlist form stores only the email address and, optionally, the subject taught.
- Game sessions. Starting a game creates a random session key. We do not ask for a name, email or account to play. In the classroom version, the key is stored with the team name the class enters and the team's decisions, so treat it like any classroom record. The game decisions you submit (prices, production levels and similar numbers) are processed under that key to run the simulation.
- Classroom game records. For each classroom game we keep a record of how it played: the team names the class typed, every round's decisions and results, the AI rivals' explanations, the coach's questions, and the teacher debrief. It holds no player keys or PINs. Team names are free text chosen in class and stored with the game records. Students are asked not to use real names. We use it to review and improve the game and to answer a teacher's questions about their class.
- Standard server logs. Our web server records each request: IP address, time, the page or endpoint requested, status and size. Logs rotate daily and we keep 14 daily files, so a log entry is deleted about two weeks after it is written. We use them to keep the service running, to stop abuse and to count usage, never to profile people.
- Terms acceptance. When a teacher creates a class, we record which version of the Terms of Use was accepted, the time, and the class join code, in that class's game record. We do not store an IP address, the access link or the teacher's email with it. It is kept and deleted together with the class's game record, including for a class that was created but never started.
What we do not collect
- No student accounts or required contact details. We do not ask students for email addresses or rosters. The team name entered in class is free text and is stored with the game records. Students are asked not to use real names.
- No tracking. No advertising, no analytics scripts, no tracking pixels, no third-party cookies. We use no cookies at all. Browser storage holds only what a session needs: the demo's game id and seed (so you can resume), the classroom student and teacher credentials plus the teacher's recent-room list, the teacher access token used to create a class, session-only recap/identity/forecast flags, and the version of the browser-storage notice you confirmed separately for students, teachers and the demo (the informatist-storage-notice-student, informatist-storage-notice-teacher and informatist-storage-notice-demo keys).
- No data sales. We do not sell or rent data. We share it only with the service providers listed below. There are no advertisers, no data brokers, and no "partners".
Students and children
Students join without an account or email address. The classroom version asks for a team name and instructs students not to use a real full name. Team names are free text, so information entered there is stored with the game records. If you believe a child has submitted personal information to us anyway, email us and we will delete it. The application asks for the applicant's contact information and class details; it never asks for student names, student emails, rosters, or grades.
How long we keep things
- Single-player demo sessions expire and are deleted within 24 hours.
- Classroom game rooms are deleted after 7 days without activity for a single-period class, or 30 days for a multi-day unit (the longer window is what lets a class resume next lesson), and in any case no later than 14 or 60 days after the class was created.
- Classroom game records are kept for one year after the class's last activity, then deleted. This includes the Terms acceptance line, which also exists for classes that never started. A room being deleted does not delete its record; to have the record deleted sooner, email admin@informatist.net with the class join code.
- Server logs rotate daily. We keep 14 daily log files, so entries are deleted about two weeks after they are written.
- Daily backups of the server data are kept for up to 180 days, so a deleted item can remain in a backup until that backup expires.
- Teacher beta applications and waitlist entries are kept while the classroom beta and its communications are active, or until you ask us to remove yours — email admin@informatist.net and we will delete it, no questions asked.
Named regulations, in plain terms
- COPPA (children under 13). Students do not need an account or email address. Team names are chosen in class and stored with game records; the join form tells students not to use full real names.
- FERPA (education records). The product does not request student rosters or grades. Teacher applications collect professional and contact information. Classroom game records include the free-text team names entered by the class, along with decisions and results.
- California SOPIPA (K-12 online services). We show no advertising, build no student profiles, and do not sell data. Classroom game records contain the team names entered in class.
These are statements of how the product actually works, written for teachers and IT staff — not legal certifications.
Service providers
These outside services handle data for us:
- DeepSeek (AI text generation). Receives game numbers — prices, production, market statistics — and refers to teams only by neutral labels ("Team 1", "Team 2"). The team name a class types in is replaced by its label before anything is sent and restored afterwards for display, so it stays on our server. We do not send names, emails or other text students typed. DeepSeek may process these requests outside your country. Teacher application data is not sent to DeepSeek.
- Amazon Web Services (hosting and email). The site and game run on AWS infrastructure in the United States (AWS region us-west-2); mail sent to admin@informatist.net is received via AWS SES, and new-application notifications are sent through AWS SES to the operator addresses.
- Google (Gmail). An operator mailbox hosted by Google (Gmail) receives short notices that a new teacher application or a service alert has arrived, and copies of emails we send to teachers, such as welcome emails with their access link. New notices contain no application details; we read applications in a password-protected admin page on our server. Notices sent before this change included application details, and copies of those may remain in the mailbox.
This list will be updated here whenever it changes.
Who is responsible, and your rights
Glidelogic Corp., 8275 S. Eastern Ave., Suite 200-#406, Las Vegas, NV 89123, USA (admin@informatist.net), runs Informatist and is responsible for the teacher applications, access links, website logs and service operation. For classroom game records, the school decides how Informatist is used in teaching. If your school needs a data-processing agreement, contact us. We use teacher application data to run the beta and contact applicants (taking steps at your request and our legitimate interest in running the program), and logs to keep the service secure (legitimate interest). Data is stored in the United States. You can ask to see, correct or delete your data, or object to its use, by emailing admin@informatist.net. We answer within one month. If you are in the EU or UK you can also complain to your data-protection authority.
Changes and contact
If this policy changes, we will post the new version here with a new effective date. Questions, deletion requests, or a school district's security review: admin@informatist.net.
This is a plain-language policy written to be read by teachers, parents, and IT administrators — not to hide anything in clause 47(b). Informatist has run browser-based economic simulations since November 11, 2006.