HoiPlayer
Home / App privacy
App privacy

Your player.
Your privacy.

What stays on your device, what reaches HoiPlayer, and what your chosen sources receive.

Updated 2 November 2026 · Android and Windows 0.5.20+74 · Google Play 0.5.21+75 (closed testing) · Microsoft Store Windows 0.5.25+79

Which edition does this notice cover? Sections 1–8 describe Android and Windows 0.5.20+74 and the Microsoft Store edition for Windows 0.5.25+79. Edition-specific source-access timing and update handling are identified below. The Google Play edition — 0.5.21+75 section explains the version-specific handling for the Android closed-testing edition.

HoiPlayer is a media player. It does not supply channels, films, series or subscriptions. You choose the sources you have the right to use. Connecting your installation and managing playlists involves data processing; this is not a “no data collected” service.

01

About this notice

This notice covers the reviewed Android phone, Android TV and Windows editions identified above, including their store and website distribution channels. It describes app use and the HoiPlayer connection service. If you open our playlist portal, register as a partner or contact us, the website and portal privacy notice provides additional details about those interactions.

02

What stays on your device

The app stores your active source sign-in details and installation access information using platform secure storage. Device-local parental-control settings include a protected PIN verifier rather than sending your parental PIN to HoiPlayer.

Other local information includes your language and playback settings, favourites, recently viewed item references, playback positions, category choices and source-specific profiles. Catalogues and artwork are cached to make browsing quicker. These caches may contain titles, images and source or playback links supplied by your provider; links can themselves contain access information. Ordinary preferences and caches are not a promise that every local file is encrypted.

The reviewed app-to-HoiPlayer service requests do not upload your favourites, viewed-title history or playback positions. Your content provider can still observe requests made to its service.

03

Connecting your installation

HoiPlayer uses a derived device identifier, a separate installation secret and a visible PL device code to recognise and authenticate your installation. On Android, the app derives the identifier locally from the platform Android ID. On Windows, it derives an application-scoped identifier through the platform device-identity path. These paths send derived values rather than the underlying raw platform identifier. The visible PL code is generated by HoiPlayer; it is not a claim to reveal your network hardware MAC address.

Our connection service receives the installation authentication values, reported platform, available app version and build, and—for Android—the phone/TV classification. It records the latest authenticated contact and playlist-management state. Source-access checks also send the source server’s protocol, host and port, without a full content path or source password in that check. In the 0.5.20+74 editions, checks can repeat during playback to apply source-access policy. In the Microsoft Store 0.5.25+79 edition, the normal idle source-policy refresh interval is five minutes. The schedule can differ while reconnecting or respecting a shorter existing policy lease. A new source selection or a new playback session can require a current access check. While an admitted playback session remains open, periodic source-policy polling is suspended; a background refresh failure or cached-policy expiry does not stop that admitted session.

Our hosting service necessarily receives your connection IP address. The service can derive an approximate country using a locally stored country database. This does not use GPS or send the IP to an external location lookup. The latest country may be inaccurate or reflect a VPN. Authorised administrators and a partner connected to your device can see operational device information, including this country.

Server records retain hashed verification values rather than readable installation secrets. Matching registered identifiers can restore installation access to saved playlists after reinstallation; matching is not hardware attestation. These identifiers are used for connection, continuity and abuse protection, not advertising.

04

Playlists, the web portal and partners

When you or an authorised partner save a playlist on hoiplayer.com, the service processes and stores its name, type, source address and any source credentials included in it, then sends the saved details to your authenticated app. Saved playlist payloads are encrypted on the server, with the key outside the public website. This is server-side encryption: the service must be able to read the details to provide playlist management.

The app displays a current six-digit Device Key, valid for up to 10 minutes and usable once, and may open an opaque handoff link in your browser. The app does not treat the public PL code alone as an owner credential. Sharing the current key with a partner authorises that partner to manage the device’s playlists. Only share it with someone you trust. The portal notice explains partner access, browser sessions, continuity requests and their retention in more detail.

05

Requests to your sources and other hosts

The app connects directly to the source you choose for account validation, catalogues, programme information and playback. These requests can include your source username or password and the requested channel, film or episode identifier. The receiving provider sees your IP address and the technical information needed to serve the request, including the player’s user agent. It can learn which content was requested.

Artwork and available previews may load when you browse or open details. Their addresses are supplied by your source and may point to separate image, media or delivery hosts, including TMDB image hosting. Those hosts receive the corresponding network request. The reviewed releases do not configure a separate TMDB API metadata-enrichment service; source-supplied metadata and image requests remain separate.

HoiPlayer service requests use HTTPS. Your source can use an HTTP or HTTPS address; an HTTP source does not provide transport encryption. Providers, delivery hosts and app stores have their own privacy practices and retention. HoiPlayer does not control their independent handling.

06

Diagnostics and updates

The reviewed apps do not include an advertising SDK or a third-party analytics or crash-reporting integration. Limited playback and connection diagnostics are handled locally using bounded event categories and counters. These releases do not automatically upload app playback logs to HoiPlayer or a third-party reporting service. Hosting access logs and service abuse protection are separate and can process connection information.

Uptodown and APKPure editions rely on their distribution channel for updates; they do not fetch or install the website update package. The Microsoft Store 0.5.25+79 edition uses Microsoft Store for app updates and does not download or install website EXE updates. Website editions can request a signed release feed and installation files from hoiplayer.com, which creates ordinary hosting requests. Opening a store or support website subjects that interaction to the destination’s privacy practices.

07

Retention and your choices

Local settings and caches remain until changed, replaced or removed using the applicable app or operating-system controls. The history-clearing control clears history and resume positions for the current source profile; it does not clear favourites or every saved source profile. Logging out removes the active source sign-in details and cached account information. It does not delete saved server playlists or guarantee that all local caches and other profiles are erased.

Device records and saved server playlists remain until removed. Expiring a key or removing the app does not itself delete those service records. The portal notice describes request-triggered cleanup, operational records and backups; there is no promise that all backup copies are erased immediately or after a fixed automatic period.

Use the playlist portal to remove saved playlists or authorised partner access. Contact us to request access, correction or removal of HoiPlayer service information. We may need enough information to identify the relevant device and verify the request. Your source provider and app store handle requests about their own records.

08

Contact HoiPlayer

For privacy questions or requests, email support@hoiplayer.com. Tell us which app edition and interaction your question concerns. Do not send passwords, Device Keys, parental PINs or complete private playlist links.

This notice is specific to the reviewed releases. Material changes to the app’s data flows require a corresponding notice update.

