Mossybook Parents · Data handling
Your family’s data.
What the product uses, how school connections work, and the controls available to you.
Who is responsible
Mossybook Parents is operated by Steven Inge, a sole proprietor in Virginia, who is responsible for the information described here. For privacy questions or requests, email hello@mossybook.com. The terms of service cover the subscription and use of the app.
Information used for your family
Mossybook Parents uses your account email, child profiles, grade levels and preferences to organize school information. Connected sources can provide grades, assignment status, teacher feedback, upcoming work, notices and readable linked documents. Saved records include their source and observation times so you can check where an update came from.
The app also keeps connection status, practice content, your Ask conversations, subscription status and email delivery records. School access is for reading authorized parent-visible information. It does not submit assignments or send messages to the school.
Who can see it
In the app, your family’s records are shown only to you and the adults you invite to your family, and each family’s records are kept separate from every other family’s. They are not private from everyone, though. Steven Inge, who runs Mossybook, can reach them to run and fix the service. The companies listed under Services involved store or process them for us: the database and website hosts, the computer that checks your school accounts, the email service and the two AI services.
Your school logins
School login details are encrypted before storage. The restricted collection worker can decrypt them to sign in to the school service on your behalf. Encryption is recoverable for that purpose; it does not mean the service has no ability to access the credentials.
The website and AI do not receive the worker’s decryption key. School passwords and session cookies are excluded from AI requests and family exports. School browser sessions are sensitive too: the current collection runtime uses temporary browser contexts and does not save school session cookies for later use.
A changed password, multi-factor authentication or a school sign-in challenge may require your help to reconnect. An incomplete check stays visible; it is not an all-clear.
What AI can read
Mossybook uses two AI services, OpenAI and TypeSafe. Requests can include your questions, children’s names and grade levels, grades, assignments, teacher feedback, school posts and messages, linked-document text and source dates. They never include your school passwords or session cookies.
Pictures of document pages and screenshots of school app pages are sent to OpenAI so it can read what plain text extraction misses, such as scanned pages, charts, slides and handwriting. OpenAI also answers Ask questions and writes practice sheets. TypeSafe receives text only, such as your Ask questions, children’s names and grades, and the text of school posts and assignments. It sorts and labels school items, decides which school pages are worth opening during a check, and helps answer questions. Each AI service processes requests under its own terms.
School questions are read-only. Answers include source references and information gaps; they do not contact teachers or change school accounts. Your 50 most recent Ask conversations are saved to your account so you can reopen them. They stay until you delete your account or leave the family.
Usage analytics
Mossybook uses first-party reports and Mixpanel to understand which screens and features parents use, where setup gets stuck, and whether features work. We send specific actions and random identifiers for your account and family. For signed-in parents, we also send the parent account name and email to Mixpanel on their profile and signed-in activity events so we can identify who used a feature. Each caregiver has a separate profile. We do not send children’s names or identifiers, grades, school content, questions, search text, photos, documents, school passwords, payment details or private links. We do not record your screen.
Usage analytics are on by default. You can turn them off under Usage analytics. Your account and school checks work with analytics off. Turning it off stops new usage tracking and requests deletion of your previous usage analytics. Provider deletion can take several weeks. First-party usage records are available only to admitted administrators and retained for 90 days. They are removed when you turn usage analytics off or delete your account. Mixpanel normally retains events in this project for up to two years unless deletion is requested sooner. Your analytics choice and the random identifiers needed to honor privacy requests are kept separately from school information.
How long information stays
School-source history has a rolling retention window of 400 days after its last successful observation. Seeing the same information again refreshes that window. A failed check does not make old information newly observed.
Completed, failed and superseded check jobs are deleted after 60 days, together with their snapshots, practice packets and email payloads. Your family’s eight most recent checks are kept however old they are, so an account whose checks have stopped still shows its last results. Copies of school pages taken during a check are kept for about a week, and screenshots for about a day, except those behind your latest results. The cleanup runs every day. The longer school-source archive is separate. Provider backups and payment records have separate retention arrangements.
Saved school login details remain until you disconnect that source or delete the family account. You can’t remove a child in the app yet. To remove one, email hello@mossybook.com, and we’ll delete that child’s profile and the school records saved for them from the app’s database.
When you invite someone by email, a scrambled code made from their address and the time of the email are kept for 31 days, to limit how many invitation emails can be sent.
Sharing: if you sign up with another family’s share link or code, we record which family’s link you used. That family sees how many families joined with their link, never who. You see their first name on the invitation. So that the same children can’t earn a free month twice, we keep a scrambled code for each child’s school record, made from the school’s student number, even after the family account is deleted. It contains no name or school information. We also keep a record of each free month we add, with its amount and Stripe reference, as part of our billing records; it no longer points to a family once that family’s account is deleted.
Your controls
Disconnect a school source: stops future collection from that connection and removes its saved sign-in. Previously collected school history remains under the retention rules above. Disconnecting does not delete your school account.
Download family data: exports child profiles, settings, school history and practice records as a JSON file. School passwords, session cookies and payment-card details are excluded. If an export cannot be completed, the app reports a failure rather than returning a partial file.
Delete the family account: requires your current password and a typed confirmation. If you have a subscription, deleting ends it right away, with no refund for the rest of the month. A payment that is still being confirmed has to finish first. Family records, Ask conversations and encrypted school logins are removed from the app’s database at once. Removing your sign-in and sessions can finish afterward; if it doesn’t complete at once, it is retried every hour.
Deletion does not remove records held by the school. It is not an instant purge of every provider’s systems or backups. A minimal account identifier remains to prevent a deleted account from being recreated by an old session. A message already being sent may still arrive.
Services involved
Supabase stores accounts and the database. Vercel hosts the website and app. The worker that checks your school accounts runs on a Google Cloud computer. It decrypts your school logins there to sign in, and reads and copies the school pages and documents it checks.
Resend sends account and school-update email. OpenAI and TypeSafe provide the AI features described above. Stripe handles payment and subscription information; the app does not store payment-card details.
The app has no advertising-pixel or behavioral-advertising integration.
This guide explains product behavior. It is not a complete legal privacy notice.
Back to Mossybook