Skip to main content
Meta Typing Club

Meta Typing Club School Agreement and Student Data Privacy Addendum

Version ⁨2026-10-v3⁩ · in effect from October 22, 2026

1. Who this agreement is between

This School Agreement ("Agreement") is between BalPary LLC, the operator of Meta Typing Club ("Meta Typing Club", "we", "us"), and the school, district or other educational organization named in the school account ("School", "you").

The Agreement is accepted by the person who creates the school account and ticks the acceptance box (the "Account Manager"). By accepting, the Account Manager declares that they accept on behalf of the School, not for themselves; that they have authority under the School's own rules to accept this Agreement for the School; and, for a public or government school, that they are an authorized representative of that school.

We record the acceptance: the version of this Agreement, the date and time, and the name and job title of the person who accepted.

Only the person who creates the School account, and so becomes its owner, can accept this Agreement. A teacher who is not authorized to bind the School should ask an administrator to create the School account instead.

2. The documents that make up the agreement

The Agreement consists of the following documents. If they conflict, they apply in this order:

  • any signed data privacy agreement between Meta Typing Club and the School or its district, for the School it covers;
  • the Student Data Privacy Addendum (Part 2 below), which controls everything about Student Data;
  • this School Agreement;
  • the general Meta Typing Club Terms of Service and Privacy Policy, which apply to the School only where this Agreement and the Addendum are silent.

The current version of this Agreement, and the version the School accepted, can be read at any time in the School's Settings and saved or printed as a PDF from there. We do not send the Agreement by email.

3. Definitions

  • Service: the Meta Typing Club web application, its typing lessons in multiple international languages, and its school features (classes, assignments, reports, login cards, roster import and data export).
  • School Users: the School's owner, administrators, teachers and staff who have accounts in the School.
  • Students: learners whose accounts belong to the School, whether the School created them or they joined the School.
  • Student Data: any information about a Student that the Service collects, receives or creates while providing the Service to the School, including information that identifies a Student and records of their typing practice. The full list is in the Addendum, Exhibit B.
  • De-identified Data: data from which all direct and indirect identifiers have been removed, so that it cannot reasonably be linked to a Student.
  • Educational Purpose: providing typing instruction and the school features to the School, for the use and benefit of the School, and for no other commercial purpose.

4. The Service and the School's plan

Trial. A new School starts with a 30-day trial with no plan limits. No payment card is needed.

Free plan. When the trial ends, the School moves automatically to the Free plan, at no cost and with no end date. On the Free plan the School may use the Service within the Free-plan limits shown on the pricing page (for example, how many teachers, classes and assignments may be active at one time, and how many lessons each Student may complete per day); the School's owner, administrators and staff are not counted as teachers. A daily limit resets at midnight in the School's time zone, or UTC if no time zone is set.

There is no limit on the number of Students. To protect the Service, a single roster import is limited to 500 Students and a School may create up to 2,000 Students per day.

Above the Free limits. Nothing is deleted when a School moves to the Free plan. Teachers, classes and assignments above the limits are paused, and the School chooses which stay active. Paused items are restored when the School moves to a plan with higher limits.

Paid plans. Paid plans, when offered, will be described in a separate order form. Payments for paid plans are governed by the "Payments and Subscriptions" section of the Terms of Service.

Changes to the Free plan. We may change the Free plan's limits. We will tell the Account Manager at least 30 days before a reduction takes effect, and a reduction will never delete Student Data.

Changes to the Service. We improve the Service over time and may change or remove features. We will not change how Student Data is collected, used or shared without following Section 12.

5. What the School is responsible for

The School will:

  • use the Service for its Educational Purpose and let only its own School Users and Students use it;
  • keep account information accurate, and remove School Users and Students who leave the School;
  • keep login cards and Student passwords confidential (they are sign-in credentials, not directory information) and give each card only to the Student it belongs to;
  • decide, under its own policies, whether to tell parents about the Service; we recommend that it does, and links them to our Privacy Policy;
  • where the School is subject to FERPA and relies on its school-official exception, include providers like Meta Typing Club in its annual notice's criteria for school officials with a legitimate educational interest;
  • obtain any consent that the School's own rules or local law require from parents, guardians or adult Students before adding them;
  • tell us promptly if it believes a School User account has been misused;
  • set the School's consent mode truthfully: the "adult" mode may only be chosen when every Student is an adult.

The School is not responsible for Meta Typing Club's own compliance with the Children's Online Privacy Protection Act (COPPA); see Section 6.

6. Children's privacy: the School as the parents' agent