09

Google Play edition — 0.5.21+75

This section applies to the Android Google Play closed-testing edition of HoiPlayer, package com.hoiplayer.app, version 0.5.21+75. It describes this edition’s data handling, including its update channel and source-access checks. Sections 1–8 above cover the 0.5.20+74 releases and the Microsoft Store 0.5.25+79 edition, with edition-specific differences identified there.

This Google Play edition uses Google Play as its update channel and disables the website APK download and installation path. Separate TMDB API metadata enrichment is disabled in this edition. Your source’s own catalogue, artwork and preview requests remain as described in Requests to your sources and other hosts.

The normal idle source-policy refresh interval is five minutes. The schedule can differ while reconnecting or respecting a shorter existing policy lease. A new source selection or a new playback session can require a current access check. While a playback session remains open, periodic source-policy polling is suspended; a background refresh failure or cached-policy expiry does not stop that admitted session.

HoiPlayer continues to receive installation identifiers and authenticated contact or playlist requests, and retains the latest approximate connection country as described above. Its operational views include registered-device, recent-contact and playlist-management totals. The app sends source-account credentials and selected content requests directly to the source you choose. Local favourites, viewed-title history and playback positions remain subject to the on-device handling described in this notice.

To request removal of information held by HoiPlayer, follow Retention and your choices or contact support@hoiplayer.com. We may need to identify the relevant device and verify your request. Requests are assessed against applicable legal and security requirements; the portal notice explains operational records and backup retention. Your source provider and app store handle their own records.

10

Planned Samsung TV edition

Before launch: proposed privacy supplement. This section describes the reviewed local preview candidate for Samsung Tizen TVs. It does not announce that the app or its connection service is available. The handling below is intended to apply if this edition launches with the reviewed features. The Android and Windows sections above retain their existing edition-specific scope.

Recognising this TV. With your permission, the planned app reads Samsung's device identifier (DUID) on the TV and derives a HoiPlayer-specific identifier locally. It sends the derived identifier, rather than the raw DUID, to HoiPlayer over HTTPS. A separately generated random 256-bit installation secret authenticates the connection; the visible PL device code is an identifier, not a password or hardware MAC address. These values support device recognition, playlist linking and access checks.

What HoiPlayer receives. The connection service receives the derived identifier and installation authentication values, Samsung platform information, app version and build. Hosting also receives your connection IP address. The service-record, approximate-country and authorised partner access information described above applies to this planned connection flow. Server verification records retain hash-based checks for the installation identifier and secret. A source-access check sends the source server's protocol, host and port, without the full media address or source password in that check.

What stays on the TV. The planned app saves the consented device record and separate installation secret using Tizen Key Manager. The app reads this information into memory when it connects. Source sign-in details, catalogue information and playback addresses are processed in memory during use; source credentials are not added to that saved device record. Favourites, hidden categories and playback progress are kept for the current app session and are not uploaded to HoiPlayer by this preview. Memory cleanup is best effort: immediate erasure of every copy held by the app or TV's playback and network components cannot be guaranteed.

Your playlists and sources. Playlists saved through the HoiPlayer portal remain on the service as described above, including encrypted saved addresses and any source credentials you provide. The authenticated TV receives supported playlist details and contacts your chosen provider directly for catalogue and playback requests. That provider receives your IP address, source credentials and the requested content information needed to serve those requests. HoiPlayer service connections use HTTPS. A source may use HTTP or HTTPS; HTTP traffic is not encrypted. Some sources may not connect when the TV's browser or connection requirements are not met.

Your choices and retention. Declining the initial permission leaves the TV disconnected; you can choose to connect later. Saved TV identity information is intended to remain between app sessions, subject to the TV's app-data controls. Removing local app data or allowing a temporary Device Key to expire does not itself delete HoiPlayer's server records or saved playlists. Use the portal to manage saved playlists and authorised partner access. For access, correction or removal requests, contact support@hoiplayer.com; we may need to identify the relevant device and verify the request. Service-record and backup retention follow Retention and your choices and the website and portal privacy notice. Do not send passwords, temporary Device Keys or complete private playlist links.

11

Planned LG webOS edition 0.2.1

Before public release: proposed privacy supplement. This section describes the local LG webOS 0.2.1 candidate prepared for TV testing. It does not announce a public app release. The handling below is intended to apply if this edition is released with the reviewed features. Its local storage and session handling are described here separately from the Android, Windows and Samsung editions.

Recognising this TV. With your permission, the planned app's local TV service obtains LG's device identifier (LGUDID) and derives a HoiPlayer-specific identifier on the TV. HoiPlayer receives the derived identifier over HTTPS, rather than the raw LGUDID. A separate random 256-bit installation secret authenticates the connection. The visible PL device code is an identifier, not a password or a report of the TV's network hardware MAC address. These values are used to recognise the installation, link playlists and check source access.

Information reaching HoiPlayer. Connection requests send the derived identifier and installation authentication values, the LG platform label, and the app version and build. Hosting receives the connection IP address. The service-record, approximate-country and authorised partner access information described above applies to this planned flow. The service retains hash-based checks for the installation identifier and secret. A source-access check sends the source server's protocol, host and port, without the full media address or source password in that check.

Local storage and memory. The app's TV service saves the consented device record and separate secret in local TV storage, then checks that the saved values can be read back correctly. The service reads these values into memory to authenticate requests. Source sign-in details, catalogue data and playback addresses are processed in service or player memory; source credentials are not added to the saved device identity record. Favourites, hidden categories and playback progress are kept for the current app session and are not uploaded to HoiPlayer by this preview. Temporary copies may remain in the local service, player or network components until their normal cleanup; immediate erasure of every memory copy is not guaranteed.

Playlists and your provider. If you or an authorised partner choose to save a playlist through the HoiPlayer portal, the service stores its details and any supplied source credentials as described above, with encrypted saved playlist payloads. The authenticated TV receives supported playlist details and contacts the chosen provider directly for catalogue and playback requests. The provider can receive your IP address, source credentials and requested content information. HoiPlayer service requests use HTTPS. A chosen source can use HTTP or HTTPS; HTTP does not encrypt its source credentials or playback requests. A source may fail to connect when the TV's security or connection requirements are not met.

Your choices and retention. Declining initial permission leaves the app disconnected, and you can choose to connect later. The local identity record is intended to remain between sessions, subject to the TV's app-data handling. Clearing local app data, removing the app or allowing a temporary Device Key to expire does not itself delete service records or saved server playlists. Use the portal to manage saved playlists and authorised partner access. Contact support@hoiplayer.com for access, correction or removal requests; identifying the relevant device and verifying the request may be necessary. Service-record and backup retention follow Retention and your choices and the website and portal privacy notice. Do not send passwords, temporary Device Keys or complete private playlist links.

