Privacy Policy
terms-2026-10-26-v1
Personal data collector and contact information
Operator: 徐登昱 (an individual in Taiwan). Residential address supplied, retained verbatim in Chinese: 台灣省桃園市蘆竹區南山北路二段422號. Contact: contact@kendomonster.com.
The personal data collector for Kendo Monster is 徐登昱. Personal data requests: contact@kendomonster.com.
Privacy Policy
Account and activity data are used for sign-in, judgments, discussions, submissions, notifications, member benefits and safe operation. Display names, appearance and public comments may be visible to others; email addresses, private preferences and individual judgments are not public information for ordinary members. The platform does not promise absolute anonymity. Email and sign-in authentication are handled by Supabase Auth; passwords are not public profile fields. Do not share passwords or recovery links.
Public data includes your public profile identifier, display name, avatar/Monster appearance, available joining date, public comments/replies and their timestamps. Where enabled, crown collections show genuine ownership, acquisition source and date, and the equipped crown. A name or comment you choose may identify you. Country is shown only through an explicit public-display setting where supported; private country settings are not automatically public.
Private member data includes self-reported rank, protected verified rank/status, country/region and optional kendo experience. Self-report is not verification. These are used for member settings and supported statistics, not public rank badges. A platform field for verification does not mean a public verification application service is available.
Individual member judgments and vote-time snapshots are not publicly shown to other ordinary members. The first finalized judgment is locked. The platform uses controlled statistical releases to reduce inference from its own outputs, and does not send suppressed raw counts to clients. Results may be delayed or show data accumulating. Agreement is not an official ruling or an accuracy score.
We do not promise absolute anonymity. Other people voluntarily revealing votes, collusion or information obtained outside the platform can enable inferences despite these controls. Authorized operational access is distinct from ordinary public access.
Visible comments and replies are public. Editing changes the visible text; author deletion displays a placeholder and preserves the thread, and is not a promise of immediate erasure from all storage. Pending/rejected submissions are private to their owner and authorized reviewers; approved published Moments are public. Reports, reporter identity, moderator authorization and operational notes are not public member attributes.
Notifications are private to their recipient. Membership entitlement sources and periods, personal analysis and collections are private member features. Paid/Gift structures do not mean billing is active. Crown ownership does not grant Monster+ or moderation authority.
Necessary session cookies support sign-in and safety; language preferences use a cookie/local browser storage. Local demo storage is separate from real member data and is not silently imported. Authentication/hosting providers may process connection and security logs. Vote snapshots do not store IP, user-agent, referrer or experience free text. We do not claim that infrastructure never processes such technical data.
Loading the YouTube player connects to YouTube/Google. Even in privacy-enhanced mode, technical information such as IP addresses and browser information may be processed under their policies. Supabase provides authentication and database services; Vercel provides website and server-side hosting; Cloudflare provides DNS and designated email forwarding; Google provides the receiving mailbox and YouTube services. Data is transmitted, stored, queried and processed for necessary security according to these purposes. Recipients include the operator and service providers needing access, and authorities or other recipients where legally required; public content is also visible to readers. The confirmed Supabase project hosting region is Tokyo, Japan. This does not mean all processing is in Japan: CDN, logs, support, email, providers and subprocessors may process data in the United States and other service locations. External services also have their own policies; we do not promise processing in one country only.
After identity verification and when the case conditions are met, a limited copy of account data, the public profile and private preferences can be obtained. This does not include all data or mean that the entire personal-data request has been fulfilled; other data, correction, restriction or deletion still require individual handling. Applicable statutory deadlines for decisions to approve or deny requests and for notifications are not limited by the service’s lack of a guarantee of immediate completion. Existing controls allow supported profile settings and your own visible comments to be edited. Appendix A lists the full limited-copy exclusions and procedure. There is no self-service account deletion or automatic completion of every request; that does not remove duties to handle applicable legal requests.
Adult self-declaration and consent to a specified terms version are separate private records linked to the member account, with server-recorded times. No date of birth is required, made public, or used in judgment statistics. Self-declaration is not legal age verification. Existing members must complete the current confirmation before participating.
If data is not provided: without necessary email, sign-in information and adult / terms confirmation, member functions cannot be created or used. A display name is needed for member presentation. Country/region, self-reported rank and kendo experience marked optional may be omitted, affecting related display, preferences or supported statistics; they must not be treated as verified rank. Do not put school, address, phone, health or other people's private information in optional fields. Without loading the external player, embedded playback is unavailable; where a source link is provided, you may decide whether to visit it.
Retention follows the categories and necessity criteria below, not a promise of unimplemented automatic cleanup. When a service, content, benefit or case ends, review whether the original purpose continues. If no longer necessary and no applicable retention reason remains, handle deletion or cessation of processing/use as required by law. Statistics, backups or pending technical features alone do not justify indefinite retention of identifiable data.
Back to contentsRetention categories and criteria
| Category | Retention and handling criteria |
|---|---|
| Account, contact, public profile and private preferences | retain as necessary to provide membership services. On termination, review outstanding matters and necessary evidence; remove or stop using unnecessary parts. Prior account existence is not a reason for permanent retention. |
| Sessions, authentication and security records | handle according to validity, expiry and revocation mechanisms. Necessary security-event data is limited to detecting, investigating and preventing abuse. Do not request or keep passwords, OTPs or recovery secrets in ordinary case records. |
| Age declarations and policy consent | retain as needed to provide service, prove the applicable version and resolve related disputes. Preserve necessary version/time evidence without overwriting history or permanently retaining all associated personal data. |
| Sources, submissions, comments, judgments and statistical history | use while content/discussion and lawful review, rights or consistency needs continue. On removal, archiving or closure, review whether identifiable data remains necessary. Locked votes and statistical consistency do not authorize permanent identity links. Hiding, archiving or a comment placeholder is not physical erasure. |
| Notifications, member benefits and crowns | retain as needed to provide them or settle outstanding matters. Read status or Plus expiry does not mean all evidence can immediately be removed, nor permit indefinite retention. Independent crown eligibility is not automatically revoked by payment cancellation. |
| Requests, reports and safety cases | retain as needed for receipt, verification, handling, lawful notice and necessary dispute handling. Prefer conclusions, times, scope and necessary reasons over unnecessary original documents. |
| Backups | only for necessary recovery and lawful retention, not expanded routine use. No uniform 30-day rotation or immediate erasure of all backups is promised. After recovery, legally deleted or restricted data must remain subject to the same treatment and must not become public again merely because it was restored. |
| Browser submission drafts | current functionality stops automatic refill more than seven days after the last save. This does not guarantee physical deletion on day seven. Browser clearing, private mode or device differences may also make drafts unavailable. |
For a specific unresolved dispute, lawful investigation or other applicable retention duty, retain only the necessary data and scope, record the reason, and review when it ends; exceptions do not extend every category indiscriminately. Exact provider log, email and backup periods have not all been verified. This policy invents neither fixed days nor instant deletion. Requests remain available through the contact channel; individual handling and applicable limits should be explained, and unverified periods must not become a reason to refuse handling.
Back to contentsAppendix A — Requests and limited copies
Applicable rights may include access/inspection, copies, supplementation/correction, stopping collection/processing/use and deletion. Write to contact@kendomonster.com with the category, broad scope, reply method and necessary related URLs. Do not send passwords, OTPs, recovery codes or full identity documents in advance; do not post private evidence publicly.
On receipt, identity and scope are checked as necessary. If sign-in access is lost, normal account recovery is considered first, with secrets entered by the person only in the official interface; manual review may be necessary. Ability to send email, a public name/ID or familiarity with content alone is not presumed sufficient. If identity cannot be established, no data is delivered and no account changed; explain safe next steps or the result under the applicable procedure, rather than suspending the request indefinitely.
After verification and when the case permits, the current download covers account, public profile and private preferences only. It excludes judgments, submissions, comments, notifications, payments, collections, consent history, case evidence and authentication secrets. This describes the tool's output, not a waiver of other rights. Other personal data, mixed third-party content and internal evidence require case-specific scope and redaction review; complete rows are not automatically delivered and not every original document is promised.
The operator currently receives and reviews personal-data requests manually. There is no self-service account deletion, automatic cleanup or automatic completion of every request. A limited copy does not fulfill the entire request; tool scope or ongoing identity checks cannot justify restricting legal rights or indefinite delay. Deletion, stopping use and archiving have different effects. Cases needing technical work are still handled under applicable law, with notice of the result or applicable limitations. The statutory decision granting or denying a request and technical completion are distinct: neither substitutes for the other or permits arbitrary delay of technical work. Applicable decision deadlines, reasons for extensions and notice duties remain unaffected by the absence of instant completion. Copies contain personal data; keep them safe.
Back to contentsContact and requests
Describe your request at contact@kendomonster.com. Do not send passwords or verification codes, provide complete identity documents in advance, or post private evidence in public comments. After receiving a request, we verify the requester’s identity through necessary procedures; if identity cannot be established, we do not disclose data or change the account. The same contact handles privacy, content-rights and reconsideration requests. Include the request category and necessary related URLs. In-product reports do not replace rights requests; receiving an email does not establish identity or completion.
