Privacy Policy
You can use casting without signing in. Sign-in is used to save projects, recommend creators, preregister candidates and add activities.
Information we collect
We store visits, selections, votes, combinations, saves, shares, return visits and checkout-entry events with an event version, random visitor/session identifiers and target type. Provider-specific one-way hashes link sign-in identifiers to accounts; original email addresses from sign-in providers are not stored in the database. Display names, saved projects and payment results are retained as needed to provide these features.
Analytics and your choices
We use behavioral analytics to understand usability and repeat use, not for personalized advertising or selling individual data. Analytics events contain only permitted feature codes, target identifiers and counts, not user-written team names, introductions, emails or URLs. Referrals are classified using defined service/campaign codes; others are recorded as “other.” Random and hashed identifiers are protected as personal data because they may be linked with other information.
Individual analytics records are deleted in hourly cleanup runs using a 90-day retention standard. Errors or backlogs are retried in later runs. This cleanup does not delete votes, saved projects, rights-consent records or payment ledgers. Collection may be skipped depending on request volume, so statistics may not include every use.
Analytics include candidate identifiers in completed fan teams and whether each selection was manual, automatically filled, or carried over. The interface language does not indicate nationality or residence.
Applies to this browser. Previously excluded records stay excluded when collection resumes.
Clearing site storage and cookies resets visitor identifiers and preferences. It may also remove the browser link needed to undo signed-out votes. You can request access, correction, deletion or restriction of account-linked data through My space or the contact below.
Group voting without sign-in
You can vote for groups without signing in. A random identifier cookie is kept for up to one year so this browser can remember and undo votes; the server stores its hash and the teams voted for. On sign-in, browser votes are linked to the account and duplicates reconciled. After sign-out, you can still view and undo votes remembered by this browser, but cannot access account or team editing. On shared devices, clear site cookies to remove this link.
To limit repeated requests, short-lived rate-limit records are linked to browser hashes and daily network hashes. Raw IP addresses are not stored in these records; expired records are cleaned up on later voting requests. Clearing cookies does not automatically delete submitted votes. Votes are deleted when undone or when the linked account or team is deleted.
Fan video library
If you save a video link, your account stores the individual YouTube/TikTok post URL, title, linked team, candidates you confirm appear in the video, and versions of the character sheet and fan-creation guide. We do not collect video files; only you can view your library. Links may contain public platform usernames. You can delete work links or export them with your account data. Account deletion also deletes the library without changing original videos on external platforms.
Private feedback and usability-study applications
When you send private feedback, we use its content, category, optional email, submission location, language and time to review and respond. An email you enter in the feedback form is retained for replies, separately from sign-in email. Usability-study invitations are only for adults who separately opt in and are not used for marketing. Only operators can view feedback; it is excluded from public lists and analytics events. This form does not record your screen, voice or typing process.
We retain daily network hashes to prevent abuse, not raw IP addresses in feedback records. Submissions older than 90 days are cleaned up on the next submission or operator review. The private deletion link shown after submission lets you delete your feedback, email and study application. Anyone holding that link can delete the submission, so do not share it.
How we use information
Events support analysis of usability, retention and candidate/concept preferences. Account and project data support saving, remixing and Beats. This site does not collect or store payment-method details such as card numbers.
External video previews
Additional activities can include YouTube, TikTok and Instagram Reels links. Displaying platform thumbnails or official previews sends browser requests to that platform. TikTok preview-image URLs are obtained from official responses and briefly cached; image and video files themselves are not stored. Previews may be unavailable if content becomes private, is deleted or restricts embedding. Opening the original is subject to that platform’s terms and privacy policy.
Fan recommendations and reports
Publishing a fan recommendation stores and displays its submitted stage name, recommendation reason and YouTube video identifier. New recommendations are linked to the signed-in author. For older anonymous recommendations, a hash of the deletion key kept in the browser verifies deletion rights. We store abuse-prevention network hashes and report types/targets, not raw IP addresses in recommendation records. We do not automatically copy external video/photo files from links. We no longer accept new real-person or activity photo files; existing materials follow the deletion procedures below. Opening a preview connects to YouTube’s official player and is subject to YouTube’s Terms of Service and Google Privacy Policy. Deleting a recommendation also deletes its content and appreciation records.
YouTube channel connection
Fans and creators use the same recommendation route. If you optionally grant Google’s YouTube read permission, we compare the recommended video’s upload-channel identifier with the connected channel. We do not receive your Google password or request permission to upload, edit or delete videos. Access tokens are used only during the verification request and are not stored.
Channel identifiers, linked accounts, recommended-video identifiers and verification times support management access and verification displays. Connections last 30 days; expired data is cleaned up, and you can reconnect to manage a profile. Connection requests expire after 10 minutes and are cleaned up. Disconnecting or deleting an account deletes connection information. We publish verification status and the latest verification date in Korean time, not exact times or account identifiers. The date records channel-management authority at that time, not personal identity verification. Public verification labels and dates are removed on expiry, disconnection, report-related hiding or account blocking.
Optional participation consent records the channel operator’s statement, policy version and time. It is not proof of the identity or adulthood of people in the video. Disconnecting also revokes participation consent. Minimal consent/processing history is retained for three years to address rights disputes. Google API information is used only for channel connection and management, not sold or used for advertising or AI training. We comply with the Limited Use requirements of the Google API Services User Data Policy.
Existing private self-applications are not automatically published and remain available for management, withdrawal and deletion. New real-person preregistrations are not accepted. Original-character applications remain under private review.
Use, processing and disclosure of Google information
IDOL FORGE requests Google’s YouTube read permission for optional channel connection. We compare the authenticated account’s YouTube channel identifier with the recommended video’s upload channel to verify channel-management authority and determine access to edit that recommendation’s introduction and add activities. This does not verify the identity or adulthood of people in the video; participation requires separate consent. We do not request permission to upload, edit or delete videos.
Google provides sign-in, permission consent and YouTube API responses. IDOL FORGE processes requests and stores necessary connection data through Cloudflare’s server execution, database and private file-storage services. Cloudflare processes this information as our infrastructure provider. Stored connection information includes channel and site-account identifiers, the recommended-video identifier, verification/expiry times and separately chosen participation-consent records. Access tokens are used only in the server’s verification request and are not stored in the database. We do not request refresh tokens or ongoing access.
Public recommendations show currently valid channel-verification status, the verification date in Korean time and separately consented participation status. The linked public channel can be viewed through the original YouTube link. Google sign-in emails, internal site-account identifiers, exact verification times and access tokens are not shown on public profiles. Access to private information is restricted to staff who need it for operations, security and rights requests.
We do not sell Google API information or provide it for personalized advertising or external AI training/inspection. It is used for the authentication and infrastructure processing described above and the channel-connection features you choose. We comply with the Limited Use requirements of the Google API Services User Data Policy.
In a private review environment restricted to authorized operators, introductions, participation choices and official activity links may be stored separately in private storage. This test data does not affect public candidates, votes or actual participation applications; only the relevant operator with a valid connection can view or edit it. It is deleted on disconnection. Test data with expired or invalid connections is deleted in scheduled cleanup.
Protecting and deleting Google data
Google authentication and API communications use HTTPS; authentication secrets are managed on the server. Channel-connection requests use single-use requests tied to the current signed-in session and PKCE verification. Private responses are prevented from being cached. IDOL FORGE does not receive Google passwords.
Connection requests last 10 minutes and channel verification lasts 30 days. Expired connection information is deleted in cleanup, and management access ends on expiry. Disconnection or account deletion removes connection data, related management rights and participation labels. Deleting a public fan recommendation is a separate recommendation-deletion/reporting process. Minimal consent/processing history follows the separate retention rules in this policy. For privacy and rights inquiries, contact contact@idolforge.net.
Candidate and generated-content rights
For each candidate, we separately record the owning account, subject type, adulthood category, identity-verification status, rights basis, consent-policy version, permitted scope and source. Existing real-person preregistrations stay private; new intake uses YouTuber recommendations. At the identity-verification request stage, we record only the request time, processing status and verification-method category; we do not collect identity documents or face photos. Official publication and verification of YouTuber self-participation are still being prepared. Fan recommendations are distinct from confirmed personal participation.
Private original-character applications
We privately receive the name, introduction/creation description and one image of your original fictional character, linked to your account. Images are reduced to JPEG in the browser; location/camera metadata and original filenames are not stored. They are held in Cloudflare private storage and visible only to the applicant and reviewers. They are not sent to external AI inspection/training services. Publication, voting, team combinations and sharing require separate consent and review. Photos of real people or images transformed from them cannot be submitted. Withdrawal or account deletion removes introductions/creation descriptions and immediately blocks image access before physical deletion. To avoid conflicts with uploads in progress, new-image deletion may wait up to one hour for scheduled cleanup; storage errors remain pending and are retried. Minimal consent/processing history follows the retention rules below.
Video activities and existing photos
Official publication of YouTuber self-participation and paid top-ups are still being prepared. New real-person/activity photo files are not accepted. Representative fan recommendations use official original YouTube links; additional activities accept original YouTube, TikTok and Instagram Reels links from the person’s official accounts. We continue to support deletion/rights requests for existing materials and necessary payment-processing history.
Adding an activity stores the author account, target member/team, title, introduction, video link, chosen activity date, publication-consent version and Beat transactions. Only reviewed content is published; account names and emails are not displayed on activities. Original video files are not stored.
Any previously submitted photos remain in Cloudflare private storage under existing access restrictions. Submitted permission-verification routes and review evidence are not displayed on public profiles. We do not run new real-person/activity photo uploads or external photo-inspection requests.
Uploads not submitted as activities are cleaned up after 24 hours. Deleting an activity, candidate or account immediately stops photo publication and initiates physical deletion. Storage errors remain pending and are retried. Private photo-permission verification routes are retained during use and progressively cleaned up 90 days after photo deletion. Account deletion removes submitted verification routes. Review evidence for deleted activities is progressively cleaned up once 90 days have passed since the record was created. Hashes of blocked photos prevent repeated posting.
Candidate comment notice added: October 6, 2026
Candidate comments
Comments are free and published immediately with their text, a separate fan alias, and date. Your sign-in name and email are not displayed. A private account identifier supports deletion, posting limits, and reports. Comments remain until you or an administrator deletes them. Deleting your account removes your comments, alias, and report links. Comments are hidden when their candidate is no longer public.
Withdrawal, export and deletion
Free Beat grants and usage are managed to prevent duplicate grants, check balances and provide support. Grant audit records contain only account identifiers, amounts, reasons, operator identifiers and times, without copying names, emails or support messages. Free grants are not recorded as payments or revenue. If insufficient balance prevents activity submission, the account identifier and date are recorded once per member per day and progressively deleted under a 90-day retention standard. Operator analytics downloads exclude names, emails, credentials and free-form text and are not automatically sent to external AI.
Withdrawing consent immediately makes the candidate private and queues related media for deletion. After signing in, My space account/registration settings let you download account data or delete account connections, saved projects and candidate consent. Deletion removes account links from behavioral events. Minimal payment records needed for refunds, tax and abuse handling may be retained separately for legally required periods.
Stage names, introductions and video-link information are deleted when an application is withdrawn or an account deleted. Minimal consent/processing history is retained for up to three years after withdrawal as an operational period for disputes, then cleaned up at the next operator review. This does not mean all records have a uniform legal three-year retention requirement. History excludes original identity documents and deleted profile introductions.
Processing and safeguards
Cloudflare handles site requests, database and file storage; Google authentication is used when you choose Google sign-in. Safeguards include encryption in transit, restricted operator access, prevention of private-response caching and server-side storage of external authentication secrets. New real-person/activity photo intake has ended; access controls and deletion for existing materials remain supported. Original-character images are accepted only within the private-review scope described in this policy.
Privacy and rights contact
Privacy processing and complaints: IDOL FORGE team · contact@idolforge.net. You can request a data copy or deletion in My space account settings, or use this address to request access, correction, deletion, restriction of processing or withdrawal of consent. We request only the minimum information needed for verification. Do not send original identity documents or resident-registration numbers for site inquiries.
For impersonation, likeness, copyright or minor-protection concerns, use the post’s report/delete feature to request initial hiding. If further explanation or a result is needed, send the post URL, case number and public materials explaining that you are the subject or rights holder to the contact above. Requesters’ personal information and submitted materials are not shown on public posts.
For help with privacy complaints, contact the Personal Information Infringement Report Center or the Personal Information Dispute Mediation Committee.
Revised: September 16, 2026 — expanded Google data processing, disclosure, protection and deletion guidance. Effective: August 31, 2026. Private feedback guidance added: September 6, 2026.