Fair Play Code
Integrity-first learning on an education-only platform
PlayTribe is a free, text-only learning site for adults 18+. We do not enable or facilitate monetary features. This Fair Play Code defines how to use our reading content and practice tools responsibly, the behaviors we prohibit, how moderation works, and what happens if rules are broken.
Last updated: 2025-11-12
1) Scope & definitions
Scope
This Code applies to all PlayTribe features: reading content, practice lineup builder, profile, and any community/leaderboard views that may be visible. It supplements the Terms, Privacy, and Responsible Play information by focusing on integrity and behavior.
Definitions (plain)
- Practice tools: text-only builder to plan role-balanced lineups for learning.
- Community views: informational lists or leaderboards; no prizes or rewards.
- UGC: user-generated content such as profile names, notes, or comments (if enabled).
- Cheating: any attempt to unfairly manipulate the site, data, or other users.
2) Eligibility & regional access
Age requirement
Use is limited to adults 18+. Date-of-birth is checked during registration.
Regional restrictions (India)
Access is not available in the following states/UTs and where prohibited by law: Andhra Pradesh, Telangana, Assam, Odisha, Nagaland, Sikkim, Meghalaya, Tamil Nadu. Users are responsible for complying with local rules.
3) Integrity principles
- Education-only: no deposits, prizes, withdrawals, or financial outcomes.
- Respect: no harassment, hate, or personal attacks.
- Transparency: accounts & practice data stored as JSON in .txt files.
- Region: do not use the site from locations where it is restricted.
- Community: informational leaderboards only; no rewards or ranks with value.
- Security: keep credentials private; report suspicious activity.
4) Prohibited conduct (detailed)
- Automating traffic to scrape, overload, or disrupt the service.
- Creating multiple fake accounts or impersonating another person or entity.
- Bypassing access controls, tampering with TXT files, or forging data.
- Uploading or posting abusive, hateful, obscene, or illegal content.
- Advertising, spam, or solicitation unrelated to learning.
- Any attempt to simulate or enable deposits, prizes, cashouts, or “rewards.”
- Sharing private account data (passwords, tokens) or doxxing others.
- Reverse engineering or exploiting security weaknesses.
- Using third-party cheats/bots to manipulate practice tools.
- Coordinated brigading to harass other users or moderators.
Violations may lead to warnings, suspension, or access termination.
5) Practice-tool rules & examples
Rules
- Use builder for role-balance learning only.
- Save notes explaining each selection’s role (anchor, finisher, strike, AR).
- Do not attempt to export or post lineups as “bets,” “tickets,” or financial advice.
- Do not auto-generate or mass-create entries using scripts/bots.
Examples (allowed vs. not allowed)
- Allowed: “Two ARs for flexibility; venue small boundaries.”
- Allowed: “Bowling-heavy mix due to overcast conditions.”
- Not allowed: “Guaranteed profit lineup,” “banker ticket,” “stake plan,” etc.
- Not allowed: Automated scripts to generate or submit practice entries.
6) User-generated content (UGC) & moderation
UGC rules
- Keep language respectful, factual, and learning-oriented.
- No threats, harassment, hate, adult/explicit, or illegal content.
- No personal data of others (addresses, phone numbers, IDs).
- No commercial promotions or affiliate links.
Moderation actions
- Content edits/removals when violating this Code.
- Feature limitations (e.g., comment muting) for repeated issues.
- Account suspension or termination for serious/continued breaches.
- Escalation to legal authorities where required by law.
7) Anti-cheating, rate-limits & audits
Detection & prevention
- Basic rate-limits to prevent flooding and scraping.
- Server logs of IP, user-agent, timestamps for security analysis.
- Integrity checks on TXT JSON structure to prevent tampering.
- Heuristics to detect bot-like behavior patterns.
Audit & retention
- Security logs may be retained for a limited period for investigation.
- Confirmed incidents recorded in a moderation log for consistency.
- Only authorized staff can access logs for the purposes above.
8) Enforcement matrix & appeals
Consequences scale with severity and repetition. Examples:
| Category | Examples | Typical action | Appeal window |
|---|---|---|---|
| Minor misuse | Spammy comments, off-topic promos | Delete content, warning | 7 days |
| Repeated violations | Persistent spam, harassment | Temp suspension (3–30 days) | 7 days |
| Serious breach | Hate speech, doxxing, security probing | Immediate suspension/termination | 14 days |
| Cheating/automation | Bots, mass scraping, data tamper | Termination; logs retained for audit | 14 days |
How to appeal
- Write from your registered email.
- Include username, decision date, and brief explanation.
- Provide any context or evidence you want reviewed.
Review timelines
We aim to review appeals within 10–15 business days. Complex security cases may take longer.
9) Safe-use & wellbeing
Plan sessions
Use short, focused reading/practice windows (30–45 minutes).
Take breaks
Brief breaks every 30–60 minutes help retention and focus.
Reflect
Add one-line rationale notes for each selection; review later against roles performed.
Early warning signs
- Skipping tasks or sleep to keep reading/practicing.
- Irritability when away from the site.
- Hiding usage from family/friends.
Device-level tools
- Do Not Disturb during focus windows.
- App limits / screen time caps.
- Scheduled “focus” modes to silence notifications.
10) Data ethics & security (summary)
What we store
- Account data: name, DOB (18+), email, state/UT, username, hashed password.
- Practice data: text-only lineups, role notes.
- Technical basics: server logs for security/diagnostics.
How it’s handled
- Storage: JSON saved in .txt files on server directories.
- Passwords: one-way hashing (e.g., bcrypt).
- Retention: while account is active and as required by operations/law.
- Access: limited to authorized staff for security/support purposes.
We do not collect or process payment data; the platform is non-transactional.
11) Reporting issues & contacts
What to send when reporting
- Your username and registered email.
- Date/time and a short description of the issue.
- Screenshots or copy of the text involved (if applicable).
- Any steps to reproduce the problem.
Contact details
- Email: support@playtribe.fun
- Phone: +91-855-551-6974
- Address: Play Tribe Private Limited, No 10/2 & 10/4, Richmond Rd, Bengaluru, Karnataka 560025, India
- Grievance Officer (India): To be nominated · grievance@playtribe.fun
For appeals, include the decision date and reason for review.
12) Transparency & versioning
Change log (summary)
- 2025-11-12: Expanded prohibited conduct, added enforcement matrix, clarified appeals, added audit/retention summary.
Legal note
This Code supports PlayTribe’s education-only mission. Breaches may be addressed under this Code and other applicable policies. Serious violations may be referred to competent authorities where the law requires.
Education & simulation only • No fees, payouts, or withdrawals • Adults 18+ • Availability may vary by region