翻谱器隐私政策

English privacy policy

Updated and effective: October 4, 2026

FanPuQi reads photo and PDF scores and supports touch-based and hands-free head-tilt page turning. This policy explains the data the app processes, its purposes, storage, retention, sharing and deletion, and your choices. The face-data practices below describe version 1.0 and distinguish build 2 from build 3.

1. Camera, TrueDepth/ARKit and face data

1.1 Data processed

The app requests Camera permission when you enter the score reader or calibration feature. With your permission, it uses Apple ARKit face tracking (ARFaceTrackingConfiguration, a TrueDepth-related API) on supported devices. Otherwise, it uses Apple Vision to estimate head pose from the front camera.

The app processes camera frames, face-tracking visibility and the face position and orientation relative to the camera on the device. It derives head angles (roll, pitch and yaw) and uses timestamps to measure how long a head tilt is held. The live camera preview helps you position yourself and keep your face in view.

In version 1.0 build 2, the ARKit adapter read four expression coefficients: left-eye blink (eyeBlinkLeft), right-eye blink (eyeBlinkRight), inner-brow raise (browInnerUp) and tongue out (tongueOut). These were included in the in-memory pose result but were not used for page turning, diagnostic files or transmission. Version 1.0 build 3 removes these four reads. It does not access ARKit expression coefficients and extracts only the head pose and tracking state needed for score page turning.

1.2 Purposes and sharing

Head angles, face visibility and timing are used for head-tilt page turning, neutral-position calibration, tracking feedback and user-enabled local diagnostics. Version 1.0 supports only head-tilt gesture page turning; build 3 does not read expression coefficients.

The app does not use face data to identify individuals, create facial identity profiles, or perform advertising, marketing, profiling, use-based data mining or model training. The app does not automatically upload, disclose or share camera frames, face-tracking data, expression coefficients or diagnostic records with the developer or third parties. ARKit and Vision are Apple on-device system frameworks used by the app; the app does not send face data to a developer-operated cloud service for processing.

1.3 Storage and retention of real-time data

Camera frames and the current face-tracking result are processed in device memory. Build 2 expression coefficients were also processed only in memory; build 3 does not read them. The app does not save camera images or video, complete face-transform matrices, face meshes or expression coefficients to files. Stopping tracking stops camera tracking and clears the app's current pose and preview references. Related memory is released when objects are released or the app process ends; stopping tracking does not imply that every memory buffer is immediately securely erased.

1.4 Optional local diagnostics: storage, retention and deletion

Diagnostic recording is disabled by default. Only after you tap the recording control in the calibration page's advanced diagnostics does the app record relative timestamps, head angles (roll, pitch and yaw) and face visibility in memory. Tapping Stop saves a CSV in the app's local Documents directory so you can investigate tracking or angle issues and adjust page-turning sensitivity.

The diagnostic CSV contains only relative timestamps, three head angles and face visibility. It contains no camera images, video, expression coefficients, face meshes, complete face-transform matrices or identity templates. Without manual diagnostic recording, the app does not write these CSV files. The app has no automatic upload or automatic sharing feature for diagnostic files.

Saved diagnostic CSVs have no automatic expiry or scheduled deletion. They remain in the local app container until its data is deleted. Tapping Stop does not delete files already saved. Diagnostic samples may also remain in memory until a new recording clears them, the recording object is released, or the app process ends. Section 4 explains deleting local data and managing backups.

2. Photo and PDF scores

Photo permission allows the app to read albums, images and related information within the scope you authorize, to display covers, thumbnails and score pages. The app does not modify or delete system photos or upload your photo-library content to the developer.

The app accesses only PDFs you select through the system file picker and renders them on the device. File names and access bookmarks are stored locally so you can reopen the files. The app does not upload the PDFs to the developer.

iCloud Photos and cloud file providers, such as iCloud Drive, may need a network connection to retrieve content you select. Those services manage their own cloud storage and transmission under their respective policies.

3. Local settings, accounts, tracking and system backups

Page-turning sensitivity and calibration angles are stored in local preferences to apply your posture and choices. These settings remain until you change them or delete the local app data; they contain no photos, video or facial identity templates. No account or login is required. The app has no developer-operated user-data backend and no integrated third-party advertising, analytics or tracking SDK.

The app does not proactively transmit your scores, head-movement records or usage behavior to the developer. System backups and system diagnostic sharing may operate according to your Apple settings. Local app data may be included in system backups you enable. This policy does not replace Apple's policies; backup copies must be managed separately through the relevant Apple settings.

4. Your choices, permission withdrawal and deletion

You can revoke the app's Camera permission or change or revoke photo access in system Settings. After Camera permission is revoked, the app cannot continue camera tracking using that permission. Touch-based page turning remains available. Opening PDFs does not require photo permission.

Removing a PDF entry in the app deletes its local access bookmark, not the original file. Selecting Delete App removes the local app container, including settings, bookmarks and diagnostic CSVs. Offload App, which preserves documents and data, does not have the same deletion effect. Deleting the app does not delete your photo library or original PDFs.

Deleting local app data does not automatically delete existing system or cloud backups. If you enabled backups, manage or delete backup copies through Apple or the relevant file provider's settings. The app has no automatically uploaded face-data database for the developer to delete remotely.

5. Contacting support voluntarily

If you email the developer, we receive the email address, text and attachments you choose to send and use them only to understand, handle and reply to your request. The app does not automatically attach or send face data, camera frames or diagnostic CSVs. Please avoid sending private photos, scores or diagnostic records unrelated to your request. You can request deletion of support materials you provided by contacting the same email address.

6. Use by minors

The app does not require minors to provide their name, an account or contact details. A parent or guardian should help decide whether to grant photo or Camera access or send material to support.

7. Policy updates and contact

This policy describes the current version's data practices. If a future version changes the purposes, scope, sharing or storage of face data, we will update this policy and the corresponding App Store privacy information when that feature is released, and obtain permission as applicable. The date at the top identifies the latest update.

Contact: Liang Sili
Email: 178272907@qq.com
Technical support