. Custom \ Privacy

ROBAE Leap Sigil. Special Privacy & Agreement｜Customization

Overview

This document is the officialSpecial Privacy Protection Agreement for ROBAE Jump Starcrest Custom Business, an exclusive supplementary statute of the brand’s general privacy and agreement system. It focuses on regulating privacy protection boundaries, data protection rules, asset ownership standards and compliance operation mechanisms for all categories of the brand’s custom services. This agreement takes effect concurrently with and complements the basic privacy agreement. It is centered onfull-process privacy and security protection for customization. It does not describe service functions or define service workflows, and only clarifies privacy protection criteria and user data rights for various custom businesses.

All custom businesses of the brand are uniformly divided intotwo core tiers: underlying architecture & data customization, and system application layer expansion customization. They cover seven vertical custom fields across all scenarios. All private data, architectural parameters, exclusive configurations and principal privacy information generated during customization transformation, deployment adaptation, system iteration and scenario expansion in all tiers and fields shall strictly comply with this privacy protection statute, and implement the core standards of end-side closed-loop, self-owned ownership, isolated protection, no leakage and no abuse throughout the whole process.

Two core customization tiers and seven vertical custom fields covered by this Agreement:

Two Core Customization Tiers: Underlying Deployment Architecture & Data Customization, Systematic Application Layer Expansion Customization

Seven Vertical Custom Fields: Private Customization, Family & Clan Customization, Healthcare Business Customization, Education Business Customization, Enterprise Customization, Group Organization Customization, Public Utility Customization

For custom development, local deployment, architecture adaptation, data transformation, persona expansion, scenario expansion and system configuration iteration in all the above tiers and fields, this Agreement uniformly regulates privacy protection standards, comprehensively protects exclusive private data and core digital assets of individuals, families, institutions, groups and public entities, and ensures absolute security, independence and controllability of digital sovereignty for all customized entities.

I. Universal Global Privacy Protection Criteria for Custom Business

Whether it is underlying architecture & data customization, application-layer scenario and persona customization, or various custom services within the seven vertical fields, all customization activities shall uniformly follow the six core privacy principles:Self-owned Ownership, Local Closed-Loop, Tiered Isolation, Least Privilege, Full-Lifecycle Protection, Controllable Iteration. Risks including privacy leakage, data misappropriation, feature fine-tuning and asset outflow are eliminated from both underlying architecture and application operation layers.

1. Exclusive Ownership of Custom Assets: All architectural parameters, data models, system configurations, persona features, scenario rules and exclusive data systems generated by customization belong exclusively to the corresponding customized entity. The brand does not hold ownership, usage rights, training rights or transfer rights of any custom assets, and has no permission for private invocation, aggregation or commercial use.

2. Closed-Loop Protection of Custom Data: All private data generated during custom debugging, architecture deployment, data adaptation and scenario iteration is stored locally in an end-side closed loop by default, processed locally and updated locally. Core private data is not uploaded to cloud, aggregated, warehoused, incorporated into public algorithm training, or circulated publicly.

3. Tiered Isolation for Privacy Protection: Custom data of different customization tiers, vertical fields and entities are physically isolated from one another. Private systems for individuals, families, education, healthcare, enterprises, groups and public utilities are independently archived, with no data crosstalk, parameter penetration, content mixing or style assimilation.

4. Principle of Minimum Voluntary Authorization: All customization-related data reading, parameter adaptation and system debugging activities are activated only upon voluntary authorization by the user or entity, and only access the minimum data scope required for customization. There is no silent collection, passive authorization, excessive access or implicit privilege expansion.

5. Full Traceability & Data Erasure: Data operations, parameter modifications, privilege changes and system iteration activities throughout the customization lifecycle are fully logged, traceable and retrievable. Users and entity administrators may withdraw authorization, reset configurations, erase custom data and restore the system to its initial state at any time to completely remove custom privacy traces.

6. Controllable Privacy During Custom Iteration: Iteration updates, architecture optimization and scenario upgrades of all customized systems are independently controlled in pace and scope by the customized entity. The iteration process strictly prevents private data leakage, without unauthorized addition of data collection privileges or expansion of privacy usage scope.

II. Privacy Protection Specifications for Underlying Deployment, Architecture and Data Customization