12

Microsoft Store Windows edition — 0.5.34+88

Updated 6 November 2026. This supplement extends the notice to the Microsoft Store Windows 0.5.34+88 edition. The data categories, recipients, purposes and privacy contacts described above continue to apply; other editions retain their existing scope.

Saved-playlist synchronisation is separate from source-access checks. The app contacts the authenticated HoiPlayer connection service to receive changes to your saved playlists and can check source access when opening the app, selecting a source or starting playback, with routine checks while idle. A temporary background check failure does not by itself stop an already admitted playback session. Confirmed playlist removal retires access to that saved source.

On Windows, catalogue records containing provider links and their backups are protected using the Windows user account. This protection is tied to that account and does not mean every preference, image or local file is encrypted. Parental-control verification and restrictions remain local. The optional playback-information panel reads playback statistics locally when opened.

App updates are managed by Microsoft Store; this edition does not install website EXE updates. Native-library licences and replacement instructions are available separately.

13

iPhone and iPad privacy

Updated 7 November 2026. This supplement extends the app notice to the iPhone and iPad edition with the connection choices described below. Other edition-specific sections retain their scope.

Information on your device

Before the first service connection, the app presents a short explanation and lets you read the privacy details without connecting. Choose Continue to start the connected app. The service connection does not start unless you continue. The choice is remembered on this device. In Settings, Stop service connection stops the connected app and returns to that choice. This preserves your saved local device identity, lists and history; it does not delete server records. You can read the bundled privacy information while disconnected. Opening the public policy or support website makes a separate website request.

HoiPlayer stores the selected source's sign-in details, installation access information and the catalogue encryption key in the iOS Keychain, with access limited to this device while it is unlocked and without Keychain synchronisation. Catalogue cache contents are protected with authenticated encryption. Language, playback and parental-control settings, favourites, recently viewed item references and playback positions are also stored locally. Artwork and other ordinary preferences and caches should not be treated as a promise that every local file is encrypted.

The app does not upload your favourites, viewed-title history, playback positions or parental PIN to the HoiPlayer connection service. Your chosen content provider can still observe requests to its service.

Connecting your installation

The app derives an app-scoped identifier on the device from Apple's identifier for vendor (IDFV) and the app's bundle identifier. It sends the derived value, rather than the raw IDFV, to HoiPlayer, together with a separate installation authentication value and the public PL device code. These values associate and authenticate your installation with its saved playlists; hashing does not make a device-associated record anonymous. The PL code is not a network-interface MAC address or a password.

Authenticated status requests also send the iOS platform label, app version and build. The service keeps the latest authenticated contact and playlist-management state. A source-access check sends the source server's protocol, host and port, without the full media address or source password in that check. HoiPlayer uses this information to provide device connection, source-access controls, continuity, service operations and support. Operational views also count registered devices, recent authenticated app contacts and playlist-save activity; these are not viewed-title or viewing-history counts.

IDFV is not a permanent hardware identifier. It can change under Apple's platform rules. The app preserves an existing valid local identity record rather than promising an unchanged hardware identifier after every reinstall. Installation continuity is subject to the service's verification process.

The connection service, saved sources and recipients

HoiPlayer's hosting receives your connection IP address. The service may use a locally stored DB-IP country database to derive the latest approximate connection country. The country record stores the country code, observation time and lookup-source label, without adding the raw IP address to that country record. This uses no GPS, city or coordinates and makes no external geolocation lookup. The result can be unknown, inaccurate or reflect a VPN or network exit.

Authorised HoiPlayer administrators can access operational device records. A partner you connect using the current Device Key can access the device information and playlist-management functions described in the website and portal privacy notice. A public PL code alone does not grant that access.

If you or an authorised partner save a playlist through the portal, HoiPlayer stores its name, type, source address and supplied source credentials and sends supported saved details to your authenticated app. Saved playlist payloads are encrypted on the server; the service can read them to provide playlist management. This is not end-to-end encryption.

Requests to your chosen sources

The app connects directly to your chosen provider for account validation, catalogues, programme information and playback. The provider receives your IP address, the required source credentials, the player user agent and the requested content information. Artwork and available previews can create requests to separate image, media or delivery hosts, including image hosts referenced by your provider. Those hosts receive the corresponding connection and request information.

HoiPlayer service requests use HTTPS. The app uses the source address supplied by you or your authorised partner, which may use HTTP or HTTPS. HTTP connections are unencrypted and can expose source sign-in details, catalogue requests and media in transit. Use an HTTPS address when your provider supports it. Source providers, delivery hosts and Apple handle their own records under their own privacy practices.

Diagnostics and permissions

The reviewed iOS edition does not include an advertising SDK or a separate third-party analytics or crash-reporting integration. It does not use an advertising identifier or send data for advertising across other companies' apps. A sanitised playback support report is displayed locally and is copied to the clipboard only when you choose to copy it. The app does not automatically send that report to support.

The reviewed features do not request access to your camera, microphone, contacts, photo library or device location. The approximate connection-country lookup does not use a location permission. Opening a website or sending support email creates a separate interaction with that service.

Retention, removal and contact

Local settings, profiles and caches remain until changed, replaced or removed through the app's and system's handling. Clearing history removes history and resume positions for the current source profile; it does not remove favourites or every other source profile. Signing out removes the active source's stored sign-in details and cached account information; it does not delete saved server playlists or promise to erase every local cache. Keychain records may survive app removal.

Device records and saved service playlists remain until removed. The operational record retains the latest contact, reported system/version/build, country observation and latest save time until the device record is removed; it is not a history of every contact. Allowing a Device Key to expire or removing the app does not itself delete these records. Protected support and migration backups have no configured automatic deletion period. Other service records and request-triggered cleanup follow the website and portal privacy notice; no exact automatic deletion time for all records or backups is promised.

Retention periods for technical records and app support

GoDaddy operates the shared-hosting logs, which can contain connection IP addresses and rotate every seven days. Rotation does not establish when every underlying copy is physically erased. The hosting provider’s recovery copies can also contain application data stored in files.

HoiPlayer configures its cPanel technical log archive files for 30-day retention. The hosting archive and rotation schedules apply. HoiPlayer manually removes its older application recovery copies within 30 days of creation and closed HoiPlayer app support correspondence within six months of closure.

