Privacy Policy

Effective 2026-09-30 · Last updated 2026-09-30 · SEONIK

1. Operator and current service

SEONIK's operator and privacy contact is Kim Yujun, seonik.official@gmail.com. The site provides its introduction and policies without login. Signup, login, personalization and conversational research input have been discontinued. No new member identifiers or profiles are collected, and existing sessions cannot access member features. This does not establish deletion of historical personal data.

2. Visits and optional analytics

Google Analytics loads only after explicit permission. Before a choice and after refusal, no analytics request, consent ping or analytics cookie is created. Permission may allow GA identifiers, query/hash-free page and referrer paths, allowlisted campaign information, language, general device/browser/OS information, broad country/region, event time and allowlisted page-use categories. Historical Research events may describe discontinued features. Email, member identifiers and original questions/answers are not sent to analytics. Consent-based analytics measures visits and use; it is not required to read the introduction.

3. International analytics processing, retention and choice

After permission, analytics is transferred over encrypted internet connections to Google LLC and disclosed affiliates/subprocessors. Processing may occur in the United States and other countries where they maintain facilities, not exclusively the US. See Google's official information below. Previously verified GA4 user/event retention is two months; standard aggregate reports may differ. Analytics cookies last at most 60 days, and the browser stores the choice for 180 days. Refuse or withdraw through Privacy and analytics settings without losing access to the site. Withdrawal stops future requests and attempts to remove current analytics cookies; it does not guarantee immediate deletion of information already held by Google.

4. Hosting, security and browser preferences

Vercel, Inc. (privacy@vercel.com, US) may process access times, request paths, status, error metadata, IP and User-Agent for hosting, CDN, security and incident response. Page access involves necessary outsourced processing over TLS; the US and disclosed subprocessor locations may be involved. Previously verified Pro runtime-log visibility is one day, not a guarantee that every copy is deleted within one day. Separate service-generated information may remain until its purpose or lawful retention ends. SEONIK is configured not to write authentication values or original member data into application logs. Display, language, reading and interaction preferences remain in the browser and are not sent to servers or Google. See the Cookie Notice for individual items and removal.

5. Historical member and Research records

Historical records may include Google sub/email, internal account/link/session identifiers, Terms/age acceptance and optional profiles, consent, revision and deletion-management records. New authentication, member access, profile saving and profile-to-AI paths are closed; these records are not used for the introduction, answers or ordering. Closing features is separate from deletion of records or cloud resources. Retention purposes and statutory exceptions must be assessed, with unnecessary information promptly deleted under an approved scope, schedule and permissions. This notice does not authorize indefinite retention. Existing daily cleanup only covers expired sessions and unprotected abandoned signups, not every member. Complete historical deletion or deletion of supplier copies has not been verified.

6. Historical storage and backup boundaries

Historical accounts used Neon, LLC and parent Databricks, Inc. (privacy@databricks.com), AWS Singapore ap-southeast-1, with support/security potentially involving the US and disclosed subprocessors. This legacy storage may remain for records, bounded cleanup and rights requests. The six-hour project restore window and the official security description of 30-day customer backups are different; neither guarantees the maximum lifetime of every copy after member deletion. Historical Upstash storage in Tokyo hnd1 may retain pseudonymous request/cost counters without original content; monthly ledgers expire 62 days after their last update and anonymous operational aggregates 30 days after the target day ends. Past AI requests follow the applicable supplier retention and legal exceptions and cannot be recalled simply by closing the service. Do not interpret unverified deletion, contracts, regions or backups as completed erasure. Restores require rechecking deletion state before exposing records. Google Gemini API abuse-monitoring guidance specifies 55-day retention for prompts, context and outputs; Google Search Grounding terms specify 30-day retention for the corresponding prompts, context and outputs. Contracts, processing types and legal exceptions may differ; these periods do not establish complete erasure of every copy for an individual member. No new member information is currently sent to AI. See supplier references below.

7. Rights, contact and erasure

Request access, correction, export, deletion, processing suspension, consent withdrawal or objection at seonik.official@gmail.com without login. Initially send only the request category and a reply contact, not passwords, keys, national identifiers, original questions/answers or unnecessary data. The operator will verify identity or representative authority using the minimum needed information, such as the previously registered contact, and reply with the result. Any extra information needed will be explained first. If statutory restrictions or retention obligations prevent full fulfillment, the reason and objection process will be explained. Unnecessary information is erased to prevent recovery; legally required records are stored separately. Request content and reply details are limited to handling the request and necessary dispute/statutory retention, with unnecessary information deleted after completion.

8. Changes

This member-feature withdrawal notice was prepared on September 30, 2026. Earlier policies remain in repository history. Material processing changes require appropriate prior notice and procedures. Future guest checkout may still create transaction and contact data and needs separate design and disclosure; no payment feature is currently offered.