The record belongs to the school.

ALOE is school-safety and student-wellbeing software operated by Alotech LLC. This policy covers the ALOE application, this website, and the demos we run for prospective schools.

When a school uses ALOE, the school stays the owner and the controller of its student records. ALOE processes that information on the school's behalf and under its direction, in the role FERPA describes as a school official with a legitimate educational interest.

Student information the school chooses to put in: roster details, attendance, behavior and incident records, health and wellness notes, check-ins, referrals, and the school-climate signals the school's own staff enter.

Staff account information: name, work email, role, and the record of actions taken in the app, so a school can always see who logged what and when.

Basic technical information needed to run the service securely, such as sign-in events and error logs.

ALOE does not ask for, and schools should not enter, information the school does not already have a legitimate educational reason to keep.

To provide the service the school is paying for: showing the right records to the right staff, surfacing patterns and early warnings, and producing the reports the school asks for.

To support the school when its team asks us for help, and to keep the service secure and working.

That is the whole list. ALOE does not sell student data. ALOE does not share it with advertisers, does not use it to target advertising, and does not build advertising or marketing profiles of students or families.

ALOE does not use student records to train machine-learning models for other customers.

Access inside ALOE is scoped by role. A custodian, a nurse, a counselor, a teacher, and a principal each see the part of the record their job requires, and the school's administrators control those roles.

On the ALOE side, access to a school's data is limited to the people who need it to run or support the service, and it is used only to operate the product or respond to a request from the school.

At the school's direction. If a school exports a report or shares a record, that is the school's call to make.

To the vendors that run the service infrastructure, such as hosting and database providers, under contracts that limit them to processing data for ALOE and nothing else.

When the law requires it. If we receive a lawful request for a school's records, our practice is to notify the school unless we are legally prohibited from doing so, so the school can respond.

Never for money. We do not sell, rent, or trade student information.

All traffic between your school and ALOE runs over encrypted connections.

Accounts are individual, permissions are role-based, and sensitive actions are recorded so a school can audit who did what.

We are an early-stage company and we will tell you plainly where we are: ALOE does not currently hold a SOC 2 or ISO 27001 certification. If your district requires one, tell us during procurement and we will be straight with you about our timeline rather than implying we already have it.

If a breach affects a school's data, our practice is to notify that school promptly with what we know, what we are doing, and what they need to do.

A school can export its data at any time while the agreement is active.

When a school ends its relationship with ALOE, we return or delete its data on request. There are no clauses that hold a school's records hostage.

Requests from parents or students about a specific child's record go to the school, not to ALOE. The school owns the record and controls access to it, and we support the school in responding.

ALOE is provided to schools, not directly to children or families. Where a school uses ALOE with students under 13, the school provides the consent required under COPPA on behalf of parents, in the same way it does for other classroom software.

ALOE collects information from students only through the school and only for the educational and safety purposes the school directs.

Many districts require a signed student-data-privacy agreement, a state-specific addendum, or a standard framework document before a contract starts. We expect that and we will sign the paperwork your district uses.

Send it to privacy@aloetech.io and we will work through it with your team.

If this policy changes in a way that materially affects how a school's data is handled, we will notify the schools using ALOE rather than quietly changing the page.