HoiPlayer restores application data only when it can verify past deletions separately and remove affected records from the recovery copy before use. When it cannot verify past deletions, restoration is limited to code and clean configuration.

Use the playlist portal to remove saved playlists or partner access. For access, correction or removal of information held by HoiPlayer, or questions about continued service use, email support@hoiplayer.com. We may need to identify the relevant device and verify the request. Do not send passwords, Device Keys, parental PINs or complete private playlist links. Your provider and Apple handle requests about their own records.

Deleting HoiPlayer service data

Use Delete HoiPlayer service data in Privacy and data choices or Settings. The app first checks whether the service supports this deletion protocol; if it is unavailable, deletion is not confirmed or started. Review the scope and explicitly confirm before proceeding. The supported service removes this installation's device record, saved server playlists, pairing/recovery records and related active device/partner entries. This does not delete an independent content-provider account or an unrelated partner account.

Before submitting a confirmed deletion, the app securely saves a pending state and stops its normal service/provider connections. It reports success only after an authenticated service response confirms deletion. A failed or lost response keeps connections stopped across restarts. Use Retry deletion to recover the result. If confirmation expired before deletion, use Review deletion again to obtain a fresh confirmation without enrolling a new account. After confirmed deletion, starting a new connection requires your explicit action. Local device identity, playlists, history and parental-control settings are preserved; this feature does not reset your PIN. Separate support records and protected historical backups remain subject to the retention and removal handling described above; no immediate blanket backup purge is promised.

During unfinished server cleanup, the service retains a bounded recovery record containing the exact recovery-request IDs, target device code and signed request binding needed to finish that cleanup. It does not discard this record merely because confirmation time has passed. After cleanup, the recovery payload is removed. The remaining record contains a purpose-specific pseudonymous registration guard, a hashed request proof, confirmation receipt and timestamps. It contains no source sign-in details, installation secret, full native identity hash or public device code. The guard prevents delayed registration from immediately recreating the deleted record and remains logically valid for 24 hours after cleanup. Hashing or HMAC does not make it anonymous. Expired completed proofs are removed during later deletion processing or the relevant registration request; this is not a promise of physical removal at exactly 24 hours.

A completed result can be recovered for 24 hours after cleanup. If its response was lost and that window has passed, contact support or explicitly prepare a connection with fresh verification. This reconnect option does not confirm that deletion completed. The service refuses reconnect while its cleanup is unfinished. A confirmed deletion requires the valid receipt and request proof for an immediate new connection; an unresolved result requires fresh authenticated reconnect authorisation. The normal Continue choice still applies. Your saved local identity and parental controls are preserved.

13

iPhone ve iPad gizliliği

Güncelleme: 7 Kasım 2026. Bu ek, uygulama bildirimini aşağıdaki bağlantı seçeneklerini içeren iPhone ve iPad sürümünü kapsayacak şekilde genişletir. Diğer sürümlerin bölümleri kendi kapsamını korur.

Cihazınızda tutulan bilgiler

Uygulama ilk hizmet bağlantısından önce kısa bir bilgilendirme gösterir; gizlilik ayrıntılarını bağlanmadan okuyabilirsiniz. Bağlı uygulamayı başlatmak için Devam et seçeneğini kullanın. Devam etmediğiniz sürece hizmet bağlantısı başlamaz. Tercih bu cihazda hatırlanır. Ayarlardaki Hizmet bağlantısını durdur işlemi bağlı uygulamayı durdurur ve bağlantı seçimine döner. Kayıtlı yerel cihaz kimliğiniz, listeleriniz ve geçmişiniz korunur; sunucu kayıtları silinmez. Bağlantı kapalıyken uygulamadaki gizlilik metnini okuyabilirsiniz. Herkese açık politika veya destek sitesini açmak ayrı bir web isteği oluşturur.

HoiPlayer seçili kaynağın giriş bilgilerini, kurulum erişim bilgilerini ve katalog şifreleme anahtarını iOS Anahtar Zinciri'nde tutar. Erişim, kilidi açık olan bu cihazla sınırlıdır; Anahtar Zinciri eşitlemesi kullanılmaz. Katalog önbelleği, bütünlük doğrulamalı şifrelemeyle korunur. Dil, oynatma ve ebeveyn denetimi ayarları, favoriler, son görüntülenen öğe referansları ve oynatma konumları da cihazda saklanır. Görseller ve diğer normal tercihler/önbellekler, her yerel dosyanın şifrelendiği anlamına gelmez.

Uygulama favorilerinizi, görüntülenen başlık geçmişini, oynatma konumlarını veya ebeveyn PIN'inizi HoiPlayer bağlantı hizmetine yüklemez. Seçtiğiniz içerik sağlayıcısı kendi hizmetine yapılan istekleri görebilir.

Kurulumunuzun bağlanması

Uygulama, Apple'ın satıcı tanımlayıcısı (IDFV) ve uygulamanın paket tanımlayıcısından cihaz üzerinde uygulama kapsamlı bir kimlik türetir. Ham IDFV yerine bu türetilmiş değeri, ayrı bir kurulum kimlik doğrulama değeri ve açık PL cihaz koduyla birlikte HoiPlayer'a gönderir. Bu değerler kurulumunuzu kayıtlı listeleriyle ilişkilendirir ve kimliğini doğrular; özetleme, cihazla ilişkili kaydı anonim yapmaz. PL kodu ağ kartının MAC adresi veya parola değildir.

Kimliği doğrulanmış durum istekleri ayrıca iOS platform etiketini, uygulama sürümünü ve derleme numarasını gönderir. Hizmet son doğrulanmış teması ve liste yönetimi durumunu saklar. Kaynak erişim kontrolünde kaynak sunucunun protokolü, alan adı ve bağlantı noktası gönderilir; bu kontrolde tam medya adresi veya kaynak parolası gönderilmez. HoiPlayer bu bilgileri cihaz bağlantısı, kaynak erişim denetimleri, süreklilik, hizmet işletimi ve destek için kullanır. Operasyonel ekranlar kayıtlı cihazları, yakın zamandaki doğrulanmış uygulama temaslarını ve liste kaydetme etkinliğini de sayar; bunlar görüntülenen başlık veya izleme geçmişi sayımları değildir.

IDFV kalıcı donanım kimliği değildir; Apple'ın platform kuralları çerçevesinde değişebilir. Uygulama mevcut geçerli yerel kimlik kaydını korur; her yeniden kurulumdan sonra donanım kimliğinin değişmeyeceğini vaat etmez. Kurulum sürekliliği, hizmetin doğrulama sürecine bağlıdır.

Bağlantı hizmeti, kayıtlı kaynaklar ve alıcılar

HoiPlayer barındırma hizmeti bağlantınızın IP adresini alır. Hizmet, yerel DB-IP ülke veritabanını kullanarak son yaklaşık bağlantı ülkesini türetebilir. Ülke kaydı ülke kodunu, gözlem zamanını ve sorgu kaynağı etiketini saklar; bu kayda ham IP adresi eklemez. GPS, şehir veya koordinat kullanılmaz; harici konum sorgusu yapılmaz. Sonuç bilinmeyebilir, yanlış olabilir veya VPN/ağ çıkışını yansıtabilir.

Yetkili HoiPlayer yöneticileri operasyonel cihaz kayıtlarına erişebilir. Güncel Device Key ile bağladığınız bir bayi, web sitesi ve portal gizlilik bildiriminde açıklanan cihaz bilgilerine ve liste yönetimi işlevlerine erişebilir. Açık PL kodu tek başına bu erişimi vermez.

Siz veya yetkilendirdiğiniz bayi portal üzerinden liste kaydettiğinizde HoiPlayer liste adını, türünü, kaynak adresini ve sağlanan kaynak giriş bilgilerini saklar; desteklenen kayıtlı bilgileri kimliği doğrulanmış uygulamanıza gönderir. Liste içeriği sunucuda şifrelenir; hizmet, liste yönetimi sağlamak için bu bilgileri okuyabilir. Bu, uçtan uca şifreleme değildir.

Seçtiğiniz kaynaklara yapılan istekler

Uygulama hesap doğrulama, katalog, program bilgisi ve oynatma için seçtiğiniz sağlayıcıya doğrudan bağlanır. Sağlayıcı IP adresinizi, gerekli kaynak giriş bilgilerini, oynatıcı kullanıcı aracısını ve istenen içeriğe ilişkin bilgileri alır. Görseller ve mevcut önizlemeler, sağlayıcınızın işaret ettiği görsel sunucuları da dahil ayrı görsel, medya veya dağıtım sunucularına istek oluşturabilir. Bu sunucular ilgili bağlantı ve istek bilgilerini alır.

HoiPlayer hizmet istekleri HTTPS kullanır. Uygulama sizin veya yetkilendirdiğiniz bayinin sağladığı kaynak adresini kullanır; bu adres HTTP veya HTTPS kullanabilir. HTTP bağlantıları şifrelenmez; kaynak giriş bilgileri, katalog istekleri ve medya aktarım sırasında açığa çıkabilir. Sağlayıcınız destekliyorsa HTTPS adresi kullanın. Kaynak sağlayıcıları, dağıtım sunucuları ve Apple kendi kayıtlarını kendi gizlilik uygulamalarına göre işler.

Tanılama ve izinler

İncelenen iOS sürümü reklam SDK'sı veya ayrı bir üçüncü taraf analiz/çökme raporlama entegrasyonu içermez. Reklam tanımlayıcısı kullanmaz; başka şirketlerin uygulamaları arasında reklam amacıyla veri göndermez. Hassas bilgilerden arındırılmış oynatma destek raporu cihazda gösterilir ve yalnızca kopyalamayı seçtiğinizde panoya kopyalanır. Uygulama bu raporu desteğe otomatik göndermez.

İncelenen özellikler kameranıza, mikrofonunuza, kişilerinize, fotoğraf arşivinize veya cihaz konumuna erişim istemez. Yaklaşık bağlantı ülkesi sorgusu konum izni kullanmaz. Web sitesi açmak veya destek e-postası göndermek, ilgili hizmetle ayrı bir etkileşim oluşturur.

Saklama, kaldırma ve iletişim

Yerel ayarlar, profiller ve önbellekler uygulama/sistem tarafından değiştirilene, yenilenene veya kaldırılana kadar kalır. Geçmişi temizlemek, mevcut kaynak profilinin geçmişini ve kaldığı yer bilgilerini kaldırır; favorileri veya diğer tüm kaynak profillerini kaldırmaz. Çıkış yapmak etkin kaynağın saklanan giriş bilgilerini ve önbellekteki hesap bilgisini kaldırır; sunucudaki listeleri silmez ve her yerel önbelleğin silinmesini vaat etmez. Anahtar Zinciri kayıtları uygulama kaldırıldıktan sonra kalabilir.

Cihaz kayıtları ve hizmete kaydedilmiş listeler kaldırılana kadar kalır. Operasyonel kayıt son teması, bildirilen sistem/sürüm/derlemeyi, ülke gözlemini ve son kaydetme zamanını cihaz kaydı kaldırılana kadar tutar; her temasın geçmişi tutulmaz. Device Key süresinin dolması veya uygulamanın kaldırılması bu kayıtları kendiliğinden silmez. Korumalı destek ve geçiş yedekleri için yapılandırılmış otomatik silme süresi yoktur. Diğer hizmet kayıtları ve istekle tetiklenen temizlikler web sitesi ve portal bildirimine tabidir; tüm kayıtların veya yedeklerin kesin bir otomatik zamanda silineceği vaat edilmez.

Teknik kayıtların ve uygulama destek yazışmalarının saklanması

GoDaddy, bağlantı IP adreslerini içerebilen paylaşımlı barındırma günlüklerini yönetir. Bu günlükler yedi günlük aralıklarla yenilenir. Bu süre, alttaki tüm kopyaların fiziksel olarak ne zaman silindiğini göstermez. Barındırma sağlayıcısının kurtarma kopyaları, dosyalarda saklanan uygulama verilerini de içerebilir.

HoiPlayer, cPanel’deki teknik günlük arşivi dosyalarının saklama süresini 30 gün olarak ayarlar. Barındırmanın arşivleme ve günlük yenileme döngüleri geçerlidir. HoiPlayer kendi eski uygulama kurtarma kopyalarını oluşturulmalarından itibaren 30 gün içinde, kapanmış uygulama destek yazışmalarını ise talebin kapanışından itibaren altı ay içinde elle temizler.

HoiPlayer, önceki silme işlemlerini ayrı kanıtlarla doğrulayabildiği ve ilgili kayıtları kullanımdan önce kurtarma kopyasından çıkarabildiği durumda uygulama verilerini geri yükler. Önceki silme işlemleri doğrulanamadığında geri yükleme, program dosyaları ve temiz yapılandırmayla sınırlı kalır.

