Skip to main content
Homebook

School Data Agreement (with College & Career addendum and state add-ons)

Effective November 21, 2026

The short version: This is the agreement Homebook signs with each school. The school owns its data and controls it. Homebook uses it only to run the school’s Homebook, never sells it, never uses it for advertising, protects it, tells the school right away if something goes wrong, and deletes it on a fixed schedule. Schedule 1 is Homebook’s notice to the school about student logins. Schedule 2 covers College & Career for schools that turn it on. Schedule 3 holds the state add-ons: Alabama, Arizona, Iowa, Oklahoma and Texas. A school can sign a copy (email privacy@gethomebook.com) or accept in Homebook with an “I accept” click. Alabama, Arizona, Iowa, Oklahoma and Texas schools accept in Homebook before adding students or families. Homebook’s AI assistant reads student records only in de-identified form; the optional AI writing helpers work only as Schedule 1, part D says.

This agreement is between [School legal name] (“the School”) and Homebook, LLC, an Arkansas limited liability company (“Homebook”). When the School accepts it in Homebook (section 13.4), it starts when the School presses “I accept”, and Homebook is bound from then. For a signed copy, it starts on the date the last person signs below.

The effective date above identifies this published version. For a School that already has an agreement with Homebook, changes take effect only after the written notice in section 13.3, with the School’s right to object or cancel.

1. What this agreement is for

1.1 The School uses Homebook, a school records service at app.gethomebook.com (the “Service”). This agreement says how Homebook protects information about the School’s students, families and staff.

1.2 Products covered: Homebook (records, attendance, gradebook, report cards and transcripts, family portal, messages, check-in and check-out, tuition and ledgers, student logins if the School turns them on) and, if the School turns it on, College & Career (Schedule 2). If Homebook adds a product that uses student information in a new way, Homebook will tell the School in writing at least 30 days before it applies to the School’s data, and the School may object (section 13.3).

1.3 Information covered (“School Data”): everything the School, its staff, families or students put into the Service, and everything the Service creates from it. Schedule 1 lists it. School Data includes information about children under 13 and teens.

1.4 If this agreement and the Homebook Terms of Service disagree about School Data, this agreement wins. If this agreement and Schedule 2 disagree about College & Career, Schedule 2 wins. Schedule 3 (the state add-ons: Alabama, Arizona, Iowa, Oklahoma and Texas) only adds protections: where a state’s add-on and the rest of this agreement differ for a School in that state, the more protective promise applies.

2. Who owns and controls the data

2.1 The School owns School Data and controls it. Homebook has no ownership of it. Homebook acts only as the School’s service provider.

2.2 Homebook uses School Data only to provide the Service to the School, on the School’s instructions, under this agreement, and for no other purpose.

2.3 FERPA protections for every School. Whether or not the School receives U.S. Department of Education program funds, Homebook acts as a “school official” with a legitimate educational interest, as 34 CFR 99.31(a)(1)(i)(B) describes: it performs a service the School would otherwise use its own staff for, it is under the School’s direct control for its use and upkeep of education records, it uses them only for the purposes of this agreement, and it does not disclose them further except as this agreement and FERPA allow (34 CFR 99.33). Homebook accesses education records only where it has a legitimate educational interest under the School’s criteria. For a School that FERPA does not cover, Homebook gives these protections by contract.

2.4 Where a state student online privacy law applies to the School or to Homebook, Homebook follows it, in addition to this agreement.

3. Parent and student requests

3.1 Records the School’s staff entered (attendance, grades, schoolwork, report cards, transcripts, discipline and support notes, health details, pickup list, tuition, messages with the School): requests from a parent or student to see, correct or delete them are sent to the School to decide, and Homebook acts on the School’s instruction. Homebook shows each request in the School’s dashboard, with a due date and reminders. This routing does not limit any right the law gives parents or students directly. If a requester shows that information is inaccurate and the School does not correct it, Homebook will work with the School to make sure it is corrected; Homebook may also deliver a copy the law requires if the School has not responded within 21 days, redacting other students’ information.

3.2 Information collected from the student (the student’s login, the notes the student sent to the office, technical sign-in data) and information a student or parent entered for optional features (College & Career): the law gives parents and teens rights over these directly (COPPA, 16 CFR 312.6; Arkansas Act 952, Ark. Code 4-88-1503(b)(3), (b)(4)). Homebook honors those requests. Homebook gives the rights Arkansas Act 952 describes for teens aged 13 to 16 to students of that age in every state, wherever the School is located; where another state’s law gives minors more (for example, rights that reach older ages), Homebook follows that law too. If a parent refuses further collection, Homebook switches off the child’s login and stops using what it collected from the child (except to complete the request) as soon as it confirms the parent’s identity, without waiting for the School, and tells the School. For deletion of a student’s login and notes, Homebook tells the School and completes the deletion within 30 days unless a law requires a note to be kept. For College & Career, the student or parent can delete in Settings and the School sees that it happened.

3.2A Student photos are optional. Homebook honors a verified request from the family or the School to remove a student’s photo, tells the School, and deletes it.

3.3 Homebook confirms the identity of anyone asking before acting, and finishes within 30 days. Homebook helps every School meet FERPA’s 45-day limit for parent access.

3.4 The School can export its data (CSV) at any time, and can download a single student’s records, for example to send them to the student’s next school.

4. What Homebook will never do

4.1 Sell or rent School Data.

4.2 Use School Data for advertising, including targeted advertising, or let anyone else do so.

4.3 Build a profile of a student for any purpose other than the School’s own use of the Service.

4.4 Market to families or students through School notices, or put promotions in Service emails.

4.5 Use School Data, including student photos, to train artificial intelligence, or use photos for facial recognition or any biometric identification.

4.6 Disclose School Data to anyone except: (a) the School and the people it authorizes; (b) Homebook’s service providers under section 6; (c) as required by law, under section 5. Bright Pathway receives no School Data from Homebook except what Schedule 2, item 3 describes for College & Career purchases, and never any student information.

4.7 Try to re-identify a student, a family or the School from de-identified data, or sell or share de-identified student data.

5. Requests from police, courts or government

If anyone other than the School asks Homebook for School Data (for example a subpoena), Homebook will tell them to ask the School, and will tell the School right away unless the law forbids it. Homebook will disclose only what the law requires.

6. Service providers (subprocessors)

6.1 Homebook uses the service providers listed in Schedule 1, part D, only to run the Service. Each one has agreed in writing to protect the data it receives (16 CFR 312.8(c)).

6.2 Homebook will tell the School at least 30 days before adding a service provider that receives School Data, by email and on gethomebook.com/privacy. The School may object (section 13.3).

6.3 Homebook is responsible for what its service providers do with School Data.

6.4 Some providers in Schedule 1, part D, or some uses of a provider listed there, are only for an optional feature the School asks for, and receive nothing for that feature from a School that has not asked. Homebook turns such a feature on only at the School’s written request. Section 6.2 still applies to that School: Homebook gives it the 30-day notice when it asks, and the provider receives nothing for that feature from it until that period ends, unless the School’s written request says to start sooner. The School may ask Homebook to turn the feature off at any time; Homebook then sends that provider nothing more for that feature from the School (work already in progress when the School asks, such as a summary or a draft, finishes first, within a few minutes).

7. What the School agrees to do

7.1 Use the Service for its educational and school-administration purposes.

7.2 Give access only to staff who need it, keep roles correct, and remove access when someone leaves.

