FELIX Privacy Notice

Who is responsible

FELIX is operated by Killian Dujardin, an individual and the founder of the FELIX ORIGIN project. FELIX ORIGIN is used as a project and trade name; it is not currently an incorporated company. Privacy and rights requests can be sent to hello@felixorigin.com, a mailbox monitored by Killian Dujardin.

The operator publication-status details remain under review. This open review does not change the named controller or the contact route published here.

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 notice covers

This notice covers FELIX on the Web and in the FELIX app for iPhone, iPad and Android: account registration, Sign in with Apple, two-step sign-in, public profiles and the links to your profiles on other networks, posts, including their GIFs and polls and the posts written in event rooms, replies, reactions, saved posts, follows, communities, feeds, direct messages, notifications, including push notifications in the app, Suns, quests, trophies, grades and the shop, letters to Felix, community notes (corrections and sources you suggest on Felix records), safety reports and account-data tools. It also covers reading Today and its RSS feed, Search and the Gallery, including source links, Felix's Instagram posts shown on FELIX, and the TikTok, Instagram and X posts that members link to. 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. The interface language of the page you registered from is kept with the account, so that confirmation and password-recovery emails are written in that language.
• Sign in with Apple, if you use it. Apple tells FELIX, through Supabase Auth, an identifier of your Apple account that stays the same for FELIX, the email address of your Apple account or, if you choose to hide it, an address Apple creates that forwards email to you (its private relay), whether Apple has verified that address and whether it is a relay address, and your name only if you choose to share it the first time. Supabase Auth keeps these with your account as a sign-in identity, and FELIX uses them only to sign you in and to send you the account emails described here. Your Apple name is not your FELIX display name and is shown to nobody. Apple sends FELIX no password. Before a new account is created with Apple, FELIX asks what the email form asks: where you live, your date of birth and the documents to accept. If the answer does not allow an account, you are not sent to Apple. If Apple creates an account without those answers, for example from the sign-in page, FELIX deletes it straight away. If the page is closed on the way back from Apple, the account cannot take part until the questions are answered, and is deleted if the answer does not allow an account. If the verified address Apple gives is that of an existing FELIX account, Sign in with Apple opens that account, and two-step sign-in, if it is on, still asks for its code.
• Two-step sign-in, if you turn it on in the Security settings on the Web. For each authenticator app you add, Supabase Auth keeps the secret key it shares with that app, the name FELIX gives it (FELIX, or FELIX 2 for a second app), whether you confirmed it, and when it was added, changed and last asked for a code; for each code you are asked for, when it was asked and confirmed and the IP address the request came from; and, for each sign-in session, which sign-in methods it went through. FELIX uses this only to ask for the code and to refuse every request from a session that has not given it. The Security settings also list your sessions, from what Supabase Auth keeps for each one: the browser and system FELIX reads from its user agent, when it began and was last active, whether it is the device you are using and whether it went through two-step sign-in. The list shows no IP address. You can sign out every other session from there.
• Handle, display name, biography and selected profile languages. A display name can be a nickname.
• Links to your own profiles on Instagram, X, TikTok, YouTube, Weverse, Threads and Bluesky, if you add them on the Web: at most one per network, the address of the profile and when you last saved your links. FELIX accepts only the address of a profile on that network and fetches nothing from it. Nothing is recorded until you have accepted this notice, and you can remove the links at any time.
• Posts, replies, reactions, follows, blocks, community memberships and notification/read-state records, together with account references and timestamps. A new profile that can take part in FELIX's social features starts out following the FELIX Editorial account and FELIX's founder; the welcome steps on the Web say so, and you can unfollow either one at any time. Once, when this version took effect, FELIX also made the members who joined before that rule follow the same two accounts, unless they had blocked or been blocked by either one or had unfollowed either one before. Nobody was notified. FELIX keeps a private note of the follows it made, so it can undo them; the note goes away with the follow.
• GIFs in posts: a photo you add to a post can be a GIF. FELIX processes it as it processes a photo, writes it again as an animated image without the file's metadata, and records that it moves, so that readers can pause it. Nothing is recorded until you have accepted this notice.
• Polls and poll votes. A post you write can carry a poll: its text is the question, and FELIX keeps its 2 to 4 choices and when it closes, 1 to 7 days after you post it. When you vote in a poll, FELIX keeps which poll, which choice and when. A vote is final: it cannot be changed or withdrawn, except by erasing your account. FELIX uses votes only to count them. Nothing is recorded until you have accepted this notice.
• Event rooms. A post you write in the room of an event in FELIX's calendar is a Public post like any other, on your profile too. FELIX also keeps which event it was written in and in which part of the room: before, during or after the event, worked out from when you posted it and the event's published times. The event's page shows the post in that part of its room, to everyone who can see the post. FELIX does not record who reads a room or who attends an event.
• Direct messages, once FELIX turns them on: one-to-one conversations between adult members who can take part in FELIX's social features. For each conversation FELIX keeps its two participants, who started it and when, whether it is a request, and how far each participant has read it, as the number of the last message read, never a time; for each message, its text, its sender, when it was sent and whether moderation removed it. You can start a conversation with an account you follow. If that account does not follow you back, the conversation is a request: it waits in that account's Requests, not in its inbox, and you can send at most three messages until it accepts. It can accept the request, delete it, which only takes it out of its own lists, or block and report as with any account. A block stops the conversation at once; an unfollow does not.
• Saved posts: when you save a post, FELIX records which post you saved and when, in a private list that only you can see in FELIX. Nobody else, including the post's author, is told that you saved it. A post that is deleted, or that you can no longer see, no longer appears in the list; you can remove a post from it at any time, and it holds at most 1,000 posts.
• Push notifications in the app, once you turn them on and allow them on a phone; the app asks for that permission only then, never when it opens. For that phone: the Expo push token that lets FELIX reach it, whether it runs iOS or Android, the app version, the language the app was in, the sign-in session it was registered under, and when the phone was first and last registered; and your push choices for hearts, replies, mentions and new followers. Once you turn push notifications on, all four kinds are on, and you can turn each one off. FELIX uses them only to send that phone the pushes you chose. A phone is registered to one account at a time, and an account to at most ten phones. A notification waiting to be pushed is kept for at most an hour, and the delivery references Expo returns for at most a day. A push says what the notification says in FELIX, such as the name of the member who replied to you, in the app's language, and opens that notification's page. It carries no post or reply text and no photo.
• Evening reminders in the app, a kind of push notification: the evening before an event you saved in My FELIX, or, if you came in the last seven days but not yet today, the day's quests and the Suns they still hold. At most one reminder a day, sent between 18:00 and 22:00 where your phone is, and none after three quest reminders without a visit until you come back. For this, FELIX keeps the time zone of each phone registered for push, as the app reports it (for example Asia/Tokyo), your two reminder choices, one for quests and one for events, both on once push notifications are on, and, for each reminder, the day, its kind, the event it was about and when it was sent. A reminder names the event and its time, or the Suns left; it opens the event or the quests.
• Three more kinds of push notification in the app, each with its own choice, on once push notifications are on: a new private message or message request, which names who wrote but never says what they wrote, and opens the conversation, several messages in the same conversation within two minutes making one push; a live of Felix the FELIX team announces, once per live, which opens the app; and a decision about your own post or reply, when it is put online after review or taken down, which never gives a reason and opens the post or the Safety Center. A decision you take yourself, such as an edit, sends nothing. For this, FELIX keeps your three choices and, while a push waits to be sent, which phone it is for, its kind, the conversation or the post it is about, who wrote, and when; no message text. Nothing is sent until you have accepted this notice.
• Suns, the points you earn on the Web by taking part in FELIX, and the shop where you spend them. Nothing is recorded until you have accepted this notice. FELIX keeps a ledger with one entry for each gain and each purchase: the amount; whether it was for the day's visit, a quest, an achievement or a purchase; which quest, achievement or item it was; the day or week it counts for; and the date and time it was recorded. The ledger therefore shows the days, counted in UTC, on which you opened FELIX on the Web while signed in, and when you first opened Today on a day or the Gallery in a week, if that earned Suns. FELIX also keeps your visit streak (how many days in a row, your best run, the day of your last visit and how many freezes you have left; a freeze covers a missed day) and the shop items you own, with when you got each one and, for an item you have equipped, since when. Your balance is not stored: it is the sum of the ledger. Your progress in quests and achievements is not stored either: it is counted from your profile, posts, replies, hearts and follows, which FELIX already holds, and from the ledger. FELIX uses all this to show you your Suns, quests and items, pay each reward only once, keep to the daily limit and keep your streak. An entry, once recorded, is never changed. Suns cannot be bought with money, exchanged for money or given to another member, and nothing in the shop is sold at random. An account that cannot take part in FELIX's social features, such as a suspended account or the hidden, reader-only account of someone under 18, earns no Suns.
• Trophies and grades, awarded on the Web from what you do on FELIX. Nothing is recorded until you have accepted this notice. For each tier of a trophy you reach (bronze, silver, gold and platinum), FELIX records which trophy and tier and when; each tier also pays Suns once, recorded in the ledger as an achievement. Trophies count your days since joining, your published posts and replies, the hearts you gave to other members' posts and those you received from other members, your followers and the accounts you follow, the days on which you opened Today, the Gallery and the Library, your visits on 15 September and on the day of a release in FELIX's calendar, and your best visit streak. For Today, the Gallery and the Library, FELIX keeps how many days, counted in UTC, you opened each one and the last of those days, not which days they were; your visits on 15 September and on release days are read from the Suns ledger. Your grade is a level counted from your days since joining, posts, replies and followers; FELIX keeps the highest grade you reached, which never goes down. FELIX also keeps the free options of your profile: whether your grade shows and in which style, whether your trophies show, your accent, banner style and layout, and when you last changed them. A tier, once awarded, is never taken back, and no trophy or grade is sold.
• Letters to Felix, if you write any: the text, the visibility you chose, whether moderation has held or removed the letter, and when you wrote it and last changed it. If you report a letter, FELIX keeps which letter, the reason, the details you add, when you sent the report, and whether, when and by which moderator it was closed. Nothing is recorded until you have accepted this notice.
• Community notes, if you write any: the record it is about, the correction you suggest (what is wrong and what it should say) or the address of the source, your explanation, when you sent it, and the FELIX editors' decision, its date and their optional reply. Only you and the FELIX editors can read a note; it is never published. When a note leads to a change, the record's public correction history may say so, without your name. Nothing is recorded until you have accepted this notice.
• A coarse registration jurisdiction, its minimum account age, a minor/adult band, policy versions and acceptance timestamps. Account creation defaults to held until the matching server boundary and Auth hook are activated. When active, the server evaluates the birth date only as a transient request value, issues a short-lived one-use receipt and sends no birth date as Auth metadata. A short-lived pseudonymous throttle key is derived from the normalized email and Vercel system request signals; the application database stores no raw email, IP or network fingerprint in that receipt. Self-declaration 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.
• Private product feedback: its suggestion, problem or other category; the message; the submitting account; an idempotent request identifier; and submission time. Do not include passwords, security codes, private locations or other sensitive information. Feedback is not a public post, a corporate contact request or an urgent safety report.
• 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.

