Cyber Bullying Preventor

Cyber Bullying Preventor

Menu
Policies — Cyberbullying Protector

Policies

Last updated:

Privacy Policy

We collect the minimum data needed to keep students safe: flagged content snippets, timestamps, platform label (e.g., “Instagram”), severity, and model scores. Purpose: safety monitoring and incident support. Legal basis: school legitimate interests and/or consent as applicable. You may request access/export/deletion subject to school policy.

  • We do not read all messages, only model-flagged snippets are shown.
  • No ads and no sale of personal data.
  • Language support: English & Bahasa Melayu.

Terms of Use

  • Roles: Guardian (parent) and Institution Staff (teacher/admin/counselor).
  • Keep your account secure and report suspected misuse.
  • Prohibited: sharing student PII externally, tampering, or attempting to deanonymize reports.

Acceptable Use (Students/Guardians)

  • Be respectful; do not harass, threaten, or spread hateful content.
  • If you believe a message was flagged incorrectly (false positive), please use the Help & Support page to submit an appeal or clarification request.
  • Do not post or share screenshots/details of other students’ incidents publicly or on social media.
  • Use this platform only for safeguarding purposes; do not attempt to bypass, probe, or misuse the system.

Data Retention & Security

  • Incidents retained for ≥30 days, then purged or anonymized per school policy.
  • Passwords hashed (Argon2id/bcrypt). 2FA supported. Encryption in transit and at rest.
  • Access limited by role (least privilege). Audit logging enabled.

Incident Handling & Appeals

  • Flags are created by the model and displayed in the dashboard.
  • All incidents are reviewed by staff; guardians are notified where appropriate.
  • Possible actions: mask sensitive content, notify a counselor, contact a guardian, or mark the case as resolved.
  • If you wish to appeal or clarify an incident (e.g., false positive), please use the Help & Support page. Responses are provided within the stated SLA (e.g., 24–48 hours).

Integrations (n8n)

We send limited metadata (event type, severity, timestamps) to n8n flows for routing and notifications. No credentials are stored client-side. Admins can manage endpoints and key rotation in “Alerts & Automation.”