Kayıtlı listeleri veya bayi erişimini kaldırmak için liste portalını kullanın. HoiPlayer'ın tuttuğu bilgilere erişim, düzeltme veya kaldırma talebi ya da hizmet kullanımına devam etme hakkındaki sorular için support@hoiplayer.com adresine yazın. İlgili cihazı belirlememiz ve talebi doğrulamamız gerekebilir. Parola, Device Key, ebeveyn PIN'i veya tam özel liste bağlantıları göndermeyin. Sağlayıcınız ve Apple kendi kayıtlarıyla ilgili talepleri kendileri ele alır.

HoiPlayer hizmet verilerinin silinmesi

Gizlilik ve veri seçenekleri veya Ayarlar içindeki HoiPlayer hizmet verilerini sil işlemini kullanın. Uygulama önce hizmetin bu silme protokolünü desteklediğini denetler; kullanılamıyorsa silme onaylanmaz veya başlatılmaz. Devam etmeden önce kapsamı inceleyip açıkça onaylayın. Destekleyen hizmet bu kurulumun cihaz kaydını, sunucudaki listelerini, eşleştirme/kurtarma kayıtlarını ve ilişkili etkin cihaz/bayi kayıtlarını kaldırır. Bağımsız içerik sağlayıcısı hesabı veya ilgisiz bayi hesabı silinmez.

Uygulama onaylanan silme isteğini göndermeden önce bekleyen durumu güvenli depoya kaydeder, normal hizmet/sağlayıcı bağlantılarını durdurur. Yalnız kimliği doğrulanmış hizmet yanıtı silmeyi onayladıktan sonra başarı bildirir. Başarısız veya kaybolan yanıtta bağlantılar yeniden açılışlarda da durur. Sonucu almak için Silmeyi yeniden dene işlemini kullanın. Onay silme yapılmadan zaman aşımına uğradıysa yeni hesap oluşturmadan yeni onay almak için Silmeyi yeniden incele işlemini kullanın. Doğrulanan silme sonrasında yeni bağlantı başlatmak açık işleminizi gerektirir. Yerel cihaz kimliği, listeler, geçmiş ve ebeveyn denetimleri korunur; bu özellik PIN sıfırlamaz. Ayrı destek kayıtları ve korumalı eski yedekler yukarıda belirtilen saklama/kaldırma işlemine tabidir; bütün yedeklerin hemen silineceği vaat edilmez.

Sunucu temizliği tamamlanana kadar hizmet, yalnız temizliği bitirmek için gerekli kesin kurtarma isteği kimliklerini, hedef cihaz kodunu ve imzalı istek bağını içeren sınırlı bir kurtarma kaydı tutar. Onay süresi geçti diye bu kaydı kaldırmaz. Temizlikten sonra kurtarma içeriği kaldırılır. Geriye amaca özel takma adlı bir yeniden kayıt engeli, hash'lenmiş istek kanıtı, onay makbuzu ve zaman bilgileri kalır. Bu kayıt kaynak giriş bilgilerini, kurulum sırrını, tam yerel kimlik hash'ini veya açık cihaz kodunu içermez. Engel, gecikmiş kayıt isteğinin silinen kaydı hemen yeniden oluşturmasını önler ve temizlikten sonra 24 saat mantıksal olarak geçerlidir. Hash veya HMAC işlemi veriyi anonim yapmaz. Süresi dolan tamamlanmış kanıtlar sonraki silme işlemlerinde veya ilgili kayıt isteğinde kaldırılır; tam 24. saatte fiziksel silinme vaat edilmez.

Tamamlanan sonuç, temizlikten sonra 24 saat boyunca yeniden alınabilir. Yanıt kaybolduysa ve bu süre geçtiyse destekle iletişime geçin veya yeni doğrulamayla açıkça bağlantı hazırlayın. Bu bağlantı seçeneği silmenin tamamlandığını doğrulamaz. Sunucu temizliği yarım kaldığında hizmet bağlantıya izin vermez. Doğrulanan silme sonrasında hemen yeni bağlantı için geçerli makbuz ve istek kanıtı; sonucu belirsiz işlemde yeni kimlik doğrulamalı bağlantı izni gerekir. Normal Devam et seçimi yine geçerlidir. Kayıtlı yerel kimliğiniz ve ebeveyn denetimleri korunur.

13

Datenschutz für iPhone und iPad

Aktualisiert am 7. November 2026. Dieser Zusatz erweitert die App-Hinweise auf die iPhone- und iPad-Version mit den nachfolgend beschriebenen Verbindungsoptionen. Andere versionsspezifische Abschnitte behalten ihren Geltungsbereich.

Informationen auf Ihrem Gerät

Vor der ersten Dienstverbindung zeigt die App eine kurze Erklärung an; Sie können die Datenschutzhinweise ohne Verbindung lesen. Mit Weiter starten Sie die verbundene App. Die Dienstverbindung startet erst, wenn Sie fortfahren. Ihre Wahl wird auf diesem Gerät gespeichert. Dienstverbindung stoppen in den Einstellungen beendet die verbundene App und kehrt zur Verbindungswahl zurück. Die gespeicherte lokale Gerätekennung, Listen und der Verlauf bleiben erhalten; Serverdaten werden nicht gelöscht. Die mitgelieferten Datenschutzhinweise können Sie auch ohne Dienstverbindung lesen. Das Öffnen der öffentlichen Datenschutz- oder Supportwebsite erzeugt eine separate Websiteanfrage.

HoiPlayer speichert die Anmeldedaten der ausgewählten Quelle, die Installationszugangsdaten und den Schlüssel für die Katalogverschlüsselung im iOS-Schlüsselbund. Der Zugriff ist auf dieses entsperrte Gerät beschränkt; eine Schlüsselbundsynchronisierung findet nicht statt. Der Katalogzwischenspeicher wird durch authentifizierte Verschlüsselung geschützt. Sprache, Wiedergabe- und Jugendschutzeinstellungen, Favoriten, Verweise auf zuletzt angesehene Inhalte und Wiedergabepositionen werden ebenfalls lokal gespeichert. Bilder und sonstige gewöhnliche Einstellungen und Zwischenspeicher bedeuten nicht, dass jede lokale Datei verschlüsselt ist.

Die App lädt Ihre Favoriten, den Verlauf angesehener Titel, Wiedergabepositionen oder Ihre Jugendschutz-PIN nicht zum HoiPlayer-Verbindungsdienst hoch. Ihr gewählter Inhalteanbieter kann weiterhin Anfragen an seinen Dienst beobachten.

Verbindung Ihrer Installation

