What the site handles and where it goes

Accounts and passwords

The inspected website has no KFT user account system. There is no KFT sign-up, no KFT password, and no feature that needs your official FPL login. Some tools ask for a public FPL manager ID because that is how official FPL public pages identify teams. A manager ID can point to public FPL profile information, so it should still be treated as personal data where it identifies a person.

Manager IDs and FPL data

Profile, Planner, and Live-style tools 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, bootstrap player/team data, and live event data. KFT Live also fetches official FPL bootstrap, fixtures, and live event data for matchday views.

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. The inspected code does not show KFT storing manager profiles, squads, or saved plans in a KFT-owned database. Hosting providers such as Netlify may still process normal technical request logs needed to serve and secure the site.

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.

Browser storage

KFT uses browser storage so the tools feel less repetitive. The inspected code uses localStorage for theme preference, saved manager IDs, the Planner hide-xPts preference, saved Planner paths, the intro gate preference, and small interface preferences for the page guide. Profile stores a saved manager ID under kftProfileSavedManagerId. Planner stores a manager ID under kft_manager_id.

If you save Planner paths, those saved plans are stored in your own browser under kft_planner_paths_v1. 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.

The homepage also uses sessionStorage to cache official FPL bootstrap data temporarily under kft_bootstrap_static_v1. That cache helps avoid repeated requests during the same browsing session and is not a user account.

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.

CSV and projection files

The public website loads local site files such as weekly_player_week.csv, mc_brackets_full_player_week.csv, and fixture-list.csv to display projections, ranges, and fixture views. 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.

Advertising, cookies, and analytics

Google AdSense is active in the inspected pages through pagead2.googlesyndication.com using publisher ID ca-pub-4156717033506549. The ads.txt file also lists Google advertising for the site. Google ads and related Google ad services may use cookies, local storage, device identifiers, or similar technologies to serve ads, measure ads, prevent fraud, and perform ad-related checks.

No Google Analytics gtag or similar analytics tag was found in the inspected website code. No first-party document.cookie usage was found. That does not mean no cookies can ever be set, because advertising providers, embedded scripts, browsers, CDNs, or hosting infrastructure may still use their own technologies. If analytics, consent tooling, accounts, or backend storage are added later, this policy should be updated before or at the time those features go live.

Your ad and cookie controls may depend on your browser, region, Google settings, and any consent tools shown by advertising services. KFT does not control every setting made available by Google or other third-party providers.

Third-party links and scripts

The site links to external platforms including Instagram, Substack, official FPL pages, and email links. Some pages load GSAP from cdnjs for interface animation. The site's security policy also allows connections needed for Google advertising and official FPL API access. When you leave KFT for another platform, that platform's own privacy policy applies.

Email and direct contact

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.

How to clear local data

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.

Questions

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

This policy reflects the inspected public website files as of the date above. If KFT later adds accounts, payments, comments, saved cloud plans, a database, analytics, newsletters collected directly on-site, or other backend storage, this page should be updated to explain the new data flow before users rely on it.