Personal Business Look closer How we work How we score Questions Security and trust Talk to us Sign in Book your audit
Legal

Security Standards

Security is at the core of Protector Class operations. This page describes the encryption standards, access controls, audit practices, and incident response protocols that govern how we protect your data.

Last updated: March 2026  ·  ADMBA ONE INC.

Why Now

Cybercriminals move at AI speed. Security standards are engineered to match.

Cybercriminals use AI to enumerate exposure at scale, generate personalized phishing, and weaponize stolen data within hours. Protector Class security standards are built for that operational pace: AES-256 encryption at rest, TLS 1.3 in transit, consent verification loop for every subject-level scan, chain-of-custody logging on every finding. Continuous coverage that never stores what shouldn't be stored.

AES-256 at Rest
TLS 1.3 in Transit
Human-Verified Intelligence
Data Stays in North America
01Introduction

At ADMBA ONE INC, security is at the core of our operations. We are committed to protecting sensitive information through strict adherence to industry best practices and security frameworks. This Security Standards page outlines the measures we take to safeguard user data (including anchor points such as full name, email, and phone identified in monitored criminal-targeting sources), prevent unauthorized access, and maintain the integrity of our platform as we proactively alert you to protect your personal and financial information.

02Compliance & Security Frameworks

Protector Class follows industry-recognized security best practices. Our security policies and controls are designed to ensure a high level of data protection and privacy for all data processed. As part of our ongoing commitment to security, we continuously refine our infrastructure and processes to meet evolving industry requirements.

2.1 Human-in-the-Loop Verification

Unlike fully automated scanners, findings are re-verified against the live source before anything is sent. Findings in the highest-severity classes are held before release and reviewed by a person, including any finding where an asset cannot be automatically confirmed as belonging to the customer. Re-verification runs on every delivery; the review step is reserved for the findings a machine cannot adjudicate, so that it stays a real check rather than a rubber stamp.

03Data Encryption & Protection

We employ advanced encryption technologies to protect user data at all times.

Data at Rest
AES-256 Encryption
Data in Transit
TLS 1.3
Password Hashing
bcrypt
Scope
All user data, reports & identifiers
  • Data at Rest: All stored data (including consent-based identifiers and breach reports) is encrypted using AES-256 encryption.
  • Data in Transit: All data transmitted between users and our platform (during outreach, signup, or dashboard access) is secured using TLS 1.3.
  • Password Hashing: User credentials are protected with strong cryptographic hashing algorithms (bcrypt) to prevent unauthorized access post-signup.
04Access Controls & Authentication

To minimize risk and prevent unauthorized access, we enforce strict access control mechanisms:

  • Multi-Factor Authentication (MFA): Required for administrative access to systems handling anchor points and user data.
  • Role-Based Access Controls (RBAC): Ensures users and staff only have access to necessary data. Dashboard reports are limited to consented users.
  • Session Timeout Policies: Automatically expire inactive sessions to protect post-signup dashboard interactions.
05Security Audits & Risk Management

Protector Class manages risk to its own systems through:

  • Continuous Monitoring: Detects potential threats and suspicious activity, including unauthorized attempts to access user-submitted data, using our Compliance Audit Trail.
  • Incident Response Plan: Addresses security incidents in a timely, structured manner to protect users alerted through our Services.
06Data Storage & Retention

We adhere to strict data retention policies to enhance security and compliance:

  • Data Centre Security: User data (including consent-based identifiers and breach reports) is stored in highly secure environments with industry-standard protections.
  • Retention Policies: Breach reports are retained for 24 months after generation, then deleted unless a legal hold applies. Consent and activity logs (Compliance Audit Trail) are retained for 3 years for legal auditing.
  • Secure Data Disposal: When no longer needed (including upon user deletion request), data is permanently removed following industry best practices. You may request deletion of your account data at any time by contacting privacy@protectorclass.com. We will permanently remove your data at your request, except where legally required to retain it.
  • Evidence Handling: For credibility and audit purposes, we provide verifiable evidence (e.g., anonymised text extracts or logs from the Compliance Audit Trail) post-consent and post-payment. Specific sources are withheld to protect proprietary methods.
07Incident Response & Breach Notification

Protector Class has a structured approach to handling security incidents:

  • 24/7 Security Monitoring: Automated monitoring runs continuously against our own systems and raises alerts to the team.
  • Breach Notification Protocol: In the event of a confirmed security breach impacting your data, affected users will be notified as soon as feasible via email or SMS, per applicable regulatory requirements (PIPEDA, CCPA).
  • Mitigation & Containment: Rapid response measures limit exposure and prevent further compromise, protecting pre-identified and consented user data.
08User Security Best Practices

While Protector Class implements platform-level security measures, users play a role in safeguarding their accounts:

  • Use strong, unique passwords and enable Two-Factor Authentication (2FA) where possible to secure your dashboard after signup.
  • Be cautious of phishing attempts and suspicious activity : verify outreach emails and SMS from us before acting (see Terms of Service Section 6).
  • Regularly review account settings and breach reports for unauthorized access or new detections tied to your anchor points.
09Contact for Security Concerns

For security-related enquiries or to report a potential vulnerability, contact us directly:

10Changes to This Security Standards Policy

We may update this Security Standards policy periodically to reflect changes in our security practices or regulatory requirements. Changes will be posted with a "Last Updated" date. Significant updates (such as changes to encryption methods or data retention policies) will be communicated via email to users who have signed up. For pre-signup users, updates will be posted as a notice on our website. We recommend reviewing this page periodically to stay informed.

Protector Class remains committed to maintaining and evolving its security standards to keep pace with industry advancements and emerging threats.

AES-256 Encrypted
PIPEDA & CCPA Aligned
Human-Verified Intelligence
Data Stays in North America