Terms of Service
The agreement between a school in the United States and Onflows for the use of the Onflows service.
Awaiting legal review. This version describes how Onflows operates today and is under review by counsel for United States. If your school needs a countersigned agreement now, ask us before you begin.
United States · version 1.0.0 · in force from 13 Oct 2026 · written against Family Educational Rights and Privacy Act (FERPA), 20 U.S.C. 1232g and 34 CFR Part 99, Children's Online Privacy Protection Act (COPPA), 15 U.S.C. 6501 to 6506 and 16 CFR Part 312, State student privacy laws, including California's Student Online Personal Information Protection Act (SOPIPA).
The agreement between a school in the United States and Onflows for the use of the Onflows service.
1. The parties and the account
These terms are an agreement between the school or district named at signup (the school, you) and Onflows, the provider of the service at onflows.app (Onflows, we, us). They apply from the moment the school's administrator accepts them while claiming the school's account, and they govern every use of the service by the school and the people the school invites.
The person who accepts these terms confirms that they are authorized to bind the school. The school's account is the school's own instance of Onflows: its records, its users and its settings. One school holds one account, and the account may not be shared with or transferred to another institution without our written agreement.
The service is offered to schools and other educational institutions, not to consumers. Where a state law or a district policy requires a specific student data privacy addendum, the school may send us its own and, once both parties sign it, it prevails over the Student Data Privacy Agreement in this pack wherever it is stricter.
2. The service
Onflows is a hosted, workflow-first operating system for educational institutions. The school receives its own portal, its own records and sign-in for the people it invites. There is nothing to install and no server for the school to run.
The service is made up of modules such as admissions, students, classes, staff and communications, and of further modules that belong to the Pro plan. Which modules a school holds is decided by its plan, as set out in section 3.
3. Plans and fees
Onflows is offered on two published plans. The Community plan is free, has no time limit and covers a school with up to 200 live students. A live student is a student with an active enrollment in the school's current academic year; students who have graduated or left do not count.
The Pro plan adds the Pro modules and is priced per live student per year, at the rate published on our pricing page or quoted to the school in writing. It is billed annually in advance on the number of live students on the day of payment. There is no adjustment during the year; the renewal counts the roll again.
Every school holds the Pro plan at no charge for the first six months after its account is opened, and is told so by email at the start of that period and before it ends. When that period ends, the Pro modules close unless the school has moved to the Pro plan. Nothing the school has recorded is deleted when a module closes, and the Community modules keep working.
A school that passes 200 live students is on the Pro plan and pays for its roll. The service warns the administrator as the roll approaches the limit and declines new admissions and imports at the limit until the plan is raised; nothing already recorded is affected.
4. Payment, invoices and tax
Payment is made outside the product, against an invoice we issue, by bank transfer or another method we agree with the school. Our rates are exclusive of sales, use and similar taxes; where such a tax applies and the school has not given us a valid exemption certificate, it is added to the invoice.
A rate quoted to a school in writing, including a launch price, remains that school's rate at renewal unless we agree a different one with the school. We may revise the published rate for new customers at any time.
If an invoice is not paid when due, we remind the school and allow a grace period before the Pro modules close. A late invoice never takes away the school's own records, and the school may export everything at any time.
5. Acceptable use
The school may use Onflows only to run the school. The school and its users must not attempt to reach another school's records, probe, overload or interfere with the service, reverse engineer the software, or upload material the school has no right to hold or that is unlawful.
Separation between schools is enforced by the database regardless of this clause, and an attempt to cross it is treated as a serious breach. We may suspend an account that breaches this section, as described in section 10.
6. The school's responsibilities
The school decides who may sign in and what role each person holds, and it reviews those roles as staff join and leave. Every action in Onflows is attributed to the signed-in person, so credentials must stay with the person they belong to. The school is responsible for the acts of its users and for the security of their credentials, and must tell us promptly if it believes an account has been compromised.
The school controls the education records it enters. It is responsible for the accuracy of that data, for its authority under FERPA and state law to disclose it to us as a school official, for any parental consent its law requires before a child's data is entered, including consent under COPPA given by the school on parents' behalf in the educational context, and for the notices it gives to parents and students.
The school must keep its own account details, billing contact and administrator current, so that the notices we are obliged to send reach someone who can act on them.
7. Onflows' responsibilities
We provide the service with reasonable skill and care and make reasonable efforts to keep it available. We do not offer a contractual uptime guarantee on the published plans. We tell the school before planned maintenance that will interrupt the service, and we keep backups of the school's data.
We process the school's data only on the school's instructions and only to run the school's own instance, as set out in the Privacy Policy and the Student Data Privacy Agreement. We do not sell the data, use it for advertising, use it for any secondary purpose, or use it to train artificial intelligence or machine learning models.
We protect the school's data with the measures described in the Privacy Policy, and we notify the school of a data breach without undue delay and in any case within 72 hours of becoming aware of it.
8. Intellectual property and the school's data
The school owns the data it enters into Onflows and everything derived from it for the school's own use, such as reports, certificates and exports. The school grants us only the license needed to store, process and display that data in order to provide the service to the school.
Onflows owns the software, its design, its documentation and the curriculum and workflow content it ships with. The school receives a non-exclusive, non-transferable right to use the service for the term of this agreement, and gains no other right in the software. Feedback the school gives us may be used to improve the service without obligation to the school.
9. Confidentiality
Each party keeps the other's confidential information in confidence and uses it only for the purposes of this agreement. The school's records are the school's confidential information. Our pricing offered privately to the school, and the non-public workings of the service, are ours.
Confidential information may be disclosed where the law requires it, including under a public records law that applies to the school, after notice to the other party where notice is lawful, and to professional advisers bound by confidentiality. The obligation survives the end of this agreement for as long as the information stays confidential.
10. Suspension and termination
The school may stop using Onflows at any time. On leaving, the school may export everything it put in, and may ask us to delete its data; we confirm the deletion in writing within 30 days of the request.
We may suspend an account for a serious breach of section 5, for a security threat to the service or to other schools, or where the law requires it. We give notice and an opportunity to cure wherever that is reasonable. We may end this agreement for a breach that is not cured within 30 days of notice.
We never delete a school's records for non-payment. An unpaid invoice closes the Pro modules after the grace period and nothing else; the school's data stays in place and remains exportable.
Sections 8, 9, 11 and 13 survive the end of this agreement.
11. Liability
Our total liability to the school under or in connection with this agreement, in any twelve month period, is limited to the fees the school paid us in the twelve months before the event giving rise to the claim. For a school on the Community plan or within its free period, that figure is nil, and our liability is limited accordingly.
Neither party is liable to the other for loss of profit, loss of business, or indirect, incidental, special or consequential damages. Nothing in these terms excludes or limits a liability that cannot lawfully be excluded or limited, including liability for fraud or willful misconduct. Nothing in this section waives a sovereign or governmental immunity a public school holds under its state law.
To the extent its state law allows, the school indemnifies us against claims arising from data the school entered without authority or from a use of the service by the school's users that breaches these terms.
12. Changes to these terms
We may change these terms. For a change that materially affects the school, we give at least 30 days notice by email to the administrator before it takes effect, and the administrator is asked to accept the new version on their next sign-in, with a summary of what changed. We do not make a material change to the privacy terms that applies to data already collected without the school's agreement.
Each version carries a version number and an effective date, and the school can see every version it has accepted, with the date and the person who accepted it, in the Legal section of its settings. A school that does not accept a new version may continue to export its data and may end the agreement under section 10.
13. Governing law and disputes
This agreement is governed by the laws of the State of Delaware, without regard to its conflict of law rules, and the state and federal courts located in Delaware have exclusive jurisdiction over any dispute arising from it. Where the school is a public body whose state law requires its own law and venue to apply, that law and venue apply instead.
Before starting proceedings, the parties attempt in good faith to resolve the dispute between their representatives within 30 days of written notice.
14. Contact
Questions about these terms, a countersigned agreement, a state-specific addendum or an Enterprise plan go to hello@onflows.app. A school already using Onflows that needs help with the service writes to care@onflows.app.