Student Privacy

Family information stays safe, private and in the school's control.

Relay is built for school-to-home communication, and nothing else. Here's what we collect, how we protect it, and how Relay helps your school and district meet the rules you follow. Everything your IT team needs is on this page or a request away.

Last updated November 10, 2026

Minimal dataParent name, phone and language, student name(s), and the messages. No grades, attendance, health or other records.
Never soldNo advertising, no selling or renting data, no profiles of students.
School-controlledEach school's admins manage their own Parents list. Data is deleted on request or when a contract ends.
Plain textsParents get ordinary text messages. No app, no account, and teachers' own numbers are never shared.

The rules schools follow, and how Relay helps

Schools stay responsible for following these rules. Relay is designed so that using it supports them rather than creating new work.

How we protect it

EncryptedAll traffic uses HTTPS (browsers are told to always use it), and the database is encrypted at rest.
Signed-in access onlyStaff sign in with their own password (new passwords need 12+ characters). Two-step sign-in with an authenticator app is available for every account.
Least accessTeachers see their own school's parents and their own conversations. School and district admins see only the schools they oversee, and only admins can change the Parents list. This is enforced on our servers, not just hidden on screen.
Activity LogViewing another teacher's inbox, moving or deleting conversations, Parents list changes and account changes are all recorded, with who and when.
Abuse protectionSign-in, sign-up and the parent sign-up form are rate-limited. Sign-out, password resets and turning off an account end that person's sessions on every device.
Locked-down databaseRow-level security is on for every table, and service keys stay on our servers, never in the browser.
Private teacher numbersTexts go out from a Relay number, so teachers' personal cell numbers are never exposed.
Checked codeEvery change is type-checked before it deploys, with exact package versions and automatic checks for known vulnerabilities.

If something goes wrong

We keep a written incident response plan. If family or student information may have been exposed, we contain it first, preserve the evidence, and notify the affected district in writing within 24 hours of learning of it, or sooner if the contract requires. The district hears first: we don't notify families or regulators before the district unless the law requires it. Within 7 days we send a written report of what happened, what was involved, the cause and what we've changed, and we help the district with anything it sends to families.

For your IT and privacy team

Email relay@stellomark.com for any of these:

Data privacy agreementWe'll sign your district's agreement or the national model agreement with your state's terms.
Security questionnaireSend us your district's vetting questionnaire; we answer quickly.
Service provider listThe providers we use to run Relay, shared with your district under a signed agreement.
Incident response summaryHow we detect, contain and report a security incident.
Message history exportAdmins can download a conversation or a school's messages themselves; we can also send one for a records request or district review.
Written deletion confirmationSpecific records within 5 business days of a request; everything within 30 days of a contract ending, confirmed in writing.
Records requestsCopies of data we hold within 2 business days of a district's open-records request or legal demand.

Relay doesn't claim to be "FERPA certified": no such certification exists. Each district decides whether a service meets its policies, and we'll give your reviewers whatever they need to decide. This page isn't legal advice.

Student Data Disclosure

This section explains, in plain language, what information about students and families Relay collects, why we collect it, how we use and share it, and how it is protected and deleted. It is written for parents, school staff and district reviewers, and supports schools’ obligations under laws such as the Family Educational Rights and Privacy Act (FERPA) and Colorado’s Student Data Transparency and Security Act (C.R.S. 22-16-101 et seq.).

Information we collect, and why

For school staff, we also keep each person’s name, work email, school, role and last sign-in, so they can sign in and administrators can manage accounts.

Students don’t use Relay. Texts go to parents and guardians, and we don’t collect information directly from children.

How we use it

  • To send and receive texts between school staff and families, translated into each family’s language.
  • To record consent and honor opt-out requests.
  • To show school administrators totals about their own school’s outreach, such as how many families were contacted.
  • To keep the service secure, working and supported.

We use student and family information only for these purposes and only as our agreement with the school allows. If we ever needed to use it another way, we would first get permission as the law requires. We don’t build profiles of students or families, and we don’t use de-identified or combined data for any other purpose without the district’s written consent; we never try to re-identify it.

Who we share it with

We share information only with the kinds of service providers below, only as needed to run Relay, and under agreements that limit their use of it to providing services to us. We don’t share it with anyone else, except where the law requires it or to protect the safety of a student, family or staff member.

Districts receive the names of these providers, and their data protection terms, as part of a signed data privacy agreement. Each provider is bound by a written agreement that limits its use to running Relay and bars marketing to students or families. We give contracted districts written notice before we add or change a provider that handles student or family information, and a district can object before the change applies to its data.

Where it is stored

Relay’s database and app are hosted in the United States. Message text is sent to our translation provider only to translate it. We will tell any district in writing, before it signs, where its data is stored and processed, and we won’t move stored data outside the United States without the district’s advance written agreement.

Legal and records requests

  • If we receive a subpoena or other legal demand for a district’s data, we tell the district right away (unless the law forbids it) and work with it before responding.
  • When a district receives an open-records (CORA) request or legal demand for data we hold, we provide copies within 2 business days. District admins can also export conversations themselves at any time.
  • We make any of a district’s data available to it within 7 days of a written request.

Correcting information

School administrators can correct a family’s details at any time on the Parents list, and the change carries into existing conversations. Parents can ask their child’s school to correct their information. We will also help any contracted school or district find and correct information within 10 days of a request: email relay@stellomark.com. If a parent contacts us directly, we tell their school promptly and help within the same 10 days.

Keeping and deleting it

  • Text messages are deleted automatically after 2 years, or after the period set in the school’s or district’s contract. Parent details stay on the Parents list while the school uses Relay.
  • If a parent replied STOP, we keep only their phone number and the opt-out, so they are never texted again.
  • When a district asks us to delete or return specific information, we do it within 5 business days.
  • When a school or district asks, or its contract ends, we securely delete all of its student and family information within 30 days (or transfer it to a provider the district names first), unless its contract says otherwise, and confirm in writing. Secure deletion follows NIST SP 800-88.
  • Backup copies kept by our database provider and delivery logs kept by our texting provider are removed on those providers’ own schedules; they are not used for anything else in the meantime.
  • A parent can reply STOP at any time to stop receiving texts.

Changes to this page

We will tell contracted schools and districts about any material change to how we collect, use or share student information before it takes effect, and update the date on this page.

Questions from your district?

We'll answer your IT team directly, sign your data privacy agreement, and help you plan a pilot.