Privacy policy

KFT offers optional accounts through Clerk. Clerk processes the details you use to sign in, account identifiers, session information, and security signals needed to authenticate you. KFT receives a verified user identifier when an account-only action calls its protected API. A KFT account is separate from your official Fantasy Premier League account: never enter or send your FPL password to KFT.

For a free account, KFT records how many projection edits you have used in Clerk's private account metadata, so the count follows your account across browsers and devices. That record holds the UK date, how many of today's free edits you have used, how many welcome edits remain, and the day your current free edits were made. It holds no projections, squads or plans, and only KFT's server can read or change it.

You can browse public projections and public-manager tools without a KFT account. When an action requires an account, KFT asks you to sign in before continuing. Account deletion and correction requests can be sent to the contact address below; requests may need identity verification.

Profile and Planner may ask for a numeric FPL manager ID. The site uses that ID to fetch public or semi-public official FPL API data such as manager profile details, team name, gameweek history, chip history, transfers, squad picks, bank, prices, leagues, league standings, fixtures, and bootstrap player/team data.

These requests are made through Netlify serverless functions where possible, mainly /.netlify/functions/fpl and /.netlify/functions/fpl-profile. The functions act as restricted proxies to official Fantasy Premier League API endpoints. KFT does not store manager profiles, squads, or saved plans in a KFT-owned database. Netlify may process technical request logs needed to deliver, monitor, and secure the service.

Because manager IDs can identify a public FPL team, avoid entering another person's manager ID in a way that would surprise them. KFT does not ask for private league credentials, paid-platform credentials, or official FPL login details.

KFT uses localStorage for theme preference, saved manager IDs, the Planner hide-xPts preference, saved Planner paths, the intro gate preference, your analytics choice (kft_analytics_consent), a cached copy of whether your account has KFT Pro (kft_pro_nav), whether you have seen the first-visit loading screen (kft_entry_first_v1), and small page-guide preferences. Profile stores a saved manager ID under kftProfileSavedManagerId. Planner stores a manager ID under kft_manager_id.

Your projection edits themselves stay in your browser: edits that apply across the site under kft_xpts_scenarios_global_v2_ (localStorage), edits made inside one table under kft_xpts_scenarios_table_v2_ (sessionStorage), and fixture difficulty edits under kft_fixture_fdr_overrides_v2_ (localStorage). They are not sent to KFT. The number of free edits you have used is kept with your account (see Accounts); your browser keeps a copy under kft_edit_allowance_v1 to show the count, plus the date of the last daily clear-out under kft_edit_sweep_v1. Changes made with free edits are deleted from your browser at midnight UK time; KFT Pro edits stay until you change or reset them. Clearing site data removes the edits but does not reset the count on your account.

If you save Planner paths, those saved plans are stored in your own browser under kft_planner_paths_v2. They can include manager ID, team name, squad, transfers, chip plan, lineup plan, captain plan, notes, gameweek, and saved date. This is local browser storage, not a KFT account. Anyone with access to the same browser profile may be able to see it.

KFT also uses sessionStorage, which your browser clears when you close the tab or window. It holds the FPL Team ID you entered for this visit, so every page uses the same team (kft_team_session_v1), and whether the loading screen has already shown this visit (kft_entry_seen_v1).

Local browser storage is controlled by your browser. It may persist across visits, sync across devices if your browser account syncs site data, or be removed by private browsing, browser cleanup tools, or manual site-data clearing. KFT cannot recover locally saved Planner paths after you clear them.

The public website loads local site files such as weekly_player_week.csv, mc_brackets_full_player_week.csv, and fixtures-list.csv to display projections, ranges, and fixture views, and match-calendar.csv for the fixture congestion calendar. That calendar is compiled ahead of time from the official FPL fixture list and ESPN's public scoreboard; your browser does not contact ESPN. Loading these files does not require a login. If you download charts, images, or tables in your browser, that download is handled locally by the browser.

KFT serves no advertising. The site loads no Google AdSense or other ad network, and its Content-Security-Policy does not permit advertising hosts to connect at all.

KFT uses Google Analytics 4 to understand which pages and tools people use, so it can improve them. This includes a few product events, such as reaching the daily free-edit limit or choosing a KFT Pro plan from it; these events carry no manager ID, squad or plan. It runs in Google Consent Mode. In the UK, the EEA and Switzerland, analytics cookies stay off until you choose Accept in the analytics bar; until then Google receives only cookieless, anonymous signals. Elsewhere, analytics is on by default. When analytics is on, Google Analytics sets cookies (such as _ga) to count visits and measure how the site is used. Advertising and ads personalisation are switched off, and KFT does not sell analytics data. Your choice is saved in your browser and you can change your analytics choice at any time.

Apart from that analytics cookie, KFT sets no first-party cookies in its own application code. Your browser's local and session storage hold your own work on your device: scenario edits, fixture-difficulty overrides, and saved transfer plans. That data stays in your browser and is not sent to KFT.

Clerk, your browser, CDNs, and hosting infrastructure may use their own cookies or storage for authentication, fraud prevention, and service delivery. KFT does not control every setting made available by those providers.

The site links to external platforms including Instagram, Substack, official FPL pages, and email links. The site's security policy allows only the connections needed for sign-in, payments, Google Analytics and official FPL API access. When you leave KFT for another platform, that platform's own privacy policy applies.

If you email KFT, the email address, message content, screenshots, attachments, and any manager ID or other details you include will be available to the mailbox receiving the message. That information is used to reply, investigate issues, correct data, or consider suggestions. Do not send FPL passwords, payment details, or private information that is not needed for the issue.

You can clear locally stored KFT data by clearing site data for kibasfpltreats.com in your browser settings. Clearing site data should remove localStorage, sessionStorage, and cookies for the site. You can also use private browsing if you do not want manager IDs or planner drafts to remain in your normal browser profile.

Payments are handled by Paddle (Paddle.com), which acts as the reseller (merchant of record). It collects the details needed to take payment and meet tax rules, such as your name, email address, billing country or address and card or other payment details, and processes them under its own privacy policy. The checkout may use its own cookies to process and protect the payment. KFT never receives or stores your full card number.

KFT receives from the provider only what it needs to run your subscription: customer and subscription identifiers, your plan, its status, renewal and end dates, your country for tax purposes, and payment, refund and cancellation events. KFT stores this with your Clerk account record and uses it to switch Pro on and off, handle refunds and support, and keep the records tax and accounting law require.

KFT also records on your account whether it was created before Pro launched, so the 12-month launch offer can be applied. Subscription records are kept while your account exists, and after that only for as long as tax and accounting law requires.

For privacy questions or data-correction concerns, contact gautamdivyansh.work@gmail.com.

KFT updates this policy when its account, advertising, analytics, storage, or hosting practices materially change. For privacy questions, account deletion, or correction requests, use the email address above.