Umbra Privacy Policy

Last updated: November 11, 2026

1. Introduction

Umbra Safety, Inc. ("Umbra," "we," "us," or "our") provides a text message (SMS) and QR code reporting platform. It lets students, employees, and others report concerns and answer surveys, and gives school and organization staff ("Administrators") tools to review, triage, and respond. This Privacy Policy explains what information we collect, how we use it, who can see it, and when it may be disclosed.

This Policy applies to:

People who submit a report or survey response through Umbra ("Reporters")
School, district, athletics, or organization staff who use the Umbra dashboard ("Administrators")
Visitors to goumbra.com

If your school or organization has a signed agreement with Umbra (a "Client"), that agreement and any Data Processing Agreement govern how your organization's data is handled. This Policy supplements those terms and does not replace them. Your school or organization can tell you how they have set up Umbra and how they respond to reports.

2. Anonymity: what it means and what it doesn't

Reporters do not need to create an account, log in, or give their name to submit a report or survey response. We describe this as anonymous to your school or organization. It is not absolute or unconditional anonymity, and we want to be direct about the difference:

Administrators see the content of a report. They do not see the Reporter's phone number, and they do not see the Reporter's name unless the Reporter includes it in their message.
We store the originating phone number in encrypted form so we can keep a conversation going and prevent abuse.
In the limited circumstances described in Section 5, Umbra may access or disclose information that could identify a Reporter.
Your wireless carrier and our messaging provider process your phone number and message details to deliver texts, as with any text message.
A Reporter can also be identified by details they include in a message, or by the circumstances a report describes.

3. Information we collect

From Reporters:

The content of messages, reports, and survey responses
The originating phone number, stored encrypted, for conversation threading and abuse prevention
Timestamps, and the QR code or link used to start the conversation, where applicable

We do not require a name, email address, student or employee ID, or login to submit a report.

From Administrators:

Name, work email, role, and organization
Login and session activity in the dashboard
Actions taken in the platform, such as viewing, assigning, replying to, or archiving a report, which are recorded in our audit log

From website visitors:

Standard server and security logs, such as IP address, browser type, and pages requested

From Clients:

Organization name, account type, and configuration settings
Billing and contact information for the account

4. How we use information

We use this information to:

Operate the reporting and survey platform
Route reports to the right Administrators at the Reporter's school or organization
Generate AI-assisted urgency scoring, categorization, summaries, and suggested replies to help Administrators triage reports (see Section 8)
Detect trends in report volume for each Client
Keep a security and compliance audit trail
Provide support to Clients
Improve the platform, using aggregated or de-identified data wherever possible

We do not sell personal information. We do not use report content for advertising, and we do not share report content with third parties for their own marketing.

5. When identifying information may be accessed or disclosed

We limit access to information that could identify a Reporter. We may access or disclose it only:

Legal process. To comply with a valid subpoena, warrant, court order, or other legal process.
Imminent safety concerns. When we believe in good faith that it is necessary to prevent serious physical harm to the Reporter or another identifiable person.
Abuse of the platform. To investigate suspected violations of our Terms of Service, such as abuse of the reporting system.
Protecting rights and safety. Where otherwise necessary to protect the rights, property, or safety of Umbra, our Clients, or others.

These circumstances are not a basis for routine identity disclosure to Administrators.

If Umbra is involved in a merger, acquisition, financing, or sale of assets, information may be transferred to a successor, subject to this Policy and appropriate safeguards.

6. How we handle disclosure requests

When a request or safety circumstance under Section 5 may require accessing identifying information:

Access is limited to a restricted Umbra disclosure workflow that standard Administrators cannot use.
Each request, the basis for it, and what was disclosed are recorded in our audit log.
Where the law allows, we make reasonable efforts to notify the affected school or organization.
We push back on requests that are overbroad, improperly served, or not legally valid.

7. What Administrators can see

Administrators can see:

The content of reports and survey responses submitted to their organization
AI-generated urgency scores, categories, summaries, and suggested replies for those reports
Trend data across their organization's reports

Administrators cannot see a Reporter's phone number through the dashboard. Replies Administrators send reach the Reporter from the organization's Umbra number, not from a staff member's personal number.

8. AI processing

We use AI models, including models provided by Anthropic, to classify reports, score urgency, summarize reports, and draft suggested replies. Report content is sent to these providers for that purpose. Under our provider's commercial terms, report content is not used to train their models, and Umbra does not use report content to train AI models.

AI outputs can be incomplete or wrong. They help Administrators prioritize and are not findings of fact. Suggested replies are drafts, and Administrators decide what is sent and what action to take.

9. Data retention

We keep report data while a Client's account is active and as needed for the purposes in this Policy, subject to the Client's instructions and applicable law. Clients may ask us to delete specific records, subject to legal holds. Some records, including entries in our audit log, are kept for security and compliance even if the underlying report is later archived or deleted.

10. Students, children, and FERPA

Umbra is used in middle school, high school, and higher education settings. The Service is not directed to children under 13. A school that lets students under 13 use Umbra is responsible for providing any required notices and obtaining any required parent or guardian consent. For school and district Clients, our agreements address our role under the Family Educational Rights and Privacy Act (FERPA).

11. Data security

We encrypt data in transit, and we encrypt Reporter phone numbers at rest using AES-256-GCM. Access to identifying information is limited to authorized personnel and logged in a tamper-evident audit log. No system is completely secure, and we cannot guarantee absolute security.

12. Service providers

We use these providers to operate Umbra:

SMS delivery: Twilio
Database and infrastructure: Supabase (hosted on Amazon Web Services) and Upstash
Authentication: WorkOS
AI processing: Anthropic
Hosting: Vercel
Security and bot protection: Cloudflare

These providers process data on our behalf and are contractually restricted from using it for their own purposes.

13. Text messaging

Umbra sends text messages only in response to a conversation a Reporter starts, or for surveys a Reporter chooses to answer. Message and data rates may apply. Message frequency varies. Reply STOP at any time to stop receiving messages, or HELP for help.

No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent will not be shared with any third parties, except service providers that deliver the messages.

14. Umbra is not an emergency service

Umbra is not monitored around the clock and does not provide emergency response. If someone is in immediate danger, call 911 or your local emergency number.

15. Your choices and requests

Because reports are submitted without an account, Reporters generally cannot access, correct, or delete a specific past report directly through Umbra. Please direct these requests to your school or organization, which controls its Umbra data. Administrators and Clients can contact us directly.

16. Changes to this Policy

We may update this Policy. If we make material changes, we will update the date above and, where required, notify Clients directly.

17. Contact us

Questions about this Policy: support@goumbra.com

Umbra Safety, Inc., Charleston, South Carolina