Privacy and collection/use consent
Operator: tac0de · wonyoungchoiseoul@gmail.com
Policy version: 2026-10-17.2
Required information and purposes
For sign-in and the private workspace, we collect Google/Firebase identifiers, email, display name, session identifiers, consent versions and times, and age self-confirmation. Generation conditions and results are stored for authentication, access control, private result delivery and withdrawal processing. Retained legacy comments, replies, votes, bookmarks and reports follow existing retention and withdrawal rules. Date of birth and marketing tracking are not collected.
Choice and refusal
Terms acceptance and required consent to collect and use personal information are separate choices. Google authentication identifies existing members. When joining for the first time, review the collection items, purposes, retention periods and overseas processing described in this privacy policy, then select the required consent and confirm you are at least 14. Plotnodes does not store a member profile or session before this confirmation. Existing members do not repeat consent on every sign-in; if policies change, they review the current policies before using member features. You may refuse consent or stop membership and can continue reading public posts without an account.
Overseas processing and service provider
Google LLC (United States) provides Firebase Authentication, Cloud Firestore, Firebase Hosting and Google Cloud for authentication, data storage and service operation. On sign-in, identifiers, email, display name and the IP address and browser information needed for authentication are automatically sent over an encrypted network to Firebase Authentication in the United States. Member features send data such as membership information, consent records, comments, replies, votes, bookmarks and reports to Firestore (nam5) in the United States for storage. Servers run in Seoul, Korea; Hosting and operation logs may be processed on Google’s global infrastructure.
Overseas authentication and storage are necessary for sign-in and member features. You may choose not to sign in or use member features; the category atlas remains accessible without signing in. Refer to Google/Firebase notices for provider privacy terms.
Plotnodes data retention and withdrawal
Membership information is retained while you use the account. Withdrawal immediately blocks access. Plotnodes removes your profile, sessions, comments, replies, votes, bookmarks, reports and identity links within the service within 30 days. Any remaining data you authored in the previous service is also removed. Structural identifiers and empty references remain to preserve other users’ comments and connections between published stories. Minimal records needed to process deletion requests and block renewed access after withdrawal (request and completion times, progress status and irreversible authentication-link identifiers) are retained separately for as long as needed. They do not contain email, display name or original Firebase identifiers. Processing status is reported separately.
Shared sign-in account and provider residual data
This Firebase sign-in account is also used by other services, so Plotnodes withdrawal does not delete it. Plotnodes membership information and identity links are removed; other services’ accounts and data remain. Your personal Google account is also retained. To request deletion of the entire shared Firebase account, contact the operator separately. We will explain the scope after checking the effect on other services.
Google states that Firebase Authentication IP logs are retained for a few weeks. Other authentication information is retained until deletion of the Firebase account is requested; removal from live and backup systems may take up to 180 days after that request. That deletion period does not begin while the shared account is retained. Firebase Hosting IP data may be retained for a few months. These provider periods are separate from the 30-day deletion period for Plotnodes data.
Storage history, backups and operational logs
As checked on October 11, 2026, production Firestore (nam5) retains past data versions for up to one hour. Point-in-time recovery (PITR) and scheduled backups are not enabled, and no managed backups or TTL policies were found. Google Cloud’s global log storage is configured to retain ordinary operational logs for 30 days and mandatory audit logs, whose retention cannot be changed, for 400 days. Provider policies apply to authentication, Hosting and residual data on Google’s infrastructure. Service withdrawal does not mean all these logs and provider residual data are removed immediately or within 30 days.
Your rights and contact
You may ask tac0de, the operator in Korea, for access, correction, deletion, suspension of processing, withdrawal of consent or account withdrawal. Contact wonyoungchoiseoul@gmail.com. You can also request withdrawal in account settings. After verifying your identity, we explain the request’s scope and result; we do not delete other people’s information or data from other services without authorization. Google/Firebase privacy inquiry routes are available through the provider information link below.
AI-authored content
Legacy public content, comments, votes and sign-in data are not sent to the AI generation API. After explicit acknowledgment, the designated administrator may request IF generation within a prepared original setting.
An administrator generation request sends the entered condition and selected setting pack to the OpenAI API. Email, login tokens, legacy content, existing comments and other users’ private results are excluded. Do not enter sensitive or third-party personal information. You may decline generation and browse categories only.
Plotnodes retains conditions and private results for up to 30 days and cleans them after expiry or withdrawal. Minimal reconciliation references for uncertain costs or outcomes may remain until resolved. Requests use store:false, which does not eliminate all OpenAI retention. Default abuse-monitoring logs may be retained for up to 30 days or under exceptions in provider policy. Details: https://developers.openai.com/api/docs/guides/your-data