FullSched

Kids' privacy notice

For parents and guardians. What FullSched collects from a child under 13, what it is for, who else receives it, and what you can do.

Last changed: November 10, 2026

Who we are and how to reach us

FullSched is run by BIZYROCKET LLC.

Mail: [BLANK: postal address]

Phone: [BLANK: phone]

Email: [BLANK: contact email]

We follow the children's privacy law

FullSched follows the Children's Online Privacy Protection Act (COPPA), the United States law about collecting information from children under 13.

A child under 13 cannot start a FullSched account. A parent or legal guardian starts it, adds the child, and decides whether the child gets their own way to sign in. We collect nothing from the child until the parent has agreed.

A child you add by first name only, whose schedule you type yourself, needs no sign-in. Then everything we hold about them came from you.

What we collect about a child, and what each is for

First name What it is for: So the child has their own column on the schedule.
Birthday What it is for: So we know who is under 13 and needs a parent's OK. We use it for nothing else.
A sign-in name and PIN, or an email address (your choice) What it is for: So the child can sign in. The PIN or password is scrambled; we cannot read it.
Their schedule, stars and goals What it is for: So they can see their day and mark what they did.
To-dos and homework they add What it is for: So nothing due is forgotten.
Requests they send ("Can I go to Kai's house?") and the answers What it is for: So a parent can say yes or no.
The network address and browser name of a device they sign in on What it is for: To keep them signed in and to keep the account safe.
Calendars a parent adds by their private address: the events from yesterday to 60 days ahead. A work calendar shows a child only the word "Work" and the times. What it is for: To show them beside the child's blocks. Read only.
Later, when it is turned on: questions they ask Ask, and the answers What it is for: To answer them. A parent can read every question and answer.
Later, when it is turned on: photos of homework, and the words of voice notes (the sound is not kept) What it is for: To turn them into to-dos.

What we do not do

  • We do not ask a child for more than is needed to use FullSched.
  • Nothing a child adds is public. A child cannot make anything public, and cannot talk to anyone outside the account.
  • We do not show ads, and we do not sell or share a child's information for marketing.
  • We do not use a child's information to train AI.

Who else receives a child's information

  • Our hosting company, Amazon Web Services: FullSched runs on a server we rent from them, so everything is stored there.
  • Our AI provider, Anthropic: when someone uses Ask, what they type and the schedule it needs to answer are sent to Anthropic to be processed. Later, when photo and voice notes are turned on, a homework photo or the words of a voice note go the same way. Anthropic does not train AI on it, and deletes it within 30 days, except anything it must keep longer to enforce its safety rules or the law.
  • Our email service, Resend: when you invite someone by email, their email address, their first name and your account's name go to Resend so the invite can be sent.
  • Google, only if you choose "Sign in with Google": Google tells us your email address and that it is really you. We send Google nothing about your schedule.
  • The authorities, when the law requires it. For example, we must report a picture that appears to show child sexual abuse to the National Center for Missing & Exploited Children.

How a parent agrees

Before a child under 13 is given a way to sign in, we show the parent a short notice and the exact words they are agreeing to. The parent ticks a box and types their name. We keep the name, the date and time, and the words, as the record.

You can say no. Your child can still be on the schedule by name, with you adding things for them.

What a parent can do, at any time

The person who runs the account does this under "Privacy and your data" (on the Family page), or by asking Ask:

  • See what kinds of information we hold about the child.
  • Read the information itself, and download it.
  • Stop us collecting more: turn off the child's own sign-in. Their place on the schedule stays.
  • Delete the child's information. It is deleted at once.
  • Or write to us at the address above and we will do it for you.

How long we keep it

Nothing about a child is kept forever. Each kind has a reason and an end.

