Privacy Policy

Effective Date: October 9, 2026

                In Short: PerciGo acts as a client-side tool. We do not collect student names or personal information for our own use. Local progress stays on the user's device or in the teacher's private Google Sheet; a small amount of anonymous performance data (see below) may be used to keep difficulty levels fair, and live multiplayer games temporarily share player names with other participants in that same game.
            

1. Data Collection

PerciGo operates on a "Bring Your Own Database" model. The application runs entirely in your web browser and prioritises student anonymity.

No User Accounts: We do not require students to create accounts, set passwords, or provide email addresses to us.
No Personal Tracking: We do not use third-party trackers, and we never link performance data to an individual student's identity.
Local Storage: Progress (Medals, Stars) and preferences (Dark Mode) are stored locally on the specific device being used. If the browser cache is cleared, this data is reset.

2. Anonymous Performance Analytics

To help ensure our achievement levels and difficulty settings are fair and accurately calibrated for each year level, PerciGo may collect anonymous performance data — such as the number of attempts needed to reach a benchmark, or time taken to complete a timed activity — alongside a student's self-reported year level.

No Personal Information: This data is never linked to a student's name, email, or any other identifying information.
Anonymous Identifier: A random, non-identifying code is generated on the student's device to prevent the same result being counted multiple times. This code cannot be used to determine who a student is.
Optional: Setting a year level is optional. If it is not set, no performance data is collected for that profile.
Storage: This anonymous data is stored in a secure database controlled by PerciGo and is not sold or shared with third parties.

3. Live Multiplayer Games

Our "Live Game" feature (hosted by a teacher for a class to join with a PIN) works like other classroom quiz tools: it requires a small amount of temporary, shared data to function.

What's Shared: When a student joins a live game, the name they type in, along with their in-game score, is visible to the teacher hosting that game and to other students in that same game — this is how the shared leaderboard works.
Not Persistent: This data relates only to that specific game session. It is not linked to any other feature of PerciGo, such as the anonymous performance analytics described above.
Access Is Restricted: Only devices actively using PerciGo can access live game data — it is not publicly readable without an active session.
Recommendation: As with any classroom activity involving shared screens or leaderboards, we recommend students use a first name or nickname rather than a full name.

4. Google Sheets Integration

Teachers may opt to use our "Teacher Sync" feature. This connects the student's device directly to a Google Sheet owned and controlled by the teacher.

What is sent: After a timed activity, the student's device sends the student name entered in Student Settings, their year level, the topic and level, the achievement earned (including partial progress towards the next achievement), and their optional 4-digit PIN. The teacher's sheet also records the date, and keeps both the student's first result and their best result on each level so teachers can see progress over time.
This information is sent directly from the student's browser to the teacher's own Google Script. PerciGo does not intercept, view, or store this data.
The PIN: The PIN is stored in the teacher's sheet. It lets a student restore their progress on a new device using "Restore from Cloud". It is not used for anything else.
The sheet's contact with PerciGo: The tracker's "Update level headers" menu item downloads a public list of PerciGo level names and codes from percigo.com.au so the year tabs match the website. No student or sheet data is sent in this request.
The teacher is the sole data controller for any information collected in their spreadsheets.

5. COPPA & GDPR Compliance

PerciGo is designed with children's privacy in mind. We do not require accounts, passwords, or email addresses, and we do not maintain a central database of student names. Two features involve limited data as described above: live multiplayer games temporarily share a student-entered name within that game only, and our anonymous analytics use a randomly generated code (not linked to any name or other identifying detail) to avoid double-counting the same student. For schools, PerciGo is intended to be used under a school's authority to approve educational tools on behalf of parents, consistent with common approaches to the U.S. Children's Online Privacy Protection Act (COPPA) and similar frameworks; schools with their own procurement or privacy requirements should review this policy against those requirements. GDPR is most relevant to users based in the European Union; PerciGo is primarily designed for Australian schools.

6. Disclaimer

While we provide the code templates for the Google Sheets integration, PerciGo is not responsible for the security settings of the teacher's Google account. Teachers are responsible for ensuring their Google Scripts are deployed correctly and their spreadsheets are kept private. When setting up the tracker, Google asks the teacher to approve permissions for the script, including access to the teacher's own spreadsheet and a connection to percigo.com.au to download the public level list. These approvals are standard for any script copied into a Google Sheet. The teacher can review them at any time under Extensions > Apps Script, or remove them in their Google account permissions.

7. Contact

If you have questions about this policy, please contact us at: perspicaciafluency@gmail.com