7.3 Student logins. Before student logins work, Homebook verifies that the School is a real school and that the person authorizing has authority to act for it (for example by checking the School’s public listing or website and confirming by phone or by email from the School’s own domain), gives the School the notice in Schedule 1, and the School confirms in the Service that it authorizes student logins for its educational use on behalf of parents. Payment alone is not enough. The authorization continues until the School withdraws it, with a yearly confirmation due by August 15: if the School has not confirmed by September 15, student logins at the School switch off until it does (school records and family access are not affected). A material change in Homebook’s practices for students under 13 needs a new authorization before it applies (section 13.3). The School agrees to tell families about student logins before turning them on. Homebook provides the notice text and can send it for the School. (Homebook remains responsible for its own duties under COPPA and Arkansas law; this clause only records the School’s authorization and its promise to tell families.)

7.4 If the School is subject to FERPA, or has agreed to follow it (for example as an Alabama CHOOSE Act school), give parents and eligible students its annual notice of FERPA rights, including its criteria for who is a school official and what counts as a legitimate educational interest. Those criteria should cover service providers such as Homebook.

7.5 Tell Homebook promptly if it believes someone has gained access to School Data who should not have.

7.6 Pass to Homebook any parent or student request it wants Homebook to handle.

8. Security

8.1 Homebook keeps a written information security program for School Data (16 CFR 312.8; Ark. Code 4-110-104; Ark. Code 4-88-1503(b)(6)). Highlights: each school’s data is separated by database rules that are tested before every release and checked automatically every day; encryption in transit and at rest; passwords stored only as hashes; private storage for documents and photos with short-lived links; two-step sign-in on every Homebook administrative account; a yearly risk assessment; and a named security contact. Homebook maintains reasonable security as Ark. Code 4-110-104 and any other applicable state law require.

8.2 Security contact: Sam Bartolotta, privacy@gethomebook.com, (501) 514-5811.

8.3 School Data is stored in the United States.

8.4 Only Homebook’s members, and the tools Homebook uses to build and fix the Service (including the AI assistant named in Schedule 1, part D), access School Data, and only to support the School, keep the Service running, or fix a problem. Everyone with access is bound to keep it confidential. Homebook’s rule is that the AI assistant reads student records only in de-identified form, through a read-only database login limited to de-identified views: each student appears as a random code, never by name, and the code never appears anywhere the School, a family or a student sees. Homebook’s own staff, not the AI, handle any support ticket that can’t be de-identified (Sam’s own email and texts are the exception described in Schedule 1, part D). The optional AI writing helpers in Schedule 1, part D are not that assistant; they work only as their row there says, and only for a School that asked for them (section 6.4).

8.5 Audit. Once a year, or after a breach, the School may ask for a summary of Homebook’s security program and the latest risk assessment results. Homebook answers within 30 days.

9. Security breaches

9.1 If Homebook discovers unauthorized access to, or acquisition of, School Data, Homebook will tell the School immediately following discovery, with the facts then known (Ark. Code 4-110-105(b)(1), and any other state breach-notice law that applies to the affected people), and will update the School as the investigation develops. As an outer limit for incidents where the facts are still unclear, Homebook will contact the School within 48 hours of first suspecting a problem; this outer limit never permits delaying a notice the law requires immediately.

9.2 The notice will say, as far as known: what happened and when, what data and which students or families were affected, what Homebook has done to contain it, what Homebook will do next, and a contact person. Homebook updates the School as it learns more.

9.3 Homebook will help the School notify affected individuals, government offices and consumer reporting agencies, as the law requires (for example the Arkansas Attorney General when more than 1,000 people are affected, Ark. Code 4-110-105(b)(2)). If the School asks in writing, Homebook will also send those notices for the School, using wording the School approves. If the breach was caused by Homebook or its service providers, Homebook will prepare the notices and pay their reasonable cost.

9.4 Homebook keeps each written breach determination and its supporting documentation for 5 years from the date of the determination, and provides them to the Arkansas Attorney General within 30 days of a written request (Ark. Code 4-110-105(g)).

9.5 Where another state’s breach-notice law applies to the affected people and sets a shorter deadline than this section, or requires notice to a state attorney general or other regulator, Homebook follows the strictest rule that applies: it meets the strictest deadline that applies to Homebook, and under section 9.3 helps the School meet any that apply to the School. Nothing in this section allows a later notice than sections 9.1 to 9.3 promise.

10. Keeping and deleting data

10.1 Homebook keeps School Data only as long as its written retention policy allows (summary in Schedule 1, part E). The School may delete sooner at any time.

10.2 When the School cancels: the School may export its data for at least 30 days; then Homebook deletes all School Data from the Service, on the nightly clean-up after day 30 and at least 7 days after the email below. The 30 days start when the cancellation takes effect: the end of the period the School has paid for, after the School cancels (or on the day Homebook ends the account under the Terms of Service). A subscription that lapses because a payment failed does not start them, and Homebook never deletes School Data automatically over an unpaid bill. Seven days before deleting, Homebook emails the School’s director and prepares a full export of the School Data for the School to download; Homebook does not delete the School Data until that export exists. Remaining backup copies expire within a further 30 days, are used only to recover from loss, and are never used to restore deleted data.

10.3 On written request, Homebook will confirm in writing that School Data has been deleted.

10.4 Homebook may keep only what the law requires it to keep; its own payment records (at least 7 years, without the link to the student once the student is deleted); and its log of privacy requests (who asked, when and what was done, with student initials and a link to the student until the student is deleted, and no child records copied in; 3 years after the request is closed). Homebook does not yet delete its payment records automatically, or clear the request log after a School’s data has been deleted, so for now they are kept.

10.5 The School decides what its records need. The School is responsible for knowing how long its own records must be kept under the laws that apply to it, its accreditor’s standards, and any scholarship, funding or meal program it takes part in. The dates in Schedule 1, part E are Homebook’s defaults. Homebook never deletes the permanent academic record on a schedule while the School uses the Service.

10.6 Notice and holds before clearing. At least 7 days before any student’s information is cleared on a schedule, Homebook emails the School’s director what will be cleared and the date it will clear on or after, with how to download the student’s record in the Service (one file with the record and its uploaded documents, plus a list of any file that could not be included) and the choice to keep it longer. Nothing is cleared on a schedule until at least 7 days after that email was sent, and nothing of the School’s students is cleared on a schedule until a director can be emailed. When a student graduates, Homebook also reminds the family to save the final report card, and a graduate’s family access and 1-year items are not cleared until that reminder was sent at least 7 days earlier. The School may place a keep-until hold on one student or on all its data at any time in the Service; Homebook does not clear a held student’s records on a schedule until the hold’s end date, and reminds the director about 7 days before a hold ends (as soon as it can for a shorter hold). A hold on one student, or on all the School’s data, covers the records tied to its students; an office note not linked to any student and Homebook’s own log of privacy requests follow their own dates even under a hold. A hold does not override a parent’s or student’s legal rights over information collected from the student. Homebook’s own demo and app-review schools are never cleared on a schedule.

11. Term and ending

11.1 This agreement lasts as long as Homebook holds any School Data.

11.2 Either party may end it in writing if the other seriously breaks it and does not fix the problem within 30 days. Ending it ends the Service.

11.3 Sections 4, 5, 9 and 10 continue until all School Data is deleted.

12. If Homebook is sold or closes

If Homebook, LLC is sold or merged, the buyer must keep this agreement’s promises for existing School Data, and Homebook will tell the School at least 30 days before the change. If Homebook stops operating, it will give the School at least 30 days to export its data and then delete it.

13. General

13.1 Arkansas law governs this agreement. Nothing in this agreement limits any right that the School, a parent or a student has under the laws of their own state.

