bGuru

bGuru Community Guidelines

Version 0.1.13published

Last updated: 2026-08-22

§0 Plain-language summary

bGuru is a community for sports prediction tipsters. To keep it useful and welcoming:

Be honest — submit picks you actually believe, not random clicks to inflate your leaderboard standing. Be respectful — no harassment, no doxxing, no hate speech, no threats. Be one person — one account, one identity. Multi-accounting loses your account permanently. Don't break the law — no illegal content (CSAM, terrorism, fraud), no impersonation, no scraping, no automation.

Report violations via long-press → Report on the offending content, or email legal@bguru.app.

When we act on a violation, we go through: warning → mute → suspension → permanent ban. CSAM and other priority illegal content skip the ladder and go straight to permanent ban + law-enforcement referral with no warning. You can appeal any other moderation decision by emailing legal@bguru.app within 30 days of being notified of the decision (EU/EEA users have at least six months — see §7.1). An in-app appeal flow will ship in a future version of the Service.

§1 How to use this document

These Community Guidelines work alongside the Terms of Service (especially §6 Acceptable use) and the Privacy Policy.

ToS §6 incorporates these Guidelines by reference: a violation of these Guidelines is a breach of the ToS. We can update these Guidelines independently of the ToS (per §10 below); ToS material changes follow the ToS §16 process separately.

§2 What's not allowed

§2.1 Universal prohibitions (all jurisdictions)

The following are prohibited regardless of where you live:

  • Child Sexual Abuse Material (CSAM) — zero tolerance. Immediate permanent ban + report to NCMEC CyberTipline + INHOPE national hotline + national CSAM authority (CEOP in UK, Lahav 433 in Israel, BKA in Germany, etc.). No appeal.
  • Terrorism content — content constituting or facilitating terrorist offences (incitement, glorification, recruitment, training, financing); support for designated terrorist organisations; symbols of proscribed terrorist groups.
  • Harassment + threats — targeted, repeated, hostile communications directed at a user or group; credible threats of violence.
  • Doxxing — sharing personal information about a user (real name, address, workplace, phone, identifying photos) without their consent, especially where the intent is to facilitate harm.
  • Hate speech — content inciting hatred, hostility, or violence against any person or group based on race, ethnicity, religion, national origin, sexual orientation, gender identity, disability, or other protected characteristic.
  • Sexual content — bGuru is not a venue for sexual content. No nudity, no sexually explicit material, no content sexualising any person under 18.
  • Non-consensual intimate imagery — sharing or threatening to share intimate images without the consent of the depicted person.
  • Violence + threats of violence — content glorifying real-world violence, mass-casualty events, or specific threats against identifiable persons.
  • Self-harm + suicide promotion — content encouraging, glorifying, or providing detailed instruction for self-harm or suicide (we moderate against Samaritans Media Guidelines; resources at §9).
  • Illegal goods + services — sale, advertisement, or facilitation of illegal drugs, weapons, stolen goods, or other illegal commerce.
  • Fraud + scams — phishing links, impersonation for financial gain, fake giveaways, Ponzi schemes, fake-bookmaker scams.
  • Impersonation — impersonating bGuru staff, another user, a public figure, or any third party with intent to mislead.
  • CSAM-adjacent solicitation + grooming — any conduct that a reasonable person would recognise as an adult attempting to gain the trust of a minor for harmful purposes triggers immediate ban + law-enforcement referral.
  • Spam — repetitive content, link farms, automated posting designed to inflate metrics or promote off-platform services.
  • Copyright + trademark infringement — see §4.5 below for the DMCA §512 process (US) and equivalent national mechanisms.

§2.2 Jurisdiction-specific overlays

United Kingdom (Online Safety Act 2023 + UK criminal law). bGuru is a user-to-user service under OSA 2023 s. 3(2) (below the Category 2B threshold of 7M UK MAU at MVP). OSA s. 10(8) "priority illegal content" includes content constituting Schedule 7 offences: terrorism (Terrorism Act 2000 ss. 11–13, 15–19, 56–58; Terrorism Act 2006 ss. 1–2); CSAM (Protection of Children Act 1978 ss. 1–2; Sexual Offences Act 2003 ss. 9–15; OSA 2023 ss. 188–192 intimate-image abuse); hate crime (Public Order Act 1986 Pt III and IIIA); drug supply (Misuse of Drugs Act 1971 ss. 4–5); fraud (Fraud Act 2006 ss. 1–4); harassment (Protection from Harassment Act 1997 ss. 1–4; Malicious Communications Act 1988 s. 1; Communications Act 2003 s. 127). For Schedule 7 priority offences, the enforcement ladder begins at permanent ban with parallel law-enforcement referral — no warning step.

European Union / EEA (DSA Art. 14 + 16 + Directive 2017/541 + Directive 2011/93 + Framework Decision 2008/913). Illegal content under DSA Art. 3(h) is content not in compliance with EU law or any member-state law. EU-baseline prohibited categories include: terrorism (Directive 2017/541 Arts. 2–14, including Art. 5 public provocation); CSAM (Directive 2011/93); incitement to violence/hatred (Framework Decision 2008/913); non-consensual intimate imagery; fraud and counterfeiting (Directive 2019/713). Germany-specific: Strafgesetzbuch §86a (use of symbols of unconstitutional organisations including swastika, SS emblems, NSDAP iconography — criminal offence up to 3 years' imprisonment; immediate removal without warning); §130 Volksverhetzung (incitement to hatred). Italy-specific (Garante posture): moderator data-access limited to the minimum required; non-consensual intimate imagery reportable to Polizia Postale e delle Comunicazioni.

United States (47 U.S.C. § 230 + 18 U.S.C. § 2258A + state defamation). Under Section 230(c)(1) of the Communications Decency Act, bGuru is not treated as the publisher of user content and is not civilly liable for what users post (subject to the FOSTA-SESTA sex-trafficking carve-out at 47 U.S.C. § 230(e)(5)). Section 230 does NOT immunise bGuru from federal criminal liability or IP claims. FOSTA-SESTA: no content soliciting, facilitating, or promoting sex trafficking under 18 U.S.C. § 1591 is permitted. CSAM: mandatory reporting to NCMEC CyberTipline under 18 U.S.C. § 2258A on actual knowledge; immunity for good-faith reporting under § 2258B(a); 90-day preservation per § 2258A(h). State defamation varies by state (NYT v. Sullivan 376 U.S. 254 actual-malice standard for public figures; anti-SLAPP statutes in CA / NY / TX shield protected speech; FL HB 991 narrowed actual-malice for anonymous speech, subject to ongoing First Amendment challenges per NetChoice v. Florida 34 F.4th 1196 and Moody v. NetChoice 603 U.S. 707).

Israel (Penal Law 5737-1977 + Defamation Law 5725-1965 + CA 1239/19 platform-liability framework). Penal Law §§144A–144D prohibit incitement to terrorism, racism, and hate-based violence. §173 prohibits grossly offensive content. §214/§214B prohibits obscene material including CSAM. The Denial of Holocaust (Prohibition) Law 5746-1986 prohibits Holocaust denial in a manner that glorifies or defends the perpetrators. Defamation Law 5725-1965 §§1–6 defines defamation; primary defences are truth (§14), honest opinion (§15), fair reporting (§§15–16). Platform-liability per CA 1239/19 Shaul v. Nidailat Y.Y. Ltd.: bGuru is not a primary publisher of user content, but may become a "secondary publisher" if it fails to act on specific credible notice within a reasonable time — bGuru's enforcement ladder is designed to satisfy this good-faith moderation standard.

Rest of world (AU / JP / KR / SG / NZ / ZA / UAE / MEA / MX / LATAM).

  • Australia — OSA 2021 + Basic Online Safety Expectations 2022. Class 1 material (CSAM, terrorism, mass-casualty instructions, non-consensual sexual activity per OSA 2021 s. 106) → 24-hour removal + eSafety Commissioner referral. Class 2 material → comply with formal removal notices under s. 111. Cyber-abuse and image-based abuse covered under OSA Pt 4.
  • Japan — Penal Code Art. 175 (obscene material) + Cyber Defamation + Transparency Act 2021. Art. 175 prohibits distribution of obscene objects (extended to digital transmission via 2011 amendment).
  • South Korea — Information and Communications Network Act Art. 44-7. Non-discretionary removal obligation for criminal/obscene/defamatory/violence-inciting/public-order-endangering content; cyber defamation criminal under Art. 70.
  • Singapore — POHA + Broadcasting Act + IMDA. Harassment under POHA Cap. 256A; Broadcasting Act + Internet Content Guidelines on public order, racial/religious harmony, criminal facilitation.
  • New Zealand — FVPCA 1993 (as amended 2022). Objectionable publications (CSAM, sexual violence, extreme violence) — making available is a criminal offence; OFLC is the relevant authority.
  • South Africa — Cybercrimes Act 2020 + FPB. s. 16 offences for harmful/menacing/objectionable data messages.
  • UAE + MENA cluster (SA / EG / MA / QA / KW). Content violating public morals/order under UAE Cybercrime Law 34/2021, Saudi Anti-Cybercrime Law of 2007, Egypt Cybercrime Law 175/2018 — content disparaging recognised religions or facilitating sexual exploitation prohibited.
  • Mexico + LATAM cluster (AR / CL / PE / CO). National criminal codes prohibit CSAM, terrorism, incitement, defamation; bGuru's baseline covers.

§3 bGuru-specific prohibitions

In addition to the §2 universal and jurisdiction-specific prohibitions, the following are prohibited on bGuru:

  • Multi-accounting — creating more than one Account for any reason. The only exception is when an account has been mistakenly created and bGuru has confirmed merger/deletion. Multi-accounting to evade enforcement results in immediate permanent ban of all accounts plus device flagging.
  • Leaderboard manipulation — coordinated picks, bot-driven picks, collusion within or across groups intended to inflate scores. Examples: voting rings where members agree to submit identical picks; sock-puppet accounts feeding picks to a primary account; off-platform coordination to game group scoring.
  • Scraping or mirroring bGuru data — bGuru's prediction data and leaderboard structure are bGuru's product. Automated extraction (including via headless browsers, scrapers, or unofficial API clients) is prohibited.
  • Automated submission of Picks — bots, scripts, headless apps. All Picks must be submitted via the official bGuru app interface by a human user.
  • Reverse-engineering the prediction engine — except where this is permitted by mandatory local law (e.g., interoperability under EU Software Directive 2009/24 Art. 6).
  • Sharing or selling Account access — your Account is for you, not for resale.
  • Impersonating bGuru moderation staff — the founder is the sole moderator at MVP. Anyone claiming to act on bGuru's behalf without being the founder is impersonating.
  • Falsifying group purpose to circumvent rate limits — creating groups with fake names/descriptions to evade group-creation rate limits.
  • Solicitation to off-platform betting / gambling / sportsbook services — zero tolerance. Posting links to or actively soliciting users to off-platform betting, gambling, sportsbook, or fantasy-sports services (in Pick comments, group descriptions, profile bio, comments) is a fast track to permanent ban. This rule protects bGuru's non-gambling classification across every jurisdiction in which the Service operates, and is foundational to the Service's legal posture. The ban on users posting affiliate links to sportsbooks, bookmakers, or paid-fantasy operators is absolute.
  • Posting affiliate links to bookmakers, sportsbooks, or fantasy operators — same zero-tolerance treatment.
  • Misuse of third-party trademarks — posting content that uses the name, crest, logo, or other mark of any league, club, competition, national football association, continental confederation, or player in a way that falsely suggests an official relationship with bGuru. Examples of prohibited conduct: using a club crest as your bGuru avatar to imply you are posting on behalf of that club as an official spokesperson; styling a group as "The Official [Club] bGuru Group" when it is not authorised by the club; representing yourself as a player's official account. Ordinary fan commentary and descriptive uses are not affected by this rule. See Terms of Service, §11 Third-party intellectual property, which sets out the nominative fair use basis for bGuru's own display of team and competition marks.

§4 How to report a violation

§4.1 In-app reporting flow (primary channel)

The in-app report mechanism lets you report a user or a group from any screen that displays them. Long-press (or tap the "..." menu) on a user profile, group screen, group member list, predictions feed card, leaderboard row, or group invite preview → Report → choose a category → optional context (max 500 characters, required for "Other") → submit. You will receive a toast confirming receipt and the review timeline.

Only two target types are available at this version of the Service: users (display name, bio, avatar, or behaviour) and groups (group name, description, or purpose). Individual Picks are not a separate report target because Picks contain no free text — anything wrong with a Pick is reported via the user who submitted it.

Categories (in this order, single-select):

  1. Child sexual abuse material or child safety concern — our Trust & Safety team is notified and reviews within 24 hours; your report triggers an immediate account suspension pending review.
  2. Hate speech, harassment, or threats — T&S review within 7 days.
  3. Sexual or explicit content (non-CSAM) — T&S review within 7 days.
  4. Impersonation or identity fraud — T&S review within 7 days.
  5. Off-platform gambling, betting, or sportsbook promotion — T&S review within 7 days (bGuru-specific category protecting non-gambling classification; see §3).
  6. Cheating, multi-accounting, or fraud — T&S review within 14 days (may require investigation).
  7. Copyright or intellectual-property infringement — routed to the DMCA §512 designated-agent workflow (see §4.5 for the counter-notice process).
  8. Other (please describe) — free-text description required; T&S triage and re-classify.

Categories 7 and 8 are triaged within the same standard 7-day review window described in §5.1, unless routed to a category-specific process with its own timeline — for category 7, the DMCA §512 workflow described in §4.5.

Use category 1 for any concern about a user under 18.

§4.2 European Union / EEA — DSA Art. 16 notice-and-action

EU/EEA users (and any third party including non-users) may submit a DSA Art. 16 notice for illegal content via:

  • In-app: same as §4.1, selecting "Illegal content (EU/EEA)"
  • Email: legal@bguru.app, subject "DSA Art. 16 — illegal content notice"

A valid notice (Art. 16(2)) includes: (1) substantiated explanation of why the content is illegal, citing EU or member-state law where possible; (2) precise URL of the content; (3) reporter name + email (anonymous accepted for CSAM-related notices or where reporter has personal-risk grounds); (4) good-faith belief statement.

bGuru's process:

  • Acknowledge receipt without undue delay per Art. 16(5).
  • Process diligently and non-discriminatorily.
  • Reasoned decision communicated to reporter within 7 days for standard reports, within 24 hours for CSAM, within 14 days for cheating investigations that require extended review, per Art. 16(3).
  • Affected user notified per Art. 16(4) with right to appeal per §7.1.
  • Trusted-flagger priority per Art. 16(6) (no trusted flaggers designated yet at MVP scale, but INHOPE/Europol/IWF/national hotline notices receive elevated internal priority).

§4.3 United Kingdom — Online Safety Act 2023 reporting

OSA s. 18 (illegal-content reporting) + s. 23 (child-safety reporting) require accessible reporting mechanisms — bGuru's in-app flow + legal@bguru.app channel satisfy both.

OSA s. 18(3) outcome notification: bGuru notifies the reporting user via in-app notification when the report is resolved, stating action taken (or no action) with plain-language reasoning.

CSAM escalation pathway: immediate content removal + permanent ban (no human viewing beyond the minimum required for the referral) → mandatory referral to CEOP (Child Exploitation and Online Protection) at ceop.police.uk/ceop-reporting → parallel NCMEC CyberTipline at cybertipline.org (international routing) → Internet Watch Foundation (IWF) at iwf.org.uk/report (hash-matching + URL-level action).

Under-18 users have access to the same in-app flow + can contact CEOP directly via ceop.police.uk/ceop-reporting per OSA s. 23 "accessible to under-18s" requirement.

§4.4 Israel — reporting + escalation

Standard channel: in-app flow + legal@bguru.app.

CSAM: escalated immediately to Israel Police Cybercrime Unit (Lahav 433 / לה"ב 433) + INHOPE network (Israel member: Israel Internet Association / ISOC-IL / איגוד האינטרנט הישראלי) + NCMEC CyberTipline in parallel. Permanent ban, no appeal.

Defamation: civil matter under Defamation Law 5725-1965. bGuru does not make unilateral defamation determinations. For contested cases, takedown requires a Tel Aviv District Court (or other competent Israeli court) order — bGuru complies within 24 hours of authenticated notice.

Terrorism / hate / racism: parallel reports to Israel Police + State Attorney's Office encouraged. bGuru cooperates with investigations by Israeli law enforcement.

Privacy violations under PPL Amendment 13: bGuru at legal@bguru.app first; escalation to the Privacy Protection Authority (PPA / רשות להגנת הפרטיות) at gov.il/en/departments/the_privacy_protection_authority.

§4.5 United States — DMCA §512 copyright + NCMEC CSAM

DMCA §512 designated agent: legal@bguru.app, subject "DMCA Notice". Notice must satisfy 17 U.S.C. § 512(c)(3): identify the copyrighted work, URL of allegedly infringing content, reporter contact info, good-faith belief statement, accuracy statement under penalty of perjury, signature. Counter-notification: legal@bguru.app, subject "DMCA Counter-Notice" per 17 U.S.C. § 512(g)(3). Content restored 10–14 business days after counter-notice unless notifying party files court action. Repeat-infringer policy maintained per § 512(i)(1)(A).

Note: USCO designated-agent registration (copyright.gov/dmca-directory, $6 one-time) deferred to MVP+1; until registered, the §512 safe harbour is technically unestablished. This is a known gap that the MVP+30d attorney engagement will address.

Misuse of DMCA: knowingly false notices expose the filer to damages + costs + attorneys' fees under § 512(f).

CSAM under 18 U.S.C. § 2258A: mandatory NCMEC CyberTipline report on actual knowledge. bGuru does not notify the reported user. 90-day preservation per § 2258A(h); good-faith immunity per § 2258B(a). No human viewing of suspected CSAM beyond the minimum required for the referral; content quarantined to a restricted-access store.

§4.6 Rest of world — escalation channels

Jurisdiction Primary external channel
Australia eSafety Commissioner: esafety.gov.au/complaints (post-bGuru-resolution attempt)
Japan Personal Information Protection Commission (PPC): ppc.go.jp/en; court-ordered sender disclosure under Transparency Act 2021
South Korea KISA: kisa.or.kr; KCSC: kocsc.or.kr
Singapore Singapore Police Force (police.gov.sg) + IMDA (imda.gov.sg); Protection from Harassment Court via State Courts
New Zealand OPC (privacy.org.nz) — raise with bGuru first per Privacy Act 2020 s. 75(2); OFLC (classificationoffice.govt.nz) for objectionable content
South Africa SAPS Cyber Crime Unit (saps.gov.za); Information Regulator (inforegulator.org.za)
UAE UAE Data Office / DIFC Commissioner / ADGM Registration Authority (jurisdiction-dependent)
Mexico INAI (inai.org.mx); 20-business-day bGuru response, then INAI escalation
Other LATAM AAIP (AR), SIC (CO), APDP (PE), Chile authority (TBD post-Law 21.719)
Other MENA SDAIA/NDMO (SA), MCIT (EG), CNDP (MA), MOTC (QA), CITRA (KW)

§5 How we moderate

§5.1 Principles

  • Human review at MVP. All moderation decisions are made by a human (currently the founder personally). No automated content moderation tool makes removal decisions independently — automation may flag content for human review (e.g., hash-matching for known CSAM) but final decisions are human-made, with the CSAM zero-tolerance category being the only exception (immediate automated removal + human escalation).
  • Proportionate response — the enforcement ladder in §6 is calibrated to the severity of the violation.
  • Transparency — users get a reasoned decision (Statement of Reasons for EU users under DSA Art. 17; equivalent for other users).
  • Right to appeal — see §7. CSAM-related decisions are excluded from internal appeal (they may be challenged via judicial remedy).
  • CSAM-pending suspensions do not disclose why. Where a suspension relates to a pending investigation into suspected child sexual abuse material, the notice shown to the affected user states that the Account is suspended but withholds the specific reason — consistent with the Terms of Service §9 carve-out for a written explanation "except where doing so would interfere with an ongoing investigation or breach a legal obligation." This applies to every user, not only EU/EEA users; §5.2 below describes the parallel EU-law basis (DSA Art. 17(9)(c)) for the same withholding.
  • Speed — most reports resolved within 7 days. Safety-critical reports (CSAM, credible threats, terrorism content) actioned same-day. EU DSA Art. 16(3) + Art. 20(4) SLAs apply.

§5.2 EU users — DSA Art. 14 + 17 transparency

DSA Art. 14 requires content-moderation rules disclosure in T&Cs — §2 + §3 + §6 of these Guidelines + ToS §6 (which incorporates by reference) constitute the disclosure.

DSA Art. 17 Statement of Reasons applies to: content removal, content disabling, demotion/restriction, account suspension/termination. Required content per Art. 17(3): (1) nature of decision; (2) facts and circumstances relied on; (3) automated-tool use (at MVP: human only); (4) legal ground if illegal-content based; (5) Guidelines / ToS provision if T&C-based; (6) statement of user's right to internal complaint per §7.1 and judicial remedy.

Statement delivery: an in-app notice, shown the next time you open the app and held as account state on our server so it is not lost if you were offline when the decision took effect — the same durable-notice approach bGuru already applies to a suspended age-gate account (see Privacy Policy, §9.1). bGuru does not send moderation decisions by email. legal@bguru.app remains the channel you use to write to us; it is not a channel bGuru uses to notify you of a decision. In practice: same day for CSAM decisions (subject to the masking described in §5.1); within 7 days for standard decisions; within 14 days for cheating investigations.

Statements may be withheld under Art. 17(9)(c) where bGuru is subject to a legal or regulatory obligation not to provide the information (e.g., active law-enforcement investigation) — bGuru notifies that a restriction has been applied with expected disclosure timeline. This is the EU-law basis for the CSAM-pending masking described in §5.1, which bGuru applies to every user regardless of jurisdiction.

Voluntary transparency reporting: bGuru is below the VLOP threshold (45M EU MAU) and not formally required to publish annual transparency reports under Art. 24. Voluntary quarterly summary of moderation statistics published in §12 Changelog beginning first full calendar quarter after launch.

§5.3 UK users — Children's Code + OSA s. 11–12

ICO Age Appropriate Design Code (under DPA 2018 s. 123) applies because the Service is likely to be accessed by under-18s — bGuru's 16+ gate doesn't exempt; it means the Code applies to 16–17 year-olds. bGuru implements the 15 standards: best interests of the child (Standard 1); DPIA for child users (Standard 2 — completed before MVP launch as a non-deferrable obligation); age-appropriate application (Standard 3); transparency in plain language (Standard 4); no detrimental use of data (Standard 5); age-appropriate policies (Standard 6); default to highest privacy (Standard 7 — under-18 leaderboard visibility = followers-only; profile = private); data minimisation (Standard 8); no commercial data sharing of child data (Standard 9); no precise geolocation (Standard 10 — city-level only); parental controls scoped to age-band (Standard 11 — lighter-touch given 16+ baseline); no profiling by default (Standard 12); no nudge techniques (Standard 13 — banner reject-as-prominent-as-accept); IoT N/A (Standard 14); age-appropriate online tools (Standard 15).

OSA ss. 11–12 (child safety duties): bGuru applies the substantive duties immediately regardless of category. Self-harm/suicide content moderated against Samaritans Media Guidelines; bGuru signposts Samaritans (116 123) and PAPYRUS HOPELineUK (0800 068 4141) in-app. Formal OSA s. 10/11 written risk-assessment deferred to UK MAU > 100k (good-practice trigger; formal Category 2B trigger at 7M).

§6 Enforcement ladder

Proportionate response, calibrated to severity:

  1. Warning — first violations of minor rules (single comment, minor incivility); in-app notification.
  2. Mute — restricted ability to comment / post / create groups; duration 24 hours, 7 days, or 30 days.
  3. Suspension — restricted access to most features; duration 1 day, 7 days, or 30 days.
  4. Permanent ban — Account closure + IP/device flagging to prevent evasion.

Escalation triggers:

  • Repeat violations within a rolling window
  • Severity of single violation
  • Multi-accounting to evade prior enforcement = automatic permanent ban
  • Threat to physical safety of any person = immediate ban + law-enforcement coordination

Bypass of ladder for Schedule 7 / priority illegal content: CSAM (zero tolerance, no appeal), terrorism content per Directive 2017/541 Arts. 2–14, grooming behaviour, credible threats of violence, intimate-image abuse — ladder skipped, immediate permanent ban + law-enforcement referral per §4.2–§4.5.

§7 How to appeal a decision

§7.1 EU users — DSA Art. 20 internal complaint-handling

EU/EEA users have the right to appeal any moderation decision (other than CSAM-related — see exclusion note below) via:

  • Email: legal@bguru.app, subject "DSA Appeal" (an in-app appeal flow will ship in a future version of the Service)
  • In-app (future): Settings → Help → "Appeal a moderation decision"

Both channels are free of charge, available to all users including those whose Account has been suspended or terminated, in line with Art. 20.

Time to lodge a complaint. You have at least six months from the date you are notified of the decision (per DSA Art. 16(5) or Art. 17) to lodge a complaint through this system — the minimum period DSA Art. 20(1) itself requires, and longer than the 30-day window described for users generally in §7.2.

Appealable decisions: content removal, demotion/restriction, mute, suspension, termination, any access-restriction resulting from moderation.

Not appealable via Art. 20: CSAM-related account terminations (the removal obligation arises directly from EU + member-state criminal law — judicial remedy available, but no internal appeal). Sexual offences involving minors equally outside Art. 20 scope.

Process per Art. 20(4):

  • Acknowledge receipt within 48 hours.
  • Process diligently, non-discriminatorily, non-arbitrarily.
  • Reasoned decision within 14 days of receipt of complete complaint.
  • Original decision upheld → explain why. Reversed → reinstate content/account without unreasonable delay.

Out-of-court dispute settlement (Art. 21): certified bodies under each member state's Digital Services Coordinator. List of certified bodies at bguru.app/legal/dsa-dispute-bodies; for the EU-wide registry see also the European Commission DSA portal at digital-strategy.ec.europa.eu/en/policies/digital-services-act-package.

Digital Services Coordinator: users may lodge complaints directly with the DSC of their member state under Art. 53.

Right to judicial remedy preserved per Brussels I bis Reg. (EU) 1215/2012 Arts. 17–19 and ToS §15.3.

§7.2 All users — universal appeal process

Outside of DSA Art. 20 (which is EU-specific), bGuru offers the same appeal process to all users as a matter of policy:

  • Submission: email legal@bguru.app subject "Appeal" (an in-app appeal flow will ship in a future version)
  • Time to submit: 30 days from the date you are notified of the decision (not from the decision itself, in case you did not see it right away)
  • Required info: account email, decision being appealed, reason, supporting context
  • bGuru response: reasoned decision within 14 days

If you're unsatisfied: UK → Ofcom complaint (separate from Art. 20-equivalent); rest of world → local consumer-protection or data-protection authority depending on the nature of the dispute. Right to seek judicial remedy preserved per ToS §15.

§8 Examples (borderline cases)

To help users + future moderators reason about edge cases:

Scenario Outcome Reasoning
Sarcastic comment disagreeing with another user's pick Warning (minor incivility) Healthy disagreement is fine; sustained pattern would escalate
User calls another user a slur in a group Immediate suspension + appeal available Hate speech category; ladder bypassed for severity
Script that submits picks based on bookmaker odds Suspension (automation prohibition) Appeal can include "I'll stop using the script"; reinstate on compliance
Second account created because user forgot password Warning + account-merge process Unintentional multi-accounting; not enforcement-evasion
Satirical group called "Pelé for WC 2026 MVP" No violation Political/sport satire in good faith is fine
User posts affiliate link to a sportsbook in a comment Permanent ban (zero tolerance — off-platform gambling solicitation) §3 specific prohibition; protects non-gambling classification
User contests a moderation decision they think was wrong Email legal@bguru.app within 30 days of being notified (EU/EEA: at least 6 months, DSA Art. 20(1)); in-app appeal flow ships in a future version Standard appeal flow; reasoned response within 14 days
Content reported as defamation (Israeli user about another Israeli user) bGuru reviews + may remove facially defamatory content; for contested cases, requires Tel Aviv District Court order per §4.4 Israeli defamation = civil matter; platform-liability framework per CA 1239/19
Content depicting violence to children Immediate permanent ban + NCMEC + national CSAM authority CSAM-adjacent; zero tolerance; no appeal
Adult user persistently messaging a 16-year-old user with personal questions, off-platform-contact requests Immediate suspension + report to relevant child-protection authority Grooming-pattern detection; bypasses ladder

§9 Children's safety

§9.1 Coordinator framing

bGuru's flat global minimum age is 16 (see Terms of Service, §3 Age eligibility, and Privacy Policy, §9 Children's data). bGuru does NOT knowingly collect data from any user under 16. If discovered:

  • Under 13: immediate hard-delete per COPPA standard (US federal floor) — no 30-day grace period, no parental-consent option, account permanently closed.
  • 13–15: same immediate-deletion treatment per bGuru's contractual gate, without the COPPA-specific COPPA immediate-deletion timeline.

16–17 users: receive the same data-minimisation + no-behavioural-targeting treatment globally as a max-protection posture.

§9.2 United States — COPPA hard-block + state minor laws

COPPA (15 U.S.C. §§ 6501–6506; 16 CFR Part 312) prohibits collecting personal information from under-13s without verifiable parental consent. bGuru's 16+ gate is designed so COPPA's VPC obligations are never triggered. On actual knowledge of an under-13 user (16 CFR § 312.3): immediate suspension + permanent deletion (no retention) + parental notification if contact info available + refund any inadvertent paid-tier charge. No VPC pathway exists — under-13 accounts are permanently closed.

State minor-data laws (under-18):

  • California KOSMA (Cal. Civ. Code § 1798.99.29 et seq., 2025) — bGuru's gated push-notification opt-in + no algorithmic feed = not currently a "social media platform" under KOSMA's addictive-design definition. Re-evaluate on feed activation.
  • NY SAFE for Kids Act (N.Y. Soc. Serv. Law § 496-a) — same analysis.
  • Maryland MODPA (Md. Code Com. Law § 14-4604(c)) — no advertising of any kind is active at this version of the Service, which trivially satisfies MODPA's targeted-advertising and profiling prohibitions; bGuru's forward no-behavioral-advertising posture + no-profiling-of-under-18 commitment (see Cookie & Ad-Tech Policy §7) continues to satisfy it if advertising is ever reintroduced.
  • Colorado CPA (C.R.S. § 6-1-1306(4)) + UOM honouring per § 6-1-1315.
  • Florida HB 3 (Fla. Stat. § 501.1736 et seq.) — bGuru not currently a "social media platform" under HB 3's algorithmic-feed definition. Re-evaluate on feed activation.

Federal KOSA / KOSPA (Pub. L. 118-186, signed Dec 2024) — duty of care for platforms accessible to minors + default protective settings for under-17s + prohibition on targeted advertising to under-17s without parental consent. bGuru's posture (no addictive feed + no advertising at this version of the Service + protective defaults) satisfies the statute as written; review against final FTC rules when published.

Grooming under 18 U.S.C. § 2422(b): zero tolerance + immediate ban + NCMEC + FBI IC3 referral.

§9.3 United Kingdom — Children's Code 15 standards + OSA s. 11–12

ICO Children's Code applies to 16–17 users (Code defines "child" as under-18 per DPA 2018 s. 123(1)). bGuru implements all 15 standards (see §5.3). DPIA addendum for child users completed before MVP launch (non-deferrable).

OSA ss. 11–12 priority harm categories for children: CSAM (zero tolerance + CEOP); grooming (immediate review + suspension on grooming-pattern indicators + CEOP ThinkUKnow signposting via in-app help at thinkuknow.co.uk); self-harm/suicide (24-hour priority moderation + Samaritans Media Guidelines + crisis-support signposting via Samaritans 116 123 and PAPYRUS HOPELineUK 0800 068 4141); violent threats involving children (24h target + police referral 999/101 by imminence).

Max-protection defaults for 16–17 UK users: leaderboard visibility = followers-only (not user-overridable to less protective by bGuru/groups); profile visibility = private; no advertising is served to any user at this version of the Service, and no targeted advertising will ever be served to under-18 users at any future version; no DMs at MVP; no default-on push notifications.

Crown Dependencies (Isle of Man, Jersey, Guernsey, Gibraltar) — bGuru applies the same Children's Code standards by policy.

Ofcom complaints: ofcom.org.uk/online-safety/reporting-concerns — separate from §7 internal appeal; no requirement to exhaust internal process before Ofcom complaint.

§9.4 European Union / EEA — DSA Art. 28

GDPR Art. 8 default consent age (16) satisfied by bGuru's 16+ gate across all EU/EEA member states.

DSA Art. 28(2) obligations applied at MVP:

  • No profiling-based advertising to minors — at this version of the Service, no advertising of any kind is served to any user, which trivially satisfies this obligation. If non-personalized contextual advertising is reintroduced in a future version (see Cookie & Ad-Tech Policy §3), it will carry no behavioral profiling; the hard "no behavioural advertising to under-18" constraint applies at all versions of the Service, permanently.
  • No algorithmic recommendation directed at minors — bGuru does not operate an Art. 27 recommender system at MVP. If recommendation systems are introduced later, under-18 users excluded from profiling-driven recommendations + default non-personalised view per Art. 28(1)(b).
  • Age-appropriate design defaults — same max-protection defaults as UK (private profile + followers-only leaderboard + DM-from-unknown confirmation).

CSAM: Directive 2011/93 Art. 25 + DSA Art. 28(3) + criminal law of every member state = immediate removal + NCMEC + INHOPE.

§9.5 Israel + Rest of world

Israel: bGuru's 16+ gate + max-protection treatment for 16–17 users exceeds Israeli legal requirements (no standalone Israeli children's online-design code at MVP). Grooming-pattern detection triggers Lahav 433 referral. No private DMs at MVP eliminates the primary grooming risk-vector.

