Trust Center · v2026.04

Trust, documented.

We ask our customers to trust us with visibility into their most critical systems. We take that seriously. This is the page where we show our work — our security posture, how we handle data, what we're certified against, and where to reach us if you find something we missed.

System Status Request Documentation
ALL SYSTEMS OPERATIONAL
Last check: Uptime (90d): 99.98%
Detection PlatformOperational
Security Operations CenterStaffed
Customer PortalOperational
Public WebsiteOperational
Incident ReportingOperational
Support ChannelOperational
01
Compliance Posture

Frameworks we actually operate under.

We map our operations to the frameworks small and mid-sized businesses get audited against. No vanity badges, no compliance theater. Details available under NDA during onboarding.

Core
SOC 2 Type II
Security, Availability, Confidentiality

Our detection and response infrastructure is audited annually against SOC 2 Type II criteria. Report available to prospects and customers under NDA.

✓ Active
NIST CSF 2.0
Full core function mapping

Operations mapped to the NIST Cybersecurity Framework 2.0 core functions: Govern, Identify, Protect, Detect, Respond, Recover.

✓ Aligned
HIPAA
Security Rule safeguards

Technical, administrative, and physical safeguards designed to support HIPAA Security Rule obligations. BAAs executed with covered entities.

✓ Aligned
PCI DSS
Merchant support

Controls supporting PCI DSS 4.0 requirements for merchants and service providers handling cardholder data. Attestation available on request.

✓ Aligned
CMMC Level 1–2
DoD contractor alignment

Practices aligned with CMMC Level 1 and 2 for Department of Defense contractors and their supply chain. Assessment documentation support available.

✓ Aligned
FFIEC
Credit unions & community banks

Controls align with FFIEC examination expectations. Proven track record with credit unions achieving top-tier NCUA exam outcomes.

✓ Aligned
02
Data Handling

Your data. Our accountability.

Honest answers to the questions our customers — and their auditors — actually ask.

Q 01

What data do you collect?

Only what's needed to detect and respond to threats: process execution telemetry, scheduled task creation, persistence mechanisms, login events, network connection metadata, and relevant system configuration. We do not collect document content, email bodies, or the personal data your employees process day-to-day.

Q 02

Where is data stored?

All customer telemetry is stored in U.S.-based data centers operated by our detection platform partner. Data in transit is encrypted with TLS 1.2+. Data at rest is encrypted with AES-256. No offshore processing.

Q 03

How long is data retained?

Telemetry data is retained for one year from collection, in line with forensic investigation requirements. Incident records are retained for seven years to support compliance and legal hold obligations. Customers can request earlier deletion for any specific data set.

Q 04

Do you sell or share data?

No. Never. We do not sell customer data, trade it, license it, or share it with advertisers, brokers, or marketing partners. Data is accessed only by our SOC analysts and our detection platform, strictly for the purpose of delivering the service.

Q 05

Who has access?

Access is limited to SOC analysts with role-based permissions, logged and audited. Minimum-necessary access is enforced — an analyst sees your telemetry only when reviewing an active alert. All analyst actions are recorded in audit logs available for customer review under NDA.

Q 06

What about law enforcement requests?

We require a valid legal process (subpoena, court order, or warrant) for any disclosure of customer data to law enforcement. We will notify the affected customer before disclosure unless legally prohibited from doing so. Full process documented in our MSA.

Q 07

What happens if I cancel?

Upon termination, your endpoint agents are deactivated and removed from active monitoring. Customer telemetry is purged from active systems within 30 days. Archival copies maintained for legal/compliance obligations are deleted at the end of their retention window. Deletion attestation available on request.

Q 08

Can I get a copy of my data?

Yes. Customers can request a full export of their telemetry and incident records at any time during an active contract. Exports are delivered in a standard format (JSON or CSV) via secure transfer, typically within 10 business days of request.

03
Subprocessors

Who touches your data. And why.

We use carefully selected third-party providers to deliver Complyn Sentinel. The categories below describe what each does at a high level. A full named subprocessor list is provided to customers under NDA as part of onboarding.

