Community guidelines: useful questions and private information
The Cyberlytics Community works best when people can ask a straightforward question and receive a respectful, useful answer. These guidelines apply to topics and replies, whether you are a business owner, a client, a developer, or someone exploring an idea.
Give context and respect other members
Describe the result you want, the website or workflow involved, and what you have already tried. Keep each topic focused enough for readers to follow. When replying, explain why your suggestion fits the situation and acknowledge any tradeoff. Disagreement is welcome when it addresses the idea; harassment, discrimination, threats, and personal attacks are not.
Keep private work in private channels
Never post passwords, login links, recovery codes, access tokens, payment details, customer records, or confidential project material. Check screenshots and copied messages for names, email addresses, order references, and other details that do not belong in a public discussion.
For help with your own Cyberlytics project or account, use private dashboard support when available. If you cannot access your account, use the public contact page to explain the problem without sending passwords or security codes. The forum is not a place to exchange credentials or arrange a private account reset.
Be accurate about advice and promotion
Separate personal experience from a verified fact or an assumption. Avoid promises about rankings, revenue, security, or delivery times that you cannot support. If you recommend a product or service you sell or represent, disclose that relationship. Links should help answer the question; repeated sales pitches, copied posts, deceptive links, and automated spam may be removed.
Report problems without spreading them
Use the Report link on a topic or reply that needs moderator attention. If a post exposes private information or a live security issue, report it without quoting the sensitive material. Moderators may edit, close, or remove content to protect members and keep the community useful.
Unsure how to describe a problem safely? Ask what general context would help before posting the details.