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
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.
| Rule | What it asks | How Relay supports it |
|---|---|---|
| FERPA (federal) | Student information shared with a vendor is used only for the school's purposes, under the school's control. | Relay uses family information only to carry school-to-home conversations, under the school's agreement. Admins control the Parents list; access is limited by role and school. |
| Colorado Student Data Transparency and Security Act | A contract with required privacy terms; a plain-language list of the data a vendor collects; correction; data destruction; breach notice. | We sign the district's data privacy agreement. Our Student Data Disclosure lists every data element, why we collect it and who we share it with. |
| Texting rules (TCPA and carrier rules) | Parents' consent for non-emergency texts, a clear way to opt out, and honoring it. | Parents opt in on their district's sign-up page, or an admin confirms consent the district collected. Relay records who, when and how. STOP and HELP work on every text, in every language. |
| Colorado breach notice (government entities) | Vendors that hold data for a district notify it and cooperate if there's a breach; the district then has 30 days to notify residents. | We notify the district in writing within 24 hours of learning of a breach, before anyone else, and send a written report within 7 days. |
| Open records and retention (CORA, district schedules) | Texts about school business may be public records, kept for the district's retention period. | Each school sets how long messages are kept (2 years by default, or the contract's period). Admins can export a conversation or a school's full message history as a spreadsheet at any time. |
| Accessibility (ADA Title II) | District websites and apps meet WCAG 2.1 Level AA. | We test the parent sign-up page and the public pages against WCAG 2.1 AA with automated checks, and fix what they find. If anything is hard to use, email relay@stellomark.com and we'll help right away. |
| Language access | Schools communicate meaningfully with parents who speak other languages. | Every text is translated into the family's language, and replies are translated back for the teacher. |
How we protect it
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:
Read: Student Data Disclosure · Privacy Policy · Terms & Conditions
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
| Information | Why we collect it | Where it comes from |
|---|---|---|
| Parent or guardian name | So teachers know who they are texting. | The school (Parents list or upload), or the parent when signing up |
| Student name(s) | So teachers know which child a conversation is about. | The school, or the parent when signing up |
| Parent mobile phone number | To deliver texts to the parent and match their replies to the right conversation. | The school, or the parent when signing up |
| Preferred language | To translate messages into the family’s language. | The school, or the parent when signing up |
| School | So only staff at the student’s school can see the family. | The school |
| Text messages, in English and in the family’s language | To carry the conversation and show staff exactly what the parent received and replied. | Teachers and parents, as they text |
| Delivery status and timestamps | To show whether a text arrived, and to troubleshoot delivery problems. | Created by the service |
| Texting consent and opt-out (STOP) status | To text only families who agreed, and to honor opt-outs. We record when consent was given, how, and which administrator confirmed it. | The school, the parent, or the parent’s STOP / START reply |
| Message topic and tone counts | To show administrators overall trends (for example, how many replies are about attendance). Worked out from message text by simple word rules when the dashboard loads; not stored, and not used to profile anyone. | Created by the service |
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.
| Service | Information involved |
|---|---|
| Text-message delivery | Parent phone numbers and the text of messages sent and received |
| Translation | The text of each message only (no names attached by us, and no phone numbers) |
| Database and staff sign-in | All of the information listed above, and staff account details |
| Website and app hosting | Information passing through the Relay website and app as people use it |
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.
