BullyAlert Privacy Policy

Effective date: October 13, 2026
Operator: Sentinel Beacon Labs, Corp.
Mailing address: Sentinel Beacon Labs, Corp., PO Box 25472, San Mateo, CA 94402
Telephone: 939-299-5611
Privacy inquiries and data requests: privacy@bullyalert.app
General inquiries: jrod@bullyalert.app

1. What this policy covers

BullyAlert helps students and families share school-safety concerns and helps authorized school staff review and follow up. This policy covers the BullyAlert website, Student and Parent/Caregiver reporting experiences, Staff portal, and supported BullyAlert mobile experiences. Available features depend on the school, device and release. It does not represent every feature as available to every user.

Schools may direct our handling of school records under an applicable agreement and law. The public website and business-contact activities are distinct from school-directed reporting. Ask your school or our privacy contact which arrangements apply. Mandatory privacy rights are not waived by a school agreement or by using BullyAlert.

2. Information we collect and why

Reports and school response. We process the incident location selected by the reporter, their account of the concern, submission time, report status, and optional permitted evidence. Where available, a reporter can voluntarily give a name for that report. Staff review notes, follow-up records and authorized exports support the school's response. Reports, free text and pictures can contain personal information about the reporter or other people even if no name field is completed. Please include only information reasonably needed to explain the concern.

Access and session information. We process the access information needed to establish the session, the server-validated role, school and grade scope, and technical actor/session references. Routine Student reporting does not require a student name, school email, student ID or roster account. Technical references used to protect sessions, keep permitted history or prevent duplicate operations are not a promise that no personal information is processed. Do not share your school access credentials.

Notifications and Location Checks. If notifications are enabled for an authorized experience and you opt in, we process a device push token or browser subscription, consent/registration and session-binding information, and delivery/retry/receipt records. These let us route generic alerts, manage changes in authorization and diagnose delivery. Location Checks use a school location and a student's selected observation; they are not a request to confront anyone. A Location Check is not continuous GPS tracking. This policy does not authorize collection of precise device location without a separate applicable notice and permission.

Learning. Available lessons process module and content-version references, authorized role/scope, progress, submitted practice decisions or self-checks, feedback and completion records. This supports lesson delivery and permitted resume. Staff completion is a record of participation in the authored learning activity, not professional certification, proof of misconduct, or a judgment about a real student's safety. Do not put real incident details into a training exercise.

Optional voice or media features. Availability depends on the experience and release. A microphone, image or other media feature, if offered, is subject to the applicable notice and device permission. Recordings, transcripts and photographs can contain personal information. The Staff Year 1 lesson reader does not require a microphone or provide recorded narration. This policy does not represent voice or AI processing as enabled on every platform, and does not state that recordings or transcripts are universally unrecorded or immediately deleted.

Website use and inquiries. Hosting and security services process technical request information such as IP address, browser/device information, request time and security events. Website measurement may process page-use information. When you email us or book a school conversation, we receive the contact information and message or appointment information you choose to provide. Marketing email is not the protected incident-reporting channel; do not send student reports, access codes or sensitive evidence there.

3. Anonymous by default is not absolute anonymity

Anonymous-by-default means that routine Student reporting does not ask the student to identify themselves. It does not mean the service processes no technical identifiers or that a report can never contain identifying information.

An optional name supplied for one report is handled in permitted incident details, not general feeds or generic notifications. Free text or evidence may identify someone independently of that field. A report-specific name choice does not by itself identify the student's broader activity.

School-managed devices, networks, browser history, downloaded documents and legal processes are outside the reporting interface. We cannot promise invisibility to a school device administrator or to a lawful process. Avoid unnecessary names and identifying details, and sign out when using a shared device.

4. Who can receive information

Authorized school personnel. Access follows the role and school/grade or other scope authorized by the service. Staff do not receive an unrestricted cross-school directory. Student and Parent/Caregiver experiences remain separate: a family session does not grant access to other families' reports or a child's anonymous history. A verified statutory records request is handled separately; it is not a reason to turn a family login into a Staff account.

Service providers. Providers may process information for hosting, protected storage, security, delivery, communications or specifically enabled media features. Current notification pathways may use Expo, Apple Push Notification service, Firebase Cloud Messaging and browser push services. Cloudflare provides website/edge hosting and security; the website may include its measurement and security scripts. Clicking the Calendly booking link sends you to an external service with its own privacy practices.

Generic notifications may include a route reference needed to open the protected application, along with technical delivery information. They do not intentionally include incident narratives, optional reporter names or evidence. Protected details are authorized again in the application. Disabling notifications does not remove previously delivered notifications from a device or delete school records.

Legal obligations and safeguarding. We may disclose information when legally required or where law permits a necessary disclosure to protect people, the service or legal rights. School personnel may have independent safeguarding and reporting obligations. We do not promise secrecy that would override a lawful duty. Requests and disclosures must be limited to what is permitted and necessary.

5. Limits on secondary use

We will not sell school-user personal information, rent it to advertisers, use school information for targeted advertising, or build unrelated commercial profiles about students. We will not use private reports, evidence or identifiable learning activity to train general-purpose AI models or for public marketing. Providers handling school information must be restricted to the agreed service purpose and applicable lawful disclosures.

6. Children and school authorization

BullyAlert is intended for K–12 school use and may be used by children under 13. We do not claim that children’s-privacy requirements disappear because routine reporting is anonymous by default. Technical identifiers, optional names, report content, photographs or voice can be personal information.

Where applicable law permits school authorization for a school-directed educational purpose, the operator must provide the required notice and establish the required authorization before collecting the covered information. School authorization does not permit unrelated commercial use. Where school authorization cannot lawfully be used, the required parent or guardian consent must be obtained through an appropriate process. Merely entering a school code or clicking “I agree” is not proof that this process has occurred. The operator remains responsible for its own duties.

