Acceptable Use Policy

Last Updated: 2026-02-25

1. Introduction

The purpose of this Acceptable Use Policy ("Policy") is to define the boundaries of acceptable conduct on MyProtektor's cloud-based security management platform and associated offerings ("Services"). It applies equally to organisation owners, administrators, security guards, clients, and lite-access users operating within our hierarchical role system.

Your continued use of the Services signifies your acceptance of this Policy together with all relevant legislation. This document forms part of, and should be read alongside, our Terms of Service and Privacy Policy.

2. Permitted Uses

The Services are intended solely for the following lawful activities:

2.1 Security Operations

• Incident Reporting: Logging authentic security events, breaches, and emergency situations
• Patrol Management: Coordinating guard routes and scanning QR-code checkpoints for verification
• Emergency Response: Initiating and managing real-time emergency alerts and dispatch workflows
• Client Communication: Exchanging information with protected clients regarding security matters

2.2 Administrative Functions

• User Management: Onboarding, offboarding, and organising personnel within an organisation
• Role Assignment: Granting the correct permissions tier to each team member
• Performance Monitoring: Reviewing patrol completion, response metrics, and guard activity
• Compliance: Generating and preserving records required by industry regulators

2.3 Business Operations

• Service Delivery: Fulfilling contracted security obligations to end-clients
• Quality Assurance: Evaluating and enhancing the standard of security services rendered
• Training: Educating personnel on operational procedures and platform functionality
• Analytics: Leveraging aggregated data to drive informed operational decisions

3. Prohibited Uses

Under no circumstances may you engage in the following activities through the Services:

3.1 Illegal Activities

• Criminal Activity: Engaging in conduct that contravenes any applicable statute or regulation
• Fraud: Furnishing false credentials, fabricated data, or misrepresenting your identity
• Money Laundering: Channelling illicit funds or facilitating terrorist financing via the platform
• Regulatory Violations: Operating outside the bounds of PSIRA or other security-industry licensing requirements

3.2 Abuse of Security Features

• False Reporting: Filing fabricated or intentionally inaccurate incident reports
• Panic Button Abuse: Activating the emergency panic feature when no genuine threat exists
• Location Spoofing: Tampering with GPS coordinates or supplying fictitious location data
• Fake Patrols: Recording checkpoint scans or patrol logs that were never physically completed

3.3 System Interference

• Unauthorized Access: Seeking to reach functionality or data outside the scope of your assigned role
• System Disruption: Degrading, overloading, or otherwise impeding normal platform operations
• Security Bypassing: Evading authentication mechanisms, encryption, or access-control safeguards
• Reverse Engineering: Decompiling, disassembling, or attempting to derive the platform's source code

3.4 Harmful Content

• Harassment: Directing threats, bullying, or intimidation at fellow platform users
• Hate Speech: Distributing material that incites hatred or unlawful discrimination
• Inappropriate Content: Submitting obscene, graphic, or otherwise objectionable material
• Spam: Broadcasting bulk or unsolicited messages, alerts, or notifications

3.5 Privacy Violations

• Data Theft: Extracting or exploiting the personal information of other individuals
• Unauthorized Disclosure: Revealing confidential or restricted data without proper authorisation
• Identity Theft: Assuming the identity of another person, organisation, or role
• Stalking: Exploiting GPS or location-tracking features to monitor individuals without consent

4. Role-Specific Requirements

4.1 LiteClient Users (Level 0)

• Panic Button: Reserve the panic alert exclusively for situations involving real danger
• Information Accuracy: Keep your emergency contact details current and truthful at all times
• Cooperation: Assist and comply with instructions from responding security personnel

4.2 Client Users (Level 1)

• Incident Viewing: Consume incident data strictly for valid security oversight purposes
• Confidentiality: Treat all security intelligence received through the platform as privileged
• Feedback: Offer honest, constructive input aimed at strengthening service delivery

4.3 Guard Users (Level 2)

• Accurate Reporting: Provide thorough, factual accounts in every incident submission
• Patrol Integrity: Complete assigned routes physically and scan checkpoints honestly
• Professional Conduct: Uphold a professional demeanour throughout every shift
• Equipment Care: Handle devices, radios, and other issued equipment responsibly

4.4 Admin Users (Level 3)

• Fair Management: Apply organisational policies equitably across all personnel
• Data Protection: Safeguard personally identifiable information and maintain strict confidentiality
• Quality Control: Assess, approve, or escalate incident submissions with due diligence
• Compliance: Verify that day-to-day operations align with all governing laws and internal policies