School authorization. Many Students are under 13. Where the School uses the Service for its Educational Purpose, the School authorizes Meta Typing Club to collect Student Data from its Students on the parents' behalf, as the Federal Trade Commission's guidance on COPPA and schools permits. That authorization covers the Educational Purpose only.

What we give the School. Before the School authorizes collection, we give it the information a parent would receive: what we collect, how we use it, who we share it with and why, and how to review and delete it. That information is the Addendum (Part 2), especially Exhibit B and Schedule 2. On the School's request we will describe the types of Student Data we hold, let the School review a Student's data, delete a Student's data, and stop further collection from a Student.

Our own responsibility. Meta Typing Club, not the School, is responsible for Meta Typing Club's compliance with COPPA. Nothing in this Agreement moves that responsibility to the School or its teachers.

No other commercial use. We use Student Data only for the Educational Purpose. We do not advertise or market to Students or their parents; we do not sell or rent Student Data; we do not build profiles of Students except for the School's own instruction (for example, showing a teacher which keys a Student finds hard); and we do not train artificial-intelligence models on Student Data. Any other use would need verifiable consent from each parent directly; the School's authorization could not cover it.

Parents' requests. A parent who asks us to review or delete their child's data will usually be referred to the School, because the School controls the account. If the School has not acted within 30 days, or the law requires us to respond directly, we verify the parent's identity in a reasonable way, act on the request ourselves, and tell the School.

Homeschools. Where a parent registers their own homeschool, that parent accepts this Agreement both for the homeschool and, as the parent or legal guardian of each Student they add, gives consent for that Student. They confirm that they are the parent or legal guardian of every Student they add.

7. Acceptable use

School Users and Students must not:

  • break any law or use the Service to harm, harass or bully anyone;
  • share another person's password or sign in as someone else;
  • try to get around plan limits, security controls or the daily lesson limit;
  • scrape, copy or resell the Service or its lessons;
  • upload malicious code or overload the Service;
  • cheat or manipulate typing results (we automatically flag improbable results; flags are deleted after 180 days).

We may suspend an individual account or the School's account where needed to stop a serious or repeated breach of this section, to protect Students, or to protect the Service. We will tell the Account Manager why, unless the law does not allow it. A suspension does not delete Student Data.

8. Who owns what

The School owns Student Data. The School (or the Student, where the law gives them rights) owns and controls Student Data. Meta Typing Club holds and processes it only on the School's behalf, under the School's direct control, and only as this Agreement and the Addendum allow.

Our licence to Student Data. The School gives us a limited, non-exclusive, non-transferable right to use Student Data only to provide, secure, support and maintain the Service for the School. We have no right to sell, rent or trade it.

De-identified Data. We may use De-identified Data to maintain and improve the Service (for example, to learn which lessons are too hard). We will not try to re-identify it and will not pass it to anyone who does not agree to the same rule. We do not sell or publish De-identified Data. For Schools in New York we do not use their Students' data, even de-identified, to develop or improve products.

Our content. The Service, its lessons, design, software and trademarks belong to Meta Typing Club or its licensors. The School gets a non-exclusive, non-transferable right to use them for its Educational Purpose while this Agreement is in force.

9. Privacy and security

The Addendum (Part 2) governs Student Data: what we collect, the purposes, security, breach notification, retention, deletion, sub-processors and state-specific terms. School Users' own account data (for example a teacher's email address) is handled under our Privacy Policy.

10. Accessibility

We design the Service to meet the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, including right-to-left layouts for right-to-left languages. If a School User or Student reports an accessibility barrier, we will investigate it and tell the School our plan to fix it. This section is a commitment to fix barriers, not a warranty that the Service conforms.

11. Term, ending the Agreement, and what happens to the data

Term. The Agreement starts when it is accepted and continues until the School account is deleted or the Agreement is ended under this section.

The School may end it at any time by deleting the School in Settings. Only the School's owner can do this, and must confirm the School's name.

Recovery window. A deleted School can be recovered by its owner for 90 days. We send reminders before the window closes.

Export before you go. At any time, including during the recovery window, the School's owner or an administrator can download a data export (the School's profile, settings, agreement record, members, classes, assignments and each Student's lesson results; the link is sent to the requester, lasts 24 hours and can be used 5 times) and the report data as a spreadsheet (CSV) from the Reports tab.

Deletion at the end. When the 90-day recovery window ends we remove the School's name and details and end every membership in the School, and within 60 days after that we delete the accounts of Students the School created together with all their Student Data, including practice records. A Student account that a family created and that later joined the School is only removed from the School, because the family controls it. On request we confirm the deletion to the School in writing.