The shop items you equip are public: a profile theme, which also colours your banner, and a badge and a collectible card on your profile; a photo frame and a name style on your profile, posts and replies; and a sticker after your name on your replies. FELIX shows them to everyone who can see your profile, posts and replies, including people who are not signed in. Your balance, your streak, your quests and the items you own without equipping them are shown only to you.

Your grade, the trophies you show, your free profile options and a profile effect you equip are public too: FELIX shows them on your profile to everyone who can see it, including people who are not signed in, each shown trophy with its highest tier and when it was awarded, and your grade next to your name unless you hide it. By default your grade and the trophies built from what FELIX already shows about you (your time on FELIX, posts, replies, hearts received, followers and follows) are shown, while the trophies that tell when you visit FELIX (Today, the Gallery, the Library, 15 September, release days and your streak) and the trophy for the hearts you give stay hidden. You can show or hide each group, and your grade, at any time. Your own profile and trophy page show you every trophy, marked when others cannot see it; the counts behind your trophies and the points of your grade are shown only to you.

The links to your social profiles are public: they appear under your biography for everyone who can see your profile, including people who are not signed in.

A letter to Felix is shown according to the visibility you choose. Public: on the letters wall, to everyone, including people who are not signed in. Followers: on the wall, to the members who follow you. For Felix only: to you alone; Felix could read it only if he ever joins FELIX, and FELIX staff may read it for moderation. FELIX is not run by Felix and cannot promise that he will read any letter. A letter is never shown across a block. A letter that three members report is taken off the wall until a moderator keeps or removes it, and moderators see the letters reported to them.

