1. Scope
This policy applies to CRYA Bot community features, reports, filters, greetings, deleted-account scanning, moderation actions, federation observations and enforcement, group audit records, and safety-related support. It supplements the Terms and Privacy Policy.
2. Group owner and administrator role
Telegram group owners set the community rules and decide which authorised CRYA controls apply. Administrators must use the least intrusive effective action, review context, protect member information, and keep a fair challenge route for significant decisions.
CRYA verifies role where possible before allowing group changes. Premium access does not create administrator authority. A group’s own rules cannot authorise unlawful conduct or remove a person’s applicable rights.
3. Conduct CRYA services must not be used to support
CRYA may restrict use connected to serious abuse or illegality.
- Child sexual abuse material, grooming, sexual exploitation, trafficking, or content that endangers a child.
- Credible threats, promotion of terrorism, targeted harassment, stalking, doxxing, or non-consensual intimate material.
- Fraud, scams, malicious impersonation, credential theft, malware, extortion, or coordinated spam.
- Unlawful discrimination, retaliation through moderation tools, fabricated evidence, or federation records used to harass.
- Attempts to bypass permissions, mass-enforce unreviewed external data, exploit duplicate actions, or conceal the source of an enforcement decision.
4. Reports and evidence
Where reports are enabled, a group member may submit the available report command or flow. Reports should include the relevant message or behaviour and must not expose unrelated private data. A report is an allegation for review, not proof by itself.
Group administrators should preserve the reason and action reference, avoid public humiliation, and remove unnecessary evidence after the purpose ends. CRYA Support handles product or data issues; it is not a substitute for emergency services or Telegram’s illegal-content reporting channel.
5. Filters and automated actions
Configured filters, spam rules, deleted-account signals, and federation matching may automatically warn, restrict, remove, or suggest an action. Owners must understand the chosen mode. Moderation can remain on while federation enforcement remains off.
An automated result can be incomplete or wrong. Significant actions should have a visible reason and review path. CRYA may add rate limits, confirmation gates, or disable a broken automation to prevent repeated harm.
6. Federation visibility and enforcement
CRYA may show that a user appears in CRYA or an external federation source, with source attribution and the available reason. Read-only federation mode allows awareness without automatic enforcement. External imports must detect duplicates and must not create repeated bans or repeated public log entries.
Owners who enable enforcement are responsible for choosing the policy and reviewing disputes. CRYA may correct a source mapping or duplicate record when evidence shows it is technically wrong; it does not rewrite another federation’s decision without authority.
7. Review and appeal
For a group action, first contact the group owner or administrators and identify the action, reason, date, and relevant message. For a CRYA federation record, imported-source issue, privacy concern, or product malfunction, open a CRYA Support case.
CRYA may ask for identity or authority verification, review audit evidence, correct technical errors, preserve lawful records, or explain why a request cannot be granted. Retaliation against a person for a good-faith report or appeal is prohibited.
8. Minors and age-appropriate settings
CRYA community-management products are not directed to children under 13. Group owners should consider the age and context of members, enable proportionate privacy and safety defaults, avoid manipulative engagement, and restrict adult-leaning Grow Game humour where unsuitable.
9. Urgent danger and illegal content
If someone may be in immediate danger, contact local emergency services. Report illegal content or account abuse to Telegram using its available tools. Contact CRYA as well when CRYA Bot or CRYA-held data is involved, but do not delay an emergency report while waiting for a support response.
10. Transparency and changes
CRYA records relevant administrator actions and product events so errors and abuse can be investigated. Public transparency must not expose victims, private evidence, security details, or personal data unnecessarily. Material changes to this policy will be versioned and dated.