We may end the Agreement if the School seriously breaches it and does not fix the breach within 30 days of our notice, or immediately where needed to comply with law. If we stop offering the Service entirely, we will give at least 90 days' notice so Schools can export their data.

Sections 6, 8, 11, 13, 14 and 15 continue after the Agreement ends.

12. Changes to this Agreement

We may update this Agreement or the Addendum. Each version has a version name and date, and past versions stay readable in the product.

Material changes need your acceptance. If a change is material, in particular any change to what Student Data we collect, how we use it or who we share it with, we will tell the Account Manager in the product and by email at least 30 days before it takes effect, and the change will apply to the School only after the School accepts the new version. Until then the School keeps the version it accepted, or may export its data and leave. We will not make a change that reduces the protection of Student Data already collected without the School's consent.

Non-material changes (for example, clearer wording or a new contact address) take effect when published.

13. Warranties and disclaimers

Each party confirms it has the power to enter into this Agreement. We will provide the Service with reasonable skill and care and in line with the Addendum. Apart from that, the Service is provided "as is" and "as available". We do not promise that it will be uninterrupted or error-free, or that Students will reach any particular typing result.

14. Liability

No payment from us. The School uses the Service at its own risk. To the fullest extent the law allows, Meta Typing Club and BalPary LLC are not liable to the School for any loss or damage arising from the Service or this Agreement, and owe the School no payment of any kind under it. Any payment obligation exists only under a separate agreement signed by the School and BalPary LLC.

Neither party is liable for indirect or consequential losses, to the extent the law allows. Nothing in this Agreement excludes liability that the law does not allow to be excluded, and where a public School's state law limits this section, it applies only as far as that law allows. Neither party gives the other an indemnity under this Agreement.

15. Governing law and disputes

This Agreement is governed by the laws of the state where BalPary LLC is organized, except that a public School may require the law of its own state to govern. Nothing in this Agreement overrides a public School's sovereign immunity or its public-records obligations.

The parties will first try to resolve a dispute by good-faith discussion for 30 days. After that, disputes go to the courts of that state, except that a public School may bring or defend any dispute in the courts of its own state.

No arbitration and no waiver for Students or parents. The School's acceptance of this Agreement does not bind Students or parents to any dispute-resolution, arbitration or class-action-waiver terms.

16. General

Notices. We send notices to the Account Manager's email address and show them in the product. The School sends notices to metatypingclub@gmail.com.

Language. This Agreement is written in English. Translations into multiple international languages are provided for convenience; if they conflict, the English version governs.

Transfer. We may transfer this Agreement to a successor that takes over the Service, but only if the successor is bound by the Addendum. We will tell the School before any transfer.

Public records. Nothing in this Agreement prevents a public School from meeting its public-records or open-meetings obligations.

Entire agreement. The documents in Section 2 are the whole agreement about the School's use of the Service. If a court finds a provision unenforceable, the rest stays in force.

Contact. BalPary LLC, operator of Meta Typing Club: metatypingclub@gmail.com.

Article I — Purpose and scope

This Addendum describes how BalPary LLC, operator of Meta Typing Club ("Provider"), protects Student Data it receives or creates while providing the Service to the School. In providing the Service, Provider acts as a school official with a legitimate educational interest, performing a service the School would otherwise use its own staff for, under the School's direct control over the use and maintenance of Student Data, and bound by the limits on use and re-disclosure in 34 CFR 99.33(a).

The services are described in Exhibit A and the Student Data in Exhibit B. Provider will not add a new category of Student Data without giving the School at least 30 days' notice and a chance to object.

Article II — Data ownership and access

Ownership. Student Data is and stays the property of, and under the control of, the School.

Access, correction and deletion. The School can see each Student's account, classes and lesson results in the product, download them, correct a Student's name, username and class membership, and delete a Student it created. For anything else the School cannot do itself, Provider answers the School's written request for access or correction within 30 days, or sooner where state law requires; requests to delete Student Data follow Article IV. If a parent or Student contacts Provider directly, Provider refers them to the School and tells the School, unless the law requires Provider to respond directly.

Sub-processors. Provider uses only the sub-processors listed in Schedule 2, binds each one to protect the data, never lets a sub-processor sell Student Data or use it for its own purposes, and gives the School at least 30 days' notice before adding or replacing one, so the School can object.

Article III — What the School does

  • Provides Student Data to Provider only as its own rules and applicable law allow.
  • If it relies on FERPA's school-official exception, includes providers like Provider in its annual notification of who counts as a school official.
  • Takes reasonable care to keep School User passwords and Student login cards confidential.
  • Tells Provider within 72 hours if it learns of unauthorized access to Student Data through a School account.

Article IV — What Provider does

