Acceptable Use Policy

Effective date: [PLACEHOLDER — confirm: effective date]

Last updated: [PLACEHOLDER — confirm: date this version is published]

Version: 1.0 (draft — not yet attorney-reviewed)

ChuEok exists for one thing: letting people leave a warm, personal message for someone at a moment that matters. These rules keep it that way. They apply to everyone — Hosts, Co-Hosts, and Guests — and they are part of our Terms of Service. The defined terms used here are the ones in §1 of the Terms.

1. The one rule that matters most: record people, not victims

Everyone in a recording should know they are being recorded and should be fine with it.

If you are recording: only record yourself and people who have agreed to it. Do not point a camera at someone who has said no, does not know, or cannot meaningfully agree.

If you are a Host: it is your job to tell your guests they are being recorded and to get whatever consent the law where you are requires — including from a parent or guardian for anyone who is a child. See Terms §5. Some places require everyone in a recording to agree. Assume you need permission and get it.

2. What you must not post

Do not upload, record, or share Content that:

Harms children

• Sexualises a minor in any way. This is an absolute line. We remove it immediately, permanently ban the account, preserve the evidence, and report it to law enforcement and to the appropriate reporting body.
• Features a child without their parent's or guardian's permission.

Harms or targets people

• Threatens, incites, or glorifies violence against anyone.
• Harasses, bullies, stalks, or targets a person with abuse.
• Attacks people because of their race, ethnicity, national origin, religion, caste, disability, disease, age, sex, gender, gender identity, or sexual orientation.
• Encourages self-harm or suicide.
• Exposes someone's private information — home address, phone number, financial details, identity documents — without their permission.
• Records someone secretly, or in a place where they would expect privacy.

Is sexual or graphic

• Nudity, sexual acts, or sexually explicit content.
• Gratuitous gore or shock content.

Is illegal or dangerous

• Anything that breaks the law where you are or where the Event is.
• Content promoting terrorism, violent extremism, or a criminal organisation.
• Sale of drugs, weapons, or other regulated goods.
• Malware, phishing, or links designed to harm people.

Isn't yours to post

• Content that infringes someone else's copyright, trademark, or other rights, including music you do not have the right to use.
• Impersonating another person, or claiming a message is from someone it is not.

Abuses the Service

• Spam, advertising, bulk or automated submissions.
• Attempts to defeat rate limits, submission caps, file-size or format limits, or to upload something other than a genuine message.
• Attempts to access another Host's Event or another person's data, to probe our systems, or to reverse-engineer, scrape, or overload the Service.
• Sharing a guest link publicly in order to flood an Event with junk.

3. Hosts: your responsibilities

Running an Event makes you responsible for what lands in it.

• Get consent before the camera rolls (see §1 and Terms §5).
• Moderate your Event. You can hide a message from view or permanently delete it. Do it when something crosses a line.
• Honour removal requests. If a Guest asks you to delete their message, delete it. This applies even if you disagree, and even if the message is perfectly nice. It is their face and their voice.
• Only share the guest link with people you actually want to hear from. It is a link, not a password — anyone who has it can record.
• Do not repurpose messages. A message given for a wedding is not material for an advertisement, a public social-media post, or a machine-learning dataset, unless the person who recorded it agreed to that.
• Choose your Co-Hosts carefully. A Co-Host sees every guest name, message, and note in the Event.

4. Guests: what you should know

• Recording is voluntary. Nothing is uploaded until you tap send.
• Your name is shown to the Host with your message. Your email, if you give one, is stored on the Event and visible to the Host and Co-Hosts.
• Once you send it, the Host can watch it, download it, and keep it — see Terms §4.1 for the exact permissions you are giving.
• You can change your mind. Ask the Host to delete it, or ask us — §6 below. You do not need an account to do that.

5. Service limits

These are the technical limits currently in force. They exist to keep Events usable and to stop abuse. We may change them.

If you hit a rate limit, wait a few minutes and try again. Whole venues often share one network, so the per-network limit is deliberately generous.

6. Reporting something — and how takedowns work

6.1 If you are the Host

Open the Event, find the message, and use the message menu to hide it (removes it from view) or delete it (removes it permanently — the stored file and the streaming copy go too). Deleting is immediate and cannot be undone.

6.2 If you are a Guest, or anyone else

Email [PLACEHOLDER — confirm: abuse/takedown email address; the code currently sends from support@mychueok.com] with:

• a link to the Event or the Event's share code, or the Event's name;
• the name shown on the message, if you know it;
• what the problem is — for example "that's me and I want it removed", "this person did not agree to be recorded", "this features my child", "this is harassing", "this infringes my copyright";
• how we can reach you.

You do not need a ChuEok account to report anything.

6.3 What we do

We will confirm receipt of your report, and tell you the outcome where it is appropriate to do so. If we remove Content, we tell the Host what was removed and why, and they can contest it by replying to that notice. [PLACEHOLDER — confirm: whether a formal appeals process and statement-of- reasons is required. If the Service is offered in the EU, counsel should assess obligations under the Digital Services Act for hosting services, including notice and action mechanisms, statements of reasons, and the point-of-contact requirements — some obligations apply regardless of size.]

6.4 Copyright

If you believe Content infringes your copyright, send a notice to [PLACEHOLDER — confirm: DMCA/copyright agent email] including: your contact details; identification of the work; identification of the Content and where to find it; a statement that you believe in good faith the use is not authorised; a statement under penalty of perjury that your notice is accurate and that you are the owner or authorised to act for them; and your signature.

We remove Content that is the subject of a valid notice and terminate repeat infringers. [PLACEHOLDER — confirm: registration of a DMCA designated agent with the US Copyright Office if relying on the §512 safe harbour. This requires a filing and a fee, and the safe harbour is not available without it.]

7. What happens when rules are broken

Depending on how serious it is, we may:

1. Remove or hide the Content.
2. Warn the Host.
3. Close the Event.
4. Suspend or permanently ban the account.
5. Preserve evidence and report to law enforcement.

For the most serious categories — content sexualising a minor, credible threats of violence — we go straight to step 5 without warning.

8. A note on what we do not do

We do not pre-screen or automatically scan Content before it is delivered to a Host. Messages go straight from the Guest to the Host who invited them. Our safety model is: Hosts control who gets the link, Hosts can hide and delete, and anyone can report to us.

[PLACEHOLDER — confirm with counsel and against Apple's Guideline 1.2: Apple requires apps with user-generated content to have (a) a method for filtering objectionable material, (b) a mechanism to report offensive content with timely responses, (c) the ability to block abusive users, and (d) published contact information. Today the app has (b) only via email, and (d) only if a support address is published in the listing. There is no in-app report button for Guests, no blocking mechanism, and no content filtering. This is a likely App Review rejection point and should be raised with the product team before submission — see the notes in data-practices.md.]

9. Contact

[PLACEHOLDER — confirm: abuse/takedown email] [PLACEHOLDER — confirm: legal entity name and business address]