13.2 Liability is as stated in the Homebook Terms of Service, except that the Terms’ liability cap does not limit Homebook’s duty to pay breach notice costs under section 9.3.

13.3 Changes. Homebook may update this agreement only by written notice at least 30 days before the change. If the School objects in writing within that time, the old terms continue for the School until it agrees or cancels; if the School cancels for this reason, Homebook refunds any prepaid fees for the unused period. A material change in how Homebook collects, uses or discloses information collected from students under 13 does not apply to the School’s students until the School renews its authorization in the Service (section 7.3); the School’s silence is not authorization.

13.4 Each person signing or accepting confirms they are allowed to act for their organization. The School may accept this agreement, with any state add-on that applies to it (Schedule 3), by its director or administrator pressing “I accept” in the Service. Homebook records who accepted, when, and which version. Accepting this way has the same effect as signing below. An Alabama, Arizona, Iowa, Oklahoma or Texas School accepts before it adds students or families.

13.5 If one part of this agreement is unenforceable, the rest still applies.

13.6 Notices go to the emails below.

Signed for the School: ______________________ Name: ____________ Title: ____________ Date: ______

Notice email: ____________

Signed for Homebook, LLC: ______________________ Sam Bartolotta, Managing Member Date: ______ Notice email: privacy@gethomebook.com

Schedule 1. Student Login Notice for Schools, data list, providers and retention

This schedule is Homebook’s direct notice to the School about the information collected from students. COPPA requires an operator relying on a school’s authorization to give the school the same notice it would give a parent (FTC COPPA FAQ N.1, N.2; contents follow 16 CFR 312.4(c)(1)).

A. Information Homebook collects directly from students who have a login

  • The school-issued email address (entered by the School), the student’s name and a password the student types when setting up the login (password stored only as a hash), sign-in times, the student’s notice choice, and any “Tell the office” note the student sends (the School can switch notes off).
  • Technical information: a session token on the student’s device, and standard request logs at Homebook’s hosting providers (IP address, browser type, request times), used only to sign the student in, run and secure the Service, and fix errors.
  • College & Career entries, only if the School turns it on and the student or parent agrees (Schedule 2).
  • Students cannot upload files, post anything publicly, message other students, or change records. Student logins work in a web browser only.
  • Use: only to let the student see their own grades, schoolwork and attendance and reach the School office; to run College & Career where enabled; and to sign the student in, keep the Service secure and fix errors.
  • Who receives it: the School (notes go to the School office; staff see what their roles allow), the student’s approved parents, Homebook, and the service providers in part D, only to run the Service. Nothing is made public, and nothing is disclosed to any other third party except where the law requires. The School can review, delete, or stop collection for any student at any time (remove the login, delete notes, delete the student), and Homebook does the same on the School’s request.
  • Without the School’s authorization, student logins do not work.

B. School records the School and families enter (Homebook does not collect these from students)

Names, grade, date of birth, student number, address, guardian and emergency contacts, attendance and check-in and check-out (including who picked a child up), grades, assignments, assessments, report cards, transcripts, documents, discipline and incident notes, support plans, goals and services, allergies, conditions, medications, doctor, office visits, pickup authorizations and requests, photos (optional), tuition and ledger entries, lunch records, messages, and notes.

C. College & Career (only if turned on)

See Schedule 2.

D. Service providers that may receive School Data

ProviderPurposeData
Supabase (on AWS, USA)Database, sign-in, file storageAll School Data
Vercel (USA)HostingApp traffic, request logs
StripeBilling; optional tuition, lunch and fee payments to the School’s own Stripe account. College & Career purchases go through Bright Pathway’s own Stripe account instead (Schedule 2, item 3)Billing contacts; payer card or bank details; payment amount and student name on the payment line
Resend (Amazon SES)Service emailsNames, emails, email content including student names and previews
Expo and ApplePhone app notifications (families and staff only)Push token, title, short preview. At a Texas School: the push token and the words “You have a new update in Homebook” only
Sentry (USA)Error monitoringTechnical details only; set up to exclude names, emails, records, form contents and IP addresses
Google WorkspaceHomebook’s email; encrypted backup storageAnything sent to Homebook by email. Backups are encrypted by Homebook before transfer: Google holds only ciphertext and cannot read the content, the encryption key is held only by Homebook, and copies are deleted within 30 days
Anthropic (Claude)AI assistant Homebook uses to build, test and fix the ServiceDe-identified student records only: each student is a random code, with no name, contact details, birthday, address, guardian or emergency contact, health information, support plan, photo or free-text note; its reads are logged. Support-ticket text has roster names, email addresses and phone numbers swapped for codes first; the rest is passed as written. It also helps Sam with his own email and texts, which it reads as written; a student’s name is never copied from them into notes, drafts or records
Anthropic (Claude), writing helpersOptional AI writing helpers inside the Service: report card comment drafts and translation of staff messages to families. Only for a School that asks Homebook in writing to turn them on (section 6.4); off for every other School. Not available to a Texas SchoolComment drafts, for one student in one subject and term: the subject, term, grade level and grading scale; the term grade, percentage, effort mark and any existing term comment; and up to 60 of that term’s assignments, each with its name, category, assigned and due dates, score, status mark (such as missing or excused) and teacher comment. Translation: the text a staff member wrote and the target language. Roster names (students, families and contacts, staff, pickup adults), email addresses and phone numbers are replaced with placeholders before sending and restored inside the Service; all other text is sent as written, and a nickname, misspelling or everyday-word name can slip past that swap. A Texas TEFA child whose family has not given consent is never included. Not used to train Anthropic’s AI; Anthropic may keep it for a limited time for safety checks, then deletes it. Homebook stores no prompt or answer text, only usage counts
OpenAI (USA)Writes the optional monthly summary for the School’s directors. Only for a School that asks Homebook in writing to turn it on (section 6.4); off for every other School. Not available to a Texas SchoolAggregate totals only: attendance percentages, counts of students, applications, tickets and messages, tuition dollar totals and upcoming calendar dates (the kind of day, never its label); classes as codes; a class with fewer than 3 students, and any attendance percentage fewer than 3 students make up, are left out. No names, contact details, identifiers, class names, notes or other free text about any student, family or staff member. Not used to train OpenAI’s AI; OpenAI keeps it in its API logs for up to 30 days by default for safety checks (longer only if the law requires it or to look into misuse or prevent harm), then deletes it

E. Retention

The full table is published in the Homebook Privacy Policy, section 8, and the written policy is available on request. “Leaves” means withdrawn or graduated; the clock starts the day the student most recently left active enrollment (re-enrolling resets it). Every scheduled clearing below happens on or after the date given, only after the 7-day notice in section 10.6, and never while a keep-until hold applies (section 10.6 says what a hold covers). Student login stops the day a student leaves and is deleted about 30 days after a withdrawal or 1 year after a graduate leaves; office notes deleted 12 months after they were sent (or with the student’s 1-year clearing, if that comes first); support tickets that name a student deleted 12 months after they are closed, except that a ticket about a student who left more than a year ago is kept until Homebook adds that clearing; health, emergency, pickup and photo details deleted about 30 days after a withdrawal or 1 year after a graduate leaves; office (nurse) visit records kept 7 years after the student leaves; family contacts and links, messages and staff notes deleted 1 year after the student leaves; enrollment forms, IEP and 504 plans, other uploaded documents and support plans, goals and services kept 5 years; records showing the School met a state scholarship or funding program’s rules kept 7 years; staff fingerprint dates (only if the School records them) kept until the School changes or removes them or deletes the staff account; lunch orders kept 3 years by default, or the number of years the School chooses in Settings; the permanent academic record (identifying details, enrollment and exit dates and reason, grades, report cards, transcripts, attendance including absence reports and check-in and check-out times, test results, and uploaded immunization, medical and birth certificate or identity records) kept until the School deletes it, for as long as the School uses the Service; discipline and behavior records kept until the student’s expected graduation plus any extra years the School chooses in Settings (or permanently, if it chooses), never cleared less than 1 year after the student leaves, and kept if Homebook cannot work out an expected graduation date; tuition and other account records kept 7 years after the last transaction; while the family owes the School a balance, only the account records and the parent’s or guardian’s contact details, home address, staff-family discount setting, family login, link to the student and notice acknowledgment are kept past their date, and the child’s own information is still deleted on schedule; the School may also ask in writing to keep any record longer for a stated educational or legal reason with a fixed end date; College & Career deleted about 30 days after a withdrawal (1 year after a graduate leaves) or about 30 days after the School stops it, whichever comes first; a student the School deletes is kept about 30 days in Recently deleted, then erased; all School Data deleted 30 or more days after the School’s cancellation takes effect (section 10.2), after a full export has been prepared for the School; backups clear within 30 days of a deletion and are never used to restore deleted data.