Law. Provider complies with the laws that apply to it in providing the Service, including COPPA, and with FERPA and PPRA as they apply to a school official and a service provider. Provider bears its own COPPA obligations; they are not the School's.

Use only for the School. Provider uses Student Data only to provide, support, secure and maintain the Service for the School, and as the School instructs through the product or in writing.

Staff. Only Provider staff who need Student Data to do their job can access it, and each is bound to keep it confidential.

No disclosure, no sale. Provider does not sell, rent or trade Student Data and does not disclose it except to its sub-processors under Article II; as the School directs; to comply with law or a court order, telling the School first unless the law forbids it; to protect the safety of a Student or others in an emergency, telling the School as soon as possible; or to a successor that takes over the Service and agrees in writing to this Addendum, with at least 60 days' notice to the School.

De-identified Data. Provider may use De-identified Data to maintain and improve the Service, will not attempt to re-identify it, and will not transfer it to anyone who does not agree to the same. Provider does not do this with New York Schools' data.

Return and deletion. On the School's written request, Provider deletes the Student Data named in it within 60 days; the School can also delete a Student it created itself, in the product. When the School is deleted it has 90 days to recover it or export its data; within 60 days after that window closes Provider deletes all Student Data of Students the School created and tells the School the date of destruction. On request Provider confirms the deletion in writing. Provider keeps only records the law requires it to keep and De-identified Data. Special instructions go in Exhibit D.

No advertising, no profiling, no commercial use. Provider does not show advertising to Students, or to School Users while they use school features; does not use Student Data or identifiers from the Service for targeted advertising, on the Service or anywhere else; does not load third-party analytics, advertising or session-recording tools for signed-in Students; does not build a profile of a Student except for the School's instruction; and does not use Student Data for any other commercial purpose, including training artificial-intelligence models.

Article V — Security and breach

Where data is stored. Student Data is stored and processed in the United States. Provider will not move primary storage outside the United States without 30 days' notice and the School's agreement.

Security measures. Provider protects Student Data with:

  • passwords stored only as Argon2id hashes (Student passwords are shown once, when they are created or reset, and are never stored in readable form); sign-in codes and reset and verification tokens stored hashed;
  • sign-in sessions in httpOnly cookies, secure in production, that expire after 30 days;
  • encrypted connections (HTTPS) for all traffic;
  • account lockout after repeated failed sign-ins, and rate limits on sign-in, sign-up and the API;
  • role checks on every school feature, so each person sees only what their role in that School allows;
  • removal of passwords and tokens from error reports;
  • an audit log of school membership and role changes, consent-mode changes, agreement acceptances, school purges and sign-ins.

Data Breach notice. If Provider confirms a Data Breach affecting the School's Student Data, it notifies the School's Account Manager within 72 hours of confirmation. The notice says, as far as known, what happened, when, which data and which Students are affected, what Provider has done, a contact person, and whether law enforcement asked for a delay. Provider cooperates with the School and law enforcement; unless the parties agree otherwise, the School decides how parents are told, with Provider's help.

Costs. Provider does not pay the School's breach-related costs (such as notification, credit monitoring, legal fees, audit costs or fines) under this Addendum, except where the law requires it. A School that needs Provider to cover such costs must sign a separate data privacy agreement with BalPary LLC.

Questionnaire. Once a year a School may send Provider a security questionnaire about this Addendum, which Provider answers within 30 days.

Article VI — General

  • Term: this Addendum lasts as long as Provider holds Student Data from the School.
  • Priority: for Student Data, this Addendum prevails over the School Agreement, the general Terms of Service and the Privacy Policy. A signed state data privacy agreement with the School prevails over this Addendum.
  • Changes: Provider will not change this Addendum to reduce the protection of Student Data without the School's acceptance of the new version.
  • Change of control: Provider tells the School at least 60 days before a change of control, and the School may then end the Agreement.
  • Governing law: for a public School, the law of the School's state governs this Addendum; otherwise Part 1, Section 15 applies.
  • Language: English governs; translations are for convenience.

Exhibit A — Description of services

  • Typing lessons and practice in multiple international languages.
  • School accounts with owner, administrator, teacher, staff and Student roles.
  • Classes, assignments of lessons to classes, and teacher progress views (speed, accuracy, lesson completion, hard keys).
  • School-wide reports, downloadable as a spreadsheet.
  • Student accounts created by the School, one by one or from a roster file, with printable login cards.
  • Badges, points and streaks for Students.
  • A School data export, and School deletion with a 90-day recovery window.

Not included: chat, messaging between Students, public profiles, public leaderboards, photo upload, voice and location.

Exhibit B — Schedule of Student Data

