Privacy Policy

Last updated 3 November 2026

CodeAcorn (“we”) is a learning website used by schools to teach coding. This page explains what information we collect, why, and the choices you have. It applies to codeacorn.com.

Who the accounts belong to

There is no public sign-up. Teachers or school staff create accounts for their students. For student accounts, the school and teacher decide what the account is used for; we process the data on their behalf to run the class.

What we collect

• Account details: name, school email address, the class you are in, and whether you are a student or teacher. If you sign in with Google, we receive your Google account ID and email (to match your account) — not your Google password or other Google data. A backup password, if you have one, is stored only in scrambled (hashed) form.
• Your work: the code you write (saved drafts and every submitted attempt), the automatic check results, scores, and comments between you and your teacher.
• Lesson activity: when you sign in, and during live lessons whether your lesson page is open and in front (used for attendance). We cannot see other websites or apps.
• Technical data: like any website, our server records IP addresses and browser details in its logs for security and to fix problems.

Visitors who are not signed in can read the public pages without giving us any personal information.

How we use it

• To run lessons, check and score work, and show teachers their students’ progress and attendance.
• To send emails you would expect, such as a teacher’s comment on your work.
• To keep the service secure (for example, limiting repeated wrong passwords).

We do not sell personal information, and we do not use students’ work or account data for advertising.

Who can see it

Students see their own work. Teachers see the work of students in their classes. School administrators of CodeAcorn can see accounts and activity to run the service. We share data only with services that help us run the site (web hosting and email delivery), or when the law requires it.

Cookies

• Needed to work: a session cookie keeps you signed in, a security cookie protects forms, and — only if you tick “Keep me signed in” — a cookie remembers you for a few days.
• Preferences: your browser may store small settings, such as which tab you last used, and a backup copy of code you are typing.
• Advertising (public pages only): see below.

Advertising

We may show ads from Google AdSense on public pages in the future. If we do, ads will never be shown inside classes, lessons, live lessons or student work.

• Third-party vendors, including Google, use cookies to serve ads based on a user’s prior visits to this website or other websites.
• Google’s use of advertising cookies enables it and its partners to serve ads to users based on their visit to this site and/or other sites on the Internet.
• You may opt out of personalised advertising by visiting Google Ads Settings, or opt out of some third-party vendors’ cookies at aboutads.info.
• Learn how Google uses information from sites that use its services: policies.google.com/technologies/partner-sites.

Where the law requires consent for advertising cookies (for example in the EEA, the UK or Switzerland), we ask for it before ads use them.

How long we keep it

Class work and grades are kept so teachers can produce term reports, and are deleted when the school asks or the account is removed. Database backups are kept for 14 days. Server logs are kept for a short time and then removed automatically.

Your rights

You can ask to see, correct or delete your personal information, or object to how it is used, in line with the law that applies to you (including Thailand’s Personal Data Protection Act). Students should normally ask their teacher first. You can also contact us directly.

Children

CodeAcorn is used by school students, some of whom are under 18. Their accounts are created and supervised by their school. We collect only what is needed for the class and never show ads inside student areas.

Security

Connections use HTTPS, passwords are stored hashed, and student code previews run in a sandbox so they can’t affect the site or other users.

Changes

If we change this policy we will update the date at the top of this page.

Contact

Questions about privacy: contact@codeacorn.com.