Photo safety
Tippytale uses a child reference to guide the personalized character and story direction. Public product pages should use approved demo assets, not private family photos or private story content.
This page explains the practical boundary: the product needs enough visual direction to create a recognizable story hero, while public pages stay general and demo-based.
Quick answer
A photo helps Tippytale shape the child's character direction. Public examples should use approved demo assets, not private family photos, child names, prompts, or generated story images.
The reference helps the illustrated story character feel connected to the child: hair, face shape, expression, and general presence. The goal is a child-safe storybook character, not a public photo album.
Public pages should use approved template art and demo examples. They should not expose private child names, uploaded photo URLs, generated family images, story prompts, or private story text.
The product can use family inputs to make a private book feel personal without turning those inputs into public marketing material.
The important promise is simple: the photo helps create a better illustrated character, while public product pages and examples stay demo-based. Ready families can move into the product without pausing on a long policy page first.
FAQ
No. Public pages should use approved demo images and product examples, not private family uploads or private generated story images.
A photo helps guide the child's illustrated character direction so the storybook feels personal.
No. Tippytale's tracking rules are designed to avoid sensitive fields such as child names, photo URLs, prompts, story text, and generated image URLs.
Related next steps
Ready to make it personal?
