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:s datalagstiftning Anv?ndarinformation om projektorn
Detta dokument beskriver vilka typer av data v?r produkt kan generera genom sina integrerade tj?nster och funktioner, hur vi anv?nder och delar dessa data samt vilka r?ttigheter du har i relation till dessa data. Observera att p? grund av skillnader i funktionerna hos v?ra olika produktmodeller och tj?nster kan de data som genereras variera i enlighet d?rmed. F?r mer detaljerad information, v?nligen kontakta oss med hj?lp av uppgifterna i avsnittet ”Anv?ndarr?ttigheter” nedan.
1. Produktidentifiering
I detta avsnitt beskrivs grundl?ggande information om produkten.
| Produkttyp | Smartphone |
2. Information om data
Detta avsnitt avser de data som produkten kan generera genom sina integrerade tj?nster och funktioner.
| Typer av data som genereras | Dataformat | Uppskattad volym | Frekvens f?r generering och insamling | Datalagring | Lagringstid f?r data | Datatyp | Hur kan anv?ndaren f? tillg?ng till s?dana data? |
COTA Krypterad IMEI: Personlig information om vanligt f?rekommande enheter MCC: Personlig information om vanligt f?rekommande enheter Mobilprogramvaruversion: Icke-personlig data CU (h?mtas direkt fr?n enhetens segenskaper, anger parametrar s?som leveransdestination och f?rg p? enhetens bakstycke): Icke-personlig information targetEcid (ECID som motsvarar en specifik operat?rskund): Icke-personliga uppgifter cotaId (anv?nds f?r att skilja mellan COTA-paketversionen som anv?nds av en specifik kund f?r en specifik enhetsmodell): Icke-personlig information Resursplaceringstatus (efter att COTA-processen ?r slutf?rd, anger om varje resurs, s?som bakgrundsbilder och ringsignaler, ?r korrekt konfigurerad): Icke-personuppgifter COTA-l?sningens versionsnummer (versionsnumret f?r COTA-l?sningen, t.ex. 1.0, 1.1): Icke-personuppgifter Enhetens omstartslogg (attribut som erh?lls direkt fr?n enhetens system, visar om -anv?ndaren har ?terst?llt enheten till fabriksinst?llningarna): Icke-personuppgifter H?ndelsestatus (statuskod som motsvarar varje h?ndelse, t.ex. 804, 1000): Icke-personuppgifter targetEcid och COTA-paketets tillst?ndsmaskinstatus: Icke-personuppgifter |
JSON | Krypterad IMEI: 4, MCC: 4, mobilprogramvaruversion: 4, CU: 4, targetEcid: 4, cotaId: 4, resursplaceringsstatus: 4, COTA-l?sningsversionsnummer: 4, enhets s omstartslogg: 4, h?ndelsestatus: 4 | N?r COTA-processen ?r klar kommer COTA-appen att s?ka efter servern och kan ?ven ladda upp h?ndelseinformation i realtid, som genereras dynamiskt. | Krypterad IMEI: Lagras b?de lokalt och i molnet MCC: Lagras b?de lokalt och i molnet Mobilprogramvaruversion: Lagras b?de lokalt och i molnet CU: Lagras b?de lokalt p? enheten och i molnet targetEcid: Lagras b?de lokalt och i molnet cotaId: Lagras b?de lokalt och i molnet Resursplaceringstatus: Lagras b?de lokalt och i molnet COTA-l?sningens versionsnummer: Lagras b?de lokalt och i molnet Enhetens omstartslogg: Lagras b?de lokalt och i molnet H?ndelsestatus: Lagras b?de lokalt och i molnet targetEcid och COTA-paketets tillst?ndsmaskinstatus: Lagras endast lokalt |
Lokalt: Tills anv?ndaren manuellt rensar cacheminnet Moln: alltid |
R?data: Krypterad IMEI, MCC, mobilprogramvaruversion, CU, targetEcid, enhetens omstartslogg Genererade data: cotaId, resursplaceringsstatus, COTA-l?sningens versionsnummer, h?ndelsestatus, targetEcid och COTA-paketets tillst?ndsmaskinstatus |
Enhet: Moln: |
| TclLauncher 1、Appinstallation information: personuppgifter 2、Anv?ndarens beteende: personuppgifter 3、BI-sp?rning: icke-personuppgifter |
Json pref |
1、Appinstallationsinformation: beror p? anv?ndarens anv?ndning 2、Anv?ndarens beteende: beror p? anv?ndarens ?tg?rder 3、BI-sp?rning: 24 |
1、Appinstallationsinformation: l?ses fr?n systemet, genereras inte; uppdateringar utl?ses efter appinstallation, avinstallation eller uppdateringar 2、Anv?ndarens beteende: genereras i realtid under anv?ndarens ?tg?rder 3、BI-sp?rning: utl?ses och rapporteras n?r anv?ndaren utf?r responsiva ?tg?rder |
2. Anv?ndarens beteende: en lagras lokalt 3. BI-sp?rning: lagras i molnet |
sparas permanent | 1、Appinstallationsinformation: genererade data 2、Anv?ndarens beteende: genererad data 3、BI-sp?rning: genererad data |
Ingen ?tkomst till data |
| TCTGDPR Icke-personuppgifter: Lagring av anv?ndar -upplevelseplanens statusinformation, COTA-slutf?rande, COTA-framg?ng, begravningspunkt |
Json | 4 (Begravningspunkt: 1 Lagring av anv?ndar sinformation om status f?r byte av upplevelseplan, COTA-slutf?rande, COTA-framg?ng: 3) |
Realtidsgenerering | P? enheten: Lagringsanv?ndarens erfarenhetsplanv?xlings statusinformation, COTA slutf?rd, COTA lyckad: P? molnservern: Begravningspunkt |
sinformation om status f?r v?xling av lagringsanv?ndarens upplevelseplan: permanent BI-data/molnet lagras i 35 dagar |
Genererade data: |
Anv?ndaren kan komma ?t data via kontaktformul?ret. |
| TTVS Personuppgifter: Varum?rke, CU, ECID, AndroidVersion, DeviceName, L?sa kameradata och samla in ansiktsdrag Icke-personuppgifter: SIM-kortinformation |
CSV | 1000 (Enhetens IMEI, m?rke, cu, ecId, androidVersion, DeviceName, SIM-kortinformation och andra enhetsdata: 10 ?tagande om dolda punkter f?r andra applikationer: 1000+) |
Realtidsgenerering: om antalet begravda punkter ?verstiger 10 g?nger kommer det att rapporteras en g?ng, dock h?gst 500 g?nger per dag |
P? molnservern: Begravda punkter | BI-data/molnet lagras i 35 dagar | R?data：Enhetens IMEI R?data: |
Ingen ?tkomst till data |
| FaceUnlock Personuppgifter: L?sa kameradata och samla in ansiktsdrag |
Json |
1 (L?sa kameradata och samla in ansiktsdrag: 1) |
Beroende p? anv?ndarens ?tg?rder: L?s kameradata och samla in ansiktsdrag |
p? enheten |
Permanent |
|
TEE |
| Inst?llningar Personuppgifter: Enhetens grundl?ggande parametrar: IMEI, MAC-adress och enhets-ID Icke-personliga data: Enhetens realtidsstatusdata, anv?ndar?tg?rder, sp?rning och annat |
CSV |
65 (1. Grundl?ggande parameterdata f?r enheten: beroende p? systemet 2. Enhetens realtidsstatusdata: beroende p? systemet 3. Anv?ndar?tg?rder: beroende p? anv?ndarens anv?ndning 4. Sp?rning: 65) |
1. Grundl?ggande parameterdata f?r enheten: Nej 2. Enhetens realtidsstatusdata: beroende p? systemet 3. Anv?ndar?tg?rder: beroende p? anv?ndarens anv?ndning 4. Sp?rning: uppladdning efter aktivering |
P? enheten: Anv?ndar?tg?rder P? molnservern: Sp?rning |
Lokalt: tills anv?ndaren manuellt rensar cacheminnet Moln: 35 dagar |
R?data: Enhetens grundl?ggande parameterdata |
Inst?llningsleverant?r |
| TctSetupWizard Icke-personliga data: Anv?ndarens beteende |
CSV |
1 (Anv?ndarens beteende: 1） |
Anv?ndarens beteende genereras i efterhand |
P? enheten |
Permanent |
Genererade data: Anv?ndarens beteende |
Attributv?rdevalue |
| SmartManager Anv?nd begravningspunkter: https://docs.qq.com/ |
JSON |
38 （Begravningsplatser: 32 Databas: 1 Delningsprestandatabell: 5） |
Generera efter aktivering |
P? molnservern: ? Begravningspunkt P? enheten: ? Batteridata ? Minnesinformation ? Information om hantering av aviseringar ? Information om popup-meddelanden ? Information om automatisk start ? Filhantering |
Begravda punktdata: beror p? varaktigheten f?r lagring av begravda punkter i molnet BI-data/molnet lagras i 35 dagar |
Genererade data: |
/data/data/com.tct /data/user_de/0/co |
|
TCT SystemUI ? Batteri- och laddningsdata {batteriniv?, laddningsstatus, laddningseffekt}: personlig information om vanligt f?rekommande enheter; https://teamwork |
JSON | Begravningspunkt: cirka 50 Anv?ndarens beteende: Beroende p? anv?ndarens ?tg?rder Utrustningsdata: cirka 20 |
Begravningspunkt: Realtidsgenerering baserad p? anv?ndarens ?tg?rder https://teamwork |
? Batteri- och laddningsdata: lokal SIM-kortinformation: lokal ? Information om aviseringar: lokal Bakgrundsbildsinformation: Lokal Information om uppl?sningstyp: Lokal WiFi-information: Lokal BT-information: Lokal Bi-data: Molnbaserad |
Begravda punktdata: beror p? varaktigheten f?r molnlagring av begravda punkter BI-data/molnet lagras i 35 dagar |
Generera data: begravda punkter https://teamwork.get |
Anv?ndaren kan komma ?t uppgifterna via kontaktformul?ret. |
| Telefonin?tverk Begravningspunkter: N?tverks Undantagsdatainformation |
JSON | Begravningsplatser: 1 | Genereras vid aktivering | Molnlagring | Nej | Generera data: Begravningsplatser |
Ingen ?tkomst till data |
| ApnHotfix Enhetens IMEI: Personlig information om vanligt f?rekommande enheter Enhetens ECID: Icke-personlig information Enhetens CU: Icke-personlig information Enhetsmodell: Icke-personlig information Enhetsprojektnamn: Icke- -personlig information APN-data: Icke-personlig information SIM-kortinformation: Icke-personlig information |
Str?ng |
Enhetens IMEI: 1 |
Genereras efter utl?sare |
Data som erh?llits av denna funktion fr?n produkten: Enhetens IMEI: Lagras lokalt och p? molnservern Enhetens ECID: Lagras lokalt Enhetens CU: Lagras lokalt Enhetsmodell: Lagras lokalt och p? molnservern server Enhetens projektnamn: Lagras lokalt APN-data: Lagras lokalt SIM-kortinformation: Lagras inte |
Nej |
Enhetens IMEI: R?data |
Enhet: |
| TctWFC Personlig information om vanligt f?rekommande enheter (IMEI, IMSI, enhets-ID osv.) Personlig grundl?ggande information (E911-adress) Anv?ndar s beteende: WFC-standardinst?llningar, v?xlingsinst?llningar |
Endast E911-adressen beh?ver visas f?r slutanv?ndaren som en str?ng |
IMEI：1 IMSI：1 enhets-ID：1 E911-adress：1 |
Rapportera efter aff?rsverksamhet |
E911-adress, IMEI och IMSI lagras i molnet |
Beroende p? lagringstiden p? operat?rens server |
R?data: IMEI, IMSI, enhets-ID, E911-adress |
Enhet: Anv?ndaren kan komma ?t data genom att anv?nda [operat?rsservrar] |
| TctPhone PLMN: Personlig gemensam enhetsinformation |
xml |
PLMN:1 R?relsesensordata: 1 Telefonnummer: 5 Samtalsl?ngd: 1 Flygplansl?gesbrytarens status: 1 HAC-omkopplarstatus: 1 Status f?r automatisk svar : 1 Status f?r vibrationsp?minnelse under uppringning och svar: 1 Status f?r Call_audio_state_ovoid-omkopplare: 1 ECID：1 |
Samtalsl?ngd i historiken: ring en g?ng, generera en g?ng |
Existens lokalt |
1. Data om samtalsl?ngd: permanent lagring 2. ?vrig data: Realtids?ndringar eller radering baserat p? anv?ndarbeteende, annars permanent sparad |
R?data: PLMN, r?relsesensordata, telefonnummer, samtalsregister, flygplansl?ge-status, HAC-status, automatisk svar-status, vibrationsp?minnelse-status vid uppringning och svar, call_oudio_state_ovoid-status, ECID |
Enhet: /mnt/oempersist/ |
| FOTA Aktuell enhets SN/IMEI: Personlig enhetsinformation |
xlsx/xls/csv |
Cirka 10 sp?rningspunkter genereras under en enda uppdatering (under normala f?rh?llanden och utan anv?ndar?tg?rder). Om det finns anv?ndar?tg?rder eller omf?rs?k p? grund av undantag kan antalet sp?rningspunkter ?ka. |
1，Datasp?rningspunkter genereras under systemuppdateringsoperationer. 2，Datasporringspunkter genereras under den 24-timmars l?nga pollningsprocessen (resultat fr?n pollning av servern). |
All information lagras i molnet |
nej |
H?mtas fr?n systemet eller enheten: SN/IMEI, CU, Ecid, versionsnummer, PLMN |
Ingen ?tkomst till data |
| AOTA Icke-personliga data: |
CSV |
17 （F?r n?rvarande installerade appar p? enheten: 2 Aktuell information om nedladdade appar: 2 Mobilappsversion: 2 CU: 2 targetEcid: 2 Uppgifts-ID: 2 Analysstatus: 2 Uppdaterings typ: 1 Switchtyp: 1 Lista ?ver uppdateringsbara appar: 1） |
1: Datasp?rningspunkt som genereras n?r anv?ndaren klickar f?r att ladda ner APK-filen 2: Genereras under 24-timmars polling 3: N?r anv?ndaren klickar p? "uppdateringsp?minnelseomkopplaren" |
P? molnservern: Sp?rningsdata P? enheten: Status f?r omkopplare i appen Lista ?ver uppdateringsbara appar |
Moln: data lagras omedelbart efter att en sp?rningsh?ndelse har utl?sts Lokalt: Appens switchstatus och listan ?ver uppdateringsbara appar lagras alltid |
R?data: CU, targetEcid |
Ingen ?tkomst till data |
|
Icke-personuppgifter: Datarapport: Icke-personuppgifter |
JSON |
11 (produktnamn：1 datarapport: 6 Latitud och longitud: 1 MNC/MCC: 1 G-sensor- eller gyroskopdata: 1 TargetEcid- (specifik ECID som motsvarar operat?rskunder): 1) |
Touch-data rapporteras n?r anv?ndaren utl?ser en responsiv ?tg?rd. Latitud och longitud erh?lls n?r anv?ndaren tar ett foto eller spelar in en video. |
P? molnservern: datarapport P? enheten: Latitud och longitud: Lagras i den tagna bilden eller videon Marknadsnamn, modell: Lagras i EXIF |
BI-data lagras i 35 dagar |
Genererade data: |
Ingen ?tkomst till data ?r tillg?nglig |
| Bluetooth Personuppgifter: Bluetooth-namn och MAC-adress Icke-personliga uppgifter: andra uppgifter |
Str?ng |
Bluetooth-parkoppling/anslutning och lagring av enhetslista |
Bluetooth-parkoppling/anslutning och lagring av enhetslista |
P? enheten |
Sparas tills du manuellt tar bort eller ?terst?ller till fabriksinst?llningar |
Genererade data: Bluetooth-interna data och anv?ndarkonfigurerat enhetsnamn |
Anv?ndaren kan komma ?t data via: /data/misc/bluedro |
| tclloginsdk Personuppgifter |
CSV |
16 |
Generering av realtids |
P? moln sservern |
/ |
R?data |
Ingen ?tkomst till data |
3. Datatillg?ng och delning
Vi kan komma ?t, anv?nda och l?mna ut icke-personliga data som genereras av din produkt genom dess integrerade tj?nster och funktioner till tredje part f?r aff?rs?ndam?l enligt beskrivningen i detta avsnitt. F?r mer information om detta h?nvisar vi till de till?mpliga anv?ndarvillkoren.
Om du vill f? information om insamling, anv?ndning, utl?mnande, ?verf?ring eller behandling av dina personuppgifter, uppmanar vi dig att l?sa det till?mpliga sekretessmeddelandet.
| Enheter med ?tkomst | Syfte med behandlingen | Delning med tredje part | Syfte med delning av data till tredje part |
| LETOU - 乐投 Communication Ltd. at 5/F, Building 22E, 22 Science Park East Avenue, Hong Kong Science Park, Shatin, NT, Hong Kong |
N?dv?ndigt f?r funktioner, eftermarknadsunderh?ll | LETOU - 乐投:s europeiska telekomoperat?rspartners. | F?r att s?kerst?lla produktcertifieringens efterlevnad och kontinuerlig produktoptimering |
4. Anv?ndarr?ttigheter
I detta avsnitt anges dina r?ttigheter, hur du kan ut?va dessa r?ttigheter samt villkoren f?r anv?ndning av data och servicekvalitet som g?ller f?r dig .
EU:s datalag kan ge dig ett antal lagliga r?ttigheter i relation till data om anslutna produkter och relaterade tj?nster.
Du kan skicka in beg?ran om tillg?ng till data och dela data med tredje part genom att anv?nda nedanst?ende kontaktuppgifter:
Kontaktformul?r f?r datalagen p? LETOU - 乐投:s officiella webbplatser >>
I den utstr?ckning som lagen till?ter kan vi inte ge tillg?ng till data som inneh?ller konfidentiella uppgifter, aff?rshemligheter, immateriella r?ttigheter eller annan skyddad information.
Om du vill ut?va dina r?ttigheter i relation till de personuppgifter som vi har om dig, v?nligen kontakta oss med hj?lp av uppgifterna i den sekretesspolicy som g?ller f?r din produkt.
F?r mer detaljerad information om anv?ndning av och tillg?ng till data, se anv?ndarvillkoren, elektroniska manualer eller annat relevant material.
Som anv?ndare har du r?tt att l?mna in ett klagom?l om du anser att n?gon av dina r?ttigheter enligt dataskyddslagen har kr?nkts. Denna r?ttighet s?kerst?ller att dina farh?gor om potentiella ?vertr?delser av best?mmelserna om tillg?ng till, delning eller anv?ndning av data blir h?rda och behandlas p? l?mpligt s?tt av den ansvariga tillsynsmyndigheten. Om du vill ut?va denna r?ttighet eller beh?ver ytterligare hj?lp, v?nligen kontakta den relevanta myndigheten i din medlemsstat p? .
5. Kontaktuppgifter
| Tillverkare | LETOU - 乐投 Communication Ltd. |
EU DATA ACT User Information on Smartphone
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 | Smartphone |
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.