StoryPic
StoryPic is a children's learning app designed to be used under parent or guardian supervision. It is an educational support tool, not a medical device, and does not diagnose, treat, or assess a condition.
This policy distinguishes installed legacy clients whose supporting calls are now retired from the planned local-device client, which is not yet released. A website or backend change does not give an older installed app the planned client's behavior.
1. Version 3 (3.6) and Earlier Builds
These installed builds were designed around the following legacy behavior:
- Cloud Photos: Photos captured in the app were sent to a cloud server and recognition provider to identify objects.
- Cloud Speech: Story text was sent off-device to a speech service, including Microsoft Azure Speech, to create narration.
- Weekly Email Summaries: A parent could register and verify an email address for progress summaries. The address was linked to an opaque profile identifier.
- Legacy learning data: Email summary snapshots could include a profile name, language, activity and story counts, observations, and vocabulary. Registration records could include verification, delivery, send, and bounce information. Earlier generation requests could carry richer learning context than the restricted candidate requests below.
- Historical Data: Production rows related to registrations, speech, and generated content are not automatically purged. Removing the app does not automatically delete a historical registration from the service.
Current backend status: The backend now retires the legacy cloud-photo, cloud text-to-speech, and weekly-email operations. Calls to the retired operations return a gone response and the weekly scheduler sends nothing. Version 3 (3.6) and earlier builds may therefore lose those features.
Cloud generation, speech, hosting, and network providers processed legacy requests and connection information. Provider logs, cached speech or illustrations, production rows, and backups can have separate retention periods. StoryPic does not promise immediate deletion or provider zero retention. Retiring an operation does not automatically delete its historical records.
2. Planned Local-Device Release
The new client described in this section is pending release verification and is not yet available. It changes how data is processed to prioritize local computation.
Information kept on the device
StoryPic has no child account or cloud sign-in. A parent PIN is a local gate, not server authentication. The app's local store can include consent state, the PIN, child profiles, a name or age range a parent enters, settings, activity history, saved stories and questions, answers, progress observations, and accessibility preferences.
Operating-system backups can copy local app data outside StoryPic's direct control. StoryPic does not make a blanket guarantee that all information exists only on one physical device.
In the planned release: Photos are processed from a local URI by an approximately 17 MB classifier bundled with the app. It maps only to cup, spoon, ball, book, and banana. Its conservative suggestion requires confirmation and is not a validated accuracy measure. Photos are not sent to StoryPic or an image-recognition provider. If matching fails or is uncertain, the user can choose one of the five objects manually.
Camera and operating-system libraries may create temporary or cache files. StoryPic does not use those files as server learning data, but cannot promise that every operating-system cache or device backup is erased immediately.
Generic cloud features (Planned Release)
New stories, illustrations, and questions require a network connection. A story request sends only an approved catalog key, language, and level; an illustration request sends only the key. A question request sends those dimensions plus a temporary token, not story text. These requests do not include a child name, age, profile or activity history, recently practised words, free text, or a photo.
The server validates the key and derives provider prompts from server-controlled catalog content. It can hold up to 500 generic story/token mappings in process memory for up to ten minutes, bound to the same item, language, and level. They disappear on expiry, eviction, or restart. Generic illustrations may be cached from a server-controlled prompt without a child-profile link.
Cloud hosting, generation providers, and network services necessarily process connection information such as IP address, request timing, and technical headers. Operational logs can contain a request ID, route, response status, timing, errors, and connection information. Infrastructure providers can keep their own security or access logs. StoryPic does not promise no logs, provider zero retention, or that all connection information is unidentifiable.
Narration (Planned Release)
The planned client does not send narration text to StoryPic or Microsoft Azure Speech. It uses voices considered eligible from metadata supplied by the operating system or installed voice provider.
Voices reported as network-required or not installed are excluded; web voices must report that they are local. Voice availability, quality, language support, download state, metadata accuracy, and any vendor processing depend on the operating system or voice provider. StoryPic cannot guarantee every vendor-provided voice operates entirely offline. Narration requires no microphone recording.
Local matching and manual five-object selection remain available offline. Previously available local content may remain usable. New cloud stories, illustrations, and questions require a connection.
Retired weekly email and parent deletion support
The planned client does not offer weekly email registration, verification, summary syncing, status checks, manual sends, or scheduled mail. The backend now returns a gone response for those retired operations and its scheduler sends nothing.
An older registration can require an authenticated unregister request using its opaque profile ID and registration token. The planned client keeps only pending opaque cleanup credentials in a retry queue across app restart, profile deletion, and "Delete Everything"; it removes an entry only after the server confirms unregistering.
Feature retirement does not automatically purge historical production rows. Contact us for help with a historical registration deletion request. We may need to verify your authority before acting.
Deletion and retention limits
Clear History removes the selected profile's learning history from the app-owned local store. Delete Profile removes that profile and its app-owned local learning data. Delete Everything removes the main local state, including the PIN, profiles, progress, saved content, and settings, while preserving only pending opaque credentials needed to retry authenticated legacy-email cleanup.
These controls do not establish deletion from device backups, operating-system camera or cache areas, provider or infrastructure logs, or historical backend rows.
Advertising and tracking
The planned client contains no third-party advertising or analytics SDK and does not use data for cross-app tracking. Provider processing needed for generic cloud features is not advertising or tracking, but it is still off-device processing as disclosed above.
Contact Us
For policy questions or help requesting deletion of a historical weekly-email registration, contact:
Do not email child photos, child names, story text, passwords, or registration tokens. An email request alone is not proof that deletion has completed.