Privacy Notice
Last updated: 25 July 2026
This notice describes information processed by the FNSquadUp Telegram bot. It does not cover separate Discord services or the privacy practices of Telegram, Epic Games, Cloudflare, Fortnite Tracker, Firecrawl, Jina AI, or other third parties. FNSquadUp is an independent community tool for helping Fortnite players find Duo teammates. It is not affiliated with, endorsed by, or sponsored by Epic Games, Inc. or Fortnite.
1. Information stored for a player profile
To operate a Telegram profile, the bot stores the Telegram account identifier and platform type needed to identify that profile. The reviewed bot code does not read or store a player’s Telegram username, first name, last name, phone number, email address, contact list, or live location.
A player profile can also contain information entered or selected in the bot: Epic display name, Fortnite region, game platform/device, input method, team role, spoken language, Telegram UI language, and self-reported age. It can contain public Fortnite Tracker-derived information such as a Tracker profile URL, lifetime earnings, Power Ranking, eligible competitive divisions, and related check dates.
2. Duo matching and activity records
When a player starts a Duo search, the bot stores the profile relationship, selected game mode, tournament context, division, Power Ranking, squad size, search/match status, and creation/expiry times. A matching player may be shown selected profile information needed for that Duo experience, including Epic display name, region, platform/device, input method, role, language, age, and applicable competitive information. The bot does not show the raw Telegram account identifier in a match card.
The bot also keeps limited activity records for its owner dashboard: event time and type, internal profile references, nickname snapshots, locale, region, game/tournament context, and a pseudonymous visitor fingerprint. The fingerprint is derived from a Telegram account identifier with a secret key; it is not the raw identifier. The application activity table is designed not to store message text, IP addresses, phone numbers, passwords, OAuth codes, or access tokens. Technical error logs may contain technical identifiers or error details.
3. Optional Epic account verification
If Epic account verification is offered in the bot, it is optional and starts only when a player presses the verification button. Epic sign-in and any two-factor authentication occur on Epic’s own website. FNSquadUp does not ask a player to send an Epic password or two-factor code to the bot.
For a verification request, the bot creates a temporary request containing the Telegram account identifier, expected Epic display name, flow type, and expiry. A successful verification can store the Epic account identifier, verified display name, verification time, and verification version with the relevant Telegram profile. The application code uses short-lived OAuth state and one-time handoff records with a 10-minute validity window. It deletes state or a handoff when it is successfully used, and expired records cannot be redeemed. The application code does not write an Epic authorization code or access token to its SQLite or D1 application databases.
4. Providers and public data sources
Depending on the feature a player chooses, the bot may communicate with:
- Telegram to receive bot updates and send bot messages.
- Fortnite Tracker and Firecrawl for a player-requested or configured lookup of a public Fortnite Tracker profile. The requested profile URL includes the Epic display name.
- Official Fortnite competitive pages and a public reader service for an official Power Rankings eligibility check using public leaderboard information.
- Epic Games and Cloudflare-based verification infrastructure only if optional Epic verification is enabled and a player starts that flow.
Third-party services have their own privacy practices and may keep operational logs under their own policies.
5. Retention and deletion
- The bot does not currently provide a self-service profile-deletion command. Player profiles and successful Epic-verification records do not have an automatic deletion schedule in the reviewed code. An Epic verification record is removed if the related saved Epic identity changes.
- When a new daily Power Ranking snapshot is saved for a profile, older snapshots for that same profile are pruned outside an approximately 45-day window. There is no separate global snapshot-purge job.
- Activity records use a 90-day retention window and are pruned during bot initialization or when a new activity event is recorded; a long idle period can delay physical cleanup.
- Completed or abandoned registration-progress records use a 30-day cleanup window. Unfinished records do not have a separate hard-purge timer in the reviewed code.
- A pseudonymous first-start marker can remain to prevent duplicate first-start notifications. It is not a raw Telegram identifier.
- Duo searches stop being active after their expiry, but their database rows are not necessarily immediately removed.
6. Questions
For questions about this notice or information associated with a FNSquadUp Telegram profile, a player can message @FNSquadUp_bot. The bot may need enough information to identify the relevant profile without disclosing another player’s data.
7. Security reminders
Players should enter Epic credentials only on official Epic pages and should never send passwords, two-factor codes, recovery codes, or account secrets to FNSquadUp. No system can guarantee absolute security.
8. Changes
If this notice is published and later changed, the publication should show an updated date.