Privacy Policy
On this page
Last updated: 13 September 2026
1. Who we are
Brockily (brockily.com) is operated by Justin Putland, an Adelaide-based educator. Contact: hello@brockily.com.
2. What we collect
| Data | Purpose | Retention |
|---|---|---|
| Display name + email | Account identification and sign-in | Until account deletion |
| Study activity (reviews, scores, schedules) | Spaced-repetition scheduling and progress reports | Until account deletion |
| Game results and earned items | Leaderboards and in-game progression | Until account deletion |
| Class membership | Connecting students to their teacher's class and homework | Until leaving the class or account deletion |
| Content you create (sets, cards, uploads) | Delivering it to the audience you chose | Until you delete it or your account |
| Subscription status (teachers) | Knowing what your account is entitled to | Until account deletion |
| Security logs (sign-ins, admin actions, IP address) | Abuse prevention, rate limiting, security audit | 24 months |
| Guest live-play data (nickname, submitted answers) | Running the game and the teacher’s post-game report | 30 days after the game |
| Browser cookie | Session authentication only — no tracking | Session duration |
If your school's licence ends, student accounts at that school and the study data attached to them are deleted 90 days after the end date. The school is told when that date is set, and can ask for an export or renew at any point inside those 90 days. Teacher accounts and the sets they created are not deleted on this schedule.
We do not collect location data, device fingerprints, or advertising identifiers, and we show no ads. Guests play under a nickname with no account. Guest does not mean no saved session data. Brock Battle Royale keeps guest nicknames and room credentials temporarily in its game service. Other classroom games can save nicknames, answers and game results for the teacher’s report. A guest session does not create an account or personal review schedule. In a live quiz the nickname and the answers given are stored so the game can run and the teacher can see the results afterwards, and are automatically deleted 30 days after the game.
Signed-in study stores review history against the learner’s account. Some study games also keep progress on the device in browser storage; device-local saves are separate from account history and can be cleared by clearing site data. Check the game’s save controls before changing devices.
3. Payments (teachers only)
The optional teacher subscription is processed by Stripe. Your card details go directly to Stripe and never touch Brockily's servers — we store only your subscription status and a Stripe customer reference. See Stripe's privacy policy. Students are never asked for payment and cannot spend real money on the Platform.
4. Who can see your data
| Viewer | What they see |
|---|---|
| Your teacher | Study progress, homework results, and review-consistency reports for their own classes |
| Classmates | Leaderboard name and rank only — never academic data |
| Other users | Content you deliberately made public (public study sets), with your display name |
| The operator | Data as needed for support and safety, access-logged |
5. Third-party services
- Render — hosting. Our servers and database run in Render's Singapore region, so your data is stored outside Australia; Render's edge network (Cloudflare) carries traffic. Render's privacy policy
- Stripe — subscription payments, as above.
- Google — only if you choose "Sign in with Google"; we receive your name and email to create or match your account. Not used otherwise.
- Email delivery — a transactional email provider sends verification and password-reset emails to the address you gave us.
We do not sell data to anyone, and no analytics or advertising SDKs run on the Platform.
6. Children's privacy
Brockily is designed for school use, including students under 18. Students can play without an account. Teachers host classroom games and choose the available guest or tracked setting: a code and a nickname, or signing in so answers feed that student’s own revision. Signing in is the default there, because the revision record is the point of the product; the no-account option is one tick away, and stores only the nickname and the answers given, deleted 30 days after the game. Where accounts are used, schools and teachers are responsible for ensuring appropriate consent under their school's policies. We handle personal information in accordance with the Australian Privacy Principles, collect the minimum needed to run the service, show no advertising, and never ask students for payment.
7. Your rights
- Access & portability: download a JSON export of your data from Settings → Account, or email hello@brockily.com.
- Correction: update your profile from account settings.
- Deletion: delete your account from Settings → Account (or email us). Erasure from the live system is immediate and irreversible — a purge, not a soft-delete. Residual copies in our hosting provider's automated database backups expire on a short rolling cycle (no longer than 90 days).
8. Security
All traffic is encrypted (HTTPS/TLS). Passwords are hashed with PBKDF2-HMAC-SHA256 (100,000 iterations, per-user salt) — we never store and cannot recover your plaintext password. Sessions use HTTP-only secure cookies. Optional two-factor authentication (with single-use recovery codes) is available on every account, and security-relevant actions are audit-logged.
9. Changes
If this policy changes materially we will say so on the Platform. The "last updated" date above reflects the latest revision.
10. Contact
Privacy questions: hello@brockily.com