Privacy Policy
Effective August 17, 2026 · Version 3
Caper (“we,” “us,” or “our”) respects your privacy. This policy explains how the Caper mobile application handles information when you capture, edit, organize, and export media, use Caper Pro, or choose notification services.
1. Consent and permissions
Before you agree to this policy, Caper does not initialize third-party SDKs, make network requests, or request access to the camera, microphone, Photos, or notifications. Agreeing to this policy does not grant a system permission or automatically enable the optional Umeng service. When a feature needs access, Caper explains why and iOS presents its own permission prompt.
2. Photos, videos, and audio
Caper uses the camera for framing and capture only after you grant permission. It uses the microphone only after permission is granted and only to record sound with video; microphone access is not required to take photos. Photos, videos, edits, thumbnails, and the private in-app library are processed and stored locally whenever possible. Caper accesses items from Photos only when you choose to import them and writes items to Photos only when you choose to export them.
We do not upload the content of your photos, videos, or audio to our servers.
3. Purchases
Purchases are processed by Apple through StoreKit. We do not receive your payment-card details. To validate purchases and provide Caper Pro access, Caper may process signed transaction information, product identifiers, transaction identifiers, the App Store environment, and an app account token. We use this information only to verify purchases, restore access, prevent fraud, and provide support.
4. Technical and local notification records
After you agree to this policy and use a feature that requires networking, the relevant service may process limited technical records, such as request timestamps, request identifiers, IP address, response status, app version, and security events, for reliability, fraud prevention, and troubleshooting. Caper stores your Umeng enablement choice on the device and retains up to 100 processed notification message identifiers for deduplication. These local records are removed when you uninstall the App or clear its data. Records under our control are retained only for as long as reasonably necessary for these purposes or to comply with law.
5. Notifications and third-party push services
After you agree to this policy, Caper requests iOS notification permission and registers with Apple Push Notification service (APNs) only when you actively choose System Notifications. This choice is independent of the optional Umeng service. Declining notifications does not affect capture, editing, purchases, or the local library.
Umeng U-Push is an optional third-party delivery service. Its bundled runtime remains unloaded and does not connect to Umeng by default. Caper loads it only after you review its data use in Settings, actively continue, and choose Allow in the iOS App Tracking Transparency prompt. Choosing Ask App Not to Track, restriction, or denial leaves Umeng unloaded. Capture, editing, purchases, the local library, and the ability to request system-notification permission and register with APNs remain available.
This release has no first-party remote-notification sender. Before Umeng has ever been enabled for this installation, notification permission or an APNs token may exist, but Caper has no remote-notification sending path under its control. If you enabled Umeng and later turn it off, Caper stops proactively calling the Umeng SDK to submit new APNs tokens and notification events. Turning it off does not automatically unregister a previously registered APNs token or delete data already held by Umeng.
When enabled, the Umeng Push SDK may process the APNs device token; IDFA (only when iOS allows tracking), IDFV, OpenUDID, GUID, and SDK-generated device identifiers; device model, operating-system, app, and SDK versions; IP address and network-connection status; notification-delivery and interaction records; and the complete remote-notification payload received by the App, including its title, body, and custom fields supplied by the sender. This information is used to establish the push mapping, deliver messages, measure delivery and interaction status, maintain service security, and troubleshoot failures. Caper does not intentionally add your photos, videos, audio, contacts, precise location, or payment-card details to that payload.
Before initializing Umeng, Caper disables Umeng analytics, entry collection, Apple Search Ads token collection, and SKAdNetwork attribution, and it does not request location permission for this service.
You can turn off Umeng in Settings > Notifications > Optional Umeng Data Use. Revoking iOS tracking permission also prevents Caper from proactively calling the Umeng SDK to submit new APNs tokens and notification events. Disabling system-notification permission controls iOS notification display and later registration; it does not by itself turn off Umeng. If the SDK is already loaded, it remains resident until the App exits. Caper stops those proactive submissions but cannot promise that the SDK’s own internal connections end immediately. After you close and reopen the App, the SDK stays unloaded while Umeng is off or tracking is not allowed.
The Umeng Push SDK is operated by Umeng Tongxin (Beijing) Technology Co., Ltd.; the unified Umeng+ Privacy Policy also identifies Beijing Ruixun Lingtong Technology Co., Ltd. as an Umeng+ operator. Retention, deletion, and rights requests for Umeng-held data follow that policy. You may contact Umeng at [email protected] or 4009901848 (subject to Umeng’s latest official notice), or ask us to help contact the provider.
6. Tracking and advertising
Caper does not sell personal information or display behaviorally targeted advertising in the app. Umeng’s bundled privacy manifest nevertheless declares collection of Advertising Data that is not linked to identity, is used for Third-Party Advertising, and is used for tracking. Caper therefore asks for tracking permission before loading Umeng.
7. Sharing
We may provide necessary information to Apple for the App Store, APNs, and purchases; provide the push and advertising data described above to Umeng and its necessary service providers only after you allow tracking and enable the optional service; provide information when required by law; or provide limited information as part of a corporate transaction subject to appropriate safeguards.
8. Retention, deletion, and your choices
On-device media remains until you delete it, uninstall Caper, or remove it through device storage controls. You can turn off Umeng in App Settings or disable tracking permission in iOS Settings to block Caper’s later proactive submissions of new APNs tokens and notification events; disabling notification permission only affects iOS notification display and later registration. After Umeng is stopped or tracking is disabled, Caper does not load the Umeng runtime on later launches. Purchase and security records are retained only as needed to provide entitlements, meet legal obligations, resolve disputes, and prevent fraud. To request access to, correction, a copy, or deletion of information under our control, withdraw a related choice, submit a complaint, or ask us to help contact a provider, email us and provide enough information to locate the relevant record.
9. Children
Caper is not directed to children below the age required for independent consent in their jurisdiction, and we do not knowingly collect personal information from children. Minors should review this policy and use Caper with guidance from a parent or guardian.
10. Security and international processing
We use reasonable administrative, technical, and organizational safeguards. Caper configures the Umeng runtime for mainland-China rather than overseas service routing, but that setting alone does not determine every final processing or storage location. As of this policy’s effective date, the Umeng+ Privacy Policy states that personal information collected and generated while serving developers in mainland China is stored in China; when the service is used outside mainland China, relevant data may be transferred to Singapore or Germany. Actual locations, cross-border scenarios, and safeguards follow Umeng’s then-current policy and the region where the service is used. You can review that policy before deciding whether to enable Umeng.
11. Changes
We may update this policy. We will publish the updated policy here, change the effective date and version, and provide any additional notice required by law. If the purposes, information categories, or third-party services change materially, Caper will request consent again when required.
12. Contact
Questions or privacy requests: [email protected]. Please identify the request and provide enough information to locate the relevant record; do not send private media, passwords, or full transaction receipts. After reasonably verifying identity, we will handle the request within the period required by applicable law.