CHRP.

Safety Policy & Community Terms

How safety and abuse reporting works on CHRP: mutual-consent pairing, blocking, and content-blind or sealed reporting on an encrypted service.

#How CHRP is different

CHRP has no accounts, no feeds, no discovery, and no strangers. Nobody can message you unless you physically met them and both of you consented to pair. Your conversations are end-to-end encrypted; CHRP's infrastructure cannot read them — not as a promise, as an architecture.

#Zero tolerance

Using CHRP for harassment, threats of violence, exploitation of minors, trafficking, or any illegal activity is prohibited. There are no warnings for child-safety violations: verified cases result in permanent loss of CHRP infrastructure service for the person AND the device, and reports to the National Center for Missing & Exploited Children (NCMEC) as required by 18 U.S.C. § 2258A.

#Your protections (all on your device, no permission needed from us)

#Reporting

Report any contact from the conversation menu ("Report a Safety Concern").

#The one exception, stated plainly

CHRP alerts you when your words are captured — screenshots ask permission, saving asks consent. The single exception: if a conversation is reported for safety, it is sent to CHRP silently. Every user is told this before their first conversation. This is deliberate: report alerts would endanger the people reports exist to protect.

#Data handling

Reports are retained at most 30 days (routine) / 180 days (serious), except where law requires preservation of verified serious-case evidence. Reports are used only for safety review — never for advertising, profiling, or any other purpose. CHRP has no accounts, so a report contains only pseudonymous device identities and what the reporter chose to include.

#Contact

Safety: [email protected] · Support: [email protected] We respond to safety reports within 24 hours.