Privacy
Operated by AI Fusion Technologies, LLC · Children and school-use guidance updated October 13, 2026.
Operator contact
AI Fusion Technologies, LLC
18015 NE 30th ST
Redmond, WA 98052
Email: support@mystorysprouts.com
For privacy questions or requests to review, remove, or stop further collection of information about your child, contact this address. Please identify the relevant book or recording without emailing identity documents or unnecessary child information. We may need to confirm your authority before providing access or taking action.
Children’s privacy and COPPA
Children may preview the first five pages of public books without an account. To keep reading, a parent or caregiver must sign in. Accounts, book submissions, comments, and recording uploads must be managed by an adult. Children must not independently enter an email address, create an account, or upload personal information.
The Children’s Online Privacy Protection Act (COPPA) addresses personal information collected online from children under 13, including images and voices. StorySprouts has not yet completed verification of the consent, retention, and parental-rights procedures needed to claim COPPA compliance for collecting student information. An adult-account notice or recording-permission checkbox is not, by itself, verified parental consent.
For teachers and schools
The current service does not provide student accounts, a school-authorization workflow, or a class-only sharing space. Do not direct students to register or submit their personal information through the site. Teachers may use the existing story library for supervised reading activities. Creating a teacher account does not establish school authorization to collect student information or permission to upload a child’s face or voice.
Do not use StorySprouts to collect identifiable student books, comments, or recordings as a classroom activity until an appropriate school or parental authorization arrangement and data-handling procedures are in place. School authorization for educational use does not automatically permit public promotion, public YouTube sharing, or commercial use of student content. Review the Author Agreement before submitting any work.
Sharing and removal choices
Use a pen name and leave children’s surnames, schools, addresses, and contact details out of submitted books and comments. Draft books are accessible to the account holder and site owner. Published public books are visible to everyone; private or restricted visibility is not a dedicated classroom space.
Parents or guardians manage children’s recordings. Unlisted YouTube links can be watched and forwarded by anyone who has the link; they are not class-only access. Public featuring requires a separate permission request and administrator approval. Account holders can delete their own comments and recordings using the controls described below. These controls do not establish a complete parental review-and-deletion process for every category of student information.
For information about COPPA, see the Federal Trade Commission’s guidance.
Reading statistics
StorySprouts collects anonymous daily totals to understand which books are opened and which pages are reached. Reading remains free of account requirements.
Our anonymous reading counters store only the date, book, event type, page number, and count. It does not store names, emails, IP addresses, account IDs, or individual reading histories. No analytics cookies or persistent reader identifiers are used. Signed-in and anonymous visits are counted the same way.
The site owner receives signup alerts containing your verified email address, and alerts for submissions and activity needing review. Resend delivers these emails.
Email sign-in
We store your verified email address and account ID. Sign-in codes and links expire after 15 minutes and work once. We store hashes of sign-in codes, links, and session tokens, not the tokens themselves. You can open the link in any browser or device. A secure sign-in cookie keeps you signed in for 90 days. This is an essential account cookie, not a tracking cookie. Signing out revokes that session. Resend receives your email address, sign-in code, and sign-in link to deliver the message. Signing in with the same verified email as an existing account preserves that account’s books.
Story drafts and submissions
When you connect an assistant, we store your site-specific account ID, the connecting app’s name and callback addresses, and an expiring connection record. Access tokens are stored as hashes. You can revoke access from My books. Draft text, pen names, descriptions, submission status, revision dates, and editorial feedback are stored in our database; uploaded illustrations are stored privately in object storage. You and the site owner can access your books. Submitting sends the book to the owner for review, but does not publish it. Your chosen AI client separately processes content you share with it.
QR invitation flyers
For public books, flyer QR codes open the story directly without sign-in, acceptance, or a reader grant. Scanning a public-book flyer does not add an email to the reader list. The generated flyer page can expire or be revoked; printed story links remain usable while the book stays public.
For selected-reader books, book owners can create shareable invitation flyers with the book’s cover or opening illustration, title, author credit, an expiration, and an optional acceptance limit. Anyone with a valid flyer link can see that illustration and sign in to accept reading access without separate owner approval. We store the flyer’s shareable identifier, issuing owner, creator, dates, limit, count, and revocation status. To enforce limits without counting scans, we store each accepting account’s verified email, account ID, flyer, and acceptance date. Acceptance adds the email to the book’s existing reader list. The owner and site admin can see that list. Expiration or revocation stops new acceptances; previously granted reading access remains until the owner removes it. The owner can reopen flyers to print or share them. No external QR-generation service receives invitation links.
Book invitations and reading requests
Owners can also email invitations to public books. We store the invited email address, book link, invitation date, and email delivery status so the owner can check delivery and resend. Resend delivers these messages. These invitations do not create a mailing-list subscription, change the book’s audience, or grant selected-reader access. Public books can be read without signing in.
Published selected-reader books appear in the library with their title, author name, description, and page count so readers can request access. Their manuscript text, cover, and illustrations remain restricted. Unpublished books are not listed.
For selected-reader books, we store invited email addresses and reading requests, including the requester’s verified email, account ID, request date, decision, and decision date. The book owner and site admin can see and manage them. A request does not grant access; the owner must approve it or invite the email address. Owners can remove reading access. Requests and invitations are private, and the owner’s contact address is not displayed to visitors. We retain request decisions to show status and prevent repeated unwanted requests.
When an owner invites an address or approves its request, Resend receives that address and a book link to deliver an invitation or confirmation. These explicit access messages are sent separately from optional activity alerts, including to invited addresses without an account. Sign in with the invited email to read; forwarding the link does not give another address access. We store delivery status and retry information. Owners receive request alerts according to their notification preference.
Notifications
We store account-specific notifications for new submissions, comments, reports, and review or publication decisions, including their dates and whether you have marked them as read. Notifications are private to the relevant author and admin. Email alerts are enabled by default when you sign in; we store your sign-in email address and preference. You can turn email alerts off from Notifications. Once email delivery is connected, enabled alerts are sent through our email provider. The provider receives your email address and a brief event summary with a link; comment text and manuscript text are not included. Delivery status and retry information are stored to avoid duplicate sends.
Book comments
Comments require an adult-managed signed-in account. We store your chosen display name, comment text, book, account ID, date, status, and moderation history. Comments appear immediately for readers with access to the book, and the book owner and site admin are notified. The owner or admin may ban or restore comments. Older comments awaiting approval are now visible; previously hidden or deleted comments remain hidden. Your email and account ID are not shown in the comments interface. Do not include contact details. You can delete your own comments, removing their text and display name from the active database while retaining a deletion record. Reports store the comment, reporter account ID, date, and resolution status; reporter identities remain private.
Reading videos
Recording uses your camera and microphone only after you enable them. Nothing is uploaded until you choose Save recording. Saving automatically uploads the recording using your selected sharing setting, under the recording terms. We initially store the combined video, account ID, book, duration, upload status, permission timestamps, and feature-review status. Private video files are available only to your account and the site owner. Private YouTube uploads retain a server copy for account playback. With your permission, new recordings are uploaded with your chosen private or unlisted visibility to the StorySprouts YouTube channel. Anyone with the link can watch and share an unlisted video, even without a StorySprouts account. We retain the video file temporarily until YouTube confirms processing, unlisted or public visibility, and unrestricted embedding; then we delete our video file and keep its YouTube ID and account metadata. If YouTube blocks unlisted access, processing fails, or cleanup is interrupted, the server copy is retained for playback or retry. Older private recordings remain private until their owner explicitly opts into unlisted sharing. My readings checks pending uploads while open and offers manual retry. Google and YouTube process those uploads under their own policies, including reviewing private videos for abuse or copyright issues.
Recording is managed by adults: you must have permission from everyone recorded and be the parent or legal guardian of every child recorded. Requesting a feature requires separate permission to share faces and voices publicly. Only the site owner can approve and publish a requested feature. Public videos may be viewed and shared by anyone. My readings lets you withdraw permission, return an unlisted reading from public to unlisted (or an older private reading to private), or delete the recording and its YouTube copy. If YouTube is unavailable, these actions remain incomplete until successfully retried. Copies downloaded by other people cannot be recalled. Unlisted links remain accessible after a feature is withdrawn; delete the recording to remove its YouTube copy. YouTube recordings and account metadata are retained until you delete them. YouTube playback uses YouTube’s privacy-enhanced player; playing a video sends information to YouTube.
Author licenses
When you continue to an account or submit a book with the linked terms notice, we store your account ID, authority declaration, acceptance time, agreement version and text, and snapshots and fingerprints of covered books. One-time acceptance covers existing submitted or published books and future submissions, without repeated acceptance. Withdrawal records preserve evidence of the license and the cutoff for future publishing. Authors can withdraw future publishing rights; copies already printed may still be sold and distributed, and earlier authorized uses remain valid. Nonpublic license records and snapshots are retained to document those rights. Earlier accepted versions retain their original provisions, including broader withdrawal rights where promised. The site owner handles rights concerns and removal obligations. We do not automatically apply commercial terms to existing books.
YouTube API Services
StorySprouts uses YouTube API Services. The channel owner authorizes uploads and management of the organization’s channel through Google OAuth; readers do not grant access to their personal YouTube accounts. We keep the channel ID and authorization credentials in protected server configuration and use them to upload recordings, check processing and visibility, change authorized visibility, and delete recordings. The channel owner can revoke this access through Google security settings. Revocation stops future API access but does not itself delete videos already uploaded; deletion must be completed through YouTube or by reconnecting the channel. Google handles information under its Privacy Policy. YouTube may receive device, network, and playback information and use cookies or similar technology when its content is loaded or played, and may show advertisements under its own policies.
Book reviews
Reviews require an adult-managed signed-in account. We store the book, account ID, a rating from 1 to 5 stars, optional written text, date, status, revision, and moderation history. Each account can review a book once. Reviews appear immediately in Reader reviews and notify the book owner and site admin. The library shows the average and count of published ratings, including for selected-reader listings, without showing reviewer account IDs. Only the site admin can ban or restore reviews; a banned review and its text are hidden and its stars are excluded from the average and count. Book owners can read reviews on their books but cannot ban them. Older written reviews remain accessible through their original stored text and no longer appear as separate comments. Previously hidden or deleted text stays hidden. Reviews are saved only when you choose Submit review, including when privacy signals are enabled.
Book likes
Liking a book requires signing in. We store your site-specific account ID, the book, and when you liked it so each account can like a book only once. Public readers and the engagement dashboard see totals, not who liked a book. Click the liked heart again to remove your like and its record. Likes do not store your name or email.
We respect browser Global Privacy Control and Do Not Track signals by skipping automatic reading statistics. Likes are saved only when you choose to like a book, including when these signals are enabled. Your hosting and sign-in providers may separately process technical information needed to deliver the site.
A visit to the final page is a last-page visit, not proof that someone finished reading. The site owner can view site-wide engagement. Signed-in authors can view aggregate reading activity and like totals for books owned by their account, including retained activity after unpublishing. Authors cannot see who read or liked their books.