Skip to content

A place to learn, not to judge

Community guidelines

A few shared promises make this space welcoming to every student.

Ask with context. Answer with care.

Describe your question, what you tried, the exact error, and what you expected. Share code as text between triple backticks. Explain your answers and acknowledge uncertainty. Community answers are peer advice, not an official guarantee.

Be kind to beginners.

No insults, threats, harassment, hate, foul language, unsolicited advertising, scams or repeated spam. Do not impersonate CookieSensei staff. Use Report to flag a problem rather than starting an argument.

Share screenshots, not secrets.

Only upload screenshots you have the right to share. Remove faces, phone numbers, emails, access tokens, passwords, payment details and personal documents. Maximum two non-animated PNG, JPG or WebP files, up to 3 MB each. We resize and re-encode images and remove metadata; this does not redact visible private information. All screenshot posts need moderator approval.

Anonymous to readers, not untraceable.

No login is needed for anonymous participation. An essential signed browser cookie identifies your posts for 30 days; clearing it or changing devices can remove your ability to find or delete those posts yourself. Email sign-in uses a private, single-use link that expires in 15 minutes. Verified email accounts can post by name or as Anonymous learner. We retain your normalized email privately for sign-in; your email never appears on posts. Community email sessions last up to 30 days and can be ended from Account. Older Google accounts retain their separate account identifier and display name. We do not automatically merge email, Google, anonymous or enrolled-student identities. Moderators can link posts to the same internal identity for abuse prevention. We store hashed client identifiers, which are pseudonymous rather than proof of full anonymity.

Public posts can be copied.

Approved posts and screenshots are visible to anyone. Discussions are marked no-index, but that is not a privacy control. Removing content hides it from our public pages; we cannot erase screenshots, copies or caches held by other people. Essential cookies and data are used for posting, login, moderation and abuse prevention.

How moderation works.

Rule-based filters automatically remove detected spam and foul language from public view. Links and possible secrets are held for review. These English and Hindi/Hinglish rules are not perfect and can miss abuse or flag innocent text. Images are reviewed by a person, not claimed to be automatically understood. Moderators can approve, remove, lock conversations, and suspend posting identities. Reports alone do not automatically delete a post.

Removal, retention and appeals.

You can remove your own posts through My posts. Removing a question hides its answers too. Hidden text and moderator actions remain available for review; removed screenshots may be purged after 30 days by the maintenance job. Verified email/Google account identities and moderation records remain until an approved deletion request is processed. Automatic removals can be appealed. Anonymous bans are not a guarantee against someone returning with a new browser or network.

For moderation appeals or personal-data removal, contact CookieSensei and include the post link. Never send a password or sign-in token. See the site privacy policy.

I’m ready to ask ↗