Privacy Policy
Last updated:
Read how the app and website use information, which controls are available, and what happens when you share an account or remove the app.
About this notice
This notice explains how the BeeForTV Android app and beefortv.com handle information. For privacy questions or requests, contact BeeForTV support at [email protected]. The app is a player for your own compatible Stalker portal account; BeeForTV does not supply channels or subscriptions.
Account setup and QR processing involve your device, while other app features communicate with your account provider and the services described below. The privacy controls for network contribution, notifications, usage statistics, and crash reports are separate. Features and controls can vary with the installed app version; the crash-reporting controls below apply to versions that include them.
Account information and local storage
The app stores saved account names, portal URLs, MAC addresses, connection details, preferences, and account-related viewing information in its local database and app settings. This can include favorites, recently used items, playback progress, and cached channel, movie, series, and program-guide information.
These local records let the app reconnect and restore your experience. They are stored in Android app storage; QR encryption does not mean that all database or settings records are encrypted by BeeForTV.
When you sign in or play content, the app sends requests to the portal and media servers for the account you selected. These requests can include the account MAC, session tokens, identifiers derived from the MAC, and the content being requested. Those servers also receive network connection information, including your IP address. Their handling of that information is governed by the account provider’s policies.
Network contribution through Infatica
BeeForTV includes an Infatica network-contribution component. When enabled, it can use your device’s internet connection to route third-party traffic to public web resources. The traffic uses your connection and public IP address and can consume data and device resources, including while the app is in the background.
The app supplies network information such as connection type and DNS configuration to the component. Infatica describes processing IP addresses, device/network and connection metadata, participation records, traffic-volume information, and security records for operating its network. See Infatica’s Privacy Policy for its data practices.
Firebase Analytics, Crashlytics, and messaging services do not provide this network-contribution feature. Network contribution does not enable optional statistics or crash reports, and turning it off does not change those separate choices.
Network contribution controls
The current app presents a Network contribution notice after you reach Home. Selecting Got it enables contribution. The notice has a Got it button and does not offer a separate decline button.
To stop contribution, open Settings → Network contribution and turn the switch off. The app saves the off state and requests the service to stop. It does not simply reset the switch to on each time you reopen the app.
After you switch it off, the app schedules a reminder after three hours. The reminder is shown when an appropriate app screen is active; time passing alone does not turn contribution back on. Selecting Got it on a later notice enables it again. An enabled service may resume during later app use or when Android restarts it.
On Android 13 and later, the app requires notification permission for contribution to run. Denying that permission stops or prevents contribution in the current implementation. You can manage notification permission in Android’s app settings.
Statistics, crash reports, notifications, and QR scanning
Optional app usage statistics
In versions with the Usage statistics setting, Settings → Usage statistics lets you choose whether to share Firebase Analytics data. Collection is off by default until you enable it. Reports include app and Android versions, device type, approximate country, feature use and network-contribution choices or service outcomes. These are installation-based statistics, not a precise count of people. They do not contain portal or MAC addresses, stream URLs, media titles, search text or private QR data. Advertising identifier collection and ad personalization are disabled. You can stop future collection in Settings; previously collected aggregate reports are not automatically erased.
Older app versions initialized Firebase Analytics and OneSignal at startup. This release replaces OneSignal with Firebase Cloud Messaging. See Firebase privacy information.
Optional crash reports
In versions that include crash reporting, BeeForTV uses Google Firebase Crashlytics to help investigate app crashes. Crash reports are off by default. You can enable or disable them in Settings → Crash reports. This choice is separate from Usage statistics, notifications, and network contribution. You can use the player and contact support with crash reporting turned off.
When enabled, reports can include the crash time, exception type, code stack traces, app and Android versions, device model and architecture, app state, and technical information such as available memory, storage, and battery state. Firebase also uses installation and session identifiers to associate reports. These identifiers mean the reports should not be treated as anonymous.
Before reports are stored or sent by Crashlytics, BeeForTV filters out exception messages, app logs and breadcrumbs, custom attributes, user identifiers supplied by the app, thread names, and raw Android “app not responding” traces. Crash reports exclude portal URLs, MAC addresses, provider access tokens, stream links, profile names, media titles, search text, and private QR data. Diagnostic code locations and the technical information described above are retained. Sending reports also involves an ordinary network connection to Google’s services.
If you contact support about a crash, we may ask you to enable Crash reports voluntarily, reproduce the problem, and reopen BeeForTV so a report can be sent. This does not recover crashes that happened while reporting was off, and not every playback or app problem produces a crash report.
Turning Crash reports off stops new report collection and requests deletion of reports still pending in Crashlytics. An upload already handed to Google’s transport service may finish. Turning the setting off does not delete reports already received by Firebase. See retention and deletion and privacy requests below.
Notifications and suggestions
The app requests announcements using its version, language and phone/TV type. It caches the latest 15 eligible messages in Settings → Notifications, with local read status. Expired messages are hidden; withdrawals apply after the next successful refresh. Devices with Google Play services can use Firebase Cloud Messaging, which processes an installation token and topic subscriptions. Android notification permissions control visible background notifications. Devices without Google services check for messages while the app is open; no background delivery is promised.
Settings → Suggestions and problems sends the message you enter, app version, device type, manufacturer/model, Android version, language and an optional reply email to BeeForTV support. Do not include passwords, private account details or QR codes. The server may add an approximate country from the connection address without asking for location permission. It does not save that raw address with your report; country remains unknown when unavailable. We use this data to investigate and respond, not for advertising. These settings are separate from network contribution.
Google ML Kit barcode scanning
The app uses ML Kit to read camera frames and QR images on your device. Google states that these input images and decoded results are not sent to its servers by ML Kit. ML Kit can send device/app information, installation identifiers, performance and usage metrics, and API configuration data. See ML Kit’s privacy information and data disclosures.
QR codes and account sharing
The website encrypts the portal URL and MAC address in your browser and generates the QR locally. Its QR form does not upload those values to BeeForTV’s server or save them in browser storage. The app also generates account QRs locally using bundled assets.
A QR contains an encrypted copy of the portal and MAC inside a website URL. A normal camera opens the website; the compatible BeeForTV scanner reads the account details. The part after the # character is not included in the browser’s HTTP request, but the full link can remain in browser history or be available to software handling the link.
Treat the QR and its full link as account credentials. A compatible app can decode them. Encryption is not a password restriction on who may use the QR. Downloaded, photographed, copied, or shared QRs remain with their recipients until separately deleted. Sharing through another app also subjects the image to that app’s handling.
Imported QR images may be copied temporarily into the app’s private storage for decoding and then cleaned up. After decoding, signing in contacts the relevant account provider as described above.
Transfers between devices and playback apps
When you choose Synch TV/Phone, BeeForTV discovers other receiving devices on the local network and sends the saved user list and associated library data to the device you select. This includes account details and can include favorites, categories, and viewing-state records. It is a direct device transfer, rather than a BeeForTV cloud account backup.
The current synchronization connection does not add transport encryption or a pairing password. Use it only on a trusted private network and confirm the receiving device. The recipient keeps a separate copy.
Phone Live sharing starts a local HTTP stream for the current channel. The receiving device requests video segments from your phone; the phone creates temporary media files while relaying the stream. The QR opens a local helper page, while the displayed link points directly to the stream. This connection has no separate pairing password or transport encryption, so use a trusted private network and keep the link private. Stop sharing ends the active relay; Exit app (keep sharing) lets it continue in the background subject to Android restrictions.
If you open a video in an external player, that app receives the playback information it needs and handles it under its own policies.
Permissions and device features
- Camera: used to scan account QR codes when you open the scanner.
- Images and storage: used where applicable to import or share QR images, save exported files, and download app updates. Android version and the action you choose affect which permissions are requested.
- Microphone and voice search: voice search invokes the device’s speech-recognition service. That service may process speech remotely under its own settings and policy; the recognized text is returned to the app for search.
- Notifications and background services: used for supported notifications and running tasks, including enabled network contribution.
- Network access: used for portal connections, media, app information, third-party SDKs, and transfers between devices.
- System settings: supported brightness controls may request permission to change display settings.
You can review granted permissions in Android’s app settings. Revoking a permission may prevent the associated feature from working.
Website, app information, and support
Cloudflare and our hosting server process requests to deliver and protect the website and app-information API. Request information can include IP addresses, browser or app request headers, requested paths, timestamps, response codes, and diagnostic information. This information can appear in access or error logs. Cloudflare may use security-related cookies according to the features enabled. See Cloudflare’s Privacy Policy.
The app-information request identifies the application package and requested operation so the server can return configuration, website links, and update information. That request does not require your portal URL or MAC address.
Website statistics are separate from app statistics. If you allow statistics in Privacy choices, Google Analytics can measure page visits, approximate country, browser/device information, APK download clicks and QR-generation success or failure. We send only approved page names and event labels, excluding URL queries/fragments and all QR form contents. Analytics cookies and identifiers are used only after permission; Privacy choices lets you decline future collection and remove this site’s analytics cookies. No advertising tracking is enabled. APK clicks do not confirm installation. Hosting services and download hosts such as GitHub still receive ordinary requests regardless of this choice.
If you email [email protected] or contact the linked support channel, the recipient and messaging provider receive your contact details and the message or files you choose to send. Do not send account credentials or a private QR unless necessary for the support you are requesting.
Retention, backups, and deletion
The notification cache contains at most 15 eligible messages. Read status, usage-statistics preferences, and crash-reporting preferences are kept locally and excluded from Android backup. Resolved feedback is deleted once it is more than 12 months old; unresolved reports may be kept while support is ongoing. Contact support to request removal. Server rate limiting uses short-lived keyed IP hashes. Dashboard audit records are kept for up to 90 days and database backup files for up to 14 days. Hosting and Google Analytics have separate retention settings; contact support about information held for this service.
Google states that Firebase Crashlytics retains crash stack traces and their associated identifiers for 90 days before beginning removal from its live and backup systems. This is not a promise of immediate deletion on day 90. See Firebase’s privacy and retention information. Usage statistics have separate Google Analytics retention settings.
Saved accounts and associated settings remain on the device until removed or until the app’s data is cleared. Cached information may be replaced as you use the app. You can remove saved users through Users List or clear app data through Android’s settings. Uninstalling normally removes private app data from that installation.
Android backup and device transfer can apply to eligible app data, depending on Android and device settings. In the current app, the account database, account settings, privacy preferences, stored Crashlytics reports, and network-contribution state are excluded by the app’s backup rules. User-created exports and copies sent to another device must be managed separately; these are not removed by changing a privacy setting.
Clearing app data or uninstalling does not automatically delete exported QR images, copies on another device, support messages, hosting logs, or records already processed by third-party services. Those records have separate retention rules and settings. Contact support about records held for the BeeForTV service, and consult the linked providers for their records and deletion options.
Security and connection choices
Keep your device locked and updated, use trusted networks, and keep account QRs private. QR encryption does not protect an account after you share a usable code, and it does not encrypt every local app record or every network connection.
The player supports both HTTP and HTTPS portal URLs. An HTTP portal or stream connection is not encrypted in transit; use HTTPS where your account provider supports it. No app, storage system, or network transfer can be guaranteed completely secure.
Your choices and privacy requests
You can manage saved accounts, stop network contribution, turn off Usage statistics or Crash reports independently, control Android permissions, and remove local app data using the controls described above. To request access, correction, deletion, restriction, portability, or to object to processing of information held for the BeeForTV service, contact [email protected]. The rights available depend on your location, the information involved, and applicable law.
Where processing relies on consent, you may withdraw it; withdrawal does not undo earlier processing. You may also complain to the relevant data-protection authority. We may need information to identify the records concerned before responding. A request to BeeForTV does not automatically remove records controlled by your portal provider or another service.
Service providers and international processing
Information is shared as needed with the portal/media providers you use, the SDK and hosting providers described above, support-message providers, and recipients or playback devices you select. Their infrastructure may process information outside your country. Their linked policies describe their processing and transfer arrangements.
Necessary information may also be disclosed in response to a valid legal requirement or to address misuse or protect the service and users. This notice does not promise that every service stores data in the same country.
Children
BeeForTV is not intended for children under 13. If you believe a child has provided personal information through the app or support channels, contact [email protected] so the circumstances and available deletion steps can be reviewed.
Changes to this notice
This page may be updated when the app, website, or data practices change. The date above identifies the latest revision. A website policy update does not itself change a saved app setting or provide consent for a new purpose.
Contact
BeeForTV support and privacy: [email protected]
Website: beefortv.com
Terms and other services
The app licence and usage terms are in the Terms of Service. A linked provider’s policy applies to its own services. Read the policies of your portal, backup, download, and messaging providers when deciding what information to share.