Last updated · April 27, 2026
Child Safety Standards
Crossings has zero tolerance for child sexual abuse material (CSAM) and any content that endangers minors. This page documents the design choices, automated safeguards, and reporting processes we use to keep the app safe for everyone.
1. Our commitment
We comply with all applicable laws and platform policies on child safety, including Google Play’s child safety standards policy and the United States’ reporting obligations to the National Center for Missing & Exploited Children (NCMEC). We act on credible reports within 24 hours.
2. Architecture-level safeguards
Crossings is a private, peer-to-peer photo-matching app. Several design choices materially reduce the surface area for grooming, unsolicited contact, and content distribution:
- No public discovery. There is no public profile, no searchable feed, no group chat, and no anonymous messaging. Connections are formed only through 6-character invite codes that two users share with each other privately.
- No public distribution of photos. Shared photos are end-to-end encrypted on the user’s device (Curve25519) before upload and can only be decrypted by the single explicitly chosen recipient. No third party, including Crossings, can read the contents.
- Server-side automated screening. Profile photos uploaded to the app are scanned by an automated not-safe-for-work classifier on the server before being made visible to anyone. Images flagged as unsafe are rejected and never stored.
- One-to-one connections. The app does not support broadcast, group chat, or any-to-any messaging. A crossing is always between exactly two consenting accounts.
3. Minimum age
Use of Crossings requires that you be at least 13 years old, or older where local law sets a higher minimum (e.g. 16 in the EU under GDPR-K). Authentication is delegated to Sign in with Apple and Sign in with Google; both providers enforce their own minimum-age requirements at the operating-system / account level. Crossings will terminate any account we have reason to believe belongs to a user below the applicable minimum age.
4. Reporting tools
Anyone — user or non-user — can report content, behavior, or accounts to us through any of the following channels:
- In-app reporting. Every connection screen has a Report content action that opens a prefilled email to our safety team.
- Email. support@crossings.so is monitored daily and is our designated point of contact for users, platform partners, and law enforcement on child-safety matters.
5. Action on reports
When we receive a report or otherwise become aware of content that may constitute CSAM, or of conduct that may endanger a minor, we take the following actions:
- The reported content is removed from our systems where technically possible, and the reported user’s ability to share further content is suspended pending review.
- The associated account is suspended pending investigation. If the report is confirmed, the account is permanently banned and the responsible party is blocked from creating new accounts on the same authentication identity.
- Confirmed CSAM is reported to the National Center for Missing & Exploited Children (NCMEC) via their CyberTipline, consistent with our obligations under U.S. federal law (18 U.S.C. § 2258A). For reports involving users in other jurisdictions, we additionally notify the appropriate national hotline (e.g. INHOPE member organizations).
- We retain records of reported content and the associated account metadata for the period required by applicable law to assist law-enforcement investigations.
6. Cooperation with law enforcement
We cooperate fully with valid legal process from law enforcement agencies investigating child-safety crimes. Law enforcement requests should be sent to support@crossings.so with subject line “Law enforcement request — child safety”. We aim to respond to emergency requests within 24 hours.
7. Designated point of contact
For questions about these standards, urgent child-safety concerns, or law-enforcement inquiries: support@crossings.so
8. Updates to these standards
We may revise these standards as the app evolves and as applicable law and best practices change. Material updates will be reflected in the date at the top of this page. Substantive changes will be published at least 30 days before they take effect, where feasible.