Privacy Policy

Controller responsible for data processing:

Pascal Bossert | BOSSERT.IO

c/o MDC Management#6445

Welserstraße 3

87463 Dietmannsried, Deutschland

Email: privacy@iptvbuddy.app

Android/iOS App: We store app settings, profiles, favorites, history, watchlists, playback progress and session/account information. Provider credentials and synced favorite data are stored in encrypted form. Offline movie and series downloads are stored on the mobile device.

Camera permission (Android/iOS App): You can use the camera to scan a TV pairing code with the mobile app. This scan is not required for setup through the portal or its integrated web editor.

Account sync: Profiles, provider credentials, M3U lists, category selections, favorites, watchlists, supported movie/series progress, EPG mappings, source choices and connected devices are kept available through your IPTV Buddy account. The portal processes these account data for setup and management. Local app data and synced account data can therefore exist alongside each other.

Android TV App: We store profiles, favorites, history, watchlist, and recording-related information (for example planned or managed recordings) on the TV device. Data available through sync can also be kept up to date on your devices through your IPTV Buddy account.

Content retrieval: For playback, the app connects to services of your IPTV provider. This involves technically necessary connection data (in particular your IP address and request information).

Program information (EPG): Program data is retrieved from epgshare01.online. The TV app can also retrieve EPG data from your Xtream provider. Depending on the source, technically necessary connection data such as your IP address and request information is sent to EPGShare or your provider; provider requests also use the stored provider credentials.

Public IP address lookup: The app can determine your public IP address via the services ipify (ipify.org), ifconfig.co, or checkip.amazonaws.com. Your IP address is processed to the extent required for this function.

Portal and web editor: We process your email address, account association, profiles, provider credentials, M3U lists, categories, favorites, device information and setup jobs. Drafts and transferred catalog data are processed for setup/editing and stored encrypted on the server. The web editor connects to a reachable TV or mobile device with the selected profile loaded; import/export files are processed for the respective operation. Exported favorite files can contain M3U URLs in plain text.

Browser storage: The portal uses technically necessary login and session cookies for login requests, account association and secured sessions. The website and portal store your language preference locally in your browser; you can remove these entries through browser settings.

External videos: The TV installation guide embeds a YouTube video through youtube-nocookie.com. Loading the embed connects to YouTube. App trailers can also open YouTube. In particular, your IP address and technical request/device information are sent to the video provider.

IPTV Buddy API: We process account association, device/session information and technical connection data, particularly IP addresses. This supports account sync, portal setup, device management, access verification, program information and secure operation including request limits. Sports Hub and discovery data are also delivered through our API.

Email and one-time-code sign-in: For your IPTV Buddy account, we process your email address, an internal user ID, short-lived login requests and session information. We send a one-time code to your inbox and store verification information for sign-in. No account password is required. Sign-in associates your account for sync, device management and TV access. The legal basis is Art. 6(1)(b) GDPR.

TV access, trials and subscriptions: We process account association, device information, trial/validity periods and purchase, status and validation information. Store purchases use references such as purchase tokens; web subscriptions use Stripe customer, checkout, subscription and invoice references. Eligibility for the one-time 24-hour trial also uses cryptographically derived verification values from provider credentials or M3U access information to limit repeated use. Mobile playback is free; TV playback requires an active subscription or an eligible trial.

Technical diagnostics with Sentry: The mobile app and TV app process error/crash reports, technical device data, operating-system/app versions, timestamps, stack traces and sanitized technical context. The mobile production configuration also includes sampled performance data, technical logs and sampled or error-related session recordings. Text and inputs are masked and media is blocked. The TV configuration disables performance tracing and interaction recording.

We use these diagnostic data for technical troubleshooting, stability monitoring and investigation of performance problems. They are not used for advertising, marketing or advertising profiles. Technical analysis can include sequences of screens and actions to the extent captured for diagnostics.

If you voluntarily submit an error report or feedback, its contents and technical context are processed to investigate the problem. Do not include provider credentials, one-time codes or private playlist contents in an error report.

We process personal data to provide app, portal and editor functions, associate accounts and devices, sync data, display program information, manage trials and TV subscriptions and operate the systems securely.