Rest of world — calibrated 16–17 parental-consent gap (calibrated-risk acceptance per Privacy Policy §9.1):

  • South Africa (POPIA s. 35) — parental consent for under-18 generally required.
  • UAE (PDPL Art. 8) — same.
  • Mexico (LFPDPPP + civil code) — same.
  • LATAM cluster (AR/CL/PE/CO) — comparable parental-consent requirements under each national framework.
  • MENA cluster (SA/EG/MA/QA/KW) — comparable.

The 16+ gate eliminates the gap for under-16s. For 16–17 users in these jurisdictions, bGuru's no-behavioural-targeting + no-payments-required + data-minimisation posture provides substantive mitigation; the formal parental-consent infrastructure gap is documented as calibrated-risk acceptance (Privacy Policy §9.1) and will be closed at v1.1 alongside the parental-consent provider integration (k-ID / PRIVO / SuperAwesome KWS / Yoti shortlist).

Australia — not available at this version of the Service. The Online Safety Amendment (Social Media Minimum Age) Act 2024 set its own operative minimum age at 16 (commenced 10 December 2025, not "end of 2026" as this document previously stated) — the same number bGuru's own baseline already uses — but matching the number does not, by itself, resolve whether bGuru is available in Australia. Two separate questions govern: (a) whether bGuru is a service covered by the Act's "age-restricted social media platform" definition at all, a test that turns on the service's own purpose and self-description rather than its declared minimum age; and (b) if covered, whether self-declaration of age — including the honest, server-enforced date-of-birth mechanism this version of the Service uses — satisfies the Australian eSafety Commissioner's binding "reasonable steps" compliance standard, which does not treat self-declaration as sufficient on its own, at any declared age. Because both questions remain open, bGuru does not make the Service available to Australian users at this version. Unlike Brazil/India below, Australia's gap is not a parental-consent gap and will not be closed by the same parental-consent-provider integration — it needs its own resolution (a coverage determination and, if covered, a compliant age-assurance mechanism beyond self-declaration). See Terms of Service §3 and Privacy Policy §9.4 for the full analysis.

