Privacy Guide

Junkuchan is a public website. There are no private posts. Assume all posts made are instantly archived by a third-party.

Don't post things online that you wouldn't want to have saved forever on a web archiving service.

Hidden, invite-only, and VIP boards should be considered novelties—not private spaces. Assume all boards are accessible to the public.

Be aware of what information in your posts may reveal about you. Using or reusing pseudonyms, posting media you've posted elsewhere, or including details about where you live and work could be used to identify you. Minor details, such as habitual post times and dialects (e.g., American English spelling, local slang, or grammatical quirks) could also be exploited to deanonymize and target you. Be especially cautious about posting your own media, as details or features could be used to identify where your photo or video was taken. While metadata (Exif data) is stripped from uploaded images, this feature should be treated as a nicety and not a reliable safeguard.

Everyone can see all posts, including the poster's chosen name, time posted, and all attached files. Everyone can also view board moderation logs.

Everyone can see staff account names when they perform moderation actions. Staff can choose to hide their account names when editing posts.

Board Staff: All staff members can see a hashed version of a poster's IP address and can therefore browse their post history for the last seven days. They can also do the same for bans and reports.

Site Owner: The webmaster can see raw IP address on posts and reports, and can view a poster's sitewide post history until their IP address irrevocably pruned after seven days. Additionally, the webmaster can view the web server logs (e.g., Nginx, Apache), which are retained for seven days. These logs can contain raw IP addresses, user agents, requested URLs, and timestamps.

Posters are encouraged to access Junkuchan through Tor via the onion service. VPNs may also be used, but they could be blocked from posting to prevent abuse.

Visitors who have logged into an account (such as staff) receive a login cookie named connect.sid.

When you load a captcha, your captcha ID is stored in a cookie named captchaid.

When block bypass is enabled on a board, your bypass ID is stored in a cookie named bypassid.