Legal bases are in particular Art. 6(1)(b) GDPR (performance of the usage contract / provision of functions), Art. 6(1)(f) GDPR (legitimate interests, in particular operational security, protection against misuse, enforcement of usage limits, and service stability), and where applicable Art. 6(1)(c) GDPR (legal obligations).

Technical diagnostics through Sentry support stability monitoring, troubleshooting, investigation of performance problems and resolution of faults. The existing legal bases for error diagnostics are particularly Art. 6(1)(f) GDPR and, where needed to provide or restore contractual app functions, Art. 6(1)(b) GDPR.

Diagnostic data are not used for advertising, marketing or advertising profiles. Masked session recordings and performance data support technical investigation of problems.

Store and payment providers: Google Play and the Apple App Store process store purchases and their payment data. Web subscriptions use Stripe for payments, subscription management and invoices. We send particularly email addresses and account/purchase references and receive status, subscription and invoice information. Payment details are entered with the respective payment provider.

IPTV providers, EPG and external media: Playback, provider checks and catalog retrieval send requests to your provider; EPG requests go to EPGShare or, in the TV app, your Xtream provider. Posters, channel logos and sports artwork can be retrieved from external image sources specified in the metadata. Each recipient receives technically necessary connection data.

Public IP lookup services: If you use the corresponding function, your public IP address is queried via ipify (ipify.org), ifconfig.co, or checkip.amazonaws.com. This involves processing technically necessary connection data (in particular your IP address).

Sentry: The service processes the technical diagnostic data described above for the mobile and TV apps. The apps use Sentry endpoints in a European data region; the settings and contractual terms applicable to our projects govern that processing.

Infrastructure and email delivery: Hosting providers operate our API and data storage. A configured email service delivers one-time codes, processing the recipient address, message containing the code and technically necessary delivery information.

Local app data (for example profiles, favorites, history, watchlist, credentials, session data) generally remains stored on your device or TV device until you delete it in the app or uninstall the app.

Portal sessions: The login cookie associates the login request. The session cookie is required for sign-in and has a maximum lifetime of 30 days; the server session becomes invalid after seven days of inactivity. Logout, revocation or account deletion can invalidate it earlier. Expired login/session identifiers no longer authorize access.

Subscription and validation data: We store purchase-related references (for example purchase token), status/validation information, and user ID only as long as required for activation, contract performance, fraud prevention, and enforcement of usage limits, and where applicable to fulfill legal obligations.

Account and sync data remain stored for account functions. You can request account deletion in the app or portal; the portal confirms deletion with a new email code. Sessions and device access are revoked. A web subscription is ended before final account deletion is completed; deletion may remain pending while payment processing is resolved. Store subscriptions must also be canceled in the respective store. An account is not automatically deleted solely because it is unused. Statutory retention obligations and payment providers’ independent data storage remain applicable.

Sentry data: Retention of error reports, performance data, logs and session recordings follows the retention settings of our Sentry projects.

We apply technical and organizational measures to protect data (for example access restrictions and protection of sensitive information).

Sensitive provider and synced configuration data are stored encrypted. Account, device and editor access is tied to valid sessions or device authorization. Technical verification and diagnostic data are processed for secure operation and troubleshooting, not marketing.

Sentry technical data are sanitized; the mobile configuration masks text/inputs in session recordings and blocks media. These measures do not replace careful selection of information you voluntarily include in feedback or error reports.

You have the right to access, rectification, erasure, restriction of processing, data portability, and objection.

Where technical diagnostic data are processed under Art. 6(1)(f) GDPR, you can object on grounds relating to your particular situation.

You also have the right to lodge a complaint with a supervisory authority.

If you use the contact form, we process the required fields you enter (name, email address, subject, message) and any additional information you provide voluntarily.

We also process technical connection and metadata (in particular IP address, timestamp, and request information) to the extent required for secure operation, abuse detection, and request limiting.

Processing is carried out to handle and respond to your inquiry and to ensure the security and stability of the contact form operation. The legal bases are Art. 6(1)(b) GDPR (where your inquiry relates to entering into or performing a contract) and otherwise Art. 6(1)(f) GDPR (legitimate interests in efficient communication, abuse prevention, and operational security).

We process form data to handle your request through our API and the database at our hosting provider. The host provides the technical processing infrastructure.

Data is stored only as long as necessary to process your inquiry and any follow-up questions; statutory retention obligations remain unaffected. Without the fields marked as required, we cannot process your inquiry.