Privacy Policy
This Privacy Policy is a globally unified official privacy compliance document for the LaylPlayer video playback software (hereinafter referred to as “This Application” or “Us”), strictly conforming to the Global General Data Protection Regulations, International Internet Privacy Guidelines, and overseas mainstream regional data security standards. It applies uniformly to users in all countries and regions worldwide without setting special terms for any regional jurisdictions. This Policy aims to inform users transparently and fully of the rules for the Application‘s collection, storage, use, transmission, protection, and deletion of user personal data, device data, and usage behavior data during the operation of the Services. All users who download, install, register and use the fully functional LaylPlayer services indicate that they have fully read, fully understood and voluntarily agreed to the full content of this Privacy Policy. User privacy consultations, data rights applications, violations complaints and collaboration communications can be connected via the official exclusive contact email: pyretictech01solutions@outlook.com, and we will complete formal response and processing within 3 to 7 business days.
1. Policy Definition and Scope
1.1 Applicable Subjects and Scenes
1.1.1 This Policy is fully applicable to all global end users who download, install, open, sign up, and pay to use all LaylPlayer services, including all officially released versions of the application for mobile, desktop, and tablet devices.
1.1.2 This Policy covers all core and subsidiary features of this Application, including all service scenarios such as local video playback, playback cache, image quality adjustment, speed adaptation, background playback, collection subscriptions, personalized recommendations, device sync, and more.
1.2 Core Terminology Definitions
1.2.1 Personal Identifiable Data: Means information that can directly or indirectly lock and identify a specific user identity, including related data such as account identification, custom nicknames, user device unique codes, and login records.
1.2.2 Non-Personal Behavioral Data: refers to anonymized, de-sensitive operational data that cannot be attributed to a single user, including application crash logs, feature usage frequency, device system adaptation parameters, overall user usage trend data, and so on.
1.2.3 Data Processing: The full-process operational behavior of collection, caching, storage, analysis, invocation, transmission, desensitization, destruction, and archiving of various types of user data.
2. Types and Methods of User Data Collection
2.1 User Proactively Authorizes Data Collection
2.1.1 Device Permission Data: To achieve the core function of video playback, after user active authorization, this application only obtains device-local storage read permission, used to identify, load local video, caption files, and does not privately read non-privacy-related files such as photo albums, contacts, and documents.
2.1.2 Account Base Data: User voluntary registration, user name submitted when logging into the account, login key, bound authentication information, used only for account authentication, cloud playback record synchronization, personal favorite content backup, no additional collection purposes.
2.1.3 Custom Preference Data: User-selected personalized configuration data such as playback quality, doubling speed, caption style, theme skin, background playback, lock screen playback, etc., is used to retain user usage habits and optimize the user experience.
2.2 System Passive Silent Collection of Data
2.2.1 Device Fundamentals: The device model, OS version, screen resolution, and device operating environment parameters obtained silently during application execution are used only to adapt the device, optimize playback compatibility, and resolve adaptation vulnerabilities.
2.2.2 Service Run Logs: Automatically generated application launch logs, function call logs, anomalous crash logs, and network connection status logs for troubleshooting program failures, fixing system vulnerabilities, and ensuring stable service operation.
2.2.3 Anonymous Usage Data: Statistical applications anonymously aggregate data such as frequency of feature use, user activity periods, feature preferences, etc. It is unable to locate individual users and is used only for product iteration and feature optimization.
3. Legal Usage of User Data
3.1 Basic Service Operational Uses
3.1.1 Based on device permissions data and system parameters, the core functions such as local video scanning, HD playback, caption matching, audio track switching, smooth screen projection, and more are implemented to ensure the normal operation of the underlying playback service.
3.1.2 Complete user identity verification through account data, enable device-to-device playback record synchronization, favorite list cloud backup, personalized configuration retention, and provide consistent cross-end user experience.
3.1.3 Use run log data to monitor application health in real time to quickly locate issues such as flashbacks, jams, audio and graphics disynchronization, decoding failures, and more, continuously optimizing playback smoothness and device suitability.
3.2 Product Optimization and Security Wind Control Uses
3.2.1 Analyze user feature usage preferences based on anonymized usage data, iteratively optimize product features, adjust interface design, and add new playback tools to adapt to user needs to continuously improve the product experience.
3.2.2 Identify risky behaviors such as unusual logins, batch swipes, malicious hacking, and illegal tampering through account login logs and device access logs to prevent security risks such as account theft, program tampering, and malicious abuse of services.
3.2.3 Maintain necessary operational data in accordance with compliance requirements, for use in violation conduct checks, security incident tracing, user rights and interests protection, and strictly comply with the International Common Compliance Standards.
4. Data Storage Specifications and Retention Cycles
4.1 Data Storage Security Standards
4.1.1 This application‘s user data is stored in a dual mode of “local cache + international compliant cloud server backup,” with all cloud servers deployed in overseas compliant data centers, with no domestic data storage and transmission involved throughout the process. 4.1.2 All stored user data is encrypted using advanced encryption algorithms, with multi-layer firewalls, data privilege isolation, and access log tracing mechanisms established. Only core operations personnel can retrieve data on demand, preventing the risk of data leakage, tampering, and loss.
4.1.3 Local cache data remains only on the user‘s personal device, and this application will not privately upload the user’s local video files, private playback content, to adequately protect the user’s local privacy security.
4.2 Hierarchical Data Retention Time
4.2.1 Account Core Data: Permanently retained until the user actively logs out of the account and requests the destruction of the data, after which all account bound data, cloud records, and backup content are completely cleared.
4.2.2 Playback records and preference data: User-local records can be automatically deleted manually, cloud-synchronized records are retained by default for 180 days, with automatic anonymous destruction at expiration, without manual retention operation.
4.2.3 Operating logs and anomaly data: Regular logs are retained for 90 days, and special logs related to troubleshooting and security wind control are retained for 120 days. They are automatically cleared immediately after the inspection treatment is complete, and are stored with short-term redundancy.
5. Third-party data sharing and cross-border transfer rules
5.1 Third Party Sharing Limit Specifications
5.1.1 This application strictly adheres to the principles of data confidentiality and will never sell, rent, or resell any user‘s personal data, playback data, device data, or any commercial data transaction for profit.
5.1.2 Only to ensure the proper operation of the service, a minimal portion of non-sensitive data may be shared with overseas compliant third-party technology providers, including cloud storage providers, security wind control providers, and application statistics providers.
5.1.3 All third parties cooperating must sign strict data confidentiality and compliance agreements that clearly define the scope of data use, retention cycles, and confidentiality obligations, and prohibit third parties from second-hand transfers and misuse of user data.
5.2 Cross-Border Data Transfer Mechanisms
5.2.1 Due to the needs of global service deployment, user data may be transferred cross-borderly between overseas compliant data centers, all transfer behaviors conforming to international data cross-border transfer Common Standards, with complete compliance assurance mechanisms.
5.2.2 All cross-border data transfers are decrypted and encrypted, removing all personally identifiable information and retaining only the common data necessary for operations, minimizing privacy risks.
5.2.3 This Application does not transfer user data to countries, regions, and institutions that do not qualify for compliance, ensuring that the cross-border data flow is secure, legal, and controllable throughout the process.
6. User Privacy Core Rights Details
6.1 Basic Data Control Rights
6.1.1 Data Query Right: Users can query all personal data content such as personal account data, cloud playback history, device binding information, data retention status, and more at any time from the privacy settings page of the application.
6.1.2 Right to Correct Information: Users who discover that their personal account information or configuration information is incorrect or incomplete can voluntarily modify the update within the application, or contact the official email address to request assistance in correcting it.
6.1.3 Permission revocation right: Users can revoke application permissions such as storage, network, etc. at any time in the device‘s system settings, and the corresponding data collection behavior will immediately terminate upon revocation, without affecting the completed compliance data processing operations.
6.2 Advanced Data Handling Rights
6.2.1 Data Deletion Right: Users can voluntarily delete local playback records, cached files, personalized configurations, and can also apply for a batch purge of all personal data in the cloud via official email.
6.2.2 Account Registration Right: Users can request to register their personal LaylPlayer account at any time, and upon completion, we will permanently destroy all data associated with that account, leaving only the wind control records necessary for compliance.
6.2.3 Rights to Objection: Users who have objections to the data processing behavior of this Application and believe that their privacy rights are compromised can submit a complaint through our official email address, and we will review and provide corrections and response solutions.
7. Special Privacy Protection Rules for Minors
7.1 Underage Usage Standards
7.1.1 LaylPlayer is open to users of all ages worldwide. Minors using this application service must be done with the knowledge, accompaniment, and supervision of the guardian. The guardian is responsible for regulating all data behaviors resulting from the autonomous operation of the minor.
7.1.2 This App does not actively collect sensitive personal privacy data such as the name, age, address, and contact information of minors, all of which are collected based on the necessary scenarios for the Basic Playback Service.
7.1.3 Apply no juvenile-specific induction functions, do not promote obscene, violent, and inappropriate content, continuously optimize the content wind control mechanism, and ensure the safety of the environment for juvenile use.
7.2 Canals for Guardian Rights
7.2.1 Guardians who discover that minors have privately uploaded privacy content, generated abnormal data records, and are at risk of privacy disclosure can at any time apply for data cleansing, permissions restrictions, and risk remediation via official email.
7.2.2 For sensitive data collected by mistake from minors, we will initiate a dedicated cleanup within 24 hours of receiving the request to completely destroy the relevant data, retaining treatment records throughout the process.
8. Data Security Protection and Risk Response Mechanisms
8.1 Normalizing Security Measures
8.1.1 Technology Protection: Data encryption transmission, local data encryption cache, and cloud data encryption storage technologies are adopted throughout the application, combined with firewall protection, regular vulnerability scanning, and penetration testing to protect against hacking attacks, data theft, and illegal access risks in all directions.
8.1.2 System protection: Establish a strict data hierarchy management system, employee data confidentiality system, operational permissions management control system, strictly control data access, operations, and transfer permissions, and prevent risk of internal data leakage.
8.1.3 Iterative Protection: Keep up with the latest global data security and privacy protection standards, regularly update protection systems, optimize privacy policies, and adapt to international compliance standards updates.
8.2 Emergency Response to Security Incidents
8.2.1 If security events such as abnormal data access, leakage, or loss occur, we will immediately initiate emergency plans to immediately block the source of risk, isolate abnormal data, and troubleshoot the impact range.
8.2.2 Quickly complete risk remediation and vulnerability remediation, provide compliance notifications for affected users, synchronously maintain full remediation logs, and ensure event transparency and traceability.
8.2.3 In response to the loss of user rights and interests caused by security incidents, we will actively cooperate with user rights in accordance with international compliance standards and assume compliance responsibilities in response.
9. Policy updates and user notification mechanisms
9.1 Policy Amendment Authority
9.1.1 We reserve the exclusive right to revise, update and optimize this Privacy Policy at any time, updating it based on scenarios including product feature iteration, global privacy compliance standards upgrades, industry standards adjustments, service model optimizations, etc.
9.1.2 Policy Updates are divided into general fine-tuning and major revisions. General fine-tuning optimizes terms and expressions and refines rules; major revisions involve core content adjustments such as the scope of data collection, usage purposes, and storage rules.
9.2 Updated Announcements and Rules of Effectiveness
9.2.1 All Policy Updates are published uniformly through the application privacy page and official disclosure channels, without the need to individually notify users, and will take effect officially from the date of publication of the latest version.
9.2.2 After the Policy update, Users continue to download, open, and use all services of this App, which is to say, automatically acknowledge and agree to the complete revised Privacy Policy and voluntarily accept the new terms and conditions.
9.2.3 If the user does not agree to the updated Policy terms, the only remedy is to immediately stop using this App, uninstall the App, and sign out of the personal account.
10. Consultation Channels and Dispute Resolution Rules
10.1 Official Consultation Connections
10.1.1 All privacy policy consultations, data rights requests, privacy complaints, problem feedback, and compliance correspondence are submitted through the single official email address pyretictech01solutions@outlook.com.
10.1.2 We set up a dedicated privacy compliance handling team and commit to completing checks, handling and feedback on results within 3 to 7 business days after receiving user emails, ensuring that user claims are efficiently met.
10.2 Dispute Resolution and Legal Effectiveness
10.2.1 All disputes arising between you and us due to this Privacy Policy and our data processing practices will be prioritized for proper resolution through friendly negotiation and email communication.
10.2.2 The two parties cannot reach an agreement on disputes by negotiation, and the decisions are unanimously applied to the International Common Data Protection and Business Compliance Standards, and do not apply to any country‘s regional exclusive laws and regulations.
10.2.3 When any individual provision of this Policy is determined to be invalid or unenforceable, it does not affect the full legal validity of all remaining provisions, which remain valid and enforce independently.
10.2.4 This Privacy Policy is the official final effective privacy compliance document for the LaylPlayer video playback software. Any third-party advertising and interpretation will not have legal validity. All will be based on the content of this Policy.