Loading page…
Loading page…
Document ID community-policy-r1-2026-10-17 · consent version community-policy-r1 · effective October 9, 2026 · service addresses corrected October 17, 2026. This document is posted at /legal/community when the community opens.
This document consists of Part 1, the community terms (an addendum to the Terms of Service), and Part 2, community privacy (an addendum to the Privacy Policy). The Privacy Policy summarises community processing; the details follow this addendum. Automatic translation is OFF (COMMUNITY_TRANSLATION_ENABLED=false). Posts are not sent to any translation provider (e.g. DeepL) and there is no overseas transfer for translation. Activity-point values and daily limits, the 90-day notification retention and the number of Honor Roasters (3 per month, ties selected together) are operated as stated in this document.
ID community-policy-r1-2026-10-17 · SHA-256 71bdb582b298009fd5b4a684d0a713d253d91b8573d882f139b0155bd48565f3
Members must not:
The community does not currently provide automatic translation. Posts are shown in the language they were written in, and post content is not sent outside the Company for translation. Enabling translation would require separate notice and any required steps, including disclosure of processors and overseas transfers.
The Company may switch the whole community off when operationally necessary. While it is off, community pages and features are unavailable and stored data is not deleted. When it is switched back on, members continue with their existing data. Roasting, billing and other services are unaffected.
When a member deletes their account, community data is handled under Part 2, Article 5. Comments other members left on the member's posts are deleted as well; other members' own posts remain.
| Category | Items | When collected |
|---|---|---|
| Profile (required) | Nickname, consent version, consent time, SHA-256 hash of the agreed document, created/updated times | Saving the community profile |
| Profile (optional) | Tagline, bio, brand/shop name, equipment brand/model, region, website link, profile image, reading/reply languages, visibility settings (bio, tier, honor participation) | When the member enters them |
| Content | Post title, body, category, brand, model, language; attached images (re-encoded JPEG stored in the database); comment bodies; accepted-answer flag; created/updated/deleted times | Creating, editing or deleting |
| Interactions | Reports (target, reason, resolved flag), blocks, bookmarks, notifications (type, target, read flag; no copy of the text) | Using each feature |
| Activity records | Point awards and reversals; Honor Roaster selection and revocation records | On award or selection |
| Staff audit records | Staff and member account IDs, item IDs, action, reason and time for honor selection/revocation and hide/unhide | On staff action |
| Derived data | Quality tier (computed from the roasting-record quality score and eligible record count; computed on request and not stored, except in the selection record when an honor is awarded) | On view or selection |
The community does not show account email, internal account IDs, payment information or raw roasting records to other members.
The only community data processed automatically by age is notifications (90 days). No period has been set for the other items and no age-based job for them is switched on, so they are kept until an event in the table below (deletion, account deletion, etc.). If the Company sets a period and switches on automatic processing, it posts the revised table before the change takes effect. Classification: content (text, images, reasons written by people), identifiers (account IDs etc.), metadata (times, states, categories).
| Item | Class | Actual handling | Retention |
|---|---|---|---|
| Profile | Content, identifiers | Overwritten on edit; deleted on account deletion | Until account deletion |
| Live posts, comments, images | Content, identifiers, metadata | Kept until the member deletes them or the account is deleted | Until deletion |
| Remaining records of deleted posts/comments | Identifiers, metadata | Content erased immediately; deleted marker, author account ID, board, category, brand, model and times remain | Until account deletion (no automatic job) |
| Other members' comments under a deleted post | Content, identifiers | Not displayed. No period is set and no automatic job is switched on | Until the commenter deletes them or either member deletes their account |
| Content hidden by staff | Content, identifiers | Kept for restoration. No period is set and no automatic job is switched on | Until the author deletes their account |
| Reports | Content (reason), identifiers | Kept whether or not resolved. No period is set and no automatic job is switched on. Deleted when the reporter or the reported author deletes their account | Until the reporter or reported author deletes their account |
| Notifications | Identifiers, metadata | Deleted when the source post/comment is deleted or hidden, or on account deletion. Other notifications are deleted by a daily automatic job 90 days after they were created | 90 days |
| Blocks | Identifiers | Deleted on unblock or when either member deletes their account | Until unblock or deletion |
| Bookmarks | Identifiers | Deleted on removal, when the post is deleted or hidden, or on account deletion | Until removed |
| Point history, honor records | Identifiers, metadata | Reversals and revocations are kept as records; deleted on account deletion | Until account deletion |
| Staff audit records (honors, hide/unhide) | Identifiers, metadata, reason | Staff and member account IDs, item IDs, action, reason, time. No email or IP address is recorded. No minimization or deletion period is set and no automatic job is switched on; records are not deleted when the member deletes the account | No period set (no automatic processing) |
| Backups | All | Privacy Policy Article 4 (backups) applies. Automated backups of the member database (Amazon RDS) are kept for 7 days and then deleted automatically. Manual snapshots taken before maintenance are not deleted automatically and remain until the Company deletes them | Automated backups 7 days; manual snapshots until deleted |
| Error reports | Partial content, identifiers | Privacy Policy Article 7 (Sentry) applies | Sentry default 30 days, backups 90 days |
| Transit processing (Cloudflare) | Identifiers (IP), metadata | Article 6 | Per Cloudflare's own practices (the Company has not verified the retention period) |
Members can change profile fields and visibility settings, edit and delete their own posts and comments, and remove blocks and bookmarks themselves. Other requests for access, correction, deletion or suspension of processing go through the contacts in Privacy Policy Articles 8 and 11.