Privacy Policy
How Onflows handles the personal data a school in India puts into the service, as the school's data processor.
Awaiting legal review. This version describes how Onflows operates today and is under review by counsel for India. If your school needs a countersigned agreement now, ask us before you begin.
India · version 1.0.0 · in force from 13 Oct 2026 · written against Digital Personal Data Protection Act 2023, Information Technology Act 2000 and the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules 2011.
How Onflows handles the personal data a school in India puts into the service, as the school's data processor.
1. Who we are and our role
Onflows provides the service at onflows.app to schools. For the personal data a school enters into Onflows, the school is the data fiduciary under the Digital Personal Data Protection Act 2023 and Onflows is the data processor. We store and process that data on the school's instructions and for no purpose of our own.
This policy explains what the service holds, why, where, for how long, and how a person reaches us about their data. It describes how the software behaves today, and every statement in it is one the service enforces.
2. What data the product holds
The service holds the following categories of data for each school.
- Account data: the name, email address, phone number where given, and role of each person the school invites, and the credentials for their sign-in. Passwords are stored only as hashes.
- Student and family records the school enters: admissions, student profiles, guardians and their contact details, enrolments, attendance, marks and report cards, fee ledgers and receipts, timetables, homework, certificates and files uploaded to a student's documents.
- Staff records the school enters: profiles, roles, subjects, attendance and leave.
- Usage logs: the time and nature of requests to the service, the network address they came from and the browser used, kept to operate and secure the service.
- An audit trail: who changed what, and when, kept append-only so that a correction is visible as a correction and not as an edit.
- Support messages: what the school writes to us at care@onflows.app or through the support form, and our replies.
3. Why we process it and on what basis
We process the school's data only to provide the service to the school: to store the records, to run the workflows the school starts, to send the messages the school sends, and to show each signed-in person what their role permits. The school decides what is collected and on what basis, including the consent the Act requires, and we act within that decision.
We process account data and usage logs to operate, secure and support the service, which is necessary to perform our agreement with the school. We do not use any of the data for advertising, do not sell it, and do not use it for any purpose beyond running the school's own instance.
4. The AI features and the no-training commitment
Some modules use a language model to help with a task the school asks for, such as drafting a timetable or answering a help question. When a person uses such a feature, the service sends only the minimum text needed for that task to the model provider, and shows the result to that person.
School data is never used to train or improve any artificial intelligence or machine learning model, by us or by anyone we engage. The model provider is contractually barred from training on the text it receives from us, and we configure its service to decline data retention wherever it offers that option. Every model call the product makes is registered in the product and reviewable.
5. Sub-processors and where data lives
We use the following sub-processors, each under a written agreement that binds it to protect the data and to use it only to provide its service to us. The current list is published at onflows.app/privacy, and we notify schools of a material change at least 30 days before it takes effect.
The school's database and files are hosted in Tokyo, Japan. The Act permits processing outside India except in countries the Central Government restricts by notification, and we will tell schools before any change of hosting location.
- Supabase: the managed Postgres database and file storage the service runs on, hosted in Tokyo, Japan.
- A transactional email provider: for invitations, password resets and notifications. It receives the recipient address and the content of that message.
- MSG91: for SMS and WhatsApp messages the school sends. It receives the recipient number and the content of that message.
- Google Gemini: the model provider for the AI module. It receives only the text needed for the task requested, and is barred from training on it.
6. Security
We protect the school's data with the following measures, which are the reasonable security practices and procedures we maintain under the Information Technology Act 2000 and the rules made under it.
- Isolation: every record carries the school's identifier, and every table carries a row-level security policy enforced by the database itself, so a read or write that crosses schools is refused regardless of application code.
- Encryption: data is encrypted in transit using TLS and at rest.
- Access control: a person sees only what their role permits, and permission is checked when an action runs, not when a menu is drawn.
- Audit: an append-only trail records who changed what and when.
- Our staff: access to production data is limited to what is necessary to operate or support the service, and is logged.
- Backups: taken regularly and held under the same protections.
7. Retention and deletion
The school's data is kept for as long as the school keeps it. Nothing is hard-deleted inside the product: closing an academic year archives it, a student who leaves keeps their history, and a wrong receipt is corrected by a visible reversal. Records the school removes are marked deleted and kept out of view, with their history preserved for audit.
If the school leaves Onflows, it may export everything it put in, and may ask us to delete its data. We carry out the deletion and confirm it in writing within 30 days of the request, keeping only what the law obliges us to keep, such as invoices.
8. Children
Most students whose records a school holds are children. The school obtains the verifiable consent of a parent or lawful guardian that the Act requires before it enters a child's data, and the school is responsible for that consent. Onflows holds no direct relationship with any child, collects nothing from a child for its own purposes, and processes children's data only as the school's processor.
The service does no tracking or behavioural monitoring of children and shows no advertising to anyone.
9. The rights people have and how a request reaches us
A data principal has the right under the Act to know what personal data a fiduciary holds about them, to have it corrected or updated, to have it erased where the purpose has ended, to nominate a person to act for them, and to raise a grievance. These rights are exercised against the school, which holds the data and decides what it is used for.
A parent, student or member of staff who wants to see, correct or erase their data should ask the school, which can act on most requests directly inside the product. If a request reaches us instead, we pass it to the school without delay and help the school answer it. The school may also write to us at hello@onflows.app for help with a request it cannot complete on its own.
10. Breach notification
If we become aware of a personal data breach affecting a school's data, we notify that school without undue delay and in any case within 72 hours, with what we know about the nature of the breach, the records affected, the likely consequences and the steps we have taken. We then help the school meet its own duty to notify the Data Protection Board of India and the affected data principals.
11. Cookies and tracking
The service sets the cookies needed to keep a person signed in and to protect their session. It uses no advertising cookies, and there are no third-party trackers on a school's portal.
12. Changes to this policy
We may change this policy. A material change is notified to the school's administrator by email at least 30 days before it takes effect and the administrator is asked to accept the new version on their next sign-in. Each version carries a number and an effective date, and earlier versions the school accepted remain available in the Legal section of its settings.
13. Contact
Questions about this policy, and requests about personal data, go to hello@onflows.app. A school already using Onflows that needs help with its records writes to care@onflows.app, which reaches the people who can act on it.