EOSEN · PRIVACY
Privacy policy
Service and privacy contacts: KimJiHo and KimTaeHeon, joint operators / EOSEN / Republic of Korea.
Functional play counts
Total plays use a per-launch token to avoid double counting. They do not set a browser tracking cookie without analytics consent. Identified unique players require consent and are limited to 90 days. Visitor hashes older than 90 days are removed while aggregate play counts are retained. Non-analytics session records expire and are cleaned within a day after expiry.
Password breach checks
When creating or resetting a password, EOSEN checks Have I Been Pwned using only the first five characters of a one-way password hash. The password, full hash and email are never sent to this service. If the check is unavailable, please retry shortly.
Audit evidence and erasure requests
Security audit originals cannot be edited or deleted through the website. Operational archiving changes only their presentation. A verified deletion request requires a separate review of legal grounds, retention obligations and affected records before an approved execution; any retained security evidence and reasons are explained to the requester.
Information collected & purposes
Email, authentication information and member IDs support signup, sign-in and recovery. Public names, usernames, bios, images, creations, descriptions, posts, comments, reactions and follows support publishing and sharing. Sessions, IP-based security counters and access/error records help prevent abuse and resolve incidents. Private support and rights requests and replies are processed to handle requests and are accessible only to the author and designated staff. Only a hash of a guest receipt code is stored, not its original value.
Membership terms & processing grounds
Membership features are available to people aged 14 and above. New and existing members confirm they are at least 14, accept the terms and acknowledge required privacy information; the notice version and time are recorded. Dates of birth and national identity numbers are not requested. Age is self-declared, not independently verified. Restrictions and deletion are considered if a user is found to be under 14. Information necessary for accounts and publishing is processed to enter into and perform the service agreement; optional analytics require a separate choice.
Analytics you choose
Allow, decline or withdraw analytics through the preferences at the bottom of the page. Collection is off by default; declining does not prevent play or membership features. Opted-in creation impressions, detail views and player time are aggregated. Creators see aggregates, not individual identifiers or IP addresses. Member and browser identifiers are replaced with keyed hashes on the server.
Retention & scheduled cleanup
Accounts, acknowledgements, content, likes, saves and follows are retained while those features are provided. Deleted content is immediately excluded from public access; recovery and report review records may be retained. Permanent deletion and account closure involve identity checks and review of authentication information, files and linked records. Reasons and retention periods are explained for records that must be kept separately. Submitting a request does not automatically erase everything immediately.
Cookies, raw records & requests
Sign-in cookies last up to 7 days, analytics preference cookies up to 180 days and opted-in browser identifiers up to 30 days. The language choice is stored as an essential preference cookie for up to one year and in local storage to synchronize browser tabs on the same device. Expired sessions and rate-limit counters are cleaned daily. Raw impressions, detail views, player time and community views older than 90 days are cleaned. Existing play counts and reactions are retained separately while their features are provided and may be covered by rights requests. Member support tickets are periodically deleted 90 days after closure. Rights requests are deleted 90 days after closure or a maximum of 180 days after submission. Staff investigate and retry failed cleanup.
Deletion & backups
When handling deletion, related database, authentication and file records are reviewed and deleted. Recovery backups have restricted access and follow provider contracts and retention policies. Moderation and report records are retained as needed to respond to disputes and abuse; retention reasons and scope are reviewed upon request. Provider policies also apply to hosting, authentication and email access logs and backups.
Providers & data location
Supabase handles authentication, databases and private files; Vercel handles hosting, execution, delivery and security logs; Google SMTP handles email addresses and verification/recovery messages. The primary region for databases, authentication, files and web functions is Seoul. Network transfers for service use and email are encrypted. EOSEN does not operate a personal-data sales or advertising disclosure feature.
Processing outside Korea
Selecting Seoul does not mean all processing remains in Korea. Vercel may process data in the United States and its subprocessors’ regions; Supabase may perform support, logging and some operations outside the selected region; Google uses global mail infrastructure. Operators must verify and manage contracts, transfer countries, recipients, contacts, retention and applicable grounds with providers. The official resources below explain provider processing. If you do not want necessary authentication, storage or hosting processing, do not use membership features or request account closure. Viewing public content still involves connection processing necessary for web requests.
Access, correction, deletion, restriction & closure
In Settings, edit your profile, download your own text records by category and end all EOSEN sessions. Submit your own or a legal representative’s request through member support or the rights form without signing in. Staff verify the subject and identity, then explain results or restrictions and retention reasons. Requests can be submitted even without account access. Keep your secret receipt code to check replies. Do not send passwords, verification codes, national identity numbers or identity documents.
Safeguards & public information
EOSEN uses HTTPS, server-side authentication and authorization, private file storage, session protection, upload validation, rate limits, audit logs and isolated creation execution. These measures are not a guarantee against every attack or an external security certification. Public profiles and posts can be viewed and copied by others. Do not publish sensitive information or secret keys.
External URL creations
Playing a URL creation opens an external site in an isolated player and may send connection information to its operator. That site’s cookie, authentication and privacy policies apply. EOSEN does not bypass its embedding restrictions.
Effective date & changes
Effective November 16, 2026. Added joint operator information, guest rights requests, personal data downloads, membership acknowledgements and scheduled retention cleanup. Changes will be announced here with their effective date and details. Necessary notice and choice procedures will be provided before changes to collection or membership rights take effect.
Official resources & assistance
Supabase data location & transfers · Supabase subprocessors · Vercel data processing agreement · Google privacy policy
In addition to submitting a request to EOSEN, you can seek guidance from the Korea Privacy Infringement Report Centerand Personal Information Dispute Mediation Committeefor further assistance.