EliteMD Match™ — CSAM Identification & Prevention Protocol

EliteMD Match™ is an adults-only (18+) platform. Child sexual abuse material, sexual exploitation of minors, grooming, or sexual solicitation involving minors is strictly prohibited. Suspected violations may result in immediate account restriction or termination and may be reported to appropriate authorities as required by law.

Protocol Name: EliteMD Trust & Safety – CSAM Prevention & Response

Priority: Critical / P0

Applies To: Profile photos, private messages, image/video uploads, profile text, links, reports, and other user-generated content.

1. Adult-only access

EliteMD Match is strictly for users 18 years of age or older. Require date of birth during registration, prohibit accounts indicating a user is under 18, and implement age/identity assurance appropriate to the platform's risk level. Users must agree that they are at least 18 before account activation.

2. Prevent prohibited content before distribution

Route uploaded images/videos through a dedicated trust-and-safety moderation pipeline before making them broadly visible where technically feasible. Use reputable CSAM-detection/hash-matching services and age-risk/content classifiers appropriate for production deployment. Do not build or train your own CSAM dataset or expose suspected material to ordinary staff.

3. Automatic safety triggers

A high-confidence CSAM/hash match, credible indication that a depicted person may be a minor in sexual content, grooming/sexual solicitation involving a minor, or a credible user report should immediately generate a P0 safety case. The system should restrict further dissemination of the content and apply appropriate account restrictions while the case is handled.

4. Human review must be tightly controlled

Suspected CSAM should never appear in ordinary admin dashboards, customer-service queues, analytics, logs, thumbnails, or developer testing environments. Only specifically authorized and appropriately trained Trust & Safety personnel should have access when necessary and lawful. Minimize copying and viewing.

5. Preserve; don't casually download or redistribute

Developers, moderators, and employees must never download suspected CSAM to personal devices, email it, screenshot it, forward it through Slack/Teams, or create additional copies merely to investigate it. Preserve required records/evidence using a restricted process consistent with applicable legal obligations.

6. Reporting and escalation

Establish a designated CSAM/child-safety escalation owner and documented procedure for reports to the appropriate authorities. For a U.S.-based provider, the company should obtain legal guidance on its obligations under 18 U.S.C. § 2258A, including reporting apparent violations to the NCMEC CyberTipline when the statutory requirements apply. Imminent danger to a child should receive emergency escalation.

7. Never conduct vigilante investigations

EliteMD personnel should not contact suspected minors, confront suspected offenders, attempt to identify children independently, or circulate content to determine whether it is illegal. Preserve the appropriate information and follow the company's authorized reporting/legal process.

8. User reporting

Every profile and conversation should contain Report → Child Safety / Suspected Minor / Sexual Exploitation. Reports should bypass normal customer-support prioritization and enter the P0 Trust & Safety queue. Users should also be able to block the reported account immediately.

9. Enforcement

Confirmed child sexual exploitation, grooming of minors, or CSAM results in permanent account removal and other actions required by law. Related accounts/devices/payment identifiers may be evaluated for enforcement consistent with the company's privacy policy and applicable law.

10. Data governance

Maintain restricted audit records covering the report/case ID, timestamps, account identifiers, enforcement actions, reporting status, and authorized personnel actions. Retention and preservation periods should be established with counsel rather than improvised by developers.

Safety Workflow

UPLOAD / MESSAGE → SAFETY SCREEN → CLEAR → PUBLISH/DELIVER

↓ POSSIBLE CSAM / CHILD EXPLOITATION

BLOCK OR QUARANTINE FROM FURTHER DISTRIBUTION → CREATE P0 CASE → RESTRICT ACCOUNT AS APPROPRIATE → AUTHORIZED TRUST & SAFETY REVIEW → REQUIRED PRESERVATION/REPORTING → ENFORCEMENT → AUDIT LOG

Suspected-content storage is isolated from normal application and admin access, with separate records maintained for safety reports, safety cases, moderation decisions, and safety audit logs.

Automated detection is treated as a safety signal that triggers a properly designed escalation process — never as an irreversible legal determination made solely from an automated score.

Report a child-safety concern: iodutola@dilorganizationealthtech.org