TRANSPARENCY

Privacy Policy.

Last updated: 9 October 2026

Free Sports Analysis operates the Telegram bot @FreeSportsAnalysisBot and this website. This policy describes information processed by the supplied software. The operator should review and add a working privacy contact before publishing.

Information collected

When you interact with our bot, we store your Telegram numeric user ID, username (if any), first name (if provided by Telegram), and the times you first and last interacted. We log commands, delivery outcomes, and timestamps for reliability. We do not need your phone number to operate the bot.

How information is used

We use these details to respond to commands, provide opted-in update messages, show aggregated usage statistics, maintain security, and troubleshoot delivery. Subscribers who explicitly opt in may receive football updates from an administrator. You can opt out any time with /unsubscribe. The community button takes you to Telegram, where Telegram's own privacy terms apply.

Sharing and storage

Data is stored with our hosting provider and processed by Telegram when messages are exchanged. We do not sell personal information. Authorized administrators can access limited interaction records. Data retention should be set by the operator before launch; this starter version retains records until removed by an administrator.

Your choices

You can send /unsubscribe to stop optional notifications, or block the bot. Blocking prevents further messages but does not automatically delete previously stored database records. To request access or deletion, contact our community administrators at our Telegram community. Before launch, replace this with a verified direct privacy contact able to handle individual requests.

Age and risk notices

Information is intended for adults where betting-related material is discussed. Match analysis cannot guarantee an outcome. Bet responsibly and follow your local laws.

Changes

We may change this policy as functionality changes. The last-updated date will be revised when changes are published.

Operator checklist: designate an actual privacy contact, a retention period, and deletion workflow before going live.