4.5 Owner Users (Level 4)

• Legal Compliance: Guarantee that the entire organisation meets its statutory obligations
• Ethical Leadership: Cultivate an ethical culture that cascades through every role level
• Data Governance: Establish and enforce robust data-handling and privacy frameworks
• Financial Responsibility: Keep subscription billing and payment records accurate and up to date

5. Data and Information Security

5.1 Data Protection Requirements

• Access Control: Retrieve only the data that your role strictly requires
• Secure Storage: Keep downloaded or cached information in encrypted or otherwise protected storage
• Transmission Security: Employ encrypted channels whenever sending sensitive data
• Retention Limits: Dispose of information once the legitimate purpose for holding it has lapsed

5.2 Incident Documentation

• Accuracy: Verify that every incident record is truthful, detailed, and factually sound
• Timeliness: Log incidents as soon as reasonably practicable after they occur
• Objectivity: Present events neutrally without embellishment or personal bias
• Evidence Preservation: Maintain the integrity and chain of custody for all associated evidence

5.3 Location Data

• Accuracy: Ensure that geolocation readings are genuine and unaltered
• Privacy: Honour the privacy rights of all individuals whose locations may be captured
• Consent: Secure appropriate consent before initiating any location-tracking feature
• Retention: Purge location records when they are no longer operationally necessary

6. Communication Guidelines

6.1 Professional Communication

• Respectful Language: Maintain a courteous, professional tone in all interactions
• Clear Communication: Express information in a direct, unambiguous manner
• Timely Response: Acknowledge and reply to messages within a reasonable timeframe
• Appropriate Channels: Direct each communication to its proper channel or recipient

6.2 Emergency Communications

• Priority: Treat every emergency alert as the highest-priority communication
• Clarity: Convey precise, actionable details during crisis situations
• Follow-up: Provide status updates until the emergency is fully resolved
• Documentation: Record all emergency-related communications for audit purposes

7. Compliance and Monitoring

7.1 Monitoring Activities

MyProtektor actively oversees platform usage to verify adherence to this Policy. Our monitoring mechanisms include:

• Automated Monitoring: Algorithm-driven systems that flag anomalous behaviour and potential breaches
• Manual Review: Human evaluation of flagged reports, accounts, and activity patterns
• Audit Trails: Comprehensive logging of user actions for accountability and regulatory compliance
• Investigation: Formal inquiry into any reported or detected policy infringement

7.2 Compliance Reporting

• Violation Reporting: Escalate confirmed breaches to the relevant internal or external authority
• Regulatory Compliance: Observe all security-industry regulations, including PSIRA requirements
• Internal Reporting: Channel compliance concerns to organisational leadership promptly
• External Reporting: Submit disclosures to regulatory bodies where legally mandated

8. Consequences of Policy Violations

8.1 Warning System

• First Violation: Written notice coupled with a mandatory policy acknowledgement
• Second Violation: Time-limited suspension of account privileges
• Third Violation: Permanent termination of the offending account
• Serious Violations: Instant termination without prior warning stages

8.2 Enforcement Actions

• Account Suspension: Temporary or indefinite revocation of platform access
• Feature Restrictions: Selective disabling of specific capabilities or modules
• Data Deletion: Removal of any content found to breach this Policy
• Legal Action: Civil or criminal proceedings for severe or repeated violations

8.3 Appeals Process

• Appeal Right: Entitlement to formally challenge any enforcement decision
• Review Process: An independent, unbiased examination of the appeal
• Evidence Submission: Ability to present supporting documentation or testimony
• Decision Communication: Transparent, written notification of the appeal outcome

9. Reporting Violations

Should you witness or become aware of conduct that contravenes this Policy, you are urged to notify us without delay:

9.1 How to Report

• Email: info@myprotektor.co.za
• Phone: +43 676 441 2714
• In-App: Tap the "Report Abuse" option located within the application
• Emergency: Dial local emergency services when an immediate physical threat is present

9.2 Information to Include

• User Information: Identifying details of the individual(s) involved
• Violation Details: A precise description of the prohibited conduct observed
• Evidence: Screenshots, logs, timestamps, or other corroborating material
• Impact: An assessment of how the violation affected operations or safety

10. Policy Updates

MyProtektor reserves the right to revise this Policy periodically. When material amendments are made, we will inform you through:

• A notification sent to the email address linked to your account
• Push notifications delivered inside the application
• An updated version published on our official website
• Prominent banners or alerts displayed within the platform interface

11. Contact Information

Should you have enquiries regarding this Acceptable Use Policy, reach out to us using the details below: