BullyAlert Acceptable Use 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. Use BullyAlert to help, not harm

BullyAlert supports good-faith reporting of school-safety concerns, authorized school response and available educational practice. It is not an emergency service. If someone is in immediate danger, seek a trusted adult or local emergency services; in the United States, call 911. Do not wait for an app response.

Permitted use includes describing a concern, sharing permitted relevant evidence, responding honestly to a neutral Location Check, reviewing information within assigned Staff scope, making authorized follow-up notes or exports, and completing your assigned learning activity.

2. Student and Parent/Caregiver reporting

Report honestly in your own words. Distinguish what you saw from what you heard or believe. You may be unsure or unable to verify a concern. A good-faith report is not misuse solely because it cannot later be substantiated.

Do not knowingly make up an incident, impersonate someone, alter evidence to mislead, threaten or harass, or retaliate against someone who reports. Do not attempt to identify an anonymous reporter through the app, credentials, technical references or coordinated questioning. Do not use a Parent/Caregiver session to access a child's anonymous history or someone else's submissions.

Use only your authorized pathway. Do not post school access credentials publicly. Include only the names or details reasonably needed to explain a concern, using the optional name choice only if you wish. Do not submit private incident content to general marketing email.

3. Safe evidence handling

Do not place yourself or anyone else at risk to obtain a photograph, recording or other evidence. Do not record in a place or manner that is unlawful or that violates necessary privacy protections. Use the report to explain the concern even when you have no attachment.

Do not upload malware, unlawful material, unrelated explicit content, or unnecessary medical, financial or identity documents. If a concern involves potentially illegal imagery or material that should not be copied, use the appropriate adult or authority process rather than downloading, forwarding or recreating it for the app. A legitimate safeguarding concern must still be raised through a safe pathway.

Protect evidence already available to you. Do not publish it to social media, group chats or other unauthorized recipients. Authorized access to an incident or PDF does not authorize unrestricted disclosure.

4. Location Checks are observations, not investigations

Answer only from what you actually observed. “I did not observe” or “I cannot verify” is a legitimate response. Seeing nothing does not resolve an incident. Do not invent observations, coordinate answers, seek the reporter's identity, confront an alleged participant or collect evidence on behalf of a prompt.

The system's role, school, eligibility and permission controls remain controlling. Parent/Caregiver users must not receive or impersonate Student automatic prompts or Staff alerts. Do not attempt to bypass those boundaries.

5. Staff access and response

Use Staff access only within your assigned role and scope and for a legitimate school purpose. Do not inspect records out of curiosity, use another role's credentials, query unrelated schools or exploit a technical defect to widen access.

Respect anonymous-by-default reporting. Do not attempt to recover an identity from technical session information or use that information for retaliation. An optional report-specific name remains protected and does not justify linking or exposing broader activity.

Keep review notes factual and proportionate. Treat allegations and neutral observations as information to assess, not automatic proof. Do not mark a report resolved only because a student observed nothing. Follow the school's safeguarding, mandatory-reporting and fair-process requirements. BullyAlert does not replace them.

Share records only with people authorized for a permitted purpose. Secure exported PDFs, downloaded evidence, screenshots and local copies. Do not place them in personal public storage or marketing materials. End sessions on shared devices and request removal of access that is no longer appropriate.

6. Learning and recognition

Use fictional or nonidentifying information in lesson practices and transfer self-checks. Do not paste identifiable student stories, private case notes or evidence into a training activity. Do not impersonate another staff member, submit practice choices for someone else, manipulate progress or represent completion as a legal or professional certification.

Do not use recognitions, badges or future credentials to rank victims, discredit a report, retaliate, speculate financially or infer a student's identity. No app recognition replaces human assessment of an actual concern.

7. Security and technical conduct

Do not bypass authentication, role/scope restrictions, rate limits, notification consent, evidence authorization or session protections. Do not scrape protected records, inject code, upload malware, overload the service or attempt to decrypt or collect credentials and endpoints.

Authorized accessibility tools are not prohibited. Routine technical testing requires the operator's permission and a bounded scope; finding a defect does not authorize access to private data. If you encounter an apparent exposure, stop accessing it, do not redistribute the information, and contact privacy@bullyalert.app. Do not include secrets or student records in an initial message.

8. Reporting misuse and corrective action

Report product/access concerns to jrod@bullyalert.app and privacy or inappropriate-access concerns to privacy@bullyalert.app. Real school incidents should use the school's protected reporting or adult-response pathway, not a public website message. These inboxes are not emergency channels.

The operator may apply necessary, proportionate access or security measures under law and the applicable school agreement. Where feasible, the affected person or school receives an explanation and a route to review the decision. No promise is made to disclose protected reporter information as part of that review. School discipline and employment action are the school's lawful decisions; this policy does not mandate termination, punishment or a finding of legal violation.

Do not retaliate against good-faith reporters, people who identify a defect, or those who exercise privacy rights. Any update to this policy must be dated and handled through the change process in the Terms and applicable school arrangement.