Necessary cookies are essential to the functionality of this website. You may disable these by changing your browser settings, but this may affect how the website functions.
EU:n tietosuojalaki Projektorin k?ytt?j?tietoja
T?ss? asiakirjassa kuvataan, mink? tyyppisi? tietoja tuotteemme voi tuottaa integroitujen palveluiden ja ominaisuuksien kautta, miten k?yt?mme ja jaamme n?it? tietoja sek? mit? oikeuksia sinulla on n?iden tietojen suhteen. Huomaa, ett? eri tuotemallien ja palveluiden ominaisuuksien eroista johtuen tuotetut tiedot voivat vaihdella. Lis?tietoja saat ottamalla meihin yhteytt? alla olevassa kohdassa ”K?ytt?j?n oikeudet” annettujen yhteystietojen avulla.
1. Tuotteen tunnistetiedot
T?ss? osiossa kuvataan tuotteen perustiedot.
| Tuotetyyppi | tabletit |
2. Tietoja tiedoista
T?m? osa koskee tietoja, joita tuote voi tuottaa integroitujen palveluiden ja ominaisuuksien kautta.
| Luodut tietotyypit: | Tietojen muoto | Arvioitu m??r? | Luomisen ja ker??misen tiheys | Tietojen tallennus | Tietojen s?ilytysaika | Tietojen luonne | Miten k?ytt?j? voi k?ytt?? t?llaisia tietoja? |
| COTA Salattu IMEI: Henkil?kohtaiset yleisesti k?ytetyt laitetiedot MCC: Henkil?kohtaiset yleisesti k?ytetyt laitetiedot Mobiiliohjelmiston versio: Ei-henkil?kohtaiset tiedot CU (saatu suoraan laitteen -ominaisuuksista, ilmaisee parametreja, kuten toimituskohteen ja laitteen takakannen v?rin): Ei-henkil?kohtaiset tiedot targetEcid (tiettyyn operaattoriasiakkaaseen liittyv? ECID): Ei-henkil?kohtaiset tiedot cotaId (k?ytet??n erottamaan tietyn laitemallin tietyn asiakkaan k?ytt?m? COTA-pakettiversio): Ei-henkil?kohtaiset tiedot Resurssien sijoitustila (COTA-prosessin p??tytty?, ilmaisee, onko kukin resurssi, kuten taustakuvat ja soitto??net, m??ritetty oikein): Ei-henkil?kohtaiset tiedot COTA-ratkaisun versionumero (COTA-ratkaisun versionumero, esim. 1.0, 1.1): Ei-henkil?kohtaiset tiedot Laitteen uudelleenk?ynnistyshistoria (laitteen j?rjestelm?st? suoraan saatu attribuutti, joka kertoo, onko -k?ytt?j? suorittanut tehdasasetusten palautuksen): Ei-henkil?kohtaiset tiedot Tapahtuman tila (kunkin tapahtuman tilakoodi, esim. 804, 1000): Ei-henkil?kohtaiset tiedot targetEcid ja COTA-paketin tilakoneen tila: Ei-henkil?kohtaiset tiedot |
JSON | Salattu IMEI: 4, MCC: 4, mobiiliohjelmiston versio: 4, CU: 4, targetEcid: 4, cotaId: 4, resurssien sijoitustila: 4, COTA-ratkaisun versionumero: 4, laitteen uudelleenk?ynnistyshistoria: 4, tapahtuman tila: 4 | Kun COTA-prosessi on valmis, COTA-sovellus kyselee palvelinta ja voi my?s ladata reaaliaikaisesti tapahtumatietoja, jotka luodaan dynaamisesti. | Salattu IMEI: Tallennettu sek? paikallisesti ett? pilvipalveluun MCC: Tallennettu sek? paikallisesti ett? pilvipalvelussa Mobiiliohjelmiston versio: Tallennettu sek? paikallisesti ett? pilvipalvelussa CU: Tallennettu sek? paikallisesti ett? pilvipalveluun targetEcid: Tallennetaan sek? paikallisesti ett? pilvipalveluun cotaId: Tallennettu sek? paikallisesti ett? pilvipalvelussa Resurssien sijoitustila: Tallennettu sek? paikallisesti ett? pilvipalvelussa COTA-ratkaisun versionumero: Tallennettu sek? paikallisesti ett? pilvipalvelussa Laitteen uudelleenk?ynnistyshistoria: Tallennettu sek? paikallisesti ett? pilvipalvelussa Tapahtuman tila: Tallennettu sek? paikallisesti ett? pilvipalvelussa targetEcid ja COTA-paketin tilakoneen tila: Tallennettu vain paikallisesti |
Paikallisesti: Kunnes k?ytt?j? tyhjent?? v?limuistin manuaalisesti Pilvi: aina |
Raakadata: salattu IMEI, MCC, mobiiliohjelmiston versio, CU, targetEcid, laitteen uudelleenk?ynnistyshistoria Luodut tiedot: cotaId, resurssien sijoitustila, COTA-ratkaisun versionumero, tapahtuman tila, targetEcid ja COTA-paketin tilakoneen tila |
Laite: Pilvi: |
| TclLauncher 1、Sovelluksen asennus -tiedot: henkil?tiedot 2、K?ytt?j?n k?ytt?ytymistiedot: henkil?tiedot 3、BI-seuranta: ei-henkil?kohtaiset tiedot |
Json pre |
1、Sovelluksen asennustiedot: riippuu k?ytt?j?n k?yt?st? 2、K?ytt?j?n k?ytt?ytymistiedot: riippuu k?ytt?j?n toimista 3、BI-seuranta: 24 |
1、Sovelluksen asennustiedot: luetaan j?rjestelm?st?, ei luoda; p?ivitykset k?ynnistyv?t sovelluksen asennuksen, poistamisen tai p?ivitysten j?lkeen 2、K?ytt?j?n toimintak?ytt?ytyminen: luodaan reaaliajassa k?ytt?j?n toimien aikana 3、BI-seuranta: k?ynnistyy ja raportoidaan, kun k?ytt?j? suorittaa reagoivia toimia |
2. K?ytt?j?n k?ytt?ytymistiedot: tallennetaan paikallisesti 3. BI-seuranta: tallennetaan pilvipalveluun |
tallennetaan pysyv?sti | 1、Sovelluksen asennustiedot: luodut tiedot 2、K?ytt?j?n toimintak?ytt?ytyminen: luodut tiedot 3、BI-seuranta: luodut tiedot |
Tietoihin ei ole p??sy? |
| TCTGDPR Ei-henkil?kohtaiset tiedot: K?ytt?j?n kokemussuunnitelman vaihto-tilan tiedot, COTA-suorituksen loppuun saattaminen, COTA-suorituksen onnistuminen, hautauspaikka |
Json | 4 (Hautauspaikka: 1 K?ytt?j? -kokemussuunnitelman vaihtotilan tietojen tallennus, COTA-suorituksen loppuun saattaminen, COTA-suorituksen onnistuminen: 3) |
Reaaliaikainen luominen | Laitteella: Tallennustilan k?ytt?j?n kokemussuunnitelman vaihto in tilatiedot, COTA valmis, COTA onnistunut: Pilvipalvelimella: Hautauskohta |
Tallennustilan k?ytt?kokemussuunnitelman vaihto in tilatiedot: pysyv? BI-data /Pilvi tallennetaan 35 p?iv?ksi |
Luodut tiedot: |
K?ytt?j? voi k?ytt?? tietoja yhteydenottolomakkeen kautta. |
| TTVS Henkil?kohtaiset tiedot: Br?ndi, CU, ECID, Android-versio, laitteen nimi Kameran tietojen lukeminen ja kasvonpiirteiden ker??minen Ei-henkil?kohtaiset tiedot: SIM-korttitiedot |
CSV | 1000 (Laitteen IMEI, merkki, cu, ecId, androidVersion, DeviceName, SIM-korttitiedot ja muut laitetiedot: 10 Muiden sovellusten haudatut pisteet: 1000+) |
Reaaliaikainen luominen: jos haudattujen pisteiden m??r? ylitt?? 10 kertaa, siit? ilmoitetaan kerran, enint??n 500 kertaa p?iv?ss? |
Pilvipalvelimella: Haudatut pisteet | BI-tiedot/pilvi tallennetaan 35 p?iv?n ajaksi | Raakadata：Laitteen IMEI Raakadata： |
Tietoihin ei ole p??sy? |
| Kasvontunnistus Henkil?kohtaiset tiedot: Kameran tietojen lukeminen ja kasvonpiirteiden ker??minen |
Json |
1 (Kamera-tietojen lukeminen ja kasvonpiirteiden ker??minen: 1) |
Riippuu k?ytt?j?n toimista: Lue kameran tiedot ja ker?? kasvonpiirteet |
laitteella |
Pysyv? |
Luodut tiedot： Lue kameran tiedot ja ker?? kasvonpiirteet |
TEE |
| Asetukset Henkil?kohtaiset tiedot: Laitteen perusparametritiedot: IMEI, MAC-osoite ja laitetunnus Ei-henkil?kohtaiset tiedot: Laitteen reaaliaikaiset tilatiedot, k?ytt?j?n toimet, seuranta ja muut |
CSV |
65 (1. Laitteen perusparametritiedot: riippuvat -j?rjestelm?st? 2. Laitteen reaaliaikaiset tilatiedot: riippuvat j?rjestelm?st? 3. K?ytt?j?n toimet: riippuvat k?ytt?j?n k?yt?st? 4. Seuranta: 65) |
1. Laitteen perusparametritiedot: Ei 2. Laitteen reaaliaikaiset tilatiedot: riippuu j?rjestelm?st? 3. K?ytt?j?n toimet: riippuu k?ytt?j?n k?yt?st? 4. Seuranta: lataa laukaisun j?lkeen |
Laitteella: K?ytt?j?n toimet Pilvipalvelimella: Seuranta |
Paikallisesti: kunnes k?ytt?j? tyhjent?? v?limuistin manuaalisesti Pilvi: 35 p?iv?? |
Raakadata: Laitteen perusparametridata |
Asetusten tarjoaja |
| TctSetupWizard Ei-henkil?kohtaiset tiedot: K?ytt?j?n toimintak?ytt?ytyminen |
CSV |
1 (K?ytt?j?n k?ytt?ytymistiedot: 1） |
K?ytt?j?n toiminta j?lkik?teen luotu |
Laitteella |
Pysyv? |
Luodut tiedot: K?ytt?j?n k?ytt?ytymistiedot |
Attribuuttiarvo |
|
SmartManager K?yt? hautauspisteit?: https://docs.qq.com/sheet/DY1dBaE9rV1pSRER5?tab=kfp588&nlc=1(https://docs.qq.com/sheet/ DY1dBaE9rV1pSRER5?tab=kfp588&nlc=1)
|
JSON |
38 （Hautauspaikat: 32 Tietokanta: 1 Osakekurssitaulukko: 5） |
Luo laukaisun j?lkeen |
Pilvipalvelimella: ? Hautauskohta Laitteella: ? Akun tiedot ? Muistitiedot ? Ilmoitusten hallintatiedot ? Ilmoitusten ponnahdusikkunoiden tiedot ? Itsest??n k?ynnistymisen tiedot ? Tiedostojen hallinta |
Haudatut pisteet: riippuu pilvipalveluun haudattujen pisteiden tallennuksen kestosta BI-tiedot/pilvi tallennetaan 35 p?iv?n ajaksi |
Luodut tiedot: |
K?ytt?j? voi k?ytt?? tietoja seuraavasti: /data/user_de/0/com.tct.onetouchbooster/databases
|
|
TCT SystemUI ? Akku- ja lataustiedot {akun varaustason, lataustilan ja lataustehon saaminen}: henkil?kohtaiset, yleisesti k?ytetyt laitetiedot; |
JSON | Hautauspaikka: noin 50 K?ytt?j?n toiminta: riippuu k?ytt?j?n toimista Laitteistotiedot: noin 20 |
Hautauspaikka: Reaaliaikainen luonti k?ytt?j?n toimien perusteella |
Akku- ja lataustiedot: paikalliset SIM-korttitiedot: paikalliset ? Ilmoitustiedot: paikalliset Taustakuvatieto: paikallinen Lukituksen avaustyyppi: paikallinen WiFi-tiedot: Paikalliset BT-tiedot: Paikalliset Bi-tiedot: Pilvipohjainen |
Haudatut pisteet: riippuu pilvipalvelussa haudattujen pisteiden tallennuksen kestosta BI-tiedot / Pilvi tallennetaan 35 p?iv?n ajaksi |
Tietojen luominen: haudatut pisteet |
K?ytt?j? voi k?ytt?? tietoja yhteydenottolomakkeen kautta. |
| Puhelinverkko Hautauspaikat: Verkko Poikkeustiedot |
JSON | Hautauspaikat: 1 | Generate upon triggering | cloud storage | No | Generate data: Burial points |
No access is available to the data |
| ApnHotfix Device IMEI: Personal commonly used device information Device ECID: Non-personal information Device CU: Non-personal information Device Model: Non-personal information Device project name: Non-personal information APN data: Non-personal information SIM card information: Non-personal information |
String |
Device IMEI: 1 Device ECID: 1 Device CU: 1 Device Model: 1 Device project name: 1 APN data: Based on the actual number of entries in the APN database SIM card information: 1 |
Generated after trigger |
Data obtained by this feature from the product: Device IMEI: Stored locally and On the cloud server server Device ECID: Stored locally Device CU: Stored locally Device Model: Stored locally and On the cloud server server Device project name: Stored locally APN data: Stored locally SIM card information: Not stored |
No |
Device IMEI: Raw data |
Device: |
| TctWFC Personal commonly used device information (IMEI, IMSI, deviceID, etc.) Personal basic information (E911 address) User operation behavior: WFC default preferences, switch settings |
Only E911 address needs to be displayed to the end user as a string |
IMEI：1 IMSI：1 deviceID：1 E911 address：1 |
Report after business operation |
E911 address, IMEI, and IMSI stored in the cloud |
Depending on the storage duration of the carrier server |
Raw data: IMEI, IMSI, deviceID, E911 address |
Device: User can access the data by using [carrier servers] |
| TctPhone PLMN: Personal Common Device Information Motion sensor data: personal commonly used device information Phone number: Personal basic information Historical call duration: Personal communication information Flight mode switch status: personal commonly used device information HAC switch status: personal commonly used device information Automatic answering switch status: Personal commonly used device information Vibration reminder switch status during dialing and answering: personal commonly used device information Call_audio_state_ovoid switch status: personal commonly used device information ECID: Personal Common Device Information |
xml |
PLMN:1 Motion sensor data: 1 Phone number: 5 History call duration: 1 Flight mode switch status: 1 HAC switch status: 1 Automatic answering switch status: 1 Vibration reminder switch status during dialing and answering: 1 Call_audio_state_ovoid switch status: 1 ECID：1 |
History call duration: call once, generate once |
Existence locally |
1. Call duration data: persistent storage 2. Other data: Real time changes or destruction based on user behavior, otherwise permanently saved |
Raw data: PLMN, motion sensor data, phone numbers, call records, flight mode switch status, HAC switch status, automatic answer switch status, vibration reminder switch status when dialing and answering, call_oudio_state_ovoid switch status, ECID |
Device: calltimeduration.xml |
| FOTA Current Device SN/IMEI: Personal device information PLMN: Personal device information Current Running Version Information: Non-personal data Mobile Software Version: Non-personal data CU: Non-personal data Ecid: Non-personal data Task ID: Non-personal data Tracking Status: Non-personal data Update Type: Non-personal data Switch Type: Non-personal data |
xlsx/xls/csv |
Approximately 10 tracking points are generated during a single update (under normal conditions and without user actions). If there are user actions or retry attempts due to exceptions, the number of tracking points may increase |
1. Data tracking points are generated during system update operations. 2. Data tracking points are generated during the 24-hour polling process (results from polling the server) |
All Information Stored in the Cloud |
No |
Retrieved from the system or the device: SN/IMEI, CU, Ecid, Version Number, PLMN |
No access is available to the data |
| AOTA Personal data: Currently installed apps on the device: Non-personal data : Current downloaded app information CU targetEcid Mobile app version Task ID Analytics status (buried point status) Update type Switch type List of updatable apps |
CSV |
17 （Currently installed apps on the device: 2 Current downloaded app information: 2 Mobile app version: 2 CU: 2 targetEcid: 2 Task ID: 2 Analytics Status: 2 Update type: 1 Switch type: 1 List of updatable apps: 1） |
1. Data tracking point generated when the user clicks to download the APK 2. Generated during 24-hour polling 3. When the user clicks the "update reminder switch" |
On the cloud server: Tracking data On the device: In-app switch status List of updatable apps |
Cloud: data is stored immediately after a tracking event is triggered; Locally: The in-app switch status and the updatable app list are always stored |
Raw data: CU, targetEcid |
No access is available to the data |
| Camera app Personal data: Latitude and Longitude, MNC/MCC,G-sensor or Gyroscope Data,TargetEcid (specific ECID corresponding to carrier customers),Product Name, Market Name, Model Non-personal data: Data report: Non-personal data |
JSON |
11 (product name：1 data report: 6 Latitude and Longitude: 1 MNC/MCC: 1 G-sensor or Gyroscope Data: 1 TargetEcid (specific ECID corresponding to carrier customers): 1) |
Touch data are reported when the user triggers a responsive action. Latitude and longitude are obtained when the user takes a photo or records a video |
On the cloud server: data report On the device: Latitude and Longitude: Stored in the captured photo or video Market Name, Model: Stored in EXIF |
BI data is stored for 35 days |
Generated data: |
No access is available to the data |
| Bluetooth Personal data: Bluetooth name and MAC address, Non-personabl data: other data |
String |
Bluetooth pairing/connection and device list storage |
Bluetooth pairing/connection and device list storage |
On the device |
Saved until you manually remove or reset to factory settings |
Gerated data: Bluetooth intrinsic data and user-configured device name |
User can access the data through:/data/misc/ bluedroid/bt_config.conf |
| tclloginsdk Personal data |
CSV |
16 |
Real-time generation |
On the cloud server |
/ |
Raw data |
No access is available to the data |
3. Tietojen k?ytt? ja jakaminen
Voimme k?ytt?? ja luovuttaa kolmansille osapuolille tuotteesi integroiduista palveluista ja ominaisuuksista syntyvi? ei-henkil?kohtaisia tietoja t?ss? osiossa kuvattuihin liiketoiminnallisiin tarkoituksiin. Lis?tietoja saat sovellettavista k?ytt?ehdoista.
Jos haluat saada tietoja henkil?tietojesi ker??misest?, k?yt?st?, luovuttamisesta, siirt?misest? tai k?sittelyst?, tutustu sovellettavaan tietosuojailmoitukseen.
| P??syn omaavat tahot | K?sittelyn tarkoitus | Tietojen jakaminen kolmansille osapuolille | Tietojen jakamisen tarkoitus kolmansille osapuolille |
| LETOU - 乐投 Communication Ltd. at 5/F, Building 22E, 22 Science Park East Avenue, Hong Kong Science Park, Shatin, NT, Hong Kong |
Tarpeellinen toimintojen ja myynnin j?lkeisen huollon kannalta | LETOU - 乐投:n eurooppalaiset teleoperaattorikumppanit. | Tuotesertifioinnin vaatimustenmukaisuuden ja jatkuvan tuoteoptimoinnin varmistaminen |
4. K?ytt?j?n oikeudet
T?ss? osiossa m??ritell??n oikeutesi, miten voit k?ytt?? oikeuksiasi sek? sinuun sovellettavat tietojen k?ytt?ehdot ja palvelun laatu .
EU:n tietosuojalaki voi antaa sinulle useita laillisia oikeuksia liittyen verkkoon liitettyjen tuotteiden tietoihin ja niihin liittyviin palveluihin.
Voit l?hett?? tietojen k?ytt?pyynt?j? ja jakaa tietoja kolmansille osapuolille k?ytt?m?ll? alla olevaa yhteystietoa:
LETOU - 乐投:n virallisilla verkkosivuilla oleva tietosuojalain yhteydenottolomake>>
Lain sallimissa rajoissa emme voi tarjota p??sy? tietoihin, jotka sis?lt?v?t luottamuksellisia tietoja, liikesalaisuuksia, immateriaalioikeuksia tai muuta omistusoikeudellista tietoa.
Jos haluat k?ytt?? oikeuksiasi, jotka liittyv?t sinusta tallentamiimme henkil?tietoihin, ota meihin yhteytt? k?ytt?m?ll? tuotteeseesi sovellettavan tietosuojailmoituksen yhteystietoja.
Lis?tietoja tietojen k?yt?st? ja p??syst? niihin on k?ytt?ehdoissa, s?hk?isiss? k?ytt?ohjeissa tai muissa asiaankuuluvissa materiaaleissa.
K?ytt?j?n? sinulla on oikeus tehd? valitus, jos uskot, ett? jotakin tietosuojalaissa m??ritelty? oikeuttasi on loukattu. T?m? oikeus takaa, ett? vastuullinen valvontaviranomainen kuulee ja k?sittelee asianmukaisesti huolenaiheesi, jotka koskevat mahdollisia tietojen saatavuutta, jakamista tai k?ytt?? koskevien s??nn?sten rikkomuksia. Jos haluat k?ytt?? t?t? oikeutta tai tarvitset lis?apua, ota yhteytt? j?senvaltion asianomaiseen viranomaiseen osoitteessa .
5. Contact information
| Manufacturer | LETOU - 乐投 Communication Ltd. |
EU DATA ACT User Information on Tablet
This document outlines the types of data our product can generate through its integrated services and features, how we use and share that data, and the rights you have in relation to the data. Please note that due to differences in the features provided by our various product models and services, the data generated may vary accordingly. For more detailed information, please contact us using the details provided in the “User Rights” section below.
1. Product Identification
This section describes the basic information of the product.
| Product type | Tablet |
2. Information about Data
This section relates to the data that the product can generate through its integrated services and features.
| Types of data generated | Data format | Estimated volume | Frequency of generation and collection |
| COTA Encrypted IMEI: Personal commonly used device information MCC: Personal commonly used device information Mobile software version: Non-personal data CU (directly obtained from device properties, indicates parameters such as the shipment destination and device back cover color): Non-personal data targetEcid (ECID corresponding to a specific operator customer): Non-personal data cotaId (used to distinguish the COTA package version used by a specific customer of a specific device model): Non-personal data Resource placement status (after the COTA process is completed, indicates whether each resource, such as wallpapers and ringtones, is properly configured): Non-personal data COTA solution version number (the version number of the COTA solution, e.g., 1.0, 1.1): Non-personal data Device reboot history (attribute directly obtained from the device system, reflects whether the user has performed a factory reset): Non-personal data Event status (status code corresponding to each event, e.g., 804, 1000): Non-personal data targetEcid and COTA package state machine status: Non-personal data |
JSON | Encrypted IMEI: 4, MCC: 4, mobile software version: 4, CU: 4, targetEcid: 4, cotaId: 4, resource placement status: 4, COTA solution version number: 4, device reboot history: 4, event status: 4 | After the COTA process is completed, the COTA app will poll the server and may also upload event information in real time, which is generated dynamically |
| TclLauncher 1. App installation information: personal data 2. User operation behavior: personal data 3. BI Tracking: non-personal data |
Json pref |
1. App installation information: depends on user usage 2. User operation behavior: depends on user actions 3. BI Tracking: 24 |
1. App installation information: read from the system, not generated; updates triggered after app installation, uninstallation, or updates 2. User operation behavior: generated in real-time during user actions 3. BI Tracking: triggered and reported when the user performs responsive actions |
| TCTGDPR Non personal data: Storage of user experience plan switch status information, COTA completion, COTA success,Burial point |
Json | 4(Burial point: 1 Storage user experience plan switch status information, COTA completion, COTA success: 3) |
Real time generation |
| TTVS Personal data: Brand, CU, ECID, AndroidVersion, DeviceName, Read camera data and collect facial features Non-personal data: SIM card information |
CSV | 1000+(Device IMEI, brand, cu, ecId, androidVersion, DeviceName, SIM card information, and other device data: 10 Undertaking buried points for other applications: 1000+) |
Real time generation: if the number of buried points exceeds 10 times, it will be reported once, not exceeding 500 times a day |
| FaceUnlock Personal data: Read camera data and collect facial features |
Json |
1(Read camera data and collect facial features: 1) |
Dependent on user actions: Read camera data and collect facial features |
| Settings Personal data: Device Basic Parameter Data: IMEI, MAC address, and DeviceID Non-personal data: Device Real-Time Status Data, User actions, Tracking and others |
CSV |
65 (1. Device Basic Parameter Data: dependent on the system 2. Device Real-Time Status Data: dependent on the system 3. User actions: dependent on user usage 4. Tracking: 65) |
1. Device Basic Parameter Data: No 2. Device Real-Time Status Data: dependent on the system 3. User actions: dependent on user usage 4. Tracking: upload after triggering |
| TctSetupWizard Non-personal data: User operation behavior |
CSV |
1 (User operation behavior: 1） |
User operation post-generated |
| Smart Manager Personal local data: Battery data {three modes for obtaining battery power, battery health (General protection, Mild protection, Medium protection, etc.)}, Memory information, Notification management information, Notification pop-up message, Self startup information, File management, BI data: personal data; DY1dBaE9rV1pSRER5?tab =kfp588&nlc=1 DY1dBaE9rV1pSRER5?tab =kfp588&nlc=1) |
JSON |
38(Burial points: 32 Database: 1 Shareperformance table: 5） |
Generate after triggering |
| TCT SystemUI shimo-h5/shimo-edit/a4 e266f2a144483598 5d9c67c9a9ee64?accessToken=ut_g1feys IQCSIltjW4cZ0jNfD5Po Gvn9Vq78v |
JSON | Burial point: about 50 User Action Behavior: Dependent on User Actions Equipment data: approximately 20 |
Burial point: Real time generation based on user operation shimo-h5/shimo-edit /a4e266f2a144483 5985d9c67c9a9ee64?accessToken=ut_g1feysI QCSIltjW4cZ0jNfD5Po Gvn9Vq78v |
| Telephony-Network Burial points: Network Exception Data Information |
JSON | Burial points: 1 | Generate upon triggering |
| ApnHotfix Device IMEI: Personal commonly used device information Device ECID: Non-personal information Device CU: Non-personal information Device Model: Non-personal information Device project name: Non-personal information APN data: Non-personal information SIM card information: Non-personal information |
String |
Device IMEI: 1 Device ECID: 1 Device CU: 1 Device Model: 1 Device project name: 1 APN data: Based on the actual number of entries in the APN database SIM card information: 1 |
Generated after trigger |
| TctWFC Personal commonly used device information (IMEI, IMSI, deviceID, etc.) Personal basic information (E911 address) User operation behavior: WFC default preferences, switch settings |
Only E911 address needs to be displayed to the end user as a string |
IMEI：1 IMSI：1 deviceID：1 E911 address：1 |
Report after business operation |
| TctPhone PLMN: Personal Common Device Information Motion sensor data: personal commonly used device information Phone number: Personal basic information Historical call duration: Personal communication information Flight mode switch status: personal commonly used device information HAC switch status: personal commonly used device information Automatic answering switch status: Personal commonly used device information Vibration reminder switch status during dialing and answering: personal commonly used device information Call_audio_state_ovoid switch status: personal commonly used device information ECID: Personal Common Device Information |
xml |
PLMN:1 Motion sensor data: 1 Phone number: 5 History call duration: 1 Flight mode switch status: 1 HAC switch status: 1 Automatic answering switch status: 1 Vibration reminder switch status during dialing and answering: 1 Call_audio_state_ovoid switch status: 1 ECID：1 |
History call duration: call once, generate once |
| FOTA Current Device SN/IMEI: Personal device information PLMN: Personal device information Current Running Version Information: Non-personal data Mobile Software Version: Non-personal data CU: Non-personal data Ecid: Non-personal data Task ID: Non-personal data Tracking Status: Non-personal data Update Type: Non-personal data Switch Type: Non-personal data |
xlsx/xls/csv |
Approximately 10 tracking points are generated during a single update (under normal conditions and without user actions). If there are user actions or retry attempts due to exceptions, the number of tracking points may increase |
1. Data tracking points are generated during system update operations. 2. Data tracking points are generated during the 24-hour polling process (results from polling the server) |
| AOTA Personal data: Currently installed apps on the device: Non-personal data : Current downloaded app information CU targetEcid Mobile app version Task ID Analytics status (buried point status) Update type Switch type List of updatable apps |
CSV |
17 （Currently installed apps on the device: 2 Current downloaded app information: 2 Mobile app version: 2 CU: 2 targetEcid: 2 Task ID: 2 Analytics Status: 2 Update type: 1 Switch type: 1 List of updatable apps: 1） |
1. Data tracking point generated when the user clicks to download the APK 2. Generated during 24-hour polling 3. When the user clicks the "update reminder switch" |
| Camera app Personal data: Latitude and Longitude, MNC/MCC,G-sensor or Gyroscope Data,TargetEcid (specific ECID corresponding to carrier customers),Product Name, Market Name, Model Non-personal data: Data report: Non-personal data |
JSON |
11 (product name：1 data report: 6 Latitude and Longitude: 1 MNC/MCC: 1 G-sensor or Gyroscope Data: 1 TargetEcid (specific ECID corresponding to carrier customers): 1) |
Touch data are reported when the user triggers a responsive action. Latitude and longitude are obtained when the user takes a photo or records a video |
| Bluetooth Personal data: Bluetooth name and MAC address, Non-personabl data: other data |
String |
Bluetooth pairing/connection and device list storage |
Bluetooth pairing/connection and device list storage |
| tclloginsdk Personal data |
CSV |
16 |
Real-time generation |
| Data storage | Data retention period | Nature of data | How can the user access such data |
| Encrypted IMEI: Stored both locally and in the cloud MCC: Stored both locally and in the cloud Mobile software version: Stored both locally and in the cloud CU: Stored both locally and in the cloud targetEcid: Stored both locally and in the cloud cotaId: Stored both locally and in the cloud Resource placement status: Stored both locally and in the cloud COTA solution version number: Stored both locally and in the cloud Device reboot history: Stored both locally and in the cloud Event status: Stored both locally and in the cloud targetEcid and COTA package state machine status: Stored locally only |
Locally: Until the user manually clears the cache Cloud: always |
Raw Data: Encrypted IMEI, MCC, mobile software version, CU, targetEcid, device reboot history; Generated Data: cotaId, resource placement status, COTA solution version number, event status, targetEcid and COTA package state machine status |
Device: |
| 2. User operation behavior: stored in local 3. BI Tracking: stored in the cloud |
Persistently save | 1. App installation information: generated data 2. User operation behavior: generated data 3. BI Tracking: generated data |
No access is available to the data |
| On the device: Storage user experience plan switch status information, COTA completed, COTA successful: On the cloud server: Burial point |
Storage user experience plan switch status information: permanent BI data /Cloud is stored for 35 days |
Generated Data: |
Users can access such data by using the Contact Form |
| On the cloud server : Buried point | BI data/Cloud is stored for 35 days | Raw Data：Device IMEI |
No access is available to the data |
| On the device |
Permanent |
Generated data： Read camera data and collect facial features |
TEE |
| On the device: User actions On the cloud server: Tracking |
Locally: Until the user manually clears the cache Cloud: 35 days |
Raw data: Device Basic Parameter Data |
Settings Provider |
| On the device |
Permanent |
Generated Data: User operation behavior |
Attribute value |
| On the cloud server: ? Burial point On the device: ? Battery data ? Memory information ?Notification management information ?Notification popup information ? Self startup information ? File management |
Buried point data: depends on the duration of cloud buried point storage BI data/Cloud is stored for 35 days |
Generated data: |
User can access the data through: touchbooster/shared_prefs touchbooster/databases |
| ? Battery and charging data: local SIM card information: Local ? Notification information: Local Wallpaper information: Local Unlock type information: Local WiFi information: Local BT Information: Local Bi Data: Cloud based |
Buried point data: depends on the duration of cloud buried point storage BI data /Cloud is stored for 35 days |
Generate data: buried points shimo-h5/shimo-edit/a4e266f2a14448359 85d9c67c9a9ee64?accessToken=ut_g1feysIQCS IltjW4cZ0jNfD5PoGvn9Vq78v |
User can access the data using the Contact form |
| cloud storage | No | Generate data: Burial points |
No access is available to the data |
| Data obtained by this feature from the product: Device IMEI: Stored locally and On the cloud server server Device ECID: Stored locally Device CU: Stored locally Device Model: Stored locally and On the cloud server server Device project name: Stored locally APN data: Stored locally SIM card information: Not stored |
No |
Device IMEI: Raw data |
Device: |
| E911 address, IMEI, and IMSI stored in the cloud |
Depending on the storage duration of the carrier server |
Raw data: IMEI, IMSI, deviceID, E911 address |
Device: User can access the data by using [carrier servers] |
| Existence locally |
1. Call duration data: persistent storage 2. Other data: Real time changes or destruction based on user behavior, otherwise permanently saved |
Raw data: PLMN, motion sensor data, phone numbers, call records, flight mode switch status, HAC switch status, automatic answer switch status, vibration reminder switch status when dialing and answering, call_oudio_state_ovoid switch status, ECID |
Device: calltimeduration.xml |
| All Information Stored in the Cloud |
No |
Retrieved from the system or the device: SN/IMEI, CU, Ecid, Version Number, PLMN |
No access is available to the data |
| On the cloud server: Tracking data On the device: In-app switch status List of updatable apps |
Cloud: data is stored immediately after a tracking event is triggered; Locally: The in-app switch status and the updatable app list are always stored |
Raw data: CU, targetEcid |
No access is available to the data |
| On the cloud server: data report On the device: Latitude and Longitude: Stored in the captured photo or video Market Name, Model: Stored in EXIF |
BI data is stored for 35 days |
Generated data: |
No access is available to the data |
| On the device |
Saved until you manually remove or reset to factory settings |
Gerated data: Bluetooth intrinsic data and user-configured device name |
User can access the data through:/data/misc/ bluedroid/bt_config.conf |
| On the cloud server |
/ |
Raw data |
No access is available to the data |
3. Data Access and Sharing
We may access, use and disclose the non-personal data generated by your product through its integrated services and features to third parties for business purposes as described in this section. For more related details, we invite you to consult the applicable Terms of Use.
If you would like to obtain information on the collection, use, disclosure, transfer or processing of your personal data, we invite you to consult the applicable privacy notice.
| Entities with access | Purpose of processing | Third-Party sharing | Purpose of data sharing to third-party |
| LETOU - 乐投 Communication Ltd. at 5/F, Building 22E, 22 Science Park East Avenue, Hong Kong Science Park, Shatin, NT, Hong Kong |
Necessary for functions, after-sales maintenance | European telecom operators partners of LETOU - 乐投 | To ensure product certification compliance and continuous product optimization |
4. User Rights
This section specifies your rights, how you can exercise the rights and the terms of use of the data and quality of service applicable to you.
EU Data Act may give you a number of legal rights in relation to the Connected Product data and Related Service data.
You can submit data access requests and share data with third parties by using below contact:
Data Act Contact Form on LETOU - 乐投's Official Websites >>
To the extent permitted by law, we are unable to provide access to data that contains confidential data, trade secrets, intellectual property, or other proprietary information.
If you would like to exercise your rights in relation to the personal data that we hold about you, please contact us using the details set out in the privacy notice applicable to your product.
For more detailed information about data use and access, please refer to the Terms of Use, electronic manuals, or other relevant materials.
As a user, you have the right to lodge a complaint if you believe that any of your rights under the Data Act have been infringed. This right ensures that your concerns regarding potential violations of data access, sharing, or usage provisions are heard and appropriately addressed by the responsible oversight body. If you wish to exercise this right or require further assistance, please contact the relevant authority in your Member State.
5. Contact information
| Manufacturer | LETOU - 乐投 Communication Ltd. |
Strictly necessary
Performance
Performance cookies will collect information about how your use the website and allow us to keep improving how our website works.
Advertiszing
These cookies track your browsing habits so that we can show you advertising and content which we hope is relevant to your interests.