Your data, explained
Privacy Policy
Effective 6 November 2026 · Apple TV, iPhone, iPad and bitemoni.com
Bitemoni is a player for sources you choose. Your saved library and viewing history stay on your device. TV setup temporarily passes connection details through our service. Apple handles purchases.
1. Who is responsible
Bitemoni is operated by Burak Ahmet Yörük, the controller responsible for the processing described here.
Burak Ahmet YörükFriedenauer Höhe 21
12159 Berlin, Germany
yorukburakahmet@gmail.com
Use this address for privacy questions, rights requests or support. Do not send playlist passwords, activation codes or payment-card details.
2. Information on your device
The app stores source addresses and credentials in the device Keychain. Profiles, saved items, collections, guide preferences, reminders, playback settings and resume history use local app storage. Bitemoni does not upload your viewing history or synchronize these records between your devices.
Local records remain until you remove them using the available app or operating-system controls. Remove saved sources in the app before uninstalling if you want their connection details removed from its active library: uninstalling an Apple app does not necessarily erase its Keychain entries. Device backups and operating-system retention follow your Apple settings; Bitemoni does not operate a cloud library backup.
3. TV setup and connection updates
When you connect a TV or update a source, the service processes a device label, source names and identifiers, random session identifiers, authorization tokens, timestamps and setup outcomes. Source names can contain personal information you enter. The website receives the selected TV's source labels so you can identify the correct source.
A playlist or Xtream server address, username or password entered on the setup website is temporarily relayed to your selected TV. Transfer data is encrypted in server memory; it is not saved as a permanent server-side source library. The service can process these details during the handoff. HTTPS protects transport between your browser and the Bitemoni setup service, and between that service and your TV; this is not a claim of end-to-end encryption between your browser and TV.
- An unclaimed setup code expires after five minutes. A claimed setup has a ten-minute completion window.
- A submitted credential transfer expires after at most two minutes, or earlier when its setup expires. Its encrypted payload is discarded on completion, rejection, cancellation, expiry or service restart.
- After setup ends, source labels and transfer details are cleared from the active session record. Limited identifiers, authorization hashes, timestamps and the final outcome remain for up to 24 hours to reconcile interrupted responses.
- Expired records are removed by routine cleanup; if the service is unavailable, cleanup resumes when it starts again. Database recovery copies, if retained, are separate from the active record and are not a credential vault: transfer payloads are not written to the pairing database.
We process this information to deliver the setup or update you request (GDPR Article 6(1)(b)), and protect the service against unauthorized access and replay (Article 6(1)(f), our legitimate interest in service security).
4. Website, cookies and security
Our hosting and network services receive connection information such as your IP address, request time, browser or app information and requested resource. The pairing backend uses IP addresses and random session tokens for security and request limits, not advertising or location profiling. Its rate-limit entries expire after five minutes and are cleared during routine cleanup.
The setup website uses one necessary first-party cookie, __Host-iptv_setup, to authorize your browser's setup session and protect requests. It expires 25 hours after it is set or renewed. Blocking or deleting it can interrupt setup. Merely opening these legal pages does not create a setup cookie.
The setup page keeps entered credentials in page memory rather than Bitemoni browser storage. Your browser or password manager may offer its own saving features. Appearance selection lasts for the current page. Fonts and images are hosted locally; the site includes no advertising, session-replay or third-party analytics scripts.
Routine request logging is disabled in the pairing application and its supplied origin proxy configuration. Hosting, network-security and fault records may still be processed to investigate incidents and maintain the service. Such records are limited to the period needed for that purpose and any applicable legal obligations; they are not used to build viewing profiles. Necessary session and security processing is based on Article 6(1)(b) and (f). We do not sell personal information or use it for cross-app advertising tracking.
5. Your media providers
Your device connects directly to the playlist, guide, artwork, preview and streaming hosts supplied by your sources. Those hosts can receive your IP address, requested media and any credentials needed for that source. Their privacy practices and content rights are separate from Bitemoni's. We do not relay your video stream through our pairing backend or receive a copy of your viewing history.
HTTP provider connections are not encrypted. Provider URLs, credentials (including Xtream login details), requested media and streams may be visible to others on the network. Use HTTPS provider URLs when available. This applies to direct provider connections; the Bitemoni setup service continues to use HTTPS.
Only add sources you trust and have permission to access. Artwork, descriptions and ratings are displayed when your source supplies them; Bitemoni does not send your library to IMDb.
6. Purchases and support
Apple processes App Store payments and maintains purchase records under its own policies. The app uses StoreKit transaction and subscription information to verify Pro access, restore purchases and respond to expiry or revocation. Bitemoni does not receive your payment-card number or Apple Account password. This verification takes place in the app; the pairing backend does not store your purchase history.
If you email us, we receive your email address, message and any information you choose to include. We use it to respond and resolve your request (Article 6(1)(b), or Article 6(1)(f) for general correspondence). We retain correspondence only as needed to resolve the matter, handle related claims and meet legal record-keeping duties (Article 6(1)(c) where applicable). Email is handled through Google Gmail. Please keep sensitive provider credentials out of support messages.
7. Service providers and international processing
We use Hetzner for hosting and Cloudflare for website delivery and network protection. Google processes email sent to our Gmail contact address. These providers may process technical or support information as needed to provide their services. Apple separately operates the App Store and its payment services. We may disclose information when legally required or necessary to establish, exercise or defend legal claims.
Some providers operate globally, including outside the European Economic Area. Applicable transfer mechanisms may include an adequacy decision or European Commission standard contractual clauses. Provider-specific information is available from Hetzner, Cloudflare, Cloudflare's contractual safeguards, Google and Apple. Contact us for information about safeguards applicable to our processing.
8. Your choices and rights
Where applicable, you can request access, correction, deletion, restriction or portability of your personal data, and object to processing based on legitimate interests. If processing relies on consent, you can withdraw it without affecting earlier lawful processing. We do not make decisions with legal or similarly significant effects using solely automated profiling.
Contact yorukburakahmet@gmail.com. We may request proportionate information to verify your request; do not send passwords. We normally respond within one month, subject to lawful extensions. We cannot remotely erase records that exist only on your device or identify every expired anonymous setup session.
You may complain to a data-protection authority, including the Berlin Commissioner for Data Protection and Freedom of Information, or the authority where you live or work. Providing source details is optional, but the requested playback or setup cannot work without the connection information it needs.
9. Changes to this policy
We will update this page when Bitemoni's data practices change and revise the effective date. Material changes will be communicated through the app or website as appropriate. New optional processing that requires consent will not be enabled merely by changing this page.