A person: name, birthday, the way they sign in Why we keep it: So they are on the schedule and can sign in. When it is deleted: When the account owner deletes that person, or the account. At once.
Schedules, stars, goals, to-dos, requests Why we keep it: They are the product. When it is deleted: With the person they belong to, or with the account.
Talks with the AI Why we keep it: So a talk can carry on and a change can be undone. When it is deleted: After 12 months, and sooner with the person or the account.
Homework photos (not turned on yet) Why we keep it: The photo is the record of what was assigned. When it is deleted: Three months after the semester it was taken in ends. Sooner if you delete the to-do.
Voice notes (not turned on yet) Why we keep it: To turn what was said into a to-do. When it is deleted: The sound is never kept. The words stay with the to-do.
An invite nobody used Why we keep it: So the person can join. When it is deleted: The link stops working after 7 days. 30 days after that, the email address is erased.
A parent's email from a teacher's recommendation Why we keep it: So the parent can join. Used only for that one invite and its link. When it is deleted: 30 days after it was sent, the email address is erased by the nightly job. The row stays only as a count, with no address and no child. A stop link erases it at once.
A parent's OK for a child under 13 Why we keep it: The law asks us to be able to show a parent agreed. When it is deleted: With the child's data.
A short record that a parent agreed to a child under 13: who agreed, when, which words, how Why we keep it: To show we followed the law. It has no child's name. When it is deleted: Three years after it is made: after the child's data or the account is deleted.
Devices signed in: network address, browser name Why we keep it: To keep you signed in. When it is deleted: When you sign out, or after 2 hours without use. "Stay signed in" lasts until you sign out.
A sign-in code for a child, made by QR code Why we keep it: So a child with no email or phone can sign in by scanning it once. When it is deleted: A day after it is used, or a day after it runs out. Until then only scrambled copies are kept.
A homework photo, and the items read from it Why we keep it: So the homework can be checked against the picture it came from. When it is deleted: Three months after the school year ends. Then the picture and its items are deleted.
A "Did it happen?" question for a block: that we asked, and when the block ended Why we keep it: So the same question is not sent twice for one block. When it is deleted: 7 days after the day the block was on.
A kid's answer to "Did it happen?" that waits for a grown-up's OK Why we keep it: So a grown-up can OK it, or say no, before it counts. When it is deleted: 30 days after the day the block was on. Once decided, it is kept until then.
A homework question after a class: that we asked, and which class Why we keep it: So the same question is not sent twice for one class and day. When it is deleted: 7 days after the day it was for.
A morning push about the day: that we sent it, and on which day Why we keep it: So the same push is not sent twice in one day. When it is deleted: 7 days after the day it was for.
A change request sent by push: that we sent it, and to whom Why we keep it: So a request is not pushed twice, and a decider sees who was told. When it is deleted: 7 days after it was sent.
Whether a grown-up said a child does better with a heads-up before each change Why we keep it: So the 5-minute alert starts on for that child, from the start. When it is deleted: With the child: removed when the child is deleted, or the account.
A kid's first walkthrough: the screen they reached, and whether they finished or skipped it Why we keep it: So the walkthrough can pick up where they left off. When it is deleted: With the kid: removed when the kid is deleted, or the account.
An email-plus step for a child under 13: the sign-in waiting for a parent's tap, and the record of the tap Why we keep it: So a parent's yes is proved by a tap on their own email. When it is deleted: A day after the link runs out, if not tapped. A confirmed record: three years after it is made, and it has no child's name once the child is deleted.
A teacher's approval: who approved them, when, the words shown, and the device Why we keep it: So we can show a head agreed to a teacher seeing a child's list. When it is deleted: Three years after the approval ended. Once the teacher's account is deleted, only the domain of their email stays.
A teacher's account: their email and name Why we keep it: So a teacher a family asked can sign in and see the list. When it is deleted: After 12 months with no sign-in and no open class. One email 30 days before. The log of what they did stays with the child's data.
A cancelled account Why we keep it: So you can come back. When it is deleted: 90 days after you cancel, everything is deleted.
How you found us: the code and date Why we keep it: To count what brings people here. When it is deleted: Kept. When you delete the account, its link to you and what you typed are erased; only the code and date stay.
A reported picture Why we keep it: So a person can look at the report, and because the law makes us keep a picture we report to the authorities. When it is deleted: When the report is closed. If it is reported to the authorities: one year after that report.
The log of data downloads, sign-ins turned off, and deletes Why we keep it: To show these controls were used. It has no names. When it is deleted: With the account, except one line that says an account was deleted.
Calendars added by link: the events kept from them Why we keep it: So they show beside your blocks, read only. When it is deleted: A day after each event ends, and at once when the calendar is removed or the person is deleted.
A work meeting flag you kept, and a move you made to a day (hand-off or step-out) Why we keep it: So a flag you kept stays hidden and a move can be taken back. When it is deleted: A week after the day it was for has passed.
The slow-request log: a line for each slow page (route name, role, time, query count, family number) Why we keep it: To find what makes the site slow. It has no names, no addresses and no paths. When it is deleted: One file a day. Each file is deleted once more than 14 days have passed since its day.
The error log: each server error (its kind and the place it was thrown) and each page error (what the browser reported, cut to 200 characters, and the script line) Why we keep it: To find and fix what breaks. A server error holds no words of anyone's. A page error holds the browser's own words, cut to 200 characters with email addresses removed. When it is deleted: One file a day. Each file is deleted once more than 14 days have passed since its day.
Backups Why we keep it: To bring the service back after a failure. When it is deleted: Each nightly backup is deleted after 7 days.
A copy of each nightly backup, kept off the server Why we keep it: To bring the service back if the server itself is lost. When it is deleted: Each copy is deleted 30 days after it is made, by the storage's own rule. It is encrypted.

After you delete

When you delete your account, we keep a short record that a parent agreed for each child under 13 (who agreed, when, and to which words) for 3 years, to show we followed the law. It has no child's name.

Pictures

Photo upload is not turned on yet. When it is, every picture will have a "Report a problem with this picture" button. A reported picture is hidden from everyone at once, and a person at FullSched reads the report.

If we learn of a picture that may show a child being sexually abused, we report it to the National Center for Missing & Exploited Children as the law requires, and keep what the law requires us to keep.