Die App leitet auf dem Gerät aus Apples Anbieterkennung (IDFV) und der Bundle-Kennung der App eine appbezogene Kennung ab. Sie sendet den abgeleiteten Wert statt der unveränderten IDFV zusammen mit einem separaten Authentifizierungswert der Installation und dem öffentlichen PL-Gerätecode an HoiPlayer. Diese Werte ordnen Ihre Installation ihren gespeicherten Wiedergabelisten zu und authentifizieren sie. Ein Hash macht einen gerätebezogenen Datensatz nicht anonym. Der PL-Code ist weder die MAC-Adresse einer Netzwerkschnittstelle noch ein Passwort.

Authentifizierte Statusanfragen senden außerdem die iOS-Plattformbezeichnung, App-Version und Build-Nummer. Der Dienst speichert den letzten authentifizierten Kontakt und den Stand der Listenverwaltung. Eine Quellenzugriffsprüfung übermittelt Protokoll, Host und Port des Quellenservers; die vollständige Medienadresse oder das Quellenpasswort werden bei dieser Prüfung nicht gesendet. HoiPlayer verwendet diese Informationen für Geräteverbindung, Quellenzugriffskontrollen, Kontinuität, Dienstbetrieb und Support. Betriebliche Ansichten zählen außerdem registrierte Geräte, kürzliche authentifizierte App-Kontakte und Listenspeicherungen. Dies sind keine Zählungen angesehener Titel oder des Wiedergabeverlaufs.

Die IDFV ist keine dauerhafte Hardwarekennung und kann sich gemäß Apples Plattformregeln ändern. Die App bewahrt einen vorhandenen gültigen lokalen Identitätsdatensatz auf, statt eine nach jeder Neuinstallation unveränderte Hardwarekennung zu versprechen. Die Installationskontinuität unterliegt dem Prüfverfahren des Dienstes.

Verbindungsdienst, gespeicherte Quellen und Empfänger

Der Hostingdienst von HoiPlayer erhält die IP-Adresse Ihrer Verbindung. Der Dienst kann daraus mithilfe einer lokal gespeicherten DB-IP-Länderdatenbank das letzte ungefähre Verbindungsland ableiten. Der Länderdatensatz speichert Ländercode, Beobachtungszeit und Bezeichnung der Abfragequelle, ohne dort die unveränderte IP-Adresse hinzuzufügen. GPS, Stadt oder Koordinaten werden nicht verwendet; es erfolgt keine externe Standortabfrage. Das Ergebnis kann unbekannt oder ungenau sein oder einen VPN- beziehungsweise Netzausgangspunkt widerspiegeln.

Berechtigte HoiPlayer-Administratoren können betriebliche Gerätedatensätze einsehen. Ein Partner, den Sie mit dem aktuellen Device Key verbinden, kann auf die in den Website- und Portal-Datenschutzhinweisen beschriebenen Geräteinformationen und Listenverwaltungsfunktionen zugreifen. Der öffentliche PL-Code allein gewährt diesen Zugriff nicht.

Wenn Sie oder ein berechtigter Partner eine Wiedergabeliste im Portal speichern, speichert HoiPlayer deren Namen, Typ, Quellenadresse und bereitgestellte Quellenzugangsdaten und sendet unterstützte gespeicherte Angaben an Ihre authentifizierte App. Die Listeninhalte werden auf dem Server verschlüsselt. Der Dienst kann sie zur Bereitstellung der Listenverwaltung lesen; dies ist keine Ende-zu-Ende-Verschlüsselung.

Anfragen an Ihre gewählten Quellen

Die App verbindet sich für Kontoprüfung, Kataloge, Programminformationen und Wiedergabe direkt mit Ihrem gewählten Anbieter. Dieser erhält Ihre IP-Adresse, erforderliche Quellenzugangsdaten, den User-Agent des Players und Angaben zum angeforderten Inhalt. Bilder und verfügbare Vorschauen können Anfragen an separate Bild-, Medien- oder Auslieferungsserver auslösen, einschließlich von Ihrem Anbieter referenzierter Bildserver. Diese Hosts erhalten die jeweiligen Verbindungs- und Anfrageinformationen.

Anfragen an HoiPlayer-Dienste verwenden HTTPS. Die App verwendet die von Ihnen oder Ihrem berechtigten Partner bereitgestellte Quellenadresse, die HTTP oder HTTPS verwenden kann. HTTP-Verbindungen sind unverschlüsselt; Quellenzugangsdaten, Kataloganfragen und Medien können während der Übertragung offengelegt werden. Verwenden Sie eine HTTPS-Adresse, wenn Ihr Anbieter diese unterstützt. Quellenanbieter, Auslieferungsdienste und Apple verarbeiten ihre eigenen Datensätze gemäß ihren eigenen Datenschutzpraktiken.

Diagnose und Berechtigungen

Die geprüfte iOS-Version enthält weder ein Werbe-SDK noch eine separate Integration eines Drittanbieters für Analysen oder Absturzberichte. Sie verwendet keine Werbekennung und übermittelt keine Daten für Werbung über Apps anderer Unternehmen hinweg. Ein bereinigter Wiedergabe-Supportbericht wird lokal angezeigt und nur auf Ihre Auswahl hin in die Zwischenablage kopiert. Die App sendet ihn nicht automatisch an den Support.

Die geprüften Funktionen fordern keinen Zugriff auf Kamera, Mikrofon, Kontakte, Fotomediathek oder Gerätestandort an. Die Ermittlung des ungefähren Verbindungslandes verwendet keine Standortberechtigung. Das Öffnen einer Website oder Senden einer Support-E-Mail ist eine separate Interaktion mit dem jeweiligen Dienst.

Aufbewahrung, Entfernung und Kontakt

Lokale Einstellungen, Profile und Zwischenspeicher bleiben erhalten, bis sie durch App- oder Systemvorgänge geändert, ersetzt oder entfernt werden. Das Löschen des Verlaufs entfernt Verlauf und Fortsetzungspositionen des aktuellen Quellenprofils, jedoch weder Favoriten noch sämtliche anderen Quellenprofile. Die Abmeldung entfernt gespeicherte Anmeldedaten der aktiven Quelle und zwischengespeicherte Kontoinformationen. Sie löscht keine serverseitigen Listen und garantiert nicht die Entfernung sämtlicher lokaler Zwischenspeicher. Schlüsselbundeinträge können nach der Entfernung der App bestehen bleiben.