A poll's choices are shown with its post, to everyone who can see the post. How many votes each choice received is shown to the poll's author at any time, to a member once they have voted, and to everyone once the poll has closed. FELIX shows nobody, the author included, who voted or what any other member chose. When a poll has few votes, the counts can still let someone guess how a person they know voted.

Fan news on Today links to one fan's own public post, only after that fan has agreed to it. FELIX shows a short summary written by the editorial team and a link to the post, with the name the post shows. It never copies the post. Beyond that link, FELIX keeps only the record of the agreement: its date, what FELIX may show and where, and how the fan takes the item down. The fan can have it taken down at any time by that route.

A direct message is shown only to the two participants, and to moderators when one of them reports it. In an accepted conversation, each participant sees « Seen » under the last of their messages the other has read. A request never tells the account that sent it whether it was read or deleted. FELIX shows no typing indicator and no online status.

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 bases

Data supports account access, the social features you use, required account messages, abuse prevention, moderation and account-data requests. FELIX relies on contract or requested pre-contract steps for account delivery, legal obligations for rights and valid orders, legitimate interests for proportionate security and moderation, and your consent, given by pressing play, for loading the YouTube player. Loading Instagram's embed of Felix's posts relies on your consent too, given by pressing the button that shows them, and so does loading a TikTok, Instagram or X post that a member linked to, given by pressing the button that shows it. Polls, like posts, rely on contract. Suns, quests and the shop are among the features of your account and, like them, rely on contract. So do trophies, grades and profile options, the links to your social profiles, letters to Felix, direct messages, community notes, two-step sign-in and Sign in with Apple. Push notifications in the app rely on your consent, which you give by turning them on in the app; the permission the phone then asks for is not, on its own, that consent. FELIX sends them only to a phone on which you turned them on in the app and allowed them when the phone asked, and only for the kinds you leave on. You can withdraw that consent at any time by turning push notifications, or one kind of them, off in the app, or by turning off notifications for FELIX in the phone's settings; nothing else in your account changes. Evening reminders are push notifications and rely on the same consent; each of their two kinds can be turned off on its own. So do the pushes about private messages, lives and decisions about your content; each of the three can be turned off on its own. Translating a post or a reply when you ask for it relies on contract, like the other social features. The detailed legal-basis assessment remains open for external review. Measuring the audience of the website in aggregate, as the Cookies, device storage and external links section describes, relies on FELIX's legitimate interest in knowing which pages are read and how fast they load. Updating the app's code, as the Providers and international processing section describes, relies on FELIX's legitimate interest in keeping the installed app working and fixed. Marketing and advertising are not approved by this notice.

