School and family pilot · updated 11 November 2026

Your information in RagnoMath.

RagnoMath is developed and operated by Jordan Morrison. Contact ragnomath@gmail.com with privacy questions, access or correction requests, or a complaint. This notice describes the pilot currently offered at ragnomath.com.

What we collect and why

• Adults: name, email, password hash, workspace name, role, class assignments and acceptance of these terms. These provide account access, school separation, recovery and account emails.
• Learners: first name or nickname, optional last initial/year level, age in years, avatar, practice settings, answers, timing evidence, game progress and last-played time. These support individual practice and reports. Students do not supply email addresses.
• Technical records: session identifiers, device labels, administrative activity, request/error logs and IP-based rate limits, used to operate and protect the service.
• Support: information an adult chooses to include in feedback or a support email. Please omit sensitive student information.

Who can see it

School Super admins and Admins manage their school's records; Teachers access assigned classes. Families manage their own children. Other workspaces cannot access your records through the app. The operator may access records to operate the service, resolve support requests or investigate security issues.

A class code lets students see the first names or nicknames in that class. Personal passwords are enabled by default when a code is created. Keep them enabled and share codes privately. Class codes and learner passwords are stored encrypted so authorised adults can view and print login cards. Adult passwords are hashed and cannot be displayed.

Providers and overseas processing

Cloudflare hosts the application and database. Resend sends account and trial emails. Support replies go to the RagnoMath Gmail inbox. These providers may process information outside Australia; this pilot does not promise Australia-only data residency. Schools should assess this before adding real learner information. Student answers and class lists are not included in transactional emails.

Stripe is configured for payment testing only. No live payment or subscription is created by this pilot. The paid service will require a separate, explicit checkout action when it becomes available.

Cookies and browser storage

Necessary cookies keep adults, students and classroom devices signed in. Browser storage supports game preferences and local play. There are no advertising trackers or public student rankings. Guest play does not create a school record.

Retention and deletion

Finishing a trial does not delete students or progress. An authorised adult can delete individual learners; workspace export or deletion can be requested by email. Account-confirmation and invitation links expire after 24 hours; password-reset links expire after one hour. Expired link records and expired session/rate-limit records are removed by the hourly maintenance task.

Deleted records may remain temporarily in provider backups until those backups expire. Support correspondence is retained for handling the request and related follow-up; contact Jordan to request its deletion. A fixed automatic workspace or support-message retention period has not yet been set for the pilot.

Using the pilot with children

Adults create and control accounts. Schools and parents are responsible for arranging their required approvals and communication before adding children. Use fictional names to evaluate the service first, and first names or nicknames when possible. Do not enter medical details, diagnoses or other sensitive notes. Reports are teaching evidence, not diagnoses or standardised assessment results.

Questions and changes

Ask Jordan for access, correction, export or deletion, or to raise a privacy concern. We verify authority before acting on a request. Material changes to this notice will be dated here and communicated to workspace administrators.