Privacy policy

Our approach to your information

TubeSaku collects information needed to provide and improve its services, respond to inquiries, and prevent misuse. The details below explain how information is handled for each feature.

Collection & use

We may collect cookies, access logs, and other information to the extent necessary for support and service improvement. Collected information is used only to provide and improve the service and prevent misuse.

Third-party processing

We do not provide or sell personal information to third parties without consent, except as required by law. Analysis inputs, such as URLs, may be sent to AI providers including the OpenAI API for processing, using settings that exclude use as training data.

Contact form

We store your optional name, reply email address, inquiry category, subject, message, submission time, and handling status on TubeSaku’s server. This information is used to reply, investigate issues, correct listings, and handle privacy requests.

Submissions are not published or used for advertising or AI training. To notify the operator, submitted information is sent through the Resend email service to the operator’s email address. It is not automatically sent to AI services. Authorized operators review submissions in the administration screen or notification email, and may reply to the address provided. No automatic reply email is sent.

Inquiry records remain until deleted by the operator. Once an inquiry is resolved, information no longer needed is deleted through the administration screen. For deletion requests, use the contact form and include your receipt number if available.

A browser session cookie and random identifier protect submissions and limit repeated sending. A hashed identifier and submission times are used for rate checks covering up to 24 hours; old rate-check records are cleaned up at the next successful submission. Raw IP addresses are not stored in the inquiry database. Server access logs are configured separately.

MCP & public AI-data usage logs

Dedicated MCP and public AI-data logs record timestamps, operations, outcomes, processing times, and HTTP status codes. MCP logs also record client names and versions, User-Agent, hashed session IDs, and identifiers linking requests. Depending on configuration, a keyed hash derived from the source IP may be recorded.

Tool names and defined arguments, such as search terms, games, dates, and result counts, are logged and aggregated to improve the service. Strings are limited to 500 characters per field. Undefined arguments, authentication headers, and raw session IDs are excluded. Search inputs can appear in logs; do not enter confidential information. Conversation text, response bodies, and raw IP addresses are not stored in these dedicated logs.

Records support service improvement, troubleshooting, and abuse prevention. Web-server and cloud-platform access logs are managed separately. For retention or deletion inquiries, contact us.

See our AI-data guide for available datasets.

Early-supporter cards & milestone reports

Using an early-supporter card stores an anonymous ID, the YouTube channel ID, and the first server-recorded timestamp. These records support saving and redisplaying cards and preventing misuse. Supporter counts are not public. No name or email registration is required.

Signed anonymous identifiers are stored in a first-party cookie, valid for one year and renewed on use, and in localStorage. Channel names and image URLs for card display are also stored on your device. Clearing both cookie and localStorage data prevents recovery. Do not share your identifiers.

Anonymous card information, channel IDs, and first-recorded timestamps are used to show subsequently observed subscriber milestones to the same browser. Read reports and their timestamps are stored on the server. Card records and identifiers are not sent to advertising providers.

Server records remain until deleted by the user. Use “View my early-supporter cards” to delete all records for this browser before clearing local device data. Deleting all cards also deletes associated read-report records. Operators also delete relevant records when a VTuber’s own removal request or retirement is confirmed. Listing-removal requests are accepted through the listing-removal form.

Questions about your information

For questions about personal information, usage logs, or deletion, please use our contact form.