These pages describe what the park does today and change when it does. Written by Cedar on 2026-10-07 by reading the server's actual code and settings (not from memory). Items marked to do are gaps found while writing it. COPPA as amended in 2025 (16 CFR 312.8(b)) asks operators to keep a written information security program with a named coordinator, a yearly risk assessment, safeguards, regular testing and a yearly review; this draft is organised that way.

Information security program

Bean's Place · internal · version 0.1 · [DATE ADOPTED]

1. Who is responsible

2. What we protect

DataWhereSensitivity
Sticker books: random id (UUID), picture name (bean colour + animal), PIN hash, device type, last seen, activity events, stickers, garden, hub visitsSQLite file ~/beansplace-backend/data/beansplace.dbLow: no names, emails, free text or location. The random id is a persistent identifier.
Performance reports (device numbers, no identifier)Same database, perf tableVery low
Web server logs (IP addresses)Hosting log files and monthly archivesLow to medium (IP addresses)
Secrets: admin key, mail service keys, mailbox passwords, alert topic, review-queue keyFiles in the operator's home folderHigh: they open other systems
Planned: parent emails, consent records, children's question text, learning-game resultsNot builtMedium to high. This program must be updated before any of it is collected.

3. Safeguards in place today

Collect less

Identity and the cookie

The server

Secrets

Changes and releases

Watching

4. To do (gaps found while writing this)

5. Yearly risk assessment

Done each [MONTH], and before any new kind of data is collected. The first one:

RiskLikelihoodImpactWhat we do
Someone breaks into the serverLowMedium: sticker books, logs, secretsHTTPS, firewall, fail2ban, backend on localhost only, secrets mode 600, updates via the control panel. To do: tighten database permissions.
A sticker book opened by someone who picks the same pictureMediumLowPIN option exists. To do: nudge PINs, or require one to find a book.
Data lost in a server failureLowMediumDaily server backup + nightly consistent database copy (30 days).
An AI assistant makes a harmful changeLowMediumPermission prompts for risky commands, dev-first changes, automatic rollback, standing rules. To do: backups (above).
A secret leaks into the code repositoryLowHighThe sync refuses key-like files and never copies .env; secrets live outside the repository.
Logs kept longer than promisedHigh (today)LowTo do: 14-day log deletion.

6. Testing and monitoring

7. If something goes wrong (incident response)

  1. Contain: take the affected part offline, or roll back the site. Change any secret that may have leaked.
  2. Assess: what data, whose, how many sticker books, and for how long.
  3. Tell people: The operator decides who must be told and by when (parents, authorities).
  4. Fix and record: fix the cause, write down what happened and what changed, and update this program.

8. Yearly review

The coordinator reviews this program at least once a year, and whenever we add a new kind of data, a new service provider, or a new person or assistant with access. Next review: [DATE].