Underlying customization serves as the core foundation of all brand custom services, covering three core components: system architecture customization, local deployment customization and private data system customization. It directly touches underlying digital assets and system operating kernels of users and various entities, with the highest privacy protection level and most stringent protection rules. Underlying customization across the seven vertical fields shall uniformly comply with the following specifications.

1. Privacy Protection for Underlying Architecture Customization

During system architecture adaptation, end-side deployment architecture transformation and private runtime framework customization exclusive to each entity, all underlying architectural parameters, system operating logic, exclusive adaptation rules and hardware adaptation configurations are archived within the local private domain. The brand only provides standardized custom technical support. It does not read, record or store any entity-specific architectural information, nor obtain underlying runtime privacy logic, eliminating risks of architecture information leakage, reuse of underlying configurations and homogenization of system logic.

2. Privacy Protection for Local Deployment Customization

For local deployment customization services for individuals, families, enterprises and various business entities, all deployment files, local runtime packages, private deployment keys and local privilege system configurations are deployed in a closed loop on user terminals or entity-exclusive private devices. There is no cloud relay, background crawling or third-party intervention during deployment. After deployment, all exclusive deployment data remains privately owned by the corresponding entity only.

3. Privacy Protection for Private Data System Customization

During customization of underlying data structures, private vector database adaptation, local data archiving rules, private data classification systems and data encryption mechanisms, all confidential data, exclusive data features, private data storage rules and encryption key information of the entity are protected with end-to-end encryption. Custom debugging only adapts the data runtime framework; it does not read original private data content, parse user confidential information or aggregate entity data features, fully securing underlying data assets.

4. Global Underlying Privacy Isolation Mechanism

Underlying customization systems of the seven vertical fields are independently isolated. Private underlying data architecture, family underlying deployment systems, enterprise and business underlying data models are non-penetrable, non-reusable and incompatible with each other. Underlying customization iteration within one field will not affect the privacy data security of other fields or cause cross-field privacy leakage.

III. Privacy Protection Specifications for Systematic Application Layer Expansion Customization

System application layer customization focuses on two core dimensions: persona expansion and scenario expansion. It forms the outer-layer application customization system for intelligent implementation of various entities, covering full-scenario application expansion demands across the seven vertical fields. Application layer customization consistently follows the core principle: application expansion shall not touch privacy kernels; function iteration shall not leak exclusive assets, to fully protect entity application-layer privacy and personalized exclusive traits.

1. Privacy Protection for Persona Expansion Customization

During addition, expansion, iteration and adaptation customization of exclusive persona systems in each field, sandbox isolation privacy rules are strictly enforced. Private personas, family personas, enterprise job personas, and exclusive personas for education/health/group/public utilities all have independent privacy sandboxes. Personality traits, behavioral logic, privilege configurations and exclusive memory systems corresponding to personas are fully independently archived. Persona expansion only updates application-layer function adaptation logic, without modifying underlying privacy parameters, accessing private data across personas or assimilating exclusive personality traits.

2. Privacy Protection for Scenario Expansion Customization

During full-field scenario-based function expansion, dedicated scenario construction and scenario interaction logic customization, only the general scenario runtime framework is adapted. Confidential interaction content, personal behavior trajectories and exclusive scenario preferences of the entity within scenarios are not collected, recorded or stored. All scenario expansion configurations, scenario runtime rules and scenario adaptation parameters are stored in isolation within the corresponding entity’s private domain. The brand only provides standardized expansion technical support and never accesses, parses or retains any entity confidential scenario data throughout the whole process, completely eliminating privacy leakage risks brought by scenario expansion and guaranteeing absolute security of scenario interaction privacy for entities in all fields.

IV. Unified Global Privacy Protection Rules for the Seven Vertical Fields

Based on the brand’s two core customization tiers, a globally unified and hierarchically stringent privacy protection standard is implemented for the seven custom fields ofindividuals, families & clans, healthcare business, education business, enterprises, group organizations and public utilities. Customization in all fields complies with principles of independent ownership, data isolation, local closed-loop, no leakage and no commercial use. Corresponding protection levels are adapted according to different entity attributes, with no exceptions for any field.

1. Privacy Protection for Private Customization

