child safety.

MemberBerries prohibits child sexual abuse and exploitation (CSAE) absolutely. There is no context, no private setting, no family relationship, and no claimed purpose that makes it permitted here.

Specifically, the following are prohibited on MemberBerries:

• Child sexual abuse material (CSAM), in any form.
• Computer-generated, drawn, edited, or AI-generated imagery that depicts a minor in a sexual manner, whether or not a real child was involved.
• Sexualisation of a minor in any image, video, recording, caption, description, tag, or profile — including a minor in the user’s own family.
• Grooming: building a relationship with a minor, inside the app or by using it, for the purpose of sexual exploitation, online or offline.
• Sextortion: threatening to release intimate material of a minor.
• Soliciting, offering, trading, or advertising CSAM or sexual contact with a minor.
• Trafficking of a minor, or any attempt to facilitate it.

This standard binds every user, in every bunch, at every privacy setting.

• 1. Reporting. Every user can report suspected CSAE from inside the app, on any memory, any profile, and any invitation. Anyone, user or not, can also write to childsafety@memberberries.app.
• 2. Response. A report about a child’s safety is handled ahead of every other report, as fast as we can. We don’t promise a number of hours.
• 3. Removal and preservation. On actual knowledge of apparent CSAM we remove it from view immediately, and preserve it and the associated account records as required by law for the authorities. We do not delete evidence ahead of a report.
• 4. Reporting to authorities. We report apparent CSAM to the National Center for Missing & Exploited Children (NCMEC) through the CyberTipline, or to the relevant authority in the user’s region, as required by applicable law including 18 U.S.C. § 2258A.
• 5. Account action. The account is closed. We keep the email address so that person cannot start again, and we remove them from every bunch that still has someone else to look after it. A bunch with no other owner stays in their name until a new owner is named. What we have preserved stays out of view.
• 6. Notifying the bunch owner. Where it is lawful and will not interfere with an investigation or put a child at risk, we tell the owner of the affected bunch that an account has been removed from it.
• 7. Review. We review these standards and our handling of reports at least once a year, and after any incident.

We comply with applicable child safety laws and regulations in the regions where MemberBerries is available, and we maintain a process for reporting confirmed CSAM to NCMEC or the relevant regional authority.

A child in the record is a subject: a name, a date of birth, and the memories their family kept about them. They have no login. The bunch owner is responsible for what is kept about them, and for the choice to keep it.

This release does not offer an account to anyone under 18. Being tagged as the subject of a memory never gives someone sight of it.

An owner can remove a child from the record. This standard still covers what is kept about them.

Designated contact for child safety matters, including notifications from Google Play and from any authority or child safety organisation:

A person reads this address. It is not an automated mailbox.

Contact your local law enforcement first. In the United States you can also report to the NCMEC CyberTipline at CyberTipline.org or 1-800-843-5678. Then tell us at childsafety@memberberries.app, so we can act on the account.