Providers and international processing

The current service uses Supabase for authentication and data, Vercel for Web delivery, and the configured email provider for required account messages.

Supabase provides Auth, database and storage from the configured Paris-region project; Vercel provides Web hosting, server execution and the audience measurement described below; Resend provides required account email; Cloudflare Turnstile provides abuse checks in the signup flow. Processing may occur outside the EEA. Provider contracts, subprocessors and transfer safeguards remain open for qualified external review.

In the app, push notifications go through the Expo push notification service of 650 Industries, Inc. (Expo), which processes them on FELIX's behalf, as a processor, under Expo's Terms of Service. Expo passes each push to Firebase Cloud Messaging (FCM) on Android, which Google LLC provides to FELIX as a processor under the Firebase Data Processing and Security Terms, or to Apple Push Notification service (APNs) on iPhone and iPad. Every push to an iPhone or iPad passes through APNs, which Apple Inc., a company based in the United States, operates and provides to FELIX under its Apple Developer Program License Agreement; that agreement does not set out Apple's role for push data under data protection law. Apple says that it does not access the content of a push except for legal, enforcement, security or fraud reasons, and that it may collect technical information about how FELIX uses APNs. Google also uses technical information about its service under its own privacy policy.

To deliver a push, these services receive the phone's push token and the push itself: the sentence the notification shows in FELIX, the link it opens and an identifier of the notification, never post or reply text and never a photo. Expo keeps the push tokens it needs to send pushes and publishes no period for keeping them. It says that it holds the content of a push only in memory and in message queues for as long as delivery takes, and it clears delivery receipts after 24 hours. FELIX asks that a push not delivered within an hour be dropped, and deletes its own copy of the push token as the Retention section describes.

The app also gets new versions of its own code, its screens and texts but not its native part, from Expo's update service (EAS Update), which 650 Industries, Inc. (Expo) provides to FELIX as a processor under the same terms. Each time the app opens, it asks that service whether a newer version exists, whether or not you are signed in. The request carries the phone's IP address, whether it runs iOS or Android, the app's update channel and runtime version, which versions of its code it runs and which recently failed to start, a random identifier the app creates when first opened, which Expo uses to count active installations, and, after the app has crashed, a description of that crash of at most 1,024 characters. Apart from what such a description may happen to quote, it carries nothing from your account: no name, email address, session or content. The app downloads a newer version in the background and uses it the next time it opens.

