house rules.

• Child sexual abuse material, in any form, real or generated. See the Child Safety Standards at memberberries.app/child-safety.
• Sexualising a child, including a child in your own family, in an image, caption, description, or tag.
• Nudity of a child presented or framed sexually. Ordinary family pictures — a baby in the bath, a toddler running through a sprinkler — are not what this rule is about, and we will not treat them as such. Framing, captioning, or tagging that sexualises such a picture is.
• Grooming, or using the app to build a relationship with a child for sexual purposes.
• Soliciting, trading, or asking anyone for sexual content involving a child.

• Sexual content involving an adult who did not consent to it being kept or shown, including intimate images shared without that person’s permission.
• Pornography and sexually explicit material. MemberBerries is not the place for it, including in a bunch of one.
• Threats of violence, intimidation, or stalking.
• Harassment and bullying — including by repetition, by tagging someone in content meant to humiliate them, or by keeping a record intended to be used against a family member.
• Content that exists to shame, humiliate, or punish a person in the bunch.
• Hate speech, or content that attacks or degrades a person or group based on race, ethnicity, national origin, religion, disability, sex, gender identity, sexual orientation, age, or immigration status.
• Sharing another person’s private information — an address, a document, a medical record, a password — to harm or expose them.

• Anything illegal where you are, or where the person in it is.
• Content promoting self-harm, suicide, or disordered eating.
• Content depicting gratuitous violence, cruelty to people or animals, or graphic injury.
• Content promoting terrorism, violent extremism, or a violent organisation.
• Instructions for making weapons, explosives, or drugs.
• Fraud, impersonation, phishing, and scams.
• Malware, or anything designed to break, overload, or get around the app’s security, storage limits, or access controls.

• Inviting someone into a bunch in order to expose them to something, rather than to include them.
• Using a dated audience or a birthday vault to leave content for a child that breaks these rules when it opens. The rules apply on the day it is kept and on the day it is read.
• Claiming to be someone you are not in a profile or an invitation.
• Using someone else’s account.

These rules apply inside a bunch of two people exactly as they apply anywhere else. Most of what passes between family members is nobody’s business, and we have built the app so that it is nobody’s business — including ours. The rules above are the short list of exceptions, and every one of them is on the list because it describes harm to a person.

We do not read your memories. Nobody here reviews what you keep, and no model is trained on it. The one exception is something reported to us — and then only that.

What we do instead:

• 1. Prevention by design. Bunches are invite-only. There is no public feed and no discovery. Every memory is tied to an audience before it can be kept. Being tagged as the subject of a memory never grants access to it. Most of the harm that happens on open services simply has no route here.
• 2. Review on report. When something is reported, we look at the reported item and what we need around it to decide. Nothing else.
• 3. Action. Where a report is founded, we remove the content, and depending on what it is we may warn, restrict, suspend, or close the account behind it, and report it to the authorities.

• A memory, photo, or recording: open it and choose “report a concern.”
• A heart or a note: choose “report a concern” beside it.
• A member: open their profile in your bunch and choose “report a concern.”
• An invitation you did not expect: choose “report a concern” on the invitation screen.
• Anything at all, including from outside the app: hello@memberberries.app.
• Anything involving a child’s safety: childsafety@memberberries.app, and see the Child Safety Standards.

Tell us what you saw and where. You do not have to explain yourself, and you do not have to be the person it was about.

Reporting something does not tell the person you reported them.

Open their profile in your bunch and choose “block this person.” A blocked person can’t tag you as the subject of a memory, can’t tag a child profile in a bunch you own, can’t add you to an audience, and can’t invite you. The two of you stop seeing each other’s memories in your timelines. You can unblock them later.

You block a member — someone with a login. A child with no login isn’t blockable.

Blocking hides; it doesn’t change who can see what. Anything they could already see, they still can. To take that away, change the memory’s audience.

If you are a bunch owner, you can also remove a member outright, which ends their access to everything in that bunch, including what they wrote themselves.

Blocking does not report anyone. If someone broke these rules, please do both.

• We aim to acknowledge within three business days.
• We aim to decide within five business days after that.
• Child safety, credible threats, and imminent risk of harm jump the queue and are handled as fast as we can.
• We tell the reporter when the report is closed. We may not be able to say what we did.
• We tell the person whose content was acted on what rule they broke, unless telling them would put someone at risk or we are legally prevented.

These are targets, and we will miss one eventually. They are not promises of a particular result.

Write to hello@memberberries.app within 30 days. Say what was removed and why you think the decision was wrong. Where it is practical, someone who was not part of the first decision will look again. Decisions about content covered by the Child Safety Standards are final.