F. Parent and student rights

See section 3 and gethomebook.com/privacy/requests.

Schedule 2. College & Career, by Bright Pathway (addendum)

Completed only if the School turns on College & Career.

  1. What it is. An optional part of Homebook for the School’s students in grades 9 to 12: a career quiz, saved scholarships with statuses, and college and financial-aid deadlines, with a read-only progress view for School staff. The quiz content and the scholarship and deadline lists are licensed from Bright Pathway Future Ready Academy, LLC (“Bright Pathway”), which sells College & Career through its own Stripe account.
  2. School Data. Quiz answers, results, saved scholarships and the activity record are School Data under this agreement.
  3. What Bright Pathway receives, and no student information. To set up a checkout, Homebook sends Stripe, as Bright Pathway’s payment processor, only what was bought and how many, the payer’s email address and a random reference number. The payer enters billing details on Stripe’s checkout page, and Bright Pathway receives them from Stripe as the seller. Neither Homebook nor Bright Pathway sees card numbers. Bright Pathway, scholarship sponsors, colleges, advertisers and data brokers receive no student information from Homebook.
  4. Turning it on. College & Career turns on once it is paid for: either the School buys seats, or the School turns on “families pay” and a parent with an approved link to an eligible student buys that student’s year in the family portal. Students never see a buy button and are never charged. The School’s director chooses which grades (9 to 12) can use it, whether parents of students aged 13 to 16 may see individual answers, and whether the Bright Pathway program card is shown. The card is a plain link with no student information.
  5. Consent. A student aged 13 or older reads a notice and ticks “I agree” before anything is saved. The Bright Pathway program card is never shown to students under 13. A parent or guardian of a student aged 13 to 16 can say yes or no for their child in Homebook; a parent’s no keeps it off for that child. In Family mode, a parent confirms they are the child’s parent or guardian before saving anything.
  6. Students under 13. College & Career is not available to a student under 13 unless the School signs a separate written authorization for that student, for the School’s educational use only. Homebook records it before the student can use the feature.
  7. Staff access. The director and counselor can see students’ answers. Other school leaders and the student’s own teachers see a summary only. The School gives these roles only to the right people.
  8. Rights. A student or parent can see, delete, or turn off College & Career data themselves (it is information they entered); the School sees that it happened.
  9. When it ends. If the School stops College & Career, access ends that day. Homebook keeps the data about 30 days so the School can ask for a copy, then deletes it after the notice in section 10.6, unless the School asks in writing for earlier deletion. A withdrawn student’s College & Career data is deleted about 30 days after withdrawal (1 year after a graduate leaves).
  10. Seats and price. Seats: __ seniors (grade 12) at $__ each; __ students in grades 9 to 11 at $__ each; for the school year ending August 15, 20__. Or: families pay (each parent buys their own student’s year at the published price).

Signed for the School: ______________________ Name: ____________ Title: ____________ Date: ______

Signed for Homebook, LLC: ______________________ Sam Bartolotta, Managing Member Date: ______

Schedule 3. State add-ons

Each state add-on below applies only to a School in that state. It adds to this agreement and never takes anything away.

Schedule 3 Alabama

Applies to every School in Alabama, including a School approved as an education service provider under the Alabama CHOOSE Act (Ala. Code 16-6J). It adds to this agreement and never takes anything away. Nothing in it gives Homebook more time for any notice or deadline elsewhere in this agreement. Version AL-1, effective November 21, 2026.

  1. FERPA. Section 2.3 applies to the School. A CHOOSE Act school agrees to comply with FERPA (Ala. Code 16-6J-5(a)(6)). That duty is the School’s: Homebook supports it under this agreement, but cannot guarantee the School’s compliance. The School’s annual FERPA notice should state its criteria for who is a school official and what counts as a legitimate educational interest, including contractors such as Homebook (34 CFR 99.7(a)(3)(iii); section 7.4).
  2. Records requests and transfers. Homebook helps the School answer a parent’s request to see a student’s records within FERPA’s 45 days, and a request to correct them, and keeps the export the School needs to send a student’s records to the next school, including a public school (Ala. Admin. Code r. 810-28-1-.05; section 3.4).
  3. Breach notice. Section 9 applies: Homebook tells the School immediately, and never more than 48 hours after first suspecting a problem, which is sooner than the 10 days Ala. Code 8-38-8 allows. Homebook gives the School the facts it needs for its own notices, and sends those notices for the School if the School asks in writing (section 9.3). For the School’s planning: when Alabama law requires notice to affected people, the School gives it as quickly as possible and without unreasonable delay, and within 45 days after Homebook tells it of the breach or it determines that a breach happened and is reasonably likely to cause substantial harm (8-38-5). The only exception is a written request from a federal or state law enforcement agency that notice would interfere with a criminal investigation or national security, and then only for as long as the agency says is needed (8-38-5(c)). If more than 1,000 people need notice, the School also notifies the Alabama Attorney General on the same timing (8-38-6(a)). If more than 1,000 people need notice at one time, the School also notifies the national consumer reporting agencies without unreasonable delay (8-38-7). Medical and health information, such as immunization records, can be covered information in Alabama (8-38-2(6)).
  4. Security and disposal. Homebook keeps reasonable security measures (section 8) and, when it deletes School Data, disposes of it so it cannot be read or rebuilt (section 10) (Ala. Code 8-38-3, 8-38-10).
  5. No sale, no advertising. Sections 4.1 and 4.2 apply and cannot be removed for an Alabama School.
  6. Small-group test reports. If Homebook prepares a school-level CHOOSE Act test report for the Alabama Department of Revenue, it does not produce one when fewer than 20 CHOOSE Act students are enrolled, and never breaks results down far enough to identify a student (Ala. Admin. Code r. 810-28-1-.05).
  7. No program logins. Homebook never asks for or stores ClassWallet, FACTS or parent Education Savings Account logins. It holds CHOOSE Act award amounts only if the School enters them.
  8. Accepting. Before the School adds students or families, its director or administrator accepts this agreement and this add-on in Homebook (section 13.4). A signed paper copy does not replace this in-app acceptance.

Schedule 3 Arizona

