核心隐私承诺：
【一叶批量重命名】是一款纯本地运行的专业文件与文件夹批量重命名与整理工具。本应用不会收集、上传、存储或共享您的任何个人身份信息、文件内容、通讯录、重命名规则或历史记录到任何远程服务器。所有规则匹配、文件名修改与撤销操作均 100% 在您的设备芯片及本地存储内完成。
1. 我们如何处理您的数据
文件处理与本地运算：为了实现流水线规则组合（如文本替换、前后缀、递增补零编号、大小写规整及正则表达式），应用仅在本地内存中对您主动挑选的文件名进行规则运算与安全冲突诊断。文件的实际内容不会被修改或读取，任何计算过程绝不通过网络向外传输。
重命名历史与一键撤销 (Undo)：应用提供可靠的操作撤销能力。每次执行重命名时，仅在设备本地应用私有沙盒存储中记录该批次文件的原路径与新路径映射。该历史记录绝不上传网络，仅供您在本地发起“撤销重命名”时使用。您可以随时主动清空历史记录，所有记录随应用卸载自动销毁。
本地配置偏好：您的排序习惯、扩展名安全保护开关等偏好设置，仅保存在手机本地的 SharedPreferences 配置文件中，不涉及任何个人隐私。
2. 设备权限使用说明
为了实现核心的文件重命名与目录管理功能，应用本着最小必要权限原则申请系统权限，我们在此对权限用途作清晰透明的声明：
所有文件访问权限 (MANAGE_EXTERNAL_STORAGE)
必要核心权限：作为专业文件重命名与文件整理工具，应用需要重命名您设备存储空间（包括内部存储及外置 SD 卡）中的文件与文件夹。此权限仅在您明确配置规则并点击“应用重命名”或“撤销”时，对您勾选的目标文件执行重命名操作，绝不用于未授权的任何其他行为。
注：为最大程度保护您的设备安全与纯净，【一叶批量重命名】不申请安装未知应用权限 (REQUEST_INSTALL_PACKAGES) 及查询所有软件包权限 (QUERY_ALL_PACKAGES)，杜绝任何冗余特权。
3. 第三方 SDK 与数据服务声明
为了保障软件运行的稳定性、持续优化用户交互体验以及及时下发重要配置，在 Google Play 发布的版本中集成了 Google 官方提供的 Firebase SDK 套件（国内渠道版本完全隔离并移除了相关 Google 远程组件）：
Google Firebase Crashlytics（异常崩溃监控）
- 使用目的：实时捕获应用在运行过程中的崩溃异常与未响应（ANR）日志，帮助开发者快速定位代码缺陷并提升软件并发重命名与文件 IO 的稳定性。
- 数据收集范围：设备机型、操作系统版本、应用版本、崩溃堆栈跟踪信息、设备状态（如可用内存与存储空间大小）。
- 隐私边界：绝不收集任何用户身份信息、网络硬件地址（MAC/IMEI）或设备中的任何文件内容、文件名与重命名历史。
Google Firebase Analytics（匿名用户分析与统计）
- 使用目的：统计应用的日常活跃指标与核心功能使用频次（如各重命名模式的选用比例），用于指导产品性能迭代与界面体验改进。
- 数据收集范围：匿名应用实例标识符（Firebase App Instance ID）、标准设备技术参数（系统语言、屏幕分辨率、操作系统版本）、匿名聚合的功能交互事件。
- 隐私边界：严格禁止并杜绝收集用户具体的替换关键词、正则表达式内容、本地文件路径、文件内容或任何可识别用户真实身份的个人数据。
Google Firebase Remote Config（远程参数与动态配置）
- 使用目的：用于动态下发合规与版本更新提示、性能优化参数、功能开关以及一叶应用工坊精品应用推荐，无需频繁重新发版即可快速响应兼容性调整。
- 数据交互：仅在应用启动或配置刷新时，向 Firebase 服务器拉取最新的只读参数键值对。不收集或回传用户本地隐私数据。
上述 Google Firebase 服务均严格遵循 Google 隐私权政策 及 Google Play 开发者分发协议。
4. 政策变更与联系我们
我们可能会根据相关法规更新本隐私政策。若您对本政策有任何疑问、建议或隐私反馈，可通过开发者邮箱与我们取得联系：KTLShu@163.com。
Our Privacy Commitment:
Leaf Batch Rename is a standalone, local-first batch file and folder renaming utility. We do NOT collect, upload, store, or share any personal identifiable information, file contents, contacts, renaming rules, or history records to external servers. All rule matching, name modifications, and undo actions are performed 100% locally on your device.
1. Data Handling & Security
Local Processing: To provide powerful pipeline rule transformations (Find & Replace, Prefix/Suffix, Sequential Zero-Padded Numbering, Letter Case Conversions, and Regular Expressions), all evaluations and collision diagnoses occur strictly within local device memory. The underlying file contents are never read or altered, and no computational data is ever transmitted externally.
Rename History & Safe Undo: The app offers an instant Undo mechanism. When a batch rename executes, only a local mapping of the old file path and new file path is saved in the app's sandboxed private storage. This data is strictly local, never leaves your device, and can be cleared at any time. It is permanently removed upon app uninstallation.
Preferences: Your sorting preferences and extension protection settings are stored exclusively in local Android SharedPreferences.
2. App Permissions & Justification
All Files Access (MANAGE_EXTERNAL_STORAGE)
Core Functional Requirement: As a dedicated batch file management and renaming utility, this permission is strictly necessary to modify filenames across internal storage and removable SD cards. It is only exercised when you explicitly configure rules and tap "Apply Rename" or "Undo", never for unauthorized or background modifications.
Note: Adhering strictly to the Principle of Least Privilege and rigorous user privacy standards, Leaf Batch Rename does NOT request permissions to install unknown apps (REQUEST_INSTALL_PACKAGES) or query device-wide installed packages (QUERY_ALL_PACKAGES).
3. Third-Party SDKs & Services (Google Firebase)
For Google Play releases, we integrate the official Google Firebase SDK Suite strictly to ensure application stability, understand aggregated feature adoption to improve performance, and deliver dynamic runtime configuration. (Domestic/China releases are completely isolated from these Google cloud services):
Google Firebase Crashlytics (Crash Reporting)
- Purpose: Diagnosing unhandled exceptions, app crashes, and Application Not Responding (ANR) events to ensure robust multi-file IO stability.
- Data Collected: Non-personally identifiable diagnostic data including device model, OS version, app version, stack traces, and device memory state at the moment of crash.
- Privacy Safeguard: Does not collect personal identity, hardware identifiers (IMEI/MAC), file contents, or specific filenames.
Google Firebase Analytics (Aggregated Product Analytics)
- Purpose: Gauging general app active metrics and aggregate feature interactions (such as the popularity of different renaming modes) to guide performance and UI optimizations.
- Data Collected: Anonymous Firebase instance identifiers, standard technical device attributes (language, screen resolution, OS version), and aggregated in-app interaction events.
- Privacy Safeguard: Strictly prohibited from capturing users' specific text replacement patterns, regular expressions, file names, file paths, or personal identifiers.
Google Firebase Remote Config (Dynamic App Configuration)
- Purpose: Retrieving up-to-date configuration flags, policy update announcements, and curated app showcase items without requiring repeated app rebuilds.
- Data Interaction: Synchronizes standard read-only configuration keys from Firebase servers upon launch. No personal or storage data is transmitted.
All Google Firebase services operate under the Google Privacy Policy.
4. Contact Us
If you have any questions or suggestions regarding this Privacy Policy, please contact the developer at: KTLShu@163.com.