gheorg is an AI mental health platform built exclusively for children aged 4–12, co-designed with children, teachers, and school counsellors from day one. We work with school districts and individual schools to embed emotional wellbeing and resilience-building into the school day — giving educators practical tools and giving children a safe, engaging space to develop the skills they need.
gheorg is currently deployed across schools in Australia, and the United States. We are in 78 countries so more will be coming!
What gheorg gives schools
For students Evidence-based CBT and ACT tools delivered through a friendly, age-appropriate AI companion. Children build emotional regulation and coping skills at their own pace — in school and at home.
For teachers and counsellors A school dashboard giving staff visibility of student engagement and wellbeing indicators — so you can identify children who need additional support before issues escalate.
For school leadership Outcomes data and reporting aligned to your wellbeing programme goals. gheorg integrates into your existing pastoral care framework without adding to teacher workload.
Built with schools, validated in schools
gheorg has been co-created with over 1,000 children, parents, and educators. Our anchor institutional contract is with Washington State Schools — outcomes data publishing July 2026, with a US schools conference presentation to follow.
gheorg holds the APA Seal of Acceptance and is the only children's mental health platform with a patented AI safety framework — VERA-MH-P — purpose-built for children aged 4–12.
How schools get started
Getting gheorg into your school is straightforward. We handle platform setup and provide a dedicated customer success contact to support your team through onboarding and activation.
Annual per-student contracts align to school and government education funding cycles.
If you're in the US, Australia, or another English-speaking market and want to explore bringing gheorg to your school or district, get in touch below.
Want to know more?
Talk to our team about Gheorg.
Leave your details below and we will be in touch.
GHEORG FOR SCHOOLS - US ONLY
TERMS OF SERVICE
Institutional Edition — for use by Schools, not individual consumers
Effective Date: 08/14/2026
These Terms of Service (“Terms”) govern access to and use of the school-deployed version of the Gheorg application (the “School Product”) by a School and its Authorized Users and Clinical Contacts. These Terms are separate from, and do not incorporate, Gheorg’s consumer Terms of Service and Privacy Policy that apply to the direct-to-parent version of the Gheorg app.
These Terms are entered into between Gheorg Inc., a Delaware corporation (“Gheorg,” “we,” “us”), and the school, school district, local education agency, or other educational institution identified in the applicable Order Form (“School,” “you”). By signing an Order Form, provisioning Student accounts, or otherwise using the School Product, the School agrees to these Terms.
The School Product is hosted on infrastructure operated by Replit, Inc. and run on Google Cloud Platform in the United States; see Privacy Policy Section 10 for detail.
1. Definitions
● “Authorized User” means School staff, administrators, counselors, or other personnel the School designates to access the School Product.
● “Clinical Contact” means an external clinical or mental health professional or organization the School designates or approves to receive Safety Alerts about specific Students.
● “Clinical Partner” means a third-party organization (e.g., a contracted telehealth or counseling provider) engaged or approved by the School whose personnel act as Clinical Contacts.
● “Institutional Agreement” means the Order Form, master services agreement, grant agreement, or other written agreement between the School and Gheorg that references and incorporates these Terms.
● “Safety Alert” means an automated notification generated when a Student’s Safety Score or another configured indicator meets or falls below a threshold set for that School.
● “Safety Score” means the 0–100 proprietary score Gheorg generates from a Student’s check-in responses, where a lower score indicates higher risk.
● “Student” means a student enrolled at the School whom the School has provisioned to use the School Product.
● “Student Data” means Personal Information about a Student collected, generated, or processed through the School Product, including Check-In Data.
● “Check-In Data” means the responses, inputs, and derived scores a Student provides or generates through the School Product.
2. The School Is the Contracting Party and Provisions Access on Behalf of Students
Unlike Gheorg’s consumer product, the School Product has no individual parent account holder and no individual subscription. The School is Gheorg’s customer. The School, not Gheorg, decides which Students are provisioned, and is responsible for satisfying its own obligations to parents and guardians (including any required notice or opt-out) before doing so.
By provisioning a Student, the School represents and warrants that it has the legal authority to consent to Gheorg’s collection, use, and disclosure of that Student’s data for the purposes described in the Privacy Policy — whether through its own general notice practices, an applicable exception under FERPA, COPPA, or state law, or parental consent it has independently obtained — and that it will provide whatever notice or opt-out its own state law or district policy requires.
Gheorg provides the School Product under the direction and control of the School for the legitimate educational purpose of supporting student safety and wellbeing, and does not use Student Data for any purpose other than the purposes directed by the School and described in the Privacy Policy. See Privacy Policy Section 3 for the legal-basis analysis this rests on.
3. Description of the School Product; Not an Emergency or Clinical Service
The School Product supports structured student emotional check-ins and generates a Safety Score intended to help School staff and, where configured, Clinical Contacts identify Students who may benefit from additional support.
THE SCHOOL PRODUCT IS NOT A CRISIS SERVICE, AN EMERGENCY RESPONSE SYSTEM, OR A SUBSTITUTE FOR PROFESSIONAL MEDICAL OR MENTAL HEALTH CARE. IT DOES NOT CONTINUOUSLY MONITOR STUDENTS AND DOES NOT GUARANTEE DETECTION OF EVERY SAFETY CONCERN. In an emergency, Authorized Users and Clinical Contacts must follow the School’s own crisis protocols and contact emergency services directly; they may not rely on the School Product as a substitute for those protocols.
Gheorg does not independently contact emergency services, Students, or Students’ families. Safety Alerts route only to the Authorized Users and Clinical Contacts the School has configured to receive them.
4. Authorized Users and Clinical Contacts
The School designates which staff are Authorized Users and which individuals or organizations are Clinical Contacts, and is responsible for keeping those rosters current and revoking access promptly when a person’s role changes or ends.
An Authorized User or Clinical Contact who wants to receive Safety Alerts by SMS text message must separately opt in as described in Privacy Policy Section 9. Designation by the School enables in-app and email alerts only; it does not, by itself, enroll anyone in SMS alerts.
5. Clinical Partners
Where the School engages or approves a Clinical Partner to receive Safety Alerts about specific Students, that partner’s personnel are Clinical Contacts and receive only the Student-specific alert information necessary to respond, as described in Privacy Policy Section 7.
Before Gheorg will route Safety Alerts to a Clinical Partner, the School must complete a Clinical Partner Designation, confirming: (a) the Clinical Partner’s name and organization; (b) that the School has vetted the Clinical Partner as suitable to receive Student safety information; and (c) whether the Clinical Partner is a HIPAA-covered entity or business associate. Where the answer to (c) is yes, the School must upload a copy of, or written confirmation of, the executed Business Associate Agreement or equivalent agreement governing the Clinical Partner’s handling of the information it receives. Gheorg maintains its own written confidentiality and minimum-necessary-use commitment directly with each Clinical Partner, separate from and in addition to the School’s own agreement with that partner.
The School remains responsible for the adequacy of its own agreement with any Clinical Partner and for that partner’s further use of the information once received. Gheorg’s role is limited to alert delivery consistent with the Clinical Partner Designation on file.
6. Acceptable Use
The School and its Authorized Users and Clinical Contacts will not: (a) use the School Product for any purpose other than supporting Student safety and wellbeing as contemplated by these Terms; (b) attempt to reidentify de-identified data; (c) attempt to gain unauthorized access to any account, system, or data; (d) reverse engineer, decompile, or attempt to extract the underlying models or scoring logic of the School Product; or (e) use the School Product in a way that violates applicable law or the School’s own code of conduct.
7. Fees, Term, and Order Forms
Pricing, term, and payment terms are set out in the applicable Order Form or Institutional Agreement, which is incorporated into these Terms by reference. In the event of a conflict between an Order Form and these Terms, the Order Form controls solely with respect to pricing and term.
8. Intellectual Property
As between the parties, Gheorg owns the School Product, including its underlying software, scoring methodology, and all improvements, excluding Student Data and other School-provided content. The School retains all rights in Student Data. Gheorg grants the School a non-exclusive, non-transferable right to use the School Product during the term of the Institutional Agreement solely for its own Students and staff.
9. Confidentiality
Each party will protect the other’s confidential information with the same degree of care it uses for its own similarly sensitive information, and not less than a reasonable degree of care. Student Data is governed by the Privacy Policy in addition to this Section.
10. Data Ownership, Return, and Deletion on Termination
As between the School and Gheorg, Student Data and Check-In Data remain the property of the School (and, as applicable, the Student or the Student’s parent/guardian).
On termination or expiration of the Institutional Agreement, Gheorg will, at the School’s direction, return or delete Student Data within 60 days, except data Gheorg is required to retain for legal, safety, or audit purposes as described in the Privacy Policy.
A School may also exercise its standalone deletion right at any time during the term of the Institutional Agreement, including the deletion right available to Washington Schools under the SUPER Act; see Privacy Policy Section 12.
11. Disclaimers; Limitation of Liability; Indemnification
THE SCHOOL PRODUCT IS PROVIDED “AS IS.” EXCEPT AS EXPRESSLY STATED IN THE INSTITUTIONAL AGREEMENT, GHEORG DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING FITNESS FOR A PARTICULAR PURPOSE. GHEORG DOES NOT WARRANT THAT THE SCHOOL PRODUCT WILL DETECT OR PREVENT ANY PARTICULAR SAFETY EVENT.
Gheorg’s aggregate liability, and the School’s aggregate liability, arising out of these Terms will not exceed the amount / fees paid in the preceding 12 months by the School, except for (a) breach of confidentiality or data protection obligations, (b) either party’s indemnification obligations, or (c) liability that cannot be limited by law. Each party will indemnify the other against third-party claims arising from its own breach of these Terms or violation of applicable law.
12. Compliance with Education Privacy Laws
Gheorg will handle Student Data consistent with FERPA (to the extent applicable, via the school-official exception), COPPA (via the school-consent exception), and applicable state student data privacy laws. Gheorg currently serves Schools in Washington and Florida and, for those states, will comply with the Washington Student User Privacy in Education Rights Act (RCW 28A.604 et seq.) and Florida’s student data privacy statutes (Section 1002.222, F.S. and Section 1006.1494, F.S.), as described in Privacy Policy Section 12. As Gheorg onboards Schools in additional states, this Policy and these Terms will be updated to address that state’s requirements before those Schools are onboarded. Where a School’s state or district requires a standardized data privacy agreement (for example, a National Student Privacy Consortium form), Gheorg will negotiate and execute a School-specific rider in good faith.
13. Governing Law; Dispute Resolution
These Terms are governed by the laws of Washington State or Florida depending on the school district we are working with, without regard to conflict-of-laws principles, except where a School’s status as a public entity requires disputes to be resolved under the law and in the forum of the School’s home state, in which case that requirement controls for that School.
14. Changes to These Terms
Gheorg may update these Terms from time to time. Material changes will be communicated to the School with reasonable advance notice before taking effect.
15. Notices; Contact
Notices under these Terms should be sent to support@gheorg.com and, for the School, to the contact designated in the Order Form. For general questions, contact support@gheorg.com
GHEORG FOR SCHOOLS
PRIVACY POLICY
Institutional Edition — applies only to the school-deployed Gheorg product
Effective Date: 08/14/2026
This Privacy Policy describes how Gheorg handles information through the school-deployed version of the Gheorg application (the “School Product”). It applies only to Schools, their Authorized Users, Clinical Contacts, and provisioned Students. It does not apply to Gheorg’s direct-to-consumer product, which is governed by a separate privacy policy available at https://www.gheorg.com/privacy-policy.
1. Who We Are
Gheorg Inc., a Delaware corporation (“Gheorg,” “we,” “us”), is the contracting party with Schools for the School Product and directs the processing described in this Policy.
The School Product runs on infrastructure provided by Replit, Inc., which operates on Google Cloud Platform in the United States. Student Data collected through the School Product is hosted in the United States. See Section 10.
As between Gheorg and a School, the School controls which Students are provisioned and is responsible for its own notice and consent obligations to parents and guardians. Gheorg acts as a school service provider, processing Student Data solely under the School’s direction for the purposes described in Section 3 and Section 5.
2. Scope
This Policy applies to: (a) Students a School has provisioned to use the School Product; (b) School staff and administrators designated as Authorized Users; and (c) Clinical Contacts, including personnel of any Clinical Partner the School has approved to receive Safety Alerts. It does not apply to individuals using Gheorg’s consumer product independently of a School.
3. Our Legal Basis for Processing Student Data Without Individual Parental Consent
3.1 FERPA — School Official Exception
Where a School is subject to the Family Educational Rights and Privacy Act (FERPA), it may disclose personally identifiable information from Students’ education records to Gheorg without individual parental consent under FERPA’s school-official exception (34 C.F.R. § 99.31(a)(1)), because Gheorg: (a) performs an institutional service the School would otherwise perform itself; (b) is under the direct control of the School with respect to the use and maintenance of Student Data; (c) is subject to FERPA’s limitations on use and redisclosure of information from education records; and (d) uses Student Data only for the purposes for which the disclosure was made. Gheorg agrees to each of these conditions.
3.2 COPPA — School-Consent Exception
For Students under 13, the Children’s Online Privacy Protection Act (COPPA) generally requires verifiable parental consent before collecting personal information from a child, but the FTC permits a school to consent on parents’ behalf where the service is used for a school-authorized educational purpose and the school-collected data is not used or disclosed for any other commercial purpose. Gheorg relies on this exception and does not use Student Data collected through the School Product for advertising, marketing, or to build behavioral profiles unrelated to the School Product.
3.3 State Student Privacy Laws
Independent of the bases above, state student-privacy laws — including Washington’s Student User Privacy in Education Rights Act (SUPER Act, RCW 28A.604 et seq.) and comparable laws such as California’s Student Online Personal Information Protection Act (SOPIPA) — prohibit vendors like Gheorg from selling Student Data, using it for targeted advertising, or building a commercial profile of a Student. Gheorg does not engage in any of these practices, in any state. See Section 12 for state-specific detail.
3.4 The School’s Own Notice Obligations
Nothing in this section relieves the School of its own obligation to provide parents and guardians notice, and where required, an opportunity to opt out, under the School’s own policies and applicable law. The School is responsible for that notice; Gheorg is not a substitute for it.
4. Information We Collect
4.1 From Students, through the School Product
First name or display name (or a School-assigned identifier), grade level or School-assigned grouping, check-in responses, derived Safety Scores, and general usage and device data. Gheorg does not require and does not knowingly collect a Student’s home address, government identification number, or financial information through the School Product.
4.2 From the School
Roster data needed to provision accounts (name, grade, School-assigned ID) and contact details for Authorized Users and Clinical Contacts the School designates (name, work email, work mobile number where SMS is enabled).
4.3 From Authorized Users and Clinical Contacts directly
SMS opt-in confirmation and alert acknowledgment or response data, where applicable.
5. How We Use Information
● To operate the School Product and generate Safety Scores from Student check-ins.
● To route Safety Alerts to the Authorized Users and Clinical Contacts the School has configured to receive them.
● To maintain, secure, support, and troubleshoot the School Product.
● To evaluate and improve the School Product’s safety-detection performance, using de-identified or aggregated data that cannot reasonably be used to identify a Student; Gheorg does not attempt to re-identify this data.
● To comply with legal obligations and respond to lawful requests.
Gheorg does not sell Student Data, does not use it for targeted advertising, and does not build a commercial profile of any Student. This commitment applies regardless of jurisdiction.
6. The Harm-Alert Pipeline: How Check-In Data Is Handled
6.1 Generation
When a Student completes a check-in, the School Product computes a Safety Score (0–100, where a lower score indicates higher risk) from the Student’s responses.
6.2 Threshold trigger
If a Score meets or falls below the threshold the School has configured, the pipeline generates a Safety Alert. A Safety Alert contains only: the Student’s name, the School, and the risk band that triggered the alert (Amber, Red, or Critical). It does not include the Student’s underlying check-in responses, free-text answers, or full Safety Score history. A recipient who needs more context than the band-level alert provides must access it through the School Product’s in-app dashboard, which applies the access controls described in Section 6.4, rather than receiving it directly in the alert itself.
6.3 Routing
The Safety Alert is delivered to the Authorized Users and Clinical Contacts the School has configured to receive alerts for that Student’s School, grade, or cohort, by in-app notification, email, or SMS. SMS delivery occurs only to recipients who have separately opted in under Section 9.
6.4 Access controls
Only the Authorized Users and Clinical Contacts the School has designated can view a given Student’s underlying check-in responses. Gheorg personnel access to Check-In Data is limited to engineering and support staff, under confidentiality obligations, on a need-to-know basis, for troubleshooting and safety-model maintenance.
6.5 Retention of Check-In Data and Safety Scores
Gheorg’s proposed default is to retain raw Check-In Data and Safety Scores for the duration of the Student’s enrolment in the School Product plus 60 days, after which the data is deleted or de-identified — unless the School directs a different schedule, a longer period is needed to respond to an active safety concern or legal hold, or the School exercises a deletion right under Section 12.
6.6 Alert records
Records that an alert was generated and delivered, and to whom, may be retained for a longer period than the underlying Check-In Data for audit and safety-accountability purposes, consistent with the School’s own recordkeeping obligations.
6.7 Security
Check-In Data is encrypted in transit and at rest, and access to it is logged. See Section 13.
7. Sharing With External Clinical Partners
Where the School approves a Clinical Partner to receive Safety Alerts about specific Students, Gheorg discloses only the alert-level information described in Section 6.2 (Student name, School, and risk band) — not the Student’s full check-in history, unless the School specifically authorizes broader access.
Before any Clinical Partner receives Safety Alerts, the School completes a Clinical Partner Designation confirming the partner’s identity, that the School has vetted the partner, and whether the partner is a HIPAA-covered entity or business associate. Where it is, the School provides Gheorg with confirmation of the Business Associate Agreement or equivalent agreement governing that partner’s handling of the information, as described in the Terms of Service. Gheorg separately requires each Clinical Partner to agree, in writing, to use the information it receives only to respond to the specific Student safety concern for which it was disclosed, and to maintain confidentiality and security protections at least as protective as this Policy.
Gheorg is not a party to, and does not control, a Clinical Partner’s own treatment records or its further use of information once received; the School’s own agreement with the Clinical Partner governs that relationship.
8. Other Sharing
Gheorg shares information with: service providers and subprocessors who support hosting, SMS delivery (via Twilio), and analytics limited to de-identified data, all under confidentiality and data-protection obligations; recipients where required by law, such as in response to a subpoena or court order, or where necessary to address an imminent safety risk to a Student consistent with mandatory-reporting obligations that School staff or Gheorg personnel may have under applicable state law; and, with notice to the School, a successor in a corporate transaction. Gheorg never sells Student Data.
9. SMS Text Message Communications to Staff and Clinical Contacts
This section applies only to Authorized Users and Clinical Contacts who choose to receive Safety Alerts by SMS. Students never send or receive SMS messages through the School Product.
9.1 Opt-in
When you are added as a notification contact for a School using Gheorg at School, you are asked to review and accept the following consent as part of account activation, before any text messages are sent to you:
“By signing this agreement, you consent to receive automated text message alerts from Gheorg when a student check-in indicates a possible safety concern requiring your attention. Message frequency varies and is triggered only by actual safety alerts, not on a fixed schedule. Message and data rates may apply depending on your mobile carrier plan. Reply HELP for assistance or STOP at any time to stop receiving text alerts.”
You must affirmatively check a box confirming “I have read and agree to receive automated text message safety alerts as described above. I understand I can reply STOP at any time to opt out” before your account is activated. Consent to receive SMS is not a condition of using the School Product; Authorized Users and Clinical Contacts who decline SMS can still receive alerts by email or in-app, where the School has configured those channels for their role.
9.2 Message frequency
Message frequency varies and is triggered only by actual Safety Alerts, not on a fixed schedule; you may receive no messages in a quiet period or several in a single day during an active safety concern.
9.3 Message and data rates
Message and data rates may apply depending on your mobile carrier plan.
9.4 Opt-out
Reply STOP at any time to stop receiving text alerts. Reply HELP for assistance, or contact school.team@gheorg.com. You may still receive Safety Alerts by email or in-app if your School has configured those channels for your role.
9.5 Carrier liability
Carriers are not liable for delayed or undelivered messages.
9.6 No sharing for marketing
Gheorg does not share your mobile number or SMS opt-in status with third parties for their own marketing or promotional purposes. This consent extends only to the Gheorg communications described in this Section.
10. Hosting and Data Location
Student Data collected through the School Product is hosted on infrastructure provided by Replit, Inc., which operates on Google Cloud Platform in the United States. Gheorg does not currently store or process Student Data outside the United States.
Replit acts as a subprocessor to Gheorg under a Data Processing Agreement. Replit's current list of its own subprocessors is available at replit.com/subprocessors, and its security and compliance information (including SOC 2 status) is available at replit.com/security. Gheorg reviews this information as part of its vendor oversight of Replit and will notify Schools of material changes to Gheorg's subprocessors consistent with the Institutional Agreement.
11. Data Retention (General)
Rosters and Authorized User / Clinical Contact contact data are retained for the duration of the Institutional Agreement plus 60 days, then deleted, except as needed to comply with law or resolve an active dispute. Retention of Check-In Data and Safety Scores is addressed in Section 6.5–6.6.
12. State-Specific Disclosures
12.1 Washington — Student User Privacy in Education Rights Act (SUPER Act, RCW 28A.604)
● Gheorg does not sell Student Data.
● Gheorg does not use Student Data for targeted advertising.
● Gheorg does not build a commercial profile of any Student, except in furtherance of the School Product’s safety-support purpose and at the School’s direction.
● Deletion right: a Washington School may request deletion of Student personal information at any time. Gheorg will delete the requested data within a reasonable time of a verified request from the School (target: 30 days), except data Gheorg is required by law to retain or that has already been de-identified.
● Gheorg maintains a comprehensive information security program consistent with RCW 28A.604.040.
● Material changes to this Policy affecting Washington Schools will be preceded by prominent notice, as required by law.
This deletion right is currently the only jurisdiction-specific, standalone deletion mechanism described in this Policy; it does not exist in the same form in Gheorg’s consumer privacy policy, where deletion is handled under general account-deletion practices rather than a statutory school-initiated right.
12.2 Florida — Section 1002.222 and Section 1006.1494, Florida Statutes
● Gheorg does not collect, obtain, or retain a Student's (or a Student's parent's or sibling's) political affiliation, voting history, religious affiliation, or biometric information.
● Gheorg does not sell Student Data and does not use it for targeted advertising.
● Gheorg discloses only the Personal Information necessary for the School Product to a Clinical Partner or other third party, consistent with Section 6 and Section 7 of this Policy.
● Deletion right: Gheorg will delete a Student's personal information upon a School's request, or within 90 days of a Student leaving the School, unless the Student's parent or guardian consents to Gheorg retaining the information.
Gheorg currently serves Schools in Washington and Florida. This Policy addresses those two states in detail because those are the states where Gheorg operates today; it does not represent that Gheorg has reviewed or currently complies with every other state's student-privacy statute. The platform-wide commitments in Sections 5, 6, and 8 (no sale, no targeted advertising, no non-educational profiling) apply regardless of state, but the state-specific mechanisms in this Section 12 will be extended state by state, with the same level of detail as Sections 12.1 and 12.2, as Gheorg onboards Schools in new states — not published in advance of that review.
13. Data Security
Gheorg encrypts Student Data in transit and at rest, enforces access controls on a least-privilege basis, and logs access to Check-In Data. Gheorg uses Vanta and regular penetration testing. In the event of a security incident affecting Student Data, Gheorg will notify the affected School in accordance with the Institutional Agreement and applicable state breach-notification law.
14. Children's Privacy
See Section 3.2 for how Gheorg handles Students under 13 under COPPA’s school-consent exception. A parent or guardian who wants to review or request deletion of their child’s information should generally contact the School first, since the School controls enrolment and consent; Gheorg will support the School in fulfilling verified requests.
15. School and Parent/Student Rights
A School may request access to, correction of, or deletion of the Student Data it has provisioned at any time, including the Washington-specific right described in Section 12.1. Gheorg’s general practice is to honor a verified deletion request from any School within 30 days.
Parents and students should generally direct requests regarding a Student’s data to the School first; Gheorg will support the School in responding to verified requests.
16. Changes to This Policy
Gheorg may update this Policy from time to time. Material changes affecting Washington Schools will be preceded by prominent notice as described in Section 12.1. Other material changes will be posted with an updated effective date, and, where required by the Institutional Agreement, communicated to the School directly.
17. Contact
Questions about this Policy, or requests relating to Student Data, can be directed to school.team@gheorg.com