Applies to every School in Arizona, including a School that takes Empowerment Scholarship Account (ESA) payments under A.R.S. 15-2401 to 15-2406. It adds to this agreement and never takes anything away. Nothing in it gives Homebook more time for any notice or deadline elsewhere in this agreement. Version AZ-1, effective November 21, 2026.

  1. Breach notice. Section 9 applies: Homebook tells the School immediately, and never more than 48 hours after first suspecting a problem, which meets the “as soon as practicable” notice and cooperation a company holding data for the School owes it under A.R.S. 18-552(C). Homebook shares the facts the School needs for its own notices, and sends those notices for the School if the School asks in writing (section 9.3). For the School’s planning: when Arizona law requires notice to affected people, the School gives it within 45 days after it determines that a breach happened (18-552(B)), unless a law enforcement agency says notice would impede a criminal investigation (18-552(D)). If more than 1,000 people need notice, the School also notifies the three largest nationwide consumer reporting agencies, the Attorney General and the director of the Arizona Department of Homeland Security (18-552(B)(2)).
  2. Student online privacy, taken on by contract. Whether or not Arizona’s student online privacy law (A.R.S. 15-1046) reaches a service used only by private schools, Homebook keeps its duties for the School: no targeted advertising, no profile of a student except for the School’s own purposes, no sale or rental of student information, reasonable security (section 8), and deletion on the School’s request (section 10). Sections 4.1 and 4.2 apply and cannot be removed for an Arizona School.
  3. No program logins or tax numbers. Homebook never asks for or stores ClassWallet or ESA portal logins, or any digits of a Social Security number or ITIN. It holds ESA award amounts only if the School enters them.
  4. Fingerprint records. If the School uses Homebook’s staff fingerprint tracker (for the ESA rule that a school fingerprints its teaching staff and anyone with unsupervised contact with students, A.R.S. 15-2402(B)(4)(a)), Homebook stores only two dates for each staff member: the day they were fingerprinted and the day it must be renewed by. Homebook never stores fingerprint images, fingerprint card or clearance card numbers, or background check results. Only the School’s director or administrator can see or change the dates of other staff; a staff member can see their own.
  5. FERPA. Section 2.3 applies to the School, whether or not it receives federal education funds. The School’s annual FERPA notice, if it gives one, should state its criteria for who is a school official and what counts as a legitimate educational interest, including contractors such as Homebook (section 7.4).
  6. Accepting. Before the School adds students or families, its director or administrator accepts this agreement and this add-on in Homebook (section 13.4). A signed paper copy does not replace this in-app acceptance.

Schedule 3 Iowa

Applies to every School in Iowa, whether or not it is accredited or takes Students First Education Savings Account (ESA) payments under Iowa Code 257.11B. It adds to this agreement and never takes anything away. Nothing in it gives Homebook more time for any notice or deadline elsewhere in this agreement. Version IA-1, effective November 21, 2026.

  1. Breach notice. Section 9 applies: Homebook tells the School immediately after discovering a breach, as Iowa Code 715C.2(2) requires of a company holding personal information for the School, and never more than 48 hours after first suspecting a problem. Homebook shares the facts the School needs for its own notices, and sends those notices for the School if the School asks in writing (section 9.3). Section 9 covers all School Data, which is more than the narrower “personal information” Iowa’s law covers (715C.1(11)). For the School’s planning: when Iowa law requires notice to affected Iowa residents, the School gives it in the most expeditious manner possible and without unreasonable delay (715C.2(1)), with the contents 715C.2(5) lists. A law enforcement agency that decides notice would impede a criminal investigation may ask in writing for a delay; the School then sends the notices once the agency tells it in writing that they will no longer compromise the investigation (715C.2(3)). That delay never postpones Homebook’s notice to the School under section 9. If the School decides, after an appropriate investigation or after consulting the law enforcement agencies involved, that no notice is needed because there is no reasonable likelihood of financial harm, it documents that in writing and keeps it for five years (715C.2(6)). If more than 500 Iowa residents need notice, the School also gives written notice to the director of the Consumer Protection Division of the Iowa Attorney General’s office within five business days after first notifying any affected Iowa resident (715C.2(8)). A government-issued number such as a driver’s license or state-assigned ID number, together with a person’s name and not encrypted or redacted, can be personal information in Iowa (715C.1(11)(a)(2)).
  2. Student online privacy, taken on by contract. Iowa’s student online personal information law (Iowa Code 279.71) is written for operators serving Iowa public school districts and their attendance centers (279.71(1)), so it likely does not reach a service used only by private schools. Whether or not it does, Homebook keeps its duties for the School: no targeted advertising, no profile of a student except for the School’s own purposes, no sale or rental of student information, no disclosure except as sections 4.6 and 6 allow, reasonable security (section 8), and deletion on the School’s request (section 10). Sections 4.1 and 4.2 apply and cannot be removed for an Iowa School.
  3. No program logins or tax numbers. Homebook never asks the School or a family for ESA portal logins (the portal Odyssey runs for the Department of Education) or any digits of a Social Security number or ITIN, and does not collect or keep a family’s ESA application for the School. If the School lets families upload documents, such as a birth certificate or ID, those documents and any messages stay School Data under this agreement (Schedule 1, part B), and section 9 covers them. Homebook never signs in to the ESA portal, SRI or the Department of Education’s other systems, and never submits anything to them for the School. It holds ESA amounts only if the School enters them.
  4. Iowa consumer data law. Iowa’s consumer data protection law (Iowa Code 715D) applies to a business only if, in a calendar year, it controls or processes the personal data of at least 100,000 Iowa consumers, or of at least 25,000 and gets more than half its gross revenue from selling personal data (715D.2(1)), subject to the law’s exemptions. Where it applies to Homebook, Homebook follows its duties. The promises in this agreement apply either way.
  5. FERPA. Section 2.3 applies to the School, whether or not it receives federal education funds. The School’s annual FERPA notice, if it gives one, should state its criteria for who is a school official and what counts as a legitimate educational interest, including contractors such as Homebook (section 7.4).
  6. Accepting. Before the School adds students or families, its director or administrator accepts this agreement and this add-on in Homebook (section 13.4). A signed paper copy does not replace this in-app acceptance.

Schedule 3 Oklahoma

Applies to every School in Oklahoma, whether or not it is accredited or takes part in the Oklahoma Parental Choice Tax Credit (70 O.S. 28-101). It adds to this agreement and never takes anything away. Nothing in it gives Homebook more time for any notice or deadline elsewhere in this agreement. Version OK-1, effective November 21, 2026.

  1. Breach notice. Section 9 applies: Homebook tells the School immediately, and never more than 48 hours after first suspecting a problem, which meets the “as soon as practicable” notice a company holding data for the School owes it under Oklahoma’s Security Breach Notification Act (24 O.S. 163(C)). Homebook shares the facts the School needs for its own notices, and sends those notices for the School if the School asks in writing (section 9.3). For the School’s planning: when Oklahoma law requires notice to affected residents, the School gives it without unreasonable delay (163(A)), unless a law enforcement agency advises that notice would impede an investigation or homeland or national security, and then as soon as it no longer would (163(D)). If 500 or more Oklahoma residents are affected by one breach, the School also notifies the Oklahoma Attorney General without unreasonable delay and within 60 days after notifying residents, with the facts 163(E) lists. These rules apply to breaches determined or notified on or after January 1, 2026 (24 O.S. 166).
  2. Reasonable safeguards. Homebook keeps the reasonable safeguards Oklahoma law describes, including risk assessments, layered technical and physical defenses, training for anyone who handles personal information, and an incident response plan (24 O.S. 162(8); section 8).
  3. Student data, taken on by contract. Oklahoma’s Student Data Accessibility, Transparency and Accountability Act (70 O.S. 3-168) governs the State Department of Education’s student data system, not a private school or its service providers. Homebook keeps its promises to the School anyway: no sale or rental of student information, no targeted advertising, no profile of a student except for the School’s own purposes, reasonable security (section 8), and deletion on the School’s request (section 10). Sections 4.1 and 4.2 apply and cannot be removed for an Oklahoma School.
  4. No tax logins or tax numbers. Homebook never asks the School or a family for OkTAP logins, any digits of a Social Security number or ITIN, a family’s tax return, income or benefits, Enrollment Verification Numbers or check numbers, and its tax credit tools have no place to enter them. Documents and messages a School or family chooses to add elsewhere in Homebook stay School Data under this agreement (Schedule 1, part B). Homebook never signs in to OkTAP or sends anything to the Oklahoma Tax Commission for the School.
  5. Tax credit tools. If a School that takes part in the Parental Choice Tax Credit uses Homebook’s tax credit tools, Homebook stores only four tax credit fields per student and school year, linked to the student’s existing record, plus who last changed them and when: whether the student is on the credit, the date the School issued the student’s Enrollment Verification Number (never the number itself), the date the check arrived and the date it was handed to the family. The June 15 report helper only reads enrollment, attendance and tuition records the School already keeps in Homebook; it stores nothing new. The credit’s dates also appear as to-dos on the School’s deadline list, including a reminder when a student withdraws. Only the School’s director or administrator can see or change these, never a Homebook support login. The School reviews the report and files it itself. These are records showing the School met a state funding program’s rules (Schedule 1, part E).
  6. FERPA. Section 2.3 applies to the School, whether or not it receives federal education funds. The School’s annual FERPA notice, if it gives one, should state its criteria for who is a school official and what counts as a legitimate educational interest, including contractors such as Homebook (section 7.4).
  7. Accepting. Before the School adds students or families, its director or administrator accepts this agreement and this add-on in Homebook (section 13.4). A signed paper copy does not replace this in-app acceptance.