South Korea: Youth Protection Act under-14 — bGuru's 16+ gate exceeds.

Brazil + India + Australia (deferred markets, v1.1): Brazil (Digital ECA Law 15.211/2025) and India (DPDP Act 2023) require parental consent for under-18; bGuru is not available in either market at MVP because the verifiable-parental-consent infrastructure required by both laws has not yet been integrated. Australia is deferred for the different reason stated in its own paragraph above (an age-assurance-method/coverage question, not parental consent). All three markets are targeted for v1.1.

§10 Changes to these Guidelines

Substantive changes to the moderation rules in §2, §3, §6, or the appeal mechanism in §7 are treated as material changes and follow the 30-day notice flow described in Terms of Service, §16 Changes to these terms, and Privacy Policy, §11 Changes to this Privacy Policy. Non-substantive changes (typos, clarifications, examples, link updates) may be published without 30-day notice; the last_updated date in the document header is the controlling indicator.

Specific triggers for amendment include: introduction of algorithmic content-recommendation feed (DSA Art. 28 + KOSMA + NY SAFE + FL HB 3 + OSA s. 12 — all simultaneously engaged); introduction of direct messaging (grooming-risk + Children's Code re-evaluation); introduction of paid Premium-Tipster tier (refund + ARL + Tipster Contributor Agreement); UK MAU crossing 100k watch threshold (internal OSA risk-assessment); crossing any state minor-data law's effective date.

EU/EEA users (DSA Art. 12): right to terminate Account during 30-day notice period without penalty.

§11 Contact us

For any concern about content, moderation, or these Guidelines:

Email: legal@bguru.app (for appeals: subject "Appeal", within 30 days of being notified of the decision; EU/EEA users have at least six months — see §7.1) In-app: Settings → Help → Contact Us

We respond within one month per GDPR Art. 12(3) and equivalent obligations, and faster on urgent matters. CSAM-related reports are actioned same-day.

Sole-proprietorship posture: bGuru is currently operated as a sole-proprietorship project of an Israeli resident (see Privacy Policy, §2 Who we are, and Terms of Service, §17.1 Controller identity). The founder is the sole moderator at MVP.

§12 Changelog

Version Effective date Changes
0.1.13 2026-08-22 The appeal-submission window is unified at 30 days, and four other gaps found in the same review are closed. Founder decision, verbatim: "i prefer 30 days or as long as we legally can." This document had been self-contradictory: §0, the §8 examples table, and the §11 contact block all said 14 days, while §7.2 already said 30 — nobody could have told from reading this document alone which number governed. Unified on 30 (the longer, more user-favorable figure) at all four sites, with the trigger event corrected at the same time from "the decision date" to "the date you are notified of the decision" — a decision you never saw cannot start a clock you're expected to beat, and this document does not promise email delivery of decisions (see the third item below), so a notified-from trigger is the only one that is actually fair. EU/EEA users now get an explicit number in §7.1: at least six months from notification, the minimum DSA Art. 20(1) itself requires (verified against the statute's own text, not assumed) — longer than the 30-day universal window, exactly as the founder's "or as long as we legally can" instructed. Treated as a non-material, user-favorable clarification published immediately without the §10 30-day material-change flow: it resolves an existing internal contradiction and only ever lengthens a window, never shortens one. Second: §4.1 categories 7 (copyright) and 8 (other) now state they fall under the same 7-day standard review window as categories 2–5 (§5.1), matching the in-app toast; previously they carried no stated window at all. Third: §5.2's "Statement delivery" no longer promises email. bGuru has no outbound-email capability (Cloudflare Email Routing is inbound-only); the paragraph now describes the true mechanism — a durable in-app notice, held as server state, the same pattern already used for the age-gate block (Privacy Policy §9.1) — and carries a publication-hold comment against the server/client rollout gap (server live now; the client screen ships in the next app-store release). Fourth: a new §5.1 bullet states, for every user and not only EU/EEA ones, that a CSAM-pending suspension's in-app notice withholds the specific reason, consistent with the Terms of Service §9 carve-out for decisions that would "interfere with an ongoing investigation." Fifth: §0's stale "see §5.2" cross-reference to the EU appeal mechanism, corrected to §7.1 — §5.2 is the Statement-of-Reasons content requirement, not the appeal process; the actual DSA Art. 20 mechanism and its window live in §7.1. No right or protection was reduced by any of these five changes. Companion changes in the same review: Terms of Service 0.1.18, Privacy Policy 0.1.20.
0.1.12 2026-08-17 Five stale Terms-of-Service cross-references corrected. The Terms of Service gained a new §11 (Third-party intellectual property) in an earlier release, which shifted every later section down by one — Geographic restrictions §13→§14, Governing law §14→§15, Changes §15→§16, Contact §16→§17 — but inbound cross-references were never updated. Each pointer below therefore sent readers to a real but wrong section. No right, obligation, or disclosure changed; this is a navigation fix. Fixed: §7.1 EU judicial remedy ToS §14.3→§15.3; §7.2 judicial remedy ToS §14→§15; §1 material-change pointer ToS §15→§16; §10 material-change pointer cited as "§15 Changes to these terms" →§16 (the cited number and the cited title disagreed, which is what surfaced the whole class); and §11 controller identity ToS §16.1→§17.1.
0.1.11 2026-08-17 §9.5 Australia correction, found by the 5-specialist debate round on the age-gating research-completion pass — the highest-priority published-document finding in that round. §9.5 stated "bGuru's 16+ gate satisfies natively" for Australia — the exact overclaim the ToS v0.1.14 / Privacy Policy v0.1.13 Australia fixes were written to remove, left uncorrected in this document for over two months (the third time this document pair — this file and Cookie & Ad-Tech Policy — has fallen through separate "Affects" tracking on an age/market-availability question: the 2026-06-08 AdMob removal, then Israel's §7 content-suitability gap, now Australia). Rewritten to state plainly Australia is not available, matching the ToS §3 / Privacy Policy §9.4 treatment; the Act's own commencement date corrected from a stale "end-2026" framing to its actual 10 December 2025 commencement; Australia added to the deferred-markets list with a note distinguishing its gap (an age-assurance-method/coverage question) from Brazil/India's parental-consent gap. No change to the 16-year minimum. Full debate record: docs/legal/_research/_history/debate-global.md Conflict 6, Tier 1 item 1.
0.1.10 2026-08-11 Completed the 2026-06-08 advertising-posture correction — this document's own pass was incomplete. The 2026-06-08 update (v0.1.9, below) removed the stale AdMob reference from §3's off-platform gambling solicitation clause, but three other present-tense AdMob/advertising references survived unnoticed in §9.2 (Maryland MODPA, Federal KOSA/KOSPA), §9.3 (UK max-protection defaults), and §9.4 (EU DSA Art. 28 minor-profiling bullet) — all still described bGuru as currently serving non-personalized contextual ads via Google AdMob NPA mode. All four now state plainly that no advertising of any kind is served at this version of the Service, with the NPA/no-profiling commitments recast as conditions that apply if and when advertising is reintroduced. No under-18 protection is weakened by this correction — if anything the position is stronger, since it no longer depends on NPA mode's non-profiling nature. Companion corrections in the same pass: Terms of Service v0.1.11 and Cookie & Ad-Tech Policy v0.1.10 (structural rewrite — that document had never been corrected at all).
0.1.9 2026-06-08 Removed reference to bGuru's own Google AdMob ad placements from the off-platform gambling solicitation prohibition (§3). At this version of the Service no advertising is active; the AdMob SDK was removed from the MVP codebase on 2026-06-08. The off-platform gambling solicitation ban is unchanged and absolute.
0.1.8 2026-06-03 Added §3 prohibition on misuse of third-party trademarks — covers false-affiliation use of club crests, competition marks, and player identity in user-generated content. Ordinary fan commentary and descriptive uses explicitly permitted. Cross-references the new ToS §11 Third-party intellectual property section.
0.1.7 2026-06-02 Collapsed the public changelog's pre-launch drafting iterations into a single summary entry for clarity.
0.1.6 2026-06-02 Updated Maryland MODPA reference (§9.2) to 'no-behavioral-advertising posture'. Softened moderation-appeal mechanism (§0, §7) to describe the email-based channel currently available; in-app appeal flow noted as shipping in a future version.
0.1.5 2026-06-02 'Contextual sponsorship ads' replaced with 'non-personalized contextual ads served through Google AdMob' (§3).
0.1.4 2026-06-02 Clarified that bGuru's own non-personalized contextual ads (Google AdMob) are distinct from the off-platform gambling affiliate links users are prohibited from posting (§3).
Pre-launch drafting iterations 2026-05-30 → 2026-06-01 Multiple internal drafting iterations during the pre-launch review period. The substantive provisions described above were drafted, refined, and consolidated through this period.