Yellz Community Guidelines (English)

ItemDetails
Version1.0
Effective date2026-10-17
Report/appeal contactsupport@yellz.app

1. Purpose and neutral operation

Yellz operates its shared live-event database through facts and transparent procedures, without improper favoritism toward or against an artist, label, promoter, venue, ticketing company, country, region, genre, or fandom. We do not alter editorial or report outcomes merely because of popularity, subscription status, fandom size, or outside pressure. We do not display advertising or conduct behavioral targeting.

These Guidelines apply to profiles, performance/venue data, setlists, corrections, reviews, attendance reports, photos, evidence URLs, reports, and all other submissions.

2. Constructive participation

DoExample
Cite evidenceLink to an artist, organizer, or venue’s official page
Admit uncertaintySelect “I don’t remember / I don’t know” when unsure
Make focused correctionsChange only the incorrect date, venue, or track order
Respect differencesDo not turn taste differences into attacks on artists or fans
Protect personal dataDo not expose ticket numbers, barcodes, seats, legal names, or contacts

3. Prohibited content and conduct

CategoryProhibited conduct
Disruption/spamMeaningless edits, mass posting, repeated rejected edits, review interference, manufactured conflict
MisinformationKnowingly false performance, artist, date, venue, setlist, cancellation, or postponement data; presenting unchecked AI suggestions as fact
Rights infringementSubstantial lyric copying; unauthorized photo, video, audio, logo, piracy, copied text, defamation, publicity/privacy infringement
Personal informationPosting without consent a name, address, contact, live location, seat, order number, QR/barcode, or private-account data, including doxxing
ImpersonationMisrepresenting affiliation with an artist, agency, organizer, venue, Company, or user. Parody must be clearly non-confusing
Harassment/dangerThreats, bullying, discrimination, sexual harassment, self-harm encouragement, exploitation of minors, unsafe meetups
Ticket abuseResale, exchange, transfer, companion recruitment, payment, or external scam solicitation; Yellz is not a marketplace
Point manipulationMultiple accounts, collusion, reward trading, bots, automation, or shared device/payment method used to inflate votes, reviews, thanks, or rankings
Security abuseUnauthorized access, exploits, malware, scraping, rate-limit evasion, prompt injection

Critical views, minority opinions, and good-faith mistakes are not violations by themselves. We consider correctability, evidence, repetition, intent, harm, and safety.

4. Shared-database review rules

ItemRule
ProposalSaved as a revision; does not immediately overwrite the confirmed version
ReviewersNormally 3–5 attendees; exclude proposer, linked companions, same-device and same-payment-method accounts
Independent reviewHide other answers and proposer identity until response
ConfirmationTwo attendee approvals, excluding proposer
RejectionTwo “incorrect” responses reject; corrections re-enter as a new proposal
Too few reviewersPublish as “needs verification” and retry when more attendees register
LockLock setlists 30 days after confirmation; later changes require a reasoned request
HistoryKeep revision history and support rollback; anonymize contributions after account closure

The “needs verification” publication rule above applies to shared-database proposal review, not to questions/answers awaiting moderation.

4.1 Fan-community questions and answers

This section describes the current question/answer feature. Its casual-chat ban and URL ban apply to that current feature; planned features in Sections 4.2–4.3 follow their own rules.

  1. You may ask and answer free-text questions about artists; content is not limited to missing performance fields. Sign-in is required. Text must contain 1–1000 characters after trimming surrounding whitespace. A public profile or attendance history is not required, and author UID, public ID, and nickname are not displayed.
  2. Only adults whose accounts are not suspended can post. Minors and users with unknown age categories can only browse; being an adult is not required to delete your own existing posts. Questions/answers alone earn no points. Performance/setlist corrections and confirmation use the existing proposal/review process.
  3. Recruitment, invitations to DM, casual chat, and contact exchange are prohibited. Rule checks also reject URLs and contact details before saving question/answer text; provide the evidence URLs encouraged in Section 2 through the corresponding proposal feature. Questions and answers in artist communities undergo rule checks followed by AI submission triage when moderation AI is enabled in the settings. If AI decisions are unavailable because of an outage, cost cap, or emergency shutdown, they are held without publication; while AI is disabled in the settings, they are published after rule checks only. Because rules cannot fully assess context, reporting and staff review are also used.
  4. You can report questions and answers. Blocking works both ways and hides the other person’s questions/answers. Posts awaiting review or hidden by staff are visible only to their author. Answering and viewing answer lists are also restricted for hidden, deleted, or blocked questions.
  5. Staff assess reports and appeals and may republish appropriate content using the content-restoration action. Dismissing a report alone does not restore a hidden post. Text deleted by its author is not restored.
  6. Deleting your question/answer clears its text and leaves a deletion marker. Deleting a question also hides its answer list, including others’ answers, but does not erase their answer text. Account closure alone retains question/answer text and anonymizes private authorship links. Delete posts before closing your account if you do not want their text retained.

