Glyphia

Privacy

This page explains what information Glyphia uses to run reading adventures for children aged 7 to 10, what we do not collect, and how to contact us with questions.

Glyphia is preparing for a small private beta. These pages describe how the product works today. They are beta basics, not a full lawyer-reviewed compliance programme, and they may change as Glyphia develops.

Privacy at Glyphia

Glyphia is a choose-your-own reading adventure for children. Your child reads short stories, picks from options we provide, and reaches an ending — there is no chat and nothing to type during the story.

We wrote this page in plain language so parents and guardians can see what happens today. It is not legal advice and has not been reviewed by lawyers.

What children do in Glyphia

Children choose a story world, hero, companion, magical object, reading level, and story voice from preset lists on the setup screen. They then read scenes and tap structured choices to continue. When the story ends, they may tap one of three simple feedback options.

There are no public user accounts and no sign-in for children or parents in the current beta.

Information used to run a story

To run an adventure, Glyphia uses:

  • Anonymous reader and story-session identifiers, so the app can keep one device's reading history separate from another's.
  • Setup selections your child makes from preset lists (world, voice, hero, companion, object, reading level).
  • A private code in a cookie on your device so repeat visits can be recognised and we can avoid offering the same finished adventure again.
  • What happened in the story: which choices were picked, the story text your child saw, the rendered scene and choice snapshots, how far they got, and when the adventure started or finished.
  • Generated story output that helps us check safety, debug problems, and improve the beta.
  • Optional ending feedback: one structured rating — Loved it, It was okay, or Not this time.
  • Coarse internal product and usage signals, such as whether a story started, a choice was selected, or a safety check passed or failed.

What children cannot type

Children cannot enter free text during the reading loop. There is no chat box, no open questions, and no way for a child to type their own messages or story ideas inside Glyphia today.

Names and objects in stories come only from preset lists on the setup screen, not from typed answers.

Feedback at the end of a story

After an ending, your child may choose Loved it, It was okay, or Not this time. There is no comment box and no free-text feedback. We store the rating together with basic details like which world and voice were used to help us improve adventures during beta.

Cookies and how we learn during beta

Glyphia sets one essential cookie: an anonymous reader identifier used for repeat-story handling. We only use the one cookie described below.

We do not use advertising trackers. We do not use outside analytics tools like Google Analytics.

Glyphia keeps simple internal notes about how the app is used during the beta, such as which story world was chosen, whether a story was rated as fun, or whether a safety check passed. We use this to fix problems and improve the experience. We do not share this with outside analytics companies.

Who helps run Glyphia

Glyphia relies on a small number of trusted partners to host and run the app. At a high level:

A hosting partner serves the website and application.

A secure online service helps store story progress, repeat-visit history, and optional ratings so adventures can run and improve.

A specialist writing service helps create new story scenes. Glyphia sends the story-generation prompt and story context needed to create a scene to that service. Every scene is checked before your child sees it.

Provider logging and broadcast settings are configured to be off in the current beta evidence, but story-generation content is still sent to the writing service when live generation is used.

These partners process data only to operate Glyphia. We do not sell personal information.

How long information is kept

During the private beta, retention is manual and practical: we keep information for as long as needed to run adventures, improve safety, debug problems, and understand how stories are used. We do not promise a global automated deletion schedule for all product data today.

Some technical usage-limit records have their own operational retention setting, but that is not a full product-data deletion policy.

We do not yet offer automated deletion tools or a parent dashboard in the app. If you have questions about access or removal, email us at the address below. We will handle requests manually during beta and respond as we can, but response times are not guaranteed.

Parent and guardian choices

Glyphia is designed for use with a parent or guardian nearby. You decide whether and when your child uses the app. There is no parent dashboard in the current beta.

If you have privacy concerns, questions about what was stored, or want to ask us to look into data linked to your child's use, please contact us.

Contact

Privacy, cookies, and data access or removal questions: privacy@glyphia.app

Child safety concerns or inappropriate content: safety@glyphia.app

General questions: hello@glyphia.app

For grown-ups: how Glyphia worksReturn home