This processing, for pushes and app updates, takes place in the United States and can take place elsewhere outside the EEA. Expo (650 Industries, Inc.) and Google LLC are on the EU-U.S. Data Privacy Framework List, and the European Commission has recognised the Framework as providing adequate protection; Expo's terms also include the European Commission's standard contractual clauses, and Google's Firebase terms apply them where the Framework does not. Apple Inc. is not on the Data Privacy Framework List, and FELIX's developer agreement with Apple contains no data processing or transfer terms for APNs. This point remains open for qualified external review.

When you ask to see a post or a reply in your language (“See translation”), FELIX sends the text of that post or reply, with the language it is written in and the language you asked for, to Cloudflare Workers AI, a service of Cloudflare, Inc., which translates it on FELIX's behalf, as a processor, and sends the translation back. Nothing else about you or its author is sent. Cloudflare says that it keeps neither the text nor the translation once the request is answered, apart from limited exceptions it describes, and that it does not use them to train AI models. FELIX keeps the translation, so that the next member who reads that language does not ask again, and deletes it with the post or reply, or when its text changes. The translation is labelled as automatic: it is never an official translation, the original stays above it, and FELIX does not use it on its own to decide anything in moderation. Cloudflare, Inc. is based in the United States, and this processing can take place outside the EEA; its transfer safeguards remain open for qualified external review, as for the other providers.

If you choose Sign in with Apple, you sign in on Apple's page, and Apple processes your Apple account, the fact that you use it with FELIX and its private relay under its own privacy policy, as its own controller, not on FELIX's behalf. Apple Inc. is based in the United States. Your Apple account settings list FELIX among the apps that use Sign in with Apple, and you can stop using it with FELIX there; that does not erase your FELIX account. Account emails sent to a relay address pass through Apple, which forwards them to your own address. Apple describes its processing in the Apple Privacy Policy.

Cookies, device storage and external links

These are the cookies FELIX and the libraries it uses can set on the Web. Several exist only in a particular moment, which each entry below says. None is for advertising, profiling or measurement. FELIX runs no advertising or tracking script on any page, and the audience measurement described below sets no cookie.

• The sign-in session, named sb-…-auth-token and split into numbered parts when it is long. It exists only while you are signed in, it is what keeps you signed in, and signing out clears it. It is set by the Supabase Auth library FELIX uses.
• sb-…-code-verifier entries, also written by that library. They exist only while a sign-up confirmation or a password-reset link is outstanding, and they are what lets FELIX complete the link you were sent on the device that asked for it.
• felix-locale, the interface language you chose. One year, readable by the server only.
• felix-privacy-acceptance, the version of this notice you accepted, the date you accepted it, and whether you were signed in at the time. One year, readable by the server only. It contains no identifier and nothing else about you, and it is cleared whenever you sign in, sign up or sign out. It is what lets FELIX ask once rather than on every visit, and it is per device: accepting on one device says nothing about another.
• felix-recovery-proof, written only when you follow a password-reset link. Fifteen minutes, limited to the reset page, readable by the server only.

The three cookies FELIX writes itself — the language, the acceptance and the reset proof — are set HttpOnly and SameSite=Lax, and Secure on an https address. The session and the code-verifier entries are written by the Supabase Auth library, on its own terms rather than FELIX's.

Separately from cookies, FELIX stores seven things in this browser itself, which never reach FELIX's servers: felix:last-visit:v1 holds the ids of the Today items and home-feed posts you last saw, so FELIX can mark what is new since your last visit; felix:theme:v1 holds Light or Dark when you choose one in Settings, and is removed when you go back to following your device; felix:today:saved:v1 and felix:official-updates:saved:v1 hold the items you saved in Today and My FELIX, on this device only — a saved copy of an official update from YouTube is dropped the next time FELIX reads or writes that list after 21 days; felix.reply-focus.visited-entries records which replies the page has already moved focus to, and is cleared when the tab closes; felix:first-steps:v1, written only in a member's browser by the welcome steps, the tour of Home or the First steps card, records whether the tour was seen or skipped, whether First steps was hidden, whether the Gallery was opened and which welcome step to come back to (the link to finish setting up opens that step, so its address names it); the spaces you pick during the welcome are not kept there or anywhere else; felix:whats-new-seen:v1 holds the newest What's new entry seen in this browser, so FELIX can show a dot when there is a newer one. FELIX never removes these last two itself, not even when you sign out: they stay until this site's data is cleared in the browser.

