BullyAlert Account and Data Deletion

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 you can request

You can ask about access to, correction of or deletion of your BullyAlert account or associated information. A parent or guardian can request action concerning their child's information, and a school can request action for records under its control. Verification and applicable law determine what action can be taken; using this page does not give someone access to another person's reports.

Routine Student reporting may use a school-code session rather than a named email account. There can still be associated technical, report or learning records. We do not assume that “anonymous by default” means no data exists or no privacy rights apply.

2. Start a request without sharing credentials

Email privacy@bullyalert.app with the subject BullyAlert Account or Data Request. You do not need to be signed in to send this request.

Include only:

1. Whether you are asking for account deletion, data deletion, access or correction.
2. Whether you are the user, a parent/guardian or an authorized school representative.
3. The school name, the experience used (Student, Parent/Caregiver or Staff), and a safe contact address for a reply.
4. An approximate date range or a nonsecret report reference already available to you, if useful. Do not include a report narrative or evidence in the initial email.

Do not send school access codes, Staff PINs, passwords, session tokens, wallet keys, government identity documents or private student evidence. If additional verification is needed, the operator must arrange an appropriate limited process.

Suggested message:

I would like to request deletion of information associated with my BullyAlert use. I can provide the school name, experience used, approximate date range and my relationship to the relevant user through an appropriate process. Please explain the information needed to verify the request, the applicable timeline and any records that must be retained. I have not included access credentials or sensitive report content.

Adapt the request type to access, correction or account deletion if that is what you need.

3. How the request is handled

The operator must handle requests under applicable law, ask only for proportionate verification, identify information it can reliably locate, and coordinate with the relevant school when needed. The requester must receive an explanation of the action, applicable completion timing and any lawful limit or documented exception.

An anonymous submission may not be reliably linkable to the person making a request. We will explain that limitation rather than create unnecessary new identity links or disclose someone else's data. School coordination is not a reason to deny a request without considering applicable rights.

4. What deletion can cover

Depending on the request and lawful obligations, deletion may cover a locatable account or technical user reference and its associated personal information, notification registrations, learning records, and report/evidence records that the operator is required or permitted to delete. A decision must assess the actual associated data, not just disable sign-in.

Some records may need to be retained for a specific legal obligation. We must identify the retained categories, lawful reason and applicable period. A school's preference alone does not override mandatory deletion rights. Records held independently by the school require action by that school; a copy exported from BullyAlert is not automatically erased when the service deletes its copy.

5. Sign-out, notifications and device copies

Signing out, clearing browser storage, deleting the app or disabling notifications is not a request to delete server-held records. These actions affect the device/session and permissions, not necessarily school records or learning progress.

You can use the available app/browser notification controls or device settings to withdraw notification permission. Notifications already delivered to a device and PDFs, screenshots or evidence downloaded outside the service may remain there. Remove or protect local copies where appropriate. Do not erase a school record outside your authority.

6. Children and former students

Parents and guardians can ask to review or delete a child's information or prevent further collection/use, subject to lawful verification and applicable rights. Schools can also ask for deletion of information under their control. Applicable rights may continue after a student leaves a school. We will assess the applicable request rather than treating continued school enrollment or school retention policy as an automatic reason to refuse it.

A parent request does not grant access to the child's anonymous activity through the Parent/Caregiver portal. Records requests are handled through the separate verified process. If you cannot identify the relevant school contact, email the operator’s privacy contact to ask for the appropriate route.

7. Requests from Android and iOS apps

For an account or data request concerning an Android or iOS BullyAlert experience, use the instructions in Section 2. You do not need to remain signed in or keep the app installed to send a request. Along with the experience and approximate dates, you may include the app version and platform if available; do not send a device push token, installation identifier, school access code or Staff PIN.

Use the subject BullyAlert Account or Data Request at privacy@bullyalert.app. Alternatively, use the operator's listed mailing address or telephone. Say whether you want account deletion, data deletion, access or correction. Ask what associated information can be located, what verification is needed, what action can be taken and what specific lawful retention limits apply.

An End session or sign-out control ends access; it is not account or server-record deletion. Uninstalling, clearing device storage or turning off notifications also does not make a records-deletion request. Do not use those actions as a substitute for the request above. Information already exported or delivered to your device can remain outside the application; protect or remove local copies within your authority.

8. Questions and limits

For privacy or request questions, contact privacy@bullyalert.app. Product questions go to jrod@bullyalert.app. Neither address is an emergency-response channel.

Live blockchain issuance is not represented as active. Any future public blockchain feature requires separate notice about permanence and choices before use; records outside our control may not be erasable. These instructions do not authorize minting or publication of personal incident information.

Read the Privacy Policy, Terms and Acceptable Use Policy together. A privacy request does not waive any non-waivable right or authorize disclosure of another person's information.