4.2 Performance threads, community expansion, and live rooms (planned)

The following features are planned under the owner decisions of 2026-10-09 (#439 and #447). Under-18s and users of unknown age may only browse performance threads, artist communities, and event-day rooms; posting requires age 18 or older and an active account (maintaining #208 eligibility). The adult casual-chat ban is withdrawn: casual-chat categories, event-day rooms, user follows, and reactions are planned for adults. Questions and answers in artist communities undergo rule checks followed by AI submission triage when moderation AI is enabled in the settings. If AI decisions are unavailable because of an outage, cost cap, or emergency shutdown, they are held without publication; while AI is disabled in the settings, they are published after rule checks only.

  1. Acceptance of the Terms and these Guidelines will be required before posting. Performance threads will have before/on/after-event tabs and up to 4 images. Artist communities will offer followers casual chat, announcements/news, travel/accommodation, and questions. Adult user follows/reactions, artist follows, and keyword muting are planned. Confirm performance/setlist data through existing DB proposals and review.
  2. Defamation, sexual content, spam, exchanging phone numbers/SNS IDs/LINE IDs or inviting external DMs, ticket resale/exchange/transfer (including free transfers), and companion recruitment are prohibited. Prevent unsafe contact with or solicitation of minors and exposure of location/contact details. DMs, permanent group chats, companion recruitment, and ticket transfers will not be offered.
  3. Age verification continues to prioritize iOS Declared Age Range / Android Play Age Signals, with self-declaration of an age category when unavailable. We do not collect dates of birth. Restricted posting by minors will not be adopted.
  4. Tag tour setlist/staging discussion and images as spoilers. Default collapsing and an always-show setting are planned. A spoiler tag does not permit prohibited content or rights infringement.
  5. AI submission triage applies to posts in performance threads and artist communities, including questions and answers. Event-day room messages are not assessed by AI or sent to AI. Rule checks reject URLs, images, contact details, prohibited words, and similar violations; subsequent handling uses reports, with automatic hiding when reports exceed a threshold. AI submission triage (Japanese, English, Korean) will publish, hold, or reject; low-confidence decisions are held. When AI is enabled, affected posts are held without publication if AI decisions are unavailable because of an outage, cost cap, or emergency shutdown. Held posts are hidden from others; rejected posts are not published. Reports above a threshold will automatically hide content for staff review. The initial-response target is 24 hours, without a resolution guarantee. Dismissing a report alone does not restore content; staff decide. People review serious safety cases and appeals; AI alone does not impose permanent bans. New-user frequency/image limits are planned.
  6. Event-day rooms are planned to open 3 hours before doors open at the performance location and close 24 hours after the show ends. They remain read-only for 7 days after closing, then logs are deleted, leaving only non-identifying statistics. Reported content is retained for investigation for 90 days, separated from ordinary logs, accessible only to reviewers, and then deleted. Everyone may browse; posting requires age 18 or older, an active account, and registration of the event as planned/attended. Only text/stamps are allowed, with no URLs/images; rate limits are planned.
  7. Attendance reports are planned to be integrated into the performance thread’s “after the event” tab. Integration alone will not broaden visibility or change existing attendance-report licensing, deletion, or account-closure treatment. Private personal records will not be automatically published, and attendance reports will not appear on W01. Room deletion deadlines do not apply to attendance reports.

To address App Store 1.2 and Google Play UGC requirements, we plan filtering, in-app content/user reporting, blocking, and operator contact support@yellz.app. Keyword muting adjusts your own view and does not replace reporting/removal.[C1][C2]

Terms, Section 7 · Privacy Policy, Sections 9.3–9.4

4.3 Cheering ads (F26, planned)

  1. Maps/lists of cheering ads, placement submissions, project announcements in the community announcement category, and ad-tour check-ins are planned. Submissions, photos, and announcements require age 18 or older and an active account. Under-18s and users of unknown age may only browse.
  2. We do not collect funds or place advertising orders in the app. Links or directions to external fundraising pages in project announcements are prohibited and will be detected by an initial AI filter. When AI decisions are unavailable, content is held without publication. Verification URLs must not direct users to fundraising either.
  3. Organizers are responsible for obtaining permission from artist agencies/rights holders and checking and complying with their guidelines. A Yellz listing does not guarantee permission or rights clearance.
  4. Listing requires verification that the ad exists, using a photo or an official announcement URL from the advertising company or organizer. Listings will be automatically archived after the placement period. Archiving is not deletion; violations and removal requests remain actionable.
  5. Rights holders may request removal at support@yellz.app with the post/URL, rights concerned, and contact information. On receipt, the targeted listing will immediately be made private while rights verification and removal are handled.
  6. Check-in location verification takes place on the device; location data is not sent to servers or disclosed to other users. Photo location metadata will be removed. Avoid exposing location/contact details in photo content or text. Referrals to advertising companies are planned for Phase 2 onward as referral revenue without directly charging users.

5. Point and ranking integrity

Points are awarded only after confirmation/adoption. Supporting or thanking requires a recorded attendance and an account at least seven days old. We may use device and payment-method duplicate signals and review rankings before finalization.

If manipulation is established, we may revoke points, badges, and benefits and exclude related accounts. Shared households or devices alone do not automatically result in permanent suspension; we consider other evidence to reduce false positives.

6. Reporting and blocking

  1. Report a post/profile through its menu with a reason and optional evidence.
  2. Blocking hides the other user’s proposals, reports, and profile and excludes both users from reviewing each other.
  3. For immediate physical danger, contact local emergency services as well as Yellz.
  4. False reports, mass-reporting to silence views, and retaliatory reports violate these Guidelines.

Apple requires UGC apps to filter objectionable material, respond timely to reports, allow blocking, and publish contact information. Google Play requires acceptance of terms, ongoing moderation, and in-app reporting/blocking.[C1][C2]

7. Moderation and enforcement

SeverityExamplesTypical action
MinorGood-faith typo, formatting issueCorrection request, label, rejection
Repeated/moderateSpam, repeated unsupported edits, lower-level harassmentVisibility limit, point revocation, rate limit, temporary suspension
SevereDoxxing, threat, fraud, coordinated manipulation, serious infringementImmediate hiding, suspension/termination, evidence preservation, legally required action

Available actions include labels, warnings, reversions, removal, setlist locking, point/benefit revocation, feature restrictions, and account suspension/termination. We consider urgency, harm, intent, repetition, history, and cooperation and seek proportionate action where practical.

Rules and Vertex AI Gemini may assist initial triage, but AI alone does not impose permanent bans. A person reviews minors’ safety, rights infringement, personal data, payment issues, and significant appeals.

Questions and answers in artist communities undergo rule checks followed by AI submission triage when moderation AI is enabled in the settings. If AI decisions are unavailable because of an outage, cost cap, or emergency shutdown, they are held without publication; while AI is disabled in the settings, they are published after rule checks only. Restoration follows Section 4.1.

8. Rights claims

A rights holder or agent may send support@yellz.app the URL/post ID, right asserted, explanation, contact details, and authority evidence. We may contact the submitter and decide whether to hide, remove, or restore. Notices under the U.S. Copyright Act (DMCA) are also accepted at support@yellz.app.

9. Notice and appeals

  1. Unless prevented by law, investigation, safety, or anti-abuse needs, we notify the target, reason, duration, and appeal route.
  2. Appeal within 30 days of the notice with the post ID, reasons, and evidence.
  3. Where practical, a reviewer not involved in the original decision re-examines it and gives the outcome and reason.
  4. If new evidence or clear error exists, we correct the action and restore recoverable points or benefits.

10. Transparency

We publish aggregate moderation volumes, main violation categories, appeals, and reversals once a year. We will not publish identifiable users or nonpublic security details. Material changes to these Guidelines will be notified in advance.

Sources

All sources checked September 24, 2026.

IDPrimary sourceUse
C1Apple App Review Guidelines 1.2 — User-Generated ContentFiltering, reporting, timely response, blocking, contact
C2Google Play User Generated Content policyTerms acceptance, ongoing moderation, in-app reporting/blocking

Additional check 2026-10-09: [C1][C2] were rechecked for the store requirements in Section 4.2.