Private underlying data architecture, individual local deployment, personal persona and scenario expansion customization operate in a closed loop centered on the user’s personal private digital assets. All private model parameters, memory data, personality traits and interaction privacy are self-owned solely by the user. The brand does not collect, store or fine-tune user personal traits. All private custom data is independently isolated and will not be shared or mixed with data from any other fields.

2. Privacy Protection for Family & Clan Customization

For family-exclusive underlying deployment architecture, family public data systems and family persona & scenario expansion customization, a clear distinction is maintained between family public domain and personal private domain. Overall family custom data is independently archived and will not penetrate members’ individual privacy sandboxes. It will not read, reuse or tamper with members’ private data, ensuring orderly family cluster collaboration and independent, secure personal privacy.

3. Privacy Protection for Healthcare Business Customization

Underlying data customization and expansion of healthcare scenarios & exclusive personas in the healthcare field involve highly sensitive private data and adopt the highest level of protection standards. All health data, physical and mental status records and healthcare adaptation parameters run in a locally encrypted closed loop. The brand has no authority to read, aggregate, commercialize or leak such data, strictly safeguarding confidential core healthcare assets.

4. Privacy Protection for Education Business Customization

Architecture deployment, learning data systems, education scenario and persona custom data within the education field are all exclusive private assets of teachers, students and education entities. Learning trajectories, education interaction records and exclusive adaptation parameters are protected in isolation, not circulated externally or used for algorithm fine-tuning, ensuring pure, secure and controllable privacy in education scenarios.

5. Privacy Protection for Enterprise Customization

Enterprise underlying architecture, business data systems, enterprise job personas and office scenario expansion customization all belong privately to the enterprise entity. Enterprise business data, business logic, job privileges and office interaction data are locally closed-loop. The brand does not obtain the enterprise’s core operational privacy or reuse enterprise custom architectures and parameters, guaranteeing absolute security of enterprise commercial data.

6. Privacy Protection for Group Organization Customization

Underlying deployment, group data, group personas and collaborative scenario custom data for associations, organizations and teams are independently archived within the group-exclusive private domain. Internal group collaboration data, organizational architecture parameters and group adaptation configurations are not disclosed to the public or shared across groups, ensuring independent privacy and controllable order for group organizations.

7. Privacy Protection for Public Utility Customization

Customization of public utility architecture, public scenario expansion and public service persona systems strictly complies with dual standards of public compliance and privacy isolation. Public service operational data is completely separated from individual confidential data. Public custom architecture only serves public scenarios and does not touch any private assets of individuals or institutions, balancing public service attributes and global privacy security.

V. Rules for Authorization, Retention and Liquidation of Custom Data

1.Authorization Rules: All custom-related data operations, architecture adaptation and expansion iterations of the brand take effect based on voluntary authorization by the entity. A least-privilege access mechanism is implemented with no default authorization, silent collection or excessive data access.

2. Data Retention: All underlying architecture data, configuration parameters and application expansion records generated from customization are retained only within the local private environment of the corresponding entity. The brand does not perform cloud backup, background storage or data aggregation.

3. Data Liquidation: The entity may terminate any custom service, withdraw authorization, reset custom configurations, erase all custom private data and fully restore the system to its initial state at any time, with no residual data or implicit reuse.

4. Agreement Iteration: Iterative updates of this Custom Privacy Agreement are limited to compliance upgrades and protection enhancements. They will never reduce privacy rights of users and various entities, nor alter the core principles of local closed-loop and self-owned ownership. Revised versions will be announced and take effect on the client side.

VI. Supplementary Provisions & Core Statements

This Agreement is the exclusive privacy protection statute for custom businesses of the ROBAE Jump Starcrest brand, applicable to the two core businesses ofunderlying architecture & data customization and systematic application layer expansion customization, covering seven vertical business fields. All customization activities consistently uphold the core principles of “Entity Self-Ownership, Local Closed-Loop, Tiered Isolation, Full Lifecycle Protection”. The brand only provides technical customization support and will not occupy, misappropriate, fine-tune or leak any entity private custom assets, comprehensively safeguarding the digital privacy sovereignty and asset security of individuals, families, enterprises and various business entities.

ROBAE | Leap Sigil

Leap Sigil · Official Announcement of Exclusive Privacy Agreement for Custom Business

Version 2026