Category
Purpose
Data Handled
Region
Detection Platform
Endpoint telemetry collection, behavioral analysis, threat detection
Process telemetry, system events, security logs
U.S.
SOC Operations
24/7 human analyst triage, investigation, and response
Alert data, investigation notes, customer contact info
U.S.
Cloud Infrastructure
Hosting of our customer portal and internal applications
Account metadata, portal activity, billing info
U.S.
Communication Services
Email delivery for alerts, reports, and customer communication
Recipient email, subject/body of outbound notifications
U.S.
Payment Processing
Subscription billing and invoice management
Billing name, payment method (via tokenization — we never store card numbers)
U.S.
Identity & Access
Authentication for our team and customer portal
Login credentials (hashed), session tokens, MFA secrets
U.S.
Changes to subprocessors: We notify customers at least 30 days in advance of any material change to our subprocessor list. Customers have the right to object per the terms of their DPA. Full named list available in your signed subprocessor appendix.
04
Our Incident Response

If something happens to us.

A cybersecurity company is a target. We've planned for it. This is our public commitment to what we'll do if Complyn experiences a security incident affecting customer data.

T+0

Detection & containment

Internal incident response team activates. Affected systems isolated. Scope of impact assessed. SOC operations continue uninterrupted for unaffected infrastructure.

< 24 hrs

Initial customer notification

Customers whose data may be affected receive direct notification within 24 hours of confirmed impact. Notification includes what we know, what we're doing, and what (if anything) the customer should do.

< 72 hrs

Regulatory notification

Where legally required (GDPR, state breach laws, sector regulations), regulators notified within statutory windows. We do not delay notifications to manage PR.

< 30 days

Full post-incident report

Affected customers receive a written post-incident report: root cause, scope, remediation, and changes we're making to prevent recurrence. Public summary published if the incident materially affected the service.

Our commitment: We will not minimize, delay, or obfuscate any security incident affecting customer data. We will communicate plainly, quickly, and in writing. If we ever fail this standard, we expect to be held accountable.

05
Responsible Disclosure

Found something? Tell us.

We welcome security research from outside our organization. If you've discovered a vulnerability in our website, customer portal, or any Complyn-controlled asset, we want to hear about it.

What we promise

  • We'll acknowledge your report within 2 business days.
  • We'll give you a substantive response within 10 business days with our assessment and planned action.
  • We will not pursue legal action against good-faith researchers who follow this policy.
  • We'll credit you publicly once the issue is resolved (if you want credit).
  • We're a small team — please be patient if the fix takes a little time.

What we ask

  • Report through the submission form below — not social media, not email blasts.
  • Give us reasonable time to fix the issue before public disclosure.
  • Don't access or modify data that isn't yours.
  • Don't degrade service for other users (no DoS testing, please).
  • Include enough detail to reproduce the issue.

Submissions are encrypted in transit and routed directly to our security team. We review every report.

06
Documentation

Need the paperwork? Here's the list.

The documents below are available to prospects evaluating Complyn and to active customers. Most are provided under NDA — typical turnaround is one business day.

Master Services Agreement
Our standard MSA covering service scope, SLAs, liability, and termination.
Standard request
Data Processing Addendum
DPA compatible with GDPR, CCPA, and state privacy laws. Includes our subprocessor appendix.
Standard request
Business Associate Agreement
HIPAA BAA for covered entities and their business associates. Pre-signed template available.
Healthcare customers
SOC 2 Type II Report
Full Type II audit report covering Security, Availability, and Confidentiality trust criteria.
Under NDA
Security Whitepaper
Technical architecture overview of the Complyn Sentinel service — detection, data flow, controls, response.
Standard request
Subprocessor List (Full)
Complete named subprocessor list with change notification commitments. Referenced by the DPA.
Under NDA

Need a document that isn't listed? Ask.

Request Documentation
Ready To Evaluate

Trust is earned in the details. We've shown ours.

When you're ready to bring Complyn into your evaluation process, we'll move quickly on documentation, security reviews, and contract terms. Most engagements are under protection within one business day of commitment.