Privacy notice
What FullSched keeps, why, who else receives it, and what you can do about it. Plain words, no fine print.
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]
The short version
- We keep what you put in so your schedule works. That is all we use it for.
- We do not sell it. We do not show ads. We do not share it for anyone's marketing.
- Nothing you put in is public. Only the people in your account see it.
- You can see it, download it, and delete it yourself, at any time.
What we keep and why
What Why
Your name, email and password (the password is scrambled; we cannot read it). If you use Google to sign in, the ID Google gives us for you.
Why: So you can sign in.
Your account's name and time zone.
Why: So times show right.
The people you add: a first name, their place in the account (parent, kid, helper), a kid's birthday, and an email or sign-in name if you give them a way to sign in.
Why: So each person has their own day, and so kids under 13 get extra care.
Schedules, one-day changes, stars, goals, to-dos and requests.
Why: This is the product.
What you type to Ask, what it answers, and what it offered to change.
Why: So a talk can carry on and a change can be undone. We also count how much the AI is used.
The email addresses of people you invite.
Why: To send the invite.
For each device that is signed in: its network address, the browser's name, and when it was last used.
Why: To keep you signed in and to keep accounts safe.
How you found us: a code or ad tag in the link you came by, the first page you opened, the page you came from, and what you type under "where did you hear about us".
Why: So we know what brings people here.
Calendars you add by their private address: the events from yesterday to 60 days ahead (title, times, place). The address itself is kept scrambled, and only its last characters are ever shown.
Why: To show them beside your blocks. Read only: nothing is written back.
Later, when they are turned on: homework photos, and the words of voice notes (the sound itself is not kept).
Why: To turn them into to-dos.
Voice notes
Voice notes are turned into words on your device. We never receive the sound.
What is saved on your device
- A sign-in cookie, and a "stay signed in" cookie if you ask for one.
- Your light or dark choice.
- At sign-up, your answer to "How old are you?", for one day.
- No ad cookies and no trackers. No page of ours loads anything from another company, except Google's sign-in window when you choose to use it.
Who else receives it
- 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.
- When you write to us from Help, your name, email address, message and the page you were on are sent to us by email through Resend.
- Our AI provider, Anthropic, for forwarded email: when an email is forwarded to someone's FullSched address, its text is sent to Anthropic to pull out the tasks and dates. Only the person who forwarded it is affected, and it is kept as described under "How long we keep it".
- Calendars you add by their private address (for example a Google Calendar's secret iCal address): we read their events, and when someone uses Ask, the events for the next week (title and times) go to Anthropic with the schedule. We never use calendar events to train AI, for ads, or for anything else.
How long we keep it
Each kind of data has a reason to be kept and a time it is deleted.
What Why we keep it When it is deleted
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.
An email forwarded to your address, the tasks pulled out of it, and the sender of one that could not be checked
Why we keep it: So the tasks and dates come from the mail they were in: the email is the source. A sender is kept so the person can fix a check that failed.
When it is deleted: When a to-do made from it is gone. A mail with none, and a sender record, go 30 days after it arrived.
What you can do
The person who runs the account can do all of this under "Privacy and your data" (on the Family page), or by asking Ask ("download everything you have on Sam"):
- See every kind of data we hold, for each person and for the account.
- Read the data itself, and download it as one file.
- Turn off someone's own sign-in, so nothing new comes from them.
- Delete one person's data, or the whole account. Deleting is real: it is gone at once. Copies in our backups run out within 7 days on our server, and within 30 days in the encrypted copy kept off the server.
- Everyone else in the account can see and download their own data on the same page.
- When the law requires, we keep data after you delete it. Today that means two things: a picture that was reported and is being held for the authorities, and the short record below.
- 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.
Children
Some accounts include children. A child under 13 gets a sign-in only after a parent or legal guardian agrees. The Kids' privacy notice says exactly what that covers.
Keeping it safe
- Every page is sent encrypted (https).
- Passwords and PINs are scrambled before they are stored. Five wrong tries lock a sign-in name for 15 minutes.
- The app checks, on every action, that you are allowed to do it. Nobody outside your account can open anything in it.
- Pictures, when they are turned on, are kept where the public web cannot reach them and are shown only to the people allowed to see that to-do.
- The database is backed up every night. Backups are kept 7 days on our server, and an encrypted copy is kept 30 days off the server.
Changes to this notice
If we change what we collect or who receives it, we will change this page and its date first, and tell account owners by email before it takes effect. For a child under 13, a change that widens what we collect or share needs a parent's new OK.