FELIX Privacy Notice — draft

Who is responsible

The legal operator, address and monitored privacy contact have not yet been finalized for public launch. A contact for privacy requests that cannot be completed in the account tools must be published before opening. This page does not receive requests.

FELIX is an independent, unofficial service. It is not operated by or affiliated with Felix Lee, Stray Kids, JYP Entertainment or ONE LABEL.

What this draft covers

This draft covers FELIX account registration, public profiles, posts, replies, reactions, follows, communities, feeds, notifications, safety reports and account-data tools. It also covers reading Today and Search, including source links. An account is not required to read the public information pages.

Data used to provide FELIX

• Account email, authentication credentials and session information used to sign in, confirm email and recover access.
• Handle, display name, biography and selected profile languages. A display name can be a nickname.
• Posts, replies, reactions, follows, blocks, community memberships and notification/read-state records, together with account references and timestamps.
• Adult-eligibility attestation and the versions and timestamps of recorded rules and terms acceptance. An attestation is not verified proof of age.
• Reports, reported content, moderation decisions and restricted evidence. Free-form text can contain personal information about its author or other people.
• Bounded action counters and operational records used to prevent abuse, investigate failures and protect the service.

Hosting and security providers also process request, browser, network and challenge-result information. The final provider inventory must establish their exact data, purposes and retention. Application log minimization does not mean that providers collect no information.

Public content and restricted records

Profiles and readable social content can be public. Do not put private contact details, private locations or information you do not want published in a profile, post or reply. A pseudonym does not make an account anonymous, and blocking another account does not promise to hide your public identity.

Reports, moderator notes and evidence have restricted access; they are separate from public content. Records can still identify people through account references or retained text. Do not submit unnecessary private information in a report.

Purposes and legal-basis review

Data supports account access, the social features you use, required account messages, abuse prevention, moderation and account-data requests. The applicable legal basis for each purpose, launch country and data category still requires qualified review. This draft does not approve optional analytics, marketing, research or a future business model.

Providers and international processing

The current service uses Supabase for authentication and data, Cloudflare Turnstile for human-verification checks, and Vercel for Web delivery. Resend currently delivers STAGING account email. Turnstile can process browser, network and challenge signals when you make an account request.

The complete processor list, public-launch email arrangements, contracts, processing locations, retention and transfer safeguards remain pending for the intended public configuration. An EU database location does not establish that all processing stays in Europe. Any legal disclosure process also requires an approved operating procedure.

Cookies, device storage and external links

The Web account flow uses session cookies. The native app uses device storage for its session so it can restore access when reopened. Language and interface preferences can be stored locally. The final cookie and provider-storage disclosures still require review; this is not a claim of cookie-free use or complete tracking assessment.

Source cards and other external links open another service, which has its own privacy practices. A downloaded account export contains personal data. Keep the file safe: signing out, uninstalling FELIX or erasing the account does not remove a copy you saved.

Access, correction and export

Account-data tools act on the signed-in account. An export can include its profile, recorded consent, memberships, follows, blocks it set, posts, replies, reactions, notifications and reports it filed. Passwords and authentication tokens are not included. Other people's reports and blocks, moderator notes, case identifiers and evidence are withheld; the export lists withheld categories.

Before a public profile exists, the export records that absence and includes the account registration details and any recorded consent, with empty social collections. Missing consent is not represented as acceptance. You can edit an eligible existing profile through its account page.

Depending on applicable law, rights may include access, correction, deletion, restriction, objection, withdrawal of consent and a complaint to a supervisory authority. The monitored contact and procedure for requests outside the account tools remain pending. No response deadline is promised by this draft.

What account erasure does

For an account with a profile, confirmed erasure removes its posts, replies, reactions, follows, blocks, memberships and notifications and replaces the public profile with a removed-account placeholder. Replies beneath its deleted posts are removed too. An owned community with no remaining owner stops operating and is archived; other people's content is not erased merely because they belonged to that community.

Before profile creation, the confirmation is uppercase ERASE, without spaces. The service records a terminal account state without creating a public profile. This account cannot later create a profile. An existing profile requires its own handle as confirmation. Erasure cannot be undone.

Sign-in credentials are a separate removal step. Reports, evidence, enforcement and erasure records can remain for safety and accountability; retained references or text can still identify people. Erasure is not a promise that every record is anonymous or removed. If an erasure reply is lost, check the recorded account state before attempting it again. Finish a confirmed erasure by signing out of the current device; this does not certify that every other session was revoked.

Retention is not yet approved

No public credential-retention duration or maximum deletion time has been approved. STAGING uses an unapproved test policy. An erasure receipt records its request time, retention boundary and policy state. Reaching that boundary makes credential removal eligible; it does not perform the removal. A named operator, execution schedule and overdue-work procedure are still required. Changing a policy does not automatically reschedule existing erasure records.

Separate periods and exceptions are also pending for unfinished accounts, reports and evidence, moderation/audit records, archived communities, security/provider logs, backups and any support or research copies. Historical proposed periods are not an approved retention schedule. The final notice and operated deletion procedures must agree before public launch.

Age eligibility

The current launch configuration requires contributor accounts to be for eligible people aged 18 or older. Registration asks for an adult attestation, not a full date of birth. Public readers may be younger. The permanent age and minor-access policy remains under review; this draft does not lower the current account threshold or approve a future age model.

Security and safety

Account-scoped access controls, restricted operational records and rate limits are implemented safeguards. They do not establish a completed security review, incident-response operation or a guarantee of absolute security. A monitored security contact and the final incident procedures remain public-launch requirements.

Read the safety page for the current reporting routes and their limits. This Privacy Notice is not a report form or an urgent safety channel.

Changes and approval

The final operator, contacts, countries, legal bases, processor details, retention schedule and effective date must be reviewed and published together. Notice versions, any required renewed acceptance and treatment of existing accounts still need an explicit decision. Opening this draft does not change your recorded consent or certify legal compliance.