A parent or guardian can contact our privacy team to request review or deletion of their child's information or to stop further collection or use, subject to verification and applicable law. A school can also request review or deletion of information under its control. We coordinate school records requests with the school where appropriate without requiring a requester to waive rights.

7. Cookies, local storage and tracking choices

The BullyAlert portals use session cookies and browser storage for access, permitted state and notification controls. Clearing that storage or ending a session can affect access and resume; it does not delete server-held reports or learning records.

The public marketing website uses Cloudflare hosting, security and website measurement. Cloudflare may set a security-clearance cookie when a browser completes a security check. Website measurement and security processing are separate purposes; a security cookie is not itself an advertising preference. Following a school-demo booking link takes you to Calendly, where its own privacy practices apply.

Do Not Track and Global Privacy Control are browser privacy signals, not account-deletion controls. They do not end an authenticated session, erase school records or control a separate website after you leave BullyAlert. We do not promise that a browser signal stops all hosting, security or website-measurement processing. To ask about applicable tracking choices or exercise other privacy rights, use the operator's privacy email, mailing address or telephone above. This request route does not replace any legally required handling of an opt-out preference signal or limit mandatory rights.

Opting in to an authorized service notification is not consent to marketing tracking. Device push tokens or browser subscriptions and their consent, session-binding and delivery records are used for the supported service-notification pathway. Withdrawing notification permission does not delete reports or previously delivered notifications.

8. Retention and deletion

Reports, permitted evidence, learning records and related technical records can remain in server-held storage after a session ends. Records can also remain in restricted recovery backups. Signing out, deleting an app, clearing browser storage, disabling notifications or changing a report's review status does not itself delete these records.

The information involved in a retention or deletion inquiry depends on its category:

• Reports and school response: incident text, any optional name, permitted evidence, review notes, follow-up and controlled exports.
• Learning: module/version and learning-cycle references, progress, practice responses, feedback and completion records.
• Access and notifications: technical actor/session references, notification registrations, requests, retries and receipts.
• Security and accountability: access, audit and security records relevant to the request.
• Website and communications: hosting/measurement information, inquiry correspondence, booking information and copies handled by the relevant service provider.
• Optional voice or media: information associated with the specifically enabled feature, if used.
• Recovery copies: backups that may contain information from the active systems at the time of the copy.

To ask how long information is retained or request its removal, contact privacy@bullyalert.app, write to the operator's PO Box or call the listed telephone number. Identify the request type, your relationship to the user or school, the experience used and an approximate date range. Do not include access credentials, incident narratives, evidence or unnecessary identity documents in an initial message. Ask for the relevant category, retention purpose, period or trigger, any specific lawful exception and the treatment of provider and backup copies.

A request is assessed under applicable law and the school-record arrangements involved, using proportionate verification and information that can reliably be located. An anonymous report may not be linkable to the requester. A specific lawful retention requirement may limit removal; a school's preference alone does not override mandatory rights. This notice does not promise that all categories are automatically purged after the same interval or that all copies disappear immediately when a request is made.

Deleting an active record does not by itself prove that retained provider or backup copies have been removed. Ask for the scope of the action, any remaining copies, their permitted retention and how a restoration would affect the deletion. Copies held independently by a school, and downloaded PDFs or screenshots outside the service, are not automatically erased through an operator request. See Account and data deletion for request instructions.

9. Security and shared devices

The current protected reporting design uses HTTPS access, server-checked role/scope, protected evidence access and session-bound controls for mutations. Notification opening does not substitute for authorization. These controls reduce risk; no system or transmission is guaranteed secure. We do not claim universal encryption at rest, zero breaches or certification based only on this notice.

Keep access credentials confidential, use a device you are authorized to use, and sign out on shared devices. Downloaded PDFs, screenshots and already delivered notifications can remain outside the app; protect or remove local copies as appropriate. Suspected access problems can be reported to privacy@bullyalert.app without including credentials or private reports in an initial message.

10. Access, correction and other rights

Depending on applicable law and the records involved, you may have rights to access, correction, deletion, restriction or other choices. Contact our privacy team to make a request. Parents, guardians and eligible students may also have rights regarding education records that are exercised through the school. We do not assume that all school-related information is exempt from California privacy law or that all privacy rights apply identically in every situation.

We may ask for reasonable evidence that you are entitled to act on the relevant record. We do not require access codes, passwords, private keys or unnecessary identity documents in an initial email. An anonymous report may not be reliably linkable to the requester; we will explain a limitation rather than create a new identity link merely to satisfy the request. We will not disclose someone else's protected content to verify a request.

Requests must be handled within applicable legal deadlines. No guaranteed acknowledgment or completion time is promised beyond those duties. Turning off notifications or choosing not to provide optional evidence does not by itself make a good-faith report invalid.

11. Future credentials and policy changes

Live blockchain issuance is not represented as active by this policy. This policy does not authorize publication of personal information on a blockchain. Before any such feature is enabled, a separate accurate notice must explain public fields, recipients, permanence and available choices, and any required authorization must be obtained. A public blockchain record may not be erasable by us; personal incident content must not be silently added to it.

When this policy materially changes, we will update its date and provide the notice required by law and applicable school arrangements, using the website and appropriate school/user channels. A policy update alone is not retroactive consent to a new purpose or disclosure. The Privacy & student choice explainer at /privacy/ does not replace this legal policy.

Contact: privacy@bullyalert.app. General product inquiries: jrod@bullyalert.app. Mail or telephone inquiries may use the operator contact details above. These contacts are not emergency-response channels.