Gerätedatensätze und im Dienst gespeicherte Listen bleiben bis zu ihrer Entfernung erhalten. Der betriebliche Datensatz behält den letzten Kontakt, gemeldetes System/Version/Build, Länderbeobachtung und letzten Speicherzeitpunkt bis zur Entfernung des Gerätedatensatzes; er enthält keinen Verlauf sämtlicher Kontakte. Der Ablauf eines Device Key oder das Entfernen der App löscht diese Datensätze nicht automatisch. Für geschützte Support- und Migrationssicherungen ist keine automatische Löschfrist eingerichtet. Andere Dienstaufzeichnungen und durch spätere Anfragen ausgelöste Bereinigungen folgen den Website- und Portalhinweisen. Für alle Datensätze oder Sicherungskopien wird kein genauer automatischer Löschzeitpunkt versprochen.

Aufbewahrungsfristen für technische Aufzeichnungen und App-Support

GoDaddy verwaltet die Protokolle des Shared Hostings. Sie können Verbindungs-IP-Adressen enthalten und werden alle sieben Tage rotiert. Daraus ergibt sich kein Zeitpunkt für die physische Löschung sämtlicher Kopien. Wiederherstellungskopien des Hosting-Anbieters können auch Anwendungsdaten enthalten, die in Dateien gespeichert sind.

HoiPlayer stellt die Aufbewahrungsdauer für technische Protokollarchivdateien in cPanel auf 30 Tage ein. Es gelten die Archivierungs- und Rotationszyklen des Hostings. HoiPlayer löscht eigene ältere Wiederherstellungskopien der App innerhalb von 30 Tagen nach ihrer Erstellung und Korrespondenz zu abgeschlossenen App-Supportfällen innerhalb von sechs Monaten nach Fallabschluss jeweils manuell.

HoiPlayer stellt App-Daten nur dann wieder her, wenn frühere Löschungen separat belegt sind und betroffene Datensätze vor der Nutzung aus der Wiederherstellungskopie entfernt werden können. Lassen sich frühere Löschungen nicht überprüfen, beschränkt sich die Wiederherstellung auf Programmdateien und eine bereinigte Konfiguration.

Über das Listenportal können Sie gespeicherte Listen oder Partnerzugriffe entfernen. Für Auskunft, Berichtigung oder Entfernung der bei HoiPlayer gespeicherten Informationen sowie Fragen zur weiteren Dienstnutzung schreiben Sie an support@hoiplayer.com. Wir müssen gegebenenfalls das betreffende Gerät zuordnen und die Anfrage überprüfen. Senden Sie keine Passwörter, Device Keys, Jugendschutz-PINs oder vollständigen privaten Listenlinks. Ihr Anbieter und Apple bearbeiten Anfragen zu ihren eigenen Datensätzen selbst.

HoiPlayer-Dienstdaten löschen

Verwenden Sie HoiPlayer-Dienstdaten löschen unter Datenschutz und Datenoptionen oder Einstellungen. Die App prüft zunächst, ob der Dienst dieses Löschprotokoll unterstützt. Ist es nicht verfügbar, wird keine Löschung bestätigt oder gestartet. Prüfen Sie den Umfang und bestätigen Sie ausdrücklich. Der unterstützende Dienst entfernt den Gerätedatensatz dieser Installation, gespeicherte Serverlisten, Kopplungs-/Wiederherstellungsdaten und zugehörige aktive Geräte-/Partnerdatensätze. Ein unabhängiges Inhalteanbieter-Konto oder ein nicht betroffenes Partnerkonto wird nicht gelöscht.

Vor dem bestätigten Löschauftrag speichert die App einen ausstehenden Status sicher und stoppt normale Dienst-/Anbieterverbindungen. Erfolg wird erst nach einer authentifizierten Löschbestätigung des Dienstes gemeldet. Bei fehlgeschlagener oder verlorener Antwort bleiben Verbindungen auch nach Neustarts gestoppt. Nutzen Sie Löschung erneut versuchen, um das Ergebnis abzurufen. Ist die Bestätigung vor der Löschung abgelaufen, erhalten Sie mit Löschung erneut prüfen eine neue Bestätigung, ohne ein neues Konto anzulegen. Nach bestätigter Löschung erfordert eine neue Verbindung Ihre ausdrückliche Aktion. Lokale Gerätekennung, Listen, Verlauf und Jugendschutzeinstellungen bleiben erhalten; die PIN wird nicht zurückgesetzt. Gesonderte Supportdatensätze und geschützte ältere Sicherungen unterliegen weiterhin den oben beschriebenen Aufbewahrungs-/Entfernungsverfahren. Eine sofortige vollständige Bereinigung aller Sicherungen wird nicht versprochen.

Während einer unvollständigen Serverbereinigung speichert der Dienst einen begrenzten Wiederherstellungsdatensatz mit den genauen Wiederherstellungsanfrage-IDs, dem Zielgerätecode und der signierten Anfragebindung, die zum Abschluss erforderlich sind. Dieser Datensatz wird nicht allein wegen abgelaufener Bestätigungszeit verworfen. Nach der Bereinigung wird sein Inhalt entfernt. Es verbleiben eine zweckgebundene pseudonyme Registrierungssperre, ein gehashter Anfragenachweis, die Bestätigungsquittung und Zeitangaben. Dieser Datensatz enthält weder Zugangsdaten zur Quelle noch Installationsgeheimnis, vollständigen nativen Kennungshash oder öffentlichen Gerätecode. Die Sperre verhindert, dass eine verspätete Registrierung den gelöschten Datensatz sofort neu erstellt, und gilt logisch 24 Stunden nach der Bereinigung. Hashing oder HMAC macht diese Daten nicht anonym. Abgelaufene abgeschlossene Nachweise werden bei späteren Löschvorgängen oder der betreffenden Registrierungsanfrage entfernt; eine physische Entfernung genau nach 24 Stunden wird nicht versprochen.

Ein abgeschlossenes Ergebnis kann 24 Stunden nach der Bereinigung erneut abgerufen werden. Ging die Antwort verloren und ist dieses Zeitfenster abgelaufen, kontaktieren Sie den Support oder bereiten Sie ausdrücklich eine Verbindung mit erneuter Prüfung vor. Diese Option bestätigt keinen Abschluss der Löschung. Bei unvollständiger Serverbereinigung verweigert der Dienst die Verbindung. Nach bestätigter Löschung erfordert eine sofortige neue Verbindung gültige Quittung und Anfragenachweis; bei unbekanntem Ergebnis ist eine neue authentifizierte Verbindungsfreigabe erforderlich. Die normale Auswahl Weiter gilt weiterhin. Gespeicherte lokale Kennung und Jugendschutz bleiben erhalten.