# Saving game progress without creating accounts for children

**URL:** <https://forum.serverless.com/t/saving-game-progress-without-creating-accounts-for-children/22077>\
**Category:** Serverless Architectures\
**Created:** [October 24, 2026, 6:32am UTC](https://forum.serverless.com/t/saving-game-progress-without-creating-accounts-for-children/22077 "2026-10-24T06:32:43Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![gregorymiller](https://avatars.discourse-cdn.com/v4/letter/g/3d9bf3/32.png) [@gregorymiller](https://forum.serverless.com/u/gregorymiller)\
**Post date:** [October 24, 2026, 6:32am UTC](https://forum.serverless.com/t/saving-game-progress-without-creating-accounts-for-children/22077/1 "2026-10-24T06:32:43Z")

</div>

I am looking at options for saving progress in short browser games without asking children to register. The Dad4Kids page I have in mind is [Reading a Clock — Free Telling Time Games for Kids](https://dad4kids.com/en/math-games-for-kids/telling-time-games/). This is an architecture question, and I do not have a deployed Lambda setup to compare yet.

For a first version I would keep progress in the browser. If a parent later wants to move it to another device, would you use a short-lived export code backed by API Gateway, Lambda and DynamoDB, or put the saved progress in a signed token?

The saved data would be the exercise identifier and completed level, without names or dates of birth. I am unsure how to handle repeated imports and expired codes without adding a permanent user identifier. I would appreciate examples of how others have handled that part.