CategoryWhat is collectedNotes
Technical dataIP address (briefly), one sign-in cookie, browser time zone, browser type in error reportsIP addresses are used only for rate limiting and kept up to one hour. Error reports are kept 30 days.
Usage dataLast sign-in time, online status, lesson start and finish timesNo third-party analytics or session recording for signed-in Students.
Student nameFirst name (required) and last name (optional)Up to 50 characters each.
Student identifiersInternal account ID, username, passwordPasswords are stored only as hashes.
EnrollmentSchool and class membership; class grade levelGrade level is stored on the class, not on the Student.
ScheduleClasses, teachers, assignments and due dates
LanguageInterface language and practice languagesOptional.
Contact informationOptional "connected email" onlySchool-created Students have no email address. No address or phone number.
PerformanceTyping results per session: speed, accuracy, errors, stars, duration, the lesson text and the characters typed; overall progress, hard keys, streaksNo keystroke timing is stored.
RewardsPoints, badges, streaksPoints history kept 400 days.
OtherA generated cartoon avatar, display preferences, automatic flags on improbable resultsNo photos or uploads. Flags kept 180 days.
Not collectedDate of birth, gender, ethnicity, address, phone, health, disability or special-education data, surveys, attendance, grades, voice, location

Exhibit C — Definitions

  • Data Breach: unauthorized access to, or acquisition, use or disclosure of, Student Data in Provider's or its sub-processors' custody.
  • Sub-processor: a third party that Provider uses to process Student Data for the Service (Schedule 2).
  • Targeted Advertising: showing ads to a Student based on information about them or their behaviour, on the Service or elsewhere.
  • Other capitalised terms have the meaning given in Part 1, Section 3.

Exhibit D — Special disposition instructions

Filled in by the School only when it asks for disposition of Student Data: which data, by when, whether to delete or transfer it, and the format for a transfer. Send it to metatypingclub@gmail.com.

Exhibit G — State terms

Where a state law below applies to the School, Provider also agrees to the listed commitments. Breach notice to the School is within 72 hours in every state.

StateLawAdditional commitments
CaliforniaBus. & Prof. Code §22584; Educ. Code §49073.1Pupil records remain the School's property; no targeted advertising; certification that records are not kept after the Agreement ends; deletion of covered information on a parent's or former pupil's documented request 60 days after un-enrolment.
New YorkEduc. Law §2-d; 8 NYCRR Part 121Provider signs the School's Parents' Bill of Rights and supplemental information; no sale, marketing or commercial use, including product improvement; staff trained before access. Provider reimburses the School's breach-notification costs only where Education Law §2-d requires it, or under a separately signed agreement.
Illinois105 ILCS 85 (SOPPA)Provider acts as a school official; breach costs are allocated as in Article V; deletion or transfer within 60 days once no longer needed; the sub-processor list is provided each fiscal and calendar year; corrections within 90 days.
ConnecticutConn. Gen. Stat. §§10-234aa–10-234ffStudent data is not Provider's property; no retention after the Agreement ends; Connecticut law governs for Connecticut Schools.
ColoradoC.R.S. 22-16-101 et seq.Plain-language data list (Exhibit B) for the School to post; notice before material privacy changes; Provider tells the School the date of destruction.
TexasEduc. Code §§32.151–32.157Deletion within 60 days of the district's request.
VirginiaCode §22.1-289.01Notice before material changes; deletion within a reasonable time on request.
UtahUtah Code 53E-9-309; R277-487The School may audit compliance through the yearly questionnaire; the School may terminate for a privacy violation with no fee or liability.

Exhibit H — Schools outside the United States

School accounts are not offered to Schools in Iran (United States sanctions) or Russia (Russian law requires Russian citizens' data to be stored in Russia). Schools in the European Union or the United Kingdom need additional data processing terms; they should contact Provider at metatypingclub@gmail.com before creating a School account.

Schedule 2 — Sub-processors

Sub-processorPurposeStudent Data involved
NetlifyHosting of the web applicationPage requests
Heroku (Salesforce)Hosting of the application serverAll Student Data while it is processed
MongoDB AtlasDatabaseAll stored Student Data
Google (email delivery)Email to School UsersNone: School-created Students have no email address
ResendSign-in code emailsOnly a Student's optional connected email, when they sign in with a code

Schedule 3 — Retention

DataHow long it is kept
Student account and learning recordsWhile the Student belongs to the School; deleted within 60 days of the School's request or of the end of the 90-day recovery window after the School is deleted
Points history400 days
Automatic result flags180 days
Daily lesson counter3 days
Sign-in sessions30 days
Error reports30 days
School data export link24 hours