Schedule 3 Texas

Applies to every School in Texas. Items 4 to 8 apply only to a School that takes part in Texas Education Freedom Accounts (TEFA) under Tex. Educ. Code 29.351 to 29.374 as an approved education service provider, for its TEFA students. It adds to this agreement and never takes anything away. Nothing in it gives Homebook more time for any notice or deadline elsewhere in this agreement. Version TX-1, effective November 21, 2026.

What your school must do (the short version)

  1. Accept this agreement and Schedule 3 Texas in Homebook before you add students or families.
  2. TEFA schools: give each TEFA family Homebook’s family notice and get a separate “yes” before you enter the child. For a child already in Homebook, or one who joins TEFA later, sharing pauses until you record the “yes”, and you have 30 days to get it or record a no. Homebook keeps the record of each “yes” for you.
  3. Record a TEFA parent’s no, or a “yes” taken back, in Homebook straight away. When Homebook announces a new service provider, confirm each TEFA family’s fresh “yes” before that provider gets the child’s information.
  4. Never type TEFA or Odyssey logins, Social Security numbers, TEFA application papers or state eligibility data into Homebook. Send TEFA audit records to the auditors yourself; Homebook gives you the files.
  5. After a data breach, tell affected families without unreasonable delay and never later than 60 days after you determine it happened, and, if 250 or more Texans are involved, the Texas Attorney General within 30 days. Homebook prepares the notices and files its own report too.
  1. The School owns its data; Homebook only serves the School. Sections 2.1 and 2.2 apply. Homebook uses School Data only to provide the Service to the School, on the School’s written instructions (this agreement, and the settings the School chooses in the Service), for the School’s educational and school-administration purposes. Homebook has no right to use School Data for itself. Everyone who works with School Data is bound to keep it confidential (section 8.4).
  2. Texas student online privacy, taken on by contract. Whether or not Tex. Educ. Code 32.151 to 32.157 reaches a service used only by private schools, Homebook keeps these duties for the School:
    1. Homebook never shows a student, parent or staff member targeted advertising, and never lets anyone else do so (section 4.2).
    2. Homebook never builds a profile of a student, from School Data or anything the Service gathers (including device or account identifiers), except for the School’s own purposes in the Service. Keeping account information that stays under the control of the student, the parent or the School is not a profile.
    3. Homebook never sells or rents School Data (section 4.1). If Homebook, LLC is sold or merged, section 12 applies, and the buyer is bound by this add-on for existing School Data.
    4. Homebook never markets anything to families or students using School Data (section 4.4). The only offers a family sees in the Service are for features the School itself has turned on (for example College & Career “families pay”, Schedule 2).
    5. Homebook discloses School Data only as section 4.6 allows: to the School and the people it authorizes; to Homebook’s listed service providers under item 3; to Bright Pathway only as Schedule 2, item 3 describes; and where a law or court order requires it, under item 11. Homebook does not use the wider disclosures Educ. Code 32.153 would allow an operator (for example research, or a disclosure “to protect against liability”).
    6. Homebook keeps reasonable security procedures and practices to protect School Data from unauthorized access, deletion, use, change or disclosure (item 14).
    7. Homebook deletes on the School’s request on the timetable in item 9: 30 days for the Service, and backups within a further 30 days. The data is gone from the Service and Homebook’s backups within 60 days, never later than the 60 days in Educ. Code 32.156, and sooner where any law sets a shorter time. The only exceptions are what section 10.4 lets Homebook keep and copies held by a service provider under its own legal duties (for example Stripe’s payment records).
    8. Sections 4.1, 4.2 and 4.3 apply and cannot be removed for a Texas School.
  3. Service providers. Homebook uses only the service providers listed in Schedule 1, part D, and only to run the Service for the School. For each provider that receives a student’s information, Homebook relies on that provider’s published data-processing terms (its data processing addendum or equivalent binding terms) and keeps a copy. Those terms forbid the provider to use School Data except to provide its service to Homebook, require reasonable protection against disclosure, and bind its own subcontractors. Two providers publish no such terms for Homebook, so for a Texas School they receive nothing about a student: Expo and Apple (phone notifications) get only a device token and the words “You have a new update in Homebook”, never a name, grade or preview; and Homebook’s AI assistant works only as item 21 says. Homebook takes reasonable steps to choose providers able to protect the data (16 CFR 312.8(c)) and is responsible for what they do (section 6.3). Homebook gives the School at least 30 days’ notice, by email and on gethomebook.com/privacy, before adding a provider that receives School Data, and the School may object or cancel (sections 6.2 and 13.3). For a TEFA School, item 5(e) also applies: a new provider Homebook adds gets no TEFA child’s information until that child’s family has said yes to it.
  4. TEFA student information is never sold. Homebook never sells information about a TEFA participating child, in any form, including de-identified or summarized information, and never receives anything of value for it. Consent, a School setting or a later version of this agreement cannot change this.
  5. TEFA student information: where it may go, and the family’s consent.
    1. Only the existing routes. Homebook holds and handles information about a TEFA participating child only as the School’s service provider under this agreement, to run the School’s own Homebook. It goes only where section 4.6 already allows: the School and the people it authorizes; the listed service providers in item 3 acting for the School; Bright Pathway’s checkout details for a College & Career purchase, as Schedule 2, item 3 describes; and a disclosure a law or court order requires under item 11. Outside those routes, Homebook never passes it to anyone, including the Comptroller, Odyssey or another TEFA organization, a public school or district, or a researcher. If the School wants information sent to someone, the School sends it itself. Consent is an extra condition, never an extra route: it never lets Homebook send information anywhere section 4.6 does not allow.
    2. Consent at enrollment. Texas law says a TEFA school may not “distribute” information about a participating child without the program participant’s consent (Educ. Code 29.369(c)(2)(B)), and it is not settled whether keeping a child’s records in an outside service such as Homebook counts. So that the School is as safe as Homebook can make it on either reading, before the School enters a TEFA participating child’s information in Homebook, it gives the child’s parent the Homebook family notice and gets the parent’s consent. The notice names what Homebook holds and why, and each service provider in Schedule 1, part D (including Stripe, Bright Pathway for College & Career purchases, and Anthropic) with what each receives. It also covers each provider’s own subcontractors as listed on that provider’s published subcontractor list, as that list is updated, with a link to each list. The consent must be a separate, specific yes, not buried in a general enrollment contract or handbook. The School records each TEFA student’s consent date in Homebook, with its confirmation that the parent got the notice and said yes; Homebook keeps that record for the School.
    3. Children already in Homebook, and mid-year joiners. This covers a TEFA child already in Homebook when the School accepts this add-on, or a child who joins TEFA later. Until the School records that child’s consent, Homebook holds every onward disclosure that depends on consent: no school emails through the email provider to the child’s family or student address, or naming the child (by full name to anyone, or by first name to anyone at the School; a first name that is also an everyday word, such as Grace or Mason, counts only with the last name), as Homebook finds them by the name the School entered; those emails are not sent later, including ones already waiting to go out (sign-in and password emails, which name no child, still go); no College & Career purchase for the child (Bright Pathway’s Stripe), no verification link a third party could look up (existing links stop answering), no child’s name on an online payment line (the line says “Tuition” only), and no sharing with anyone for the School. Phone notifications in Texas never carry a child’s information at all (item 3), and the AI assistant leaves the child out of the student records and tickets it works on (item 21). Four things continue: Homebook keeps storing the child’s records for the School on its core service providers (database and hosting); the School’s own users and the child’s approved parents can see them in the Service; the School can export or download them at any time (section 3.4, including audit records under item 8); and Homebook makes notices and disclosures the law requires (breach notices under items 12 and 13, and item 11). The School resolves it within 30 days of accepting this add-on or of the child joining TEFA, whichever is later: it either records consent or treats the case as a refusal under item 5(d). The 30 days is a deadline to resolve, not a period of normal sharing. By accepting this add-on, a TEFA School confirms it will follow items 5(b) and 5(c).
    4. When a parent says no or takes consent back. The School records it in Homebook as soon as it knows, which also tells Homebook. From that moment, Homebook stops every disclosure the consent covered: the same emails as in item 5(c); no College & Career purchase for the child, no verification link and no child’s name on an online payment line, and no sharing for the School; the child’s student login is switched off, and section 3.2 (COPPA) applies at once to information collected from the child. Three things continue: the School’s own users and the child’s approved parents can still see the child’s records in the Service; Homebook can give the School a secure export of the child’s records (section 3.4); and Homebook can make a disclosure the law requires (item 11). Within 10 days, Homebook gives the School that export and removes the child’s records from the Service. Backups expire as item 9 says. The School should keep the export, because it may need those records for a TEFA audit (item 8; Educ. Code 29.363(b)). The only other exception is what the School and the parent agree in writing may stay. That agreement can never allow Homebook to keep anything a law requires to be deleted.
    5. New service providers and subcontractors. A new service provider that Homebook adds receives no information about a TEFA participating child until the School confirms to Homebook in writing (or in the Service, once Homebook adds that step) that it has that child’s parent’s consent covering the new provider. Silence is not consent. Homebook cannot control which subcontractors a listed provider adds. Those are covered by the family’s consent to the provider and its subcontractors as listed on its published list, as updated (item 5(b)). When Homebook learns that a listed provider’s published list has changed, it sends the School updated family notice text. Any family that then objects is handled under item 5(d). If Homebook cannot keep a child’s information away from a new provider, it does not move the School’s data to that provider until every TEFA family at the School has consented or been handled under item 5(d). Homebook gives the School updated family notice text with its 30-day notice. Section 13.3’s separate rule still applies: a material change for students under 13 needs the School’s renewed authorization.
  6. TEFA eligibility data.
    1. What it is. “Eligibility data” means information exchanged with the Comptroller, Odyssey or another TEFA administrator, the Texas Education Agency or a school district to decide whether a child is eligible for TEFA or for a priority group. Examples: public-school enrollment or attendance-funding status, household income or income tier, lottery or priority category, and the eligibility decision itself. It does not include the School’s own records that the School keeps for its own purposes, such as a birth certificate, an IEP or 504 plan, or an enrollment form. Those follow Schedule 1, part E and section 10.
    2. Homebook never collects it on purpose. Homebook never connects to or imports from those offices, and no field in Homebook asks for eligibility data. A School may record in Homebook only whether a student takes part in TEFA and the award or payment amounts the School itself enters.
    3. If some is entered by accident (for example in a note or upload), Homebook uses it for nothing and never passes it on, beyond the listed providers that already store all School Data. Homebook flags it to the School’s director within 7 days of finding it and limits who can see it to the director. Unless the School tells Homebook in writing that it is not eligibility data, Homebook deletes it from the Service within 30 days of finding it, or sooner if the School asks or says its eligibility step is finished. The backup copies of that data expire within a further 30 days, so the data is fully gone within 60 days of discovery at most. No retention schedule or keep-until hold extends these deadlines. This item is voluntary: the Texas rules it mirrors bind the TEFA administrator, not Homebook.
  7. No TEFA logins, Social Security numbers or TEFA application papers.
    1. Homebook never asks for or collects TEFA, Odyssey or Comptroller portal logins or passwords (the School’s or a parent’s), any digits of a Social Security number or ITIN, or copies of papers made for a family’s TEFA application (tax returns or transcripts, income proof, and citizenship or immigration papers submitted for TEFA). The School agrees not to enter them. This does not cover records the School keeps for its own enrollment, such as a birth certificate (item 6(a)).
    2. If one is entered by accident, Homebook removes it from the Service when found, tells the School, and lets backups expire as item 9 says.
  8. TEFA audit records. A TEFA School must give the Comptroller’s audit contractor and the State Auditor information and documentation about any TEFA transaction (Educ. Code 29.363(b); 34 TAC 16.404(a)(4)(G)). Homebook helps the School download its tuition, fee, payment, refund and enrollment records (CSV, at any time; section 3.4). It keeps them on the schedule in Schedule 1, part E (tuition and account records 7 years after the last transaction) unless the School deletes them sooner. The School sends the records to the auditor. If an auditor asks Homebook directly, item 11 applies.
  9. Deletion on request and at the end. When the School asks in writing (or deletes in the Service), Homebook offers an export first and deletes the School Data named from the Service within 30 days. Remaining backup copies expire within a further 30 days, are used only to recover from loss, and are never used to restore deleted data. When the School cancels, section 10.2 applies. Homebook destroys School Data by erasing it so it cannot be read or rebuilt (Tex. Bus. & Com. Code 521.052(b)), and confirms the deletion in writing on request (section 10.3). Homebook keeps only what section 10.4 allows.
  10. Parent and student requests. Section 3 applies. Requests to see, correct or delete records the School’s staff entered go to the School to decide. Within 10 days of the School’s request, Homebook gives the School what it needs to answer (an export of that student’s records, or a correction the School approves), so the School can meet FERPA’s 45 days where FERPA applies. Information collected from the student follows section 3.2 (COPPA).
  11. Police, courts, auditors and other demands. Section 5 applies, with these details for a Texas School:
    1. Homebook asks the requester to go to the School, and tells the School about the demand right away, before disclosing anything, unless a law or court order forbids telling the School.
    2. Advance notice to the family. Before Homebook discloses education records under a subpoena or court order, Homebook makes sure a reasonable effort has been made to tell the parent or eligible student first, so they can seek protection. Homebook does this either by getting the School’s written confirmation that it has done so, or by sending the notice itself. The only exception is a subpoena or order of the kinds that forbid notice (34 CFR 99.31(a)(9)(ii)(A) to (C); 99.33(b)(2)).
    3. Homebook discloses only the minimum the demand legally requires, and only after checking that it is valid and comes from someone with authority. Homebook asks the requester to narrow a demand that is too broad.
    4. Homebook keeps a record of each demand and what it disclosed. Unless a law or court order forbids it, Homebook gives the School a copy and, for a TEFA participating child, tells the School exactly what was disclosed so the School can tell the family.
  12. Breach notice to the School. Section 9 applies in full. If Homebook discovers unauthorized access to, or acquisition of, any School Data, it tells the School immediately following discovery (section 9.1). For a breach of sensitive personal information, Texas law also requires notice to the School “immediately after discovering the breach” (Bus. & Com. Code 521.053(c)). As Homebook’s own contract promise, it contacts the School within 48 hours of first suspecting a problem. That 48 hours is an outer limit and never permits a later notice than the law requires (sections 9.1 and 9.5). In Texas, a name with health information (allergies, conditions, medications, office visits) is “sensitive personal information” (521.002(a)(2)(B)), so a breach of health records counts even with no ID number involved. Nothing in this item lets Homebook delay telling the School. If a law enforcement agency asks for a delay, Homebook passes the request to the School. Homebook’s report gives, as far as known: what happened and when; what data and which people are affected, including how many Texas residents; how many have already been told directly; what Homebook has done; what it will do next; whether law enforcement is investigating; and a contact (section 9.2). These match what the Texas Attorney General’s form asks for (521.053(i)).
  13. Breach notices to families, the Attorney General and credit bureaus.
    1. Families. The School tells affected people without unreasonable delay and never later than 60 days after it determines that the breach happened (521.053(b)). Homebook prepares those notices whenever Homebook or its service providers caused the breach, and otherwise when the School asks. It sends them for the School if the School asks in writing, and pays their reasonable cost when Homebook or its providers caused the breach (section 9.3).
    2. Texas Attorney General. If 250 or more Texas residents are involved, the School reports to the Attorney General on the Attorney General’s online form, as soon as practicable and never later than 30 days after it determines the breach happened (521.053(i)). The Attorney General’s page counts from discovery, so plan on the earlier date. Because Texas law may also make Homebook a person required to give notice under that section, Homebook also files its own report on the same form for a breach of sensitive personal information Homebook holds. It does so whenever 250 or more Texas residents are involved, counted across every affected school, as soon as practicable and within 30 days of discovery. Homebook may file it jointly with the School, and gives the School a copy.
    3. Credit bureaus. If more than 10,000 people must be told at one time, the nationwide consumer reporting agencies are also told without unreasonable delay (521.053(h)). Homebook prepares that notice.
  14. Security program. Section 8 applies. For a Texas School, Homebook keeps a written information security program that includes: a named coordinator (section 8.2); encryption in transit and at rest, and each school’s data separated and tested; access only for people who need it, with two-step sign-in on every Homebook administrative account; a risk assessment, testing of safeguards, and a review and update of the program at least once a year (16 CFR 312.8(b)); yearly privacy and security training for everyone at Homebook who can reach School Data; and reasonable procedures to protect sensitive personal information (Bus. & Com. Code 521.052(a)).
  15. De-identified information. Section 4.7 applies unchanged: Homebook never tries to re-identify a student, a family or the School, and never sells or shares de-identified student data. That holds even at the School’s request and even for research. “De-identified” means information that cannot reasonably be linked to a student, a family, a staff member, the School, or a device. Homebook may use it only to run, secure and fix the Service for the School. De-identified TEFA information is covered by item 4 as well.
  16. No biometric identifiers. Homebook never captures or derives a biometric identifier: a retina or iris scan, fingerprint, voiceprint, or record of hand or face geometry (Bus. & Com. Code 503.001(a)(2)). Homebook never asks for one or keeps one on purpose. Student and staff photos are optional, are stored only as pictures, and are never used to measure faces, for facial recognition, or to train AI (section 4.5). Homebook’s staff fingerprint tracker, where used, holds dates only. The School agrees not to upload fingerprint images, fingerprint cards or voice recordings for identification. If one is uploaded by accident, Homebook tells the School, removes it from the Service, and lets backups expire as item 9 says.
  17. FERPA and federal law. Section 2.3 applies to the School whether or not it receives federal education funds. TEFA money alone does not make a school a recipient of federal financial assistance (Educ. Code 29.368(a)). Homebook complies with COPPA for student logins (section 7.3 and Schedule 1), and follows state and federal law on keeping student educational information confidential (Educ. Code 29.369(c)(1)).
  18. Processor terms (taken on voluntarily). Homebook acts only as the School’s processor. It takes on the following whether or not the Texas Data Privacy and Security Act applies to Homebook: this agreement sets out Homebook’s instructions, the nature, purpose and type of processing, how long it lasts, and each side’s rights and duties; everyone who handles School Data is bound to confidentiality (section 8.4); Homebook deletes or returns School Data at the end (section 10.2); on the School’s reasonable request, Homebook gives it the information Homebook has that the School needs to show Homebook’s compliance with this agreement and any privacy law that applies; Homebook allows and cooperates with reasonable assessments by the School or an assessor it names, at the School’s cost, or instead may arrange for a qualified, independent assessor to assess Homebook’s policies and its technical and organizational measures, using an appropriate and accepted control standard or framework and assessment procedure, and give the School the report on request (541.104(c)); Homebook gives the School the information it needs for any data protection assessment the law requires of it; and Homebook binds its subcontractors in writing (item 3) and helps the School answer privacy requests from families and staff (item 10).
  19. Accepting. Before the School adds students or families, its director or administrator accepts this agreement and this add-on in Homebook (section 13.4). A TEFA School also confirms items 5(b) and 5(c) at the same time. A signed paper copy does not replace this in-app acceptance.
  20. Order of precedence. Where this add-on and the rest of this agreement differ for a Texas School, the more protective promise applies (section 1.4). Where a law gives the School, a family or a student more protection, that law applies too (sections 2.4 and 13.1). Nothing in this add-on gives Homebook more time for any notice or deadline.
  21. The AI assistant and student records. Homebook’s rule is that its AI assistant (Anthropic’s Claude, which Homebook uses to build, test and fix the Service) reads student records only through a read-only database login limited to de-identified views, and those reads are logged: each student appears as a random code, with no name, contact details, birthday, address, guardian or emergency contact, health information, support plan, photo or free-text note. Support-ticket text goes through a tool that replaces the names on the School’s roster (students, their families and contacts), email addresses and phone numbers with codes before the assistant reads it; the rest is passed as written, and a nickname, a misspelled name or a name that is also an everyday word can slip past that swap. A TEFA child whose family has not said yes, or has said no, is left out of those records, and a ticket naming that child is held back for Homebook’s staff to read. The codes never appear anywhere the School, a family or a student sees. The assistant also helps Sam with his own email and texts: a message a School or family sends there is read as written, and the assistant never copies a child’s name from it into notes, drafts or Homebook’s records. Code changes the assistant makes are tested and reviewed before release; data fixes are made against the student codes and checked afterward.
Homebook
Help & guidesHow-to videosFunding HelperArkansasAlabamaArizonaIowaOklahomaTexasTennesseeSchool FinderCollege & CareerSwitching from GradelinkSwitching from FACTSTermsPrivacySecuritySystem statusManage subscription
Made in Central Arkansas · sam@gethomebook.com · © 2026 Homebook, LLC