The FELIX app uses device storage for its session so it can restore access when reopened. The session is kept in the device's secure storage: the Keychain on iPhone and iPad, and on Android storage encrypted with a key held by the Android Keystore. Signing out removes it. If that storage refuses the session, the app keeps it in memory only, and you sign in again the next time the app opens. The same secure storage holds, on this device only, the interface language you chose, your choice of Light, Dark or your device's own mode, and the Today items you saved. If you turn push notifications on, or answer the app's offer of them, it also holds whether they are on and for which account, the phone's push token, the language and the time it was last sent to FELIX, and whether the app has already offered them; signing out clears it. Three more entries there never leave the phone: where you are in the welcome steps, the tour and the « First steps » card (the app's copy of the website's first-steps entry), whether Today was opened on this phone, and which Today items the app last showed you, so it can mark the new ones. Signing out does not remove them; they stay until the app is uninstalled or its data is cleared. Images shown in the app are kept in a memory and disk cache on your device so they load faster. The cache is emptied when you sign out in the app (which also happens when you delete your account from the app); the system may empty it earlier. Deleting your account from the website or being signed out remotely empties it at your next sign-out in the app, or when you uninstall the app. The app also keeps a copy of the public Today content, the same for everyone and containing nothing about you, in its cache so that Today opens without a connection; the device can clear it at any time. The app also keeps the recent versions of its code it downloaded and the random identifier it sends to Expo's update service; they stay until the app is uninstalled or its data is cleared.

Five providers can place storage of their own. When the operator turns on the abuse check, the landing page and the sign-in, sign-up, password-reset and email-verification screens load the Cloudflare Turnstile widget from challenges.cloudflare.com; Cloudflare may then store what that check needs, under Cloudflare's own terms, and FELIX neither reads nor receives it. YouTube can do the same once you press play on a YouTube video, as the YouTube API Services section below describes, and Instagram once you press the button that shows Felix's Instagram posts or a post a member linked to, and TikTok and X once you press the button that shows a post from them, as the two sections after it describe. Apart from these five, and the audience measurement below, which Vercel serves from FELIX's own address, no page loads anything from another company. This list describes what FELIX stores and can be checked against the code; it is not a review of what a provider does under its own policy, and it is not a claim of cookie-free use.

FELIX measures the audience of its website with Vercel Web Analytics and Vercel Speed Insights, from Vercel, which already hosts FELIX. Their two scripts load from FELIX's own address, set no cookie, store nothing in your browser and are never told who you are, so nothing they record is linked to your account. They record the page you open, without the part of its address after ? or #, the site you came from, your approximate location (country, region, city), the type of device, its system and browser, and how fast the page loaded on your connection. Vercel tells visits apart with a code computed from the request, which it discards after 24 hours, and FELIX sees only totals. The FELIX app does not use them.

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.

YouTube API Services

FELIX uses the YouTube API Services to read public information about videos published on the official YouTube channels it follows: a video's title, publication date, identifier and link. FELIX uses no YouTube account, asks for no access to yours, and obtains no information about you from YouTube.

These requests come from FELIX's servers, so nothing about you or your device is sent to YouTube when FELIX reads a channel. FELIX keeps what it reads for at most 30 days without refreshing it from YouTube, and deletes it otherwise.

On the Web and in the FELIX app, a YouTube video linked in a post, and some videos from those official channels on Today and, on the Web, in the Gallery, can be played on FELIX in YouTube's own player. Until you press its play button, FELIX shows only a panel of its own, loads nothing from YouTube or Google and sends nothing about you to them. The line under the button says what pressing it does, and pressing it is your consent to that; FELIX remembers no consent, so each video asks again. Pressing it loads the embedded player that YouTube, a Google service, provides, in YouTube's privacy-enhanced mode, from www.youtube-nocookie.com; the player then connects to the other Google addresses it needs to play the video. From that moment YouTube receives your IP address, information about your device and browser, which video you play and that you play it on FELIX, and the other information it describes in its own policy. Even in privacy-enhanced mode, YouTube can store information on your device, cookies included, under that policy. The player can also show advertising, which FELIX neither chooses nor approves. FELIX neither reads nor receives any of it, and places no YouTube cookie itself. A video's link still opens it on YouTube, where YouTube's own practices apply.

In the app, the player works the same way inside a web view, a browser built into the app. What YouTube stores there is kept in that web view's storage, inside the app on your device. A link in the player that leads away from the video, such as one to watch it on YouTube, opens outside the app, in YouTube's app or your browser.

When you press play, FELIX and Google are jointly responsible for collecting this information and sending it to YouTube. The recipient is Google Ireland Limited for people in the European Economic Area and Switzerland, and Google LLC elsewhere. What is done with the information after that is Google's responsibility alone, under the Google Privacy Policy.

Content FELIX obtains through the YouTube API Services, and the YouTube player, are subject to the YouTube Terms of Service. How Google handles data, including what YouTube receives through the player, is described in the Google Privacy Policy.

Felix's Instagram posts

On the Web, the Felix on social media page can show Felix's own Instagram posts on FELIX, in the embed of his profile that Instagram, a Meta service, provides. Until you press the button that shows them, FELIX shows only a panel of its own, loads nothing from Instagram or Meta and sends nothing about you to them. The line under the button says what pressing it does, and pressing it is your consent to that; FELIX remembers no consent, so the page asks again each time you open it. Pressing it loads Instagram's page for that profile from www.instagram.com, which then loads what it needs from Meta's other addresses. From that moment Meta receives your IP address, information about your device and browser, that you are viewing that profile and that you are viewing it on FELIX, and the other information it describes in its own policy. Instagram can store information on your device, cookies included, under that policy, and if you are signed in to Instagram in that browser, Meta can link what it receives to your Instagram account. FELIX neither reads nor receives any of it, places no Instagram cookie itself, and copies, stores and rehosts none of Felix's posts. Links in the embed open Instagram, where Instagram's own practices apply.

When you press the button, FELIX and Meta are jointly responsible for collecting this information and sending it to Meta. The recipient is Meta Platforms Ireland Limited for people in the European Economic Area and Switzerland, and Meta Platforms, Inc. elsewhere. What is done with the information after that is Meta's responsibility alone, under the Instagram Privacy Policy.

Meta can process this information in the United States and elsewhere outside the EEA. Meta Platforms, Inc. is on the EU-U.S. Data Privacy Framework List, and the European Commission has recognised the Framework as providing adequate protection. This point remains open for qualified external review.

TikTok, Instagram and X posts in members' posts

On the Web, a post that links to a TikTok video, an Instagram post or an X post can show it on FELIX, in the embed that service provides for that one post. FELIX recognises only the usual address of a post on each service and fetches nothing from it: until you press the button under the post, FELIX shows only a panel of its own, loads nothing from TikTok, Instagram, Meta or X and sends nothing about you to them. The line under the button says what pressing it does, and pressing it is your consent to that; FELIX remembers no consent, so each post asks again. Pressing it loads that service's embed, from www.tiktok.com, www.instagram.com or platform.twitter.com, which then loads what it needs from that service's other addresses. From that moment the service receives your IP address, information about your device and browser, which post you are viewing and that you are viewing it on FELIX, and the other information it describes in its own policy. It can store information on your device, cookies included, under that policy, and if you are signed in to it in that browser, it can link what it receives to your account there. FELIX asks X not to use the visit to personalise what it shows you. FELIX neither reads nor receives any of it, places no cookie of these services itself, and copies, stores and rehosts none of their posts. Links in an embed open that service, where its own practices apply.

When you press the button, FELIX and that service are jointly responsible for collecting this information and sending it to the service. What is done with the information after that is the service's responsibility alone, under its own policy. For TikTok, the recipient is TikTok Technology Limited for people in the European Economic Area and Switzerland, and the TikTok company its policy names elsewhere, under the TikTok Privacy Policy. For Instagram, it is Meta, as the previous section describes, under the Instagram Privacy Policy. For X, it is the X company its policy names for your country, under the X Privacy Policy.

These services can process this information in the United States and elsewhere outside the EEA, under their own policies. Which transfer safeguards each one relies on remains open for qualified external review.

Access, correction and export

Account-data tools act on the signed-in account. The export on the Web is version 17, and in the app too once the app is updated. It includes recorded consent, the Privacy Notice version you accepted and when, and, where one exists, a minimized age-eligibility record, alongside the profile, memberships, follows, blocks it set, posts, replies, reactions, saved posts, notifications and reports it filed, and your push choices and the phones registered for push: for each, its platform, app version and language, when it was first and last registered, and only the last six characters of its push token. Version 11 also includes your Suns: your balance, every entry of the ledger, your streak and the shop items you own, with when you got and equipped them. Version 12 adds your trophies, grade and profile options, the links to your social profiles, your letters to Felix and the reports you filed about letters; for each direct-message conversation, alongside its messages, whether it is a request and how far you have read it, and how far the other participant has once it is accepted; and your authenticator apps and your sessions as the Security settings list them. Version 13 adds the polls you wrote, with their choices and when they close, and your own poll votes, with the choice you made; never another member's vote. Version 14 adds, for each post you wrote in an event room, the event and the part of the room it was written in. Version 15 adds the time zone of each phone registered for push, your two reminder choices and the reminders FELIX sent you. Version 16 adds your community notes, with the editors' decision, its date and their reply, never the name of the editor who decided. Version 17 adds your three choices for pushes about private messages, lives and decisions about your content. The export does not include your Apple sign-in identity, which Supabase Auth keeps with your sign-in credentials. The age record contains no birth date or exact age. Passwords and authentication tokens are not included, nor are the secret key of an authenticator app and the IP addresses Supabase Auth records. The JSON export also does not contain the binary file for a profile photo or banner. 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 mailbox above receives requests that cannot be served through the account tools. The final handling procedure and response commitments remain pending; no response deadline is promised by this notice.

What account erasure does

For an account with a profile, confirmed erasure removes its posts, replies, reactions, saved posts, follows, blocks, memberships, notifications, push registrations and choices, Suns (the ledger, the streak and the shop items), trophies, grade and profile options, the links to its social profiles, its letters to Felix and the reports it filed about letters, its polls and its poll votes, every direct-message conversation it took part in, for both participants, its community notes, and private product feedback, 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.

The account deletion page, which you can read without an account, explains how to erase an account in the app, on the Web, or by email if you cannot sign in.

Retention and deletion

Account credentials are scheduled for deletion 30 days after a confirmed erasure. The active service removes or anonymizes the account's social data during that operation. An erasure receipt records the request time and retention boundary. Reaching the boundary makes credential removal eligible; the operator must execute and verify the purge.

Your phone's push token is deleted when you sign out in the app, when you turn push notifications off, when the sign-in session it was registered under ends (for example a sign-out from another device, a password change or the deletion of your account), when it stops being valid, and at the latest 90 days after you last opened the app. Once that session has ended no notification is sent to that phone, and the token is erased within a day. If the phone is offline when you sign out or turn push notifications off, the token is deleted at the next of these moments. If you turn off notifications for FELIX in the phone's settings instead, the app deletes the token the next time it opens. If another account turns push notifications on, on the same phone, the token moves to that account. A phone's time zone goes with its token. The record of a reminder is kept for 30 days, so that a day never gets two and the pause after three can be counted, and is deleted with your account. A push about a private message, a live or a decision about your content is kept for at most an hour, sent or not, and is deleted with the phone, with your account, or with the account of who wrote.

Your Suns ledger, your streak and your shop items are kept for as long as your account exists, and are deleted when you erase it.

Your trophies, grade and profile options, the links to your social profiles and your letters to Felix are kept the same way, unless you remove a link or delete a letter first, which you can do at any time. A letter that moderation removed is no longer shown, even to you, and is deleted when you erase your account. A direct-message conversation is kept, with its messages, its request state and its read markers, until one of its two participants erases their account; deleting a request only takes it out of your lists. Supabase Auth keeps an authenticator app until you remove it, and otherwise deletes it with your sign-in credentials. It keeps your Apple sign-in identity, with the address and the name Apple shared, the same way, and deletes it with your sign-in credentials.

Your community notes are kept for as long as your account exists and are deleted when you erase it.

A poll is kept with its post, and deleted with it. Your poll votes are kept for as long as both your account and the poll exist: a vote is deleted when the poll's post is deleted, and all your votes when you erase your account.

Reports and safety evidence are retained for 12 months after closure, moderation audit records for 24 months, and operational logs, service email and backups for no longer than 30 days unless an incident, legal hold or provider limit requires a documented exception. Exact provider deletion behavior and the adequacy of these periods remain open for external review.

Age eligibility

Launch thresholds are 15 in France, 14 in South Korea, 13 in the United States, 16 in other EEA countries and 18 elsewhere. The United Kingdom uses the 18+ fallback at launch. Once active, the service uses the date only transiently, stores the coarse result and sends only a one-use opaque receipt to Auth. FELIX does not collect parental consent: people below the local threshold may read public information without an account. Eligible people under 18 receive a hidden, reader-only account with no social writes, relationships, discoverability or messages. Detailed country-by-country review remains recommended.

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

A change that adds a new kind of personal data, a new recipient or a new purpose is a new version of this notice: it is dated, announced in What's new, and you are asked to accept it before you post, reply or write again. Any other change, such as a clarification or a correction, keeps the version you accepted: the date it was updated appears at the top of this notice and the change is announced in What's new, with nothing to accept again. External review of country rules, legal bases, processors and retention remains open. That review does not turn this notice into a certification.