Privacy policy
How FanEye handles camera video, local replay transfers, online room state, service activity counts, subscriptions, logs, permissions and deletion.
Originally effective: 5 August 2026 · Revision effective: 11 September 2026.
1. Scope
This policy explains how the FanEye iOS app and its online services handle information. FanEye currently does not require account registration.
2. Camera, Video and Photos
FanEye uses the camera for live framing, challenges, and replay. Video is temporarily cached and processed on each phone and is not uploaded to FanEye servers. Only when you choose to save a clip will the app, with permission, write the generated video to Photos. You manage or delete saved clips in the Photos app.
3. Professional Local Connection
Professional local connection uses Bonjour and the local network to discover phones on the same LAN and exchange temporary device identifiers, roles, connection state, and commands such as start, pause, resume, challenge, replay, and return. Video stays on each phone by default. When using a dedicated controller, a camera's replay is temporarily sent to the controller over the current LAN only when you select that camera, for viewing in that court session. It is not uploaded to FanEye cloud servers.
4. Pro Online Sync
When creating or joining a Pro online court, the app sends or receives temporary court codes, phone names, a randomly generated persistent app-instance identifier stored on the device, temporary participant identifiers used for room sessions, roles, room count and control state, and control commands such as start, challenge, replay, acknowledgement, and return. The server processes connection IP addresses as connection metadata only for rate limiting, security, and abuse prevention. This information is used to provide and protect multi-phone synchronization and does not include video content.
4.1 Service Activity Counts
To observe synchronization service operation, the health endpoint provides retained-room, active-room and online-participant counts, plus room creation and last-activity times rounded to the minute. This summary does not expose court codes, phone names, IP addresses or video. It does not count single-phone or LAN-only use; the participant count is not a deduplicated count of physical phones.
5. Subscriptions and Apple Transaction Verification
Purchases, restores, and entitlement checks for Pro and Professional are handled by Apple StoreKit and the App Store. FanEye does not receive your Apple account password or payment-card information. After StoreKit verifies a transaction, the app sends the product identifier, transaction identifier, original transaction identifier, Apple environment, and the verified Transaction's signed JWS to FanEye servers when a paid host creates an online court. The server uses this information to verify subscription status with Apple. The JWS body is used only for entitlement verification and is not written to app or service logs. Participating camera phones do not need to purchase and do not submit their own subscription entitlements.
6. On-device Performance Samples
To help the app record replay operation on the device, FanEye stores a limited set of recent performance samples and the current capture mode locally. These may include time, thermal and battery state, segment success or failure counts, segment and replay-preparation timing, frame rate, and resolution. These data and the capture mode remain in the app's on-device settings, contain no video content, and are not uploaded to FanEye servers. They are removed when app data is cleared, such as when the app is deleted.
7. Information We Do Not Process
FanEye currently requires no FanEye account and does not collect your phone number, contact email, contacts, GPS or precise location. It contains no third-party advertising SDK and does not use information to track you across apps or websites. Information you voluntarily email to support is used only to handle your support request.
8. Retention, Deletion and Security
On-device challenge cache is overwritten as recording continues or removed when app data is cleared. Online temporary rooms are cleared after they end, and inactive rooms are automatically deleted after no more than about three hours. Standard access logs on the Guangzhou and Hong Kong services record connection IP, request method, full path and query string, status, transferred size, and User-Agent; a court code or temporary participant identifier may therefore appear in a request query string. These logs are used for operations, troubleshooting, security, and abuse prevention, not advertising, and do not record request bodies, Authorization headers, or Apple signed JWS data. Access and error logs rotate daily, retain 14 rotations, and are compressed. Service journals use the system-default size-based rotation, so the current configuration cannot be converted into a fixed number of retention days. Apple entitlement-observation logs record only outcome, error code, entitlement tier when granted, and latency, not JWS bodies. Network data in transit is protected with HTTPS or WSS.
9. Permissions and Choices
You can manage Camera, Local Network, and Photos permissions in iOS Settings. Disabling a permission will make camera capture, local multi-phone connection, or saving clips unavailable. FanEye has no account, so there is no account-deletion process. You can clear court-line settings in the app. Deleting the app clears FanEye settings, the persistent app-instance identifier, and recent performance samples stored on the device; saved clips in Photos must be deleted separately in the Photos app. You can also cancel auto-renewal through Apple subscription management.
10. Changes to This Policy
If FanEye materially changes its data practices, we will update this page and its effective date and, where appropriate, notify users through the app or store listing.
11. Contact Us
If you have questions about this privacy policy, contact us at: