WristSnap Privacy Policy and Service Agreement
Last Updated: June 2026
Welcome to WristSnap! This center aims to transparently explain how this application handles your device information, personal data, and compliance policies regarding high system permissions (such as Accessibility Services), third-party advertising SDKs, and User-Generated Content (UGC).
1. Prominent Disclosure and Usage of AccessibilityService API
WristSnap's core function is to serve as a remote operation control tool for smartphone camera apps using Amazfit smartwatches, and a local automation execution tool for smartphone camera applications. To achieve cross-device automated control, this application requires the use of the Android system's AccessibilityService API.
Specific Purposes:
- Remote Shooting Control: Receive and execute commands from your paired Amazfit smartwatch (Zepp OS device) to simulate clicking the shutter in your phone's camera interface.
- Real-time View: Capture the current screen content and transmit it to the smartwatch for composition preview.
- Photo Preview: To confirm the shooting result, the app captures a screenshot of the camera app's interface showing the last photo taken and transmits it back to your smartwatch via local network/Bluetooth channels.
- Automated Instructions: Record and play back your personal tap and drag actions on your phone screen for adjusting camera configurations (including camera shutter, photo playback configuration, recording drivers, and training preset instructions).
- UI State Recognition: During the process of recording drivers and training preset instructions, the system will perform visual analysis on screenshots (including text recognition and icon object recognition) to accurately identify the state of UI elements in the camera interface (such as parameter panels and parameter values), ensuring the accurate execution of automated instructions.
Permissions and Privacy Commitments:
- The use of this permission is strictly limited to the shooting or automation scenarios you actively configure.
- Your screen content and real-time visuals only flow locally and between your actively configured and connected Amazfit smartwatch devices.
- Visual analysis (including text and icon object recognition) is processed exclusively locally on the device, and you are required to cover the camera before recognition. We will never upload any of your screen visuals, photos, or content without your permission to any external cloud servers.
- We will absolutely not use the accessibility service to record your non-essential operations in the background.
Custom App Risk Warning: WristSnap allows you to customize the target "camera app." If you actively set a non-camera app (such as social software, browsers, etc.) as the target app, the smartwatch will also receive and display the screen of that app. Please use this custom feature in a safe and private environment.
2. Cloud Services and Data Processing
This application introduces cloud backup and community sharing features, and data processing strictly follows the principles of lightweight design and maximum privacy:
- Account-less Authentication Mechanism: We do not collect traditional identity information such as your real name, phone number, or email address. The app uses account-less authentication via local Ed25519 key pair technology, generating a public-private key pair locally on your device for identity verification.
- Nickname and Environment Fingerprint: To use the cloud market and configuration backup features, you must set a "user nickname" locally upon your first use. Meanwhile, to prevent configuration misalignments caused by device fragmentation, the system will record an environment fingerprint (including: target camera app package name, system language, phone model, and screen resolution) when you actively upload data.
- Cloud Asset Management: When you backup your recorded "Camera Drivers" or "Preset Instructions", their status is set to [🔒 Private Backup]. At this time, the data is for your personal use only to restore across devices using your key credentials. Only when you actively enable [🌐 Publish to Public Market], will this configuration data be publicly shared for other users with the same phone environment.
- Data Transmission Security: All uploading, restoring, and downloading of cloud data are transmitted through standard HTTPS encrypted channels to ensure data security during transmission.
- Community Governance and UGC Moderation Data: To maintain a safe and pure community environment, the system automatically reviews text uploaded to the public market (such as nicknames, driver, and preset descriptions) for sensitive content. Content that fails the review cannot be uploaded. Additionally, the app provides "Report Resource" and "Block User" functions. When you trigger these functions, the system only records necessary public key instructions to execute content isolation and takedown logic. For specific user conduct guidelines, please refer to the "WristSnap Cloud Community Guidelines & UGC Agreement" in the appendix.
3. Local Diagnostic Logs and Configuration Data Handling
- Local Diagnostic Logs: To facilitate troubleshooting cross-device connection and execution issues, the system records necessary diagnostic information locally (including: phone model, OS version, App version, target package and component names, and local HTTP request interaction records). These logs are strictly stored locally on your device and absolutely do not contain your personally identifiable information or sensitive privacy.
- Local Configuration Backup: To maintain the user experience of the legacy version (V1), your V1 version shortcut instructions (macros) are saved by default in your device's local storage .
- Controlled Data Export: The aforementioned diagnostic logs and local V1 version configuration files will only generate external files through the Android system's native standard file sharing mechanism (Share Intent) after you actively trigger them (e.g., enabling debug mode and tapping "Export Logs," or tapping "Local Export Backup"). We promise that the app will never automatically package or stealthily upload this local diagnostic and configuration data in the background.
4. Third-Party Advertising SDK and Advertising ID
To maintain the app's daily operations and cloud server expenses, this application integrates the Google AdMob advertising service network.
- Use of Advertising ID: The Google AdMob SDK may collect and use your device's Advertising ID and some non-personally identifiable device information (such as device model, network status, etc.) to provide personalized ad displays, control ad frequency, and analyze ad performance.
- Control and Opt-out: You can reset your Advertising ID or opt-out of personalized ads at any time via Android system settings (e.g., "Settings" > "Privacy" > "Ads"). For users in specific regions like the EU, the app integrates UMP privacy settings. We will strictly comply with GDPR regulations to obtain your explicit consent via pop-ups, allowing you to independently choose to accept or decline.
- PRO In-App Purchase Ad-Free Privilege: This application offers a "PRO Version" in-app purchase service. Once upgraded to a PRO user, the app will completely remove all ad displays. We promise that for devices with an activated PRO status, we will block the data tracking logic of the advertising SDK, and your Advertising ID will no longer be used for any advertising purposes.
5. User Data Control and Complete Deletion
We respect and guarantee your absolute right to control your own data:
- One-Click Toggle and Deletion: In your "My Cloud" asset list, you can toggle uploaded resources between "Public" and "Private" statuses at any time, and you can delete cloud asset data.
- Complete Account Deletion and Clearing: This application provides a prominent red [Delete and Clear All My Cloud Data] function on the "My Cloud" page. Once you actively trigger this action, the system will immediately and irreversibly delete your public key, nickname, all interaction/like records, and all private and public configuration presets you have uploaded from our cloud database.
6. Contact Us
If you have any questions regarding this privacy policy or the app's data compliance, please contact the developer via: Email: hermes.sun@gmail.com
Appendix: WristSnap Cloud Community Guidelines & UGC (User-Generated Content) Agreement
Notice: When you use the cloud services in the app for the first time, you must read and agree to this agreement before generating cloud identity credentials.
1. Content Ownership and Visibility
Your ownership of the "Camera Drivers" and "Preset Instructions" recorded using this app belongs solely to you. When you choose to "Publish to Public Market," it indicates your consent to publicly share this configuration item for other community users with the same phone environment to download and use for free.
2. User Conduct and UGC Content Guidelines
When setting a user nickname and describing custom preset configurations, you must comply with local laws, regulations, and community consensus. Publishing content with the following characteristics is strictly prohibited:
- Content containing pornography, vulgarity, violence, gore, or disturbing explicit material;
- Statements or nicknames promoting hate, discrimination, personal attacks, insults, or harassment;
- Any content infringing on others' intellectual property rights (e.g., stealing someone else's original macro and claiming it as your own) or invading others' privacy;
- Forged configuration files containing malicious fraud, phishing, viruses, or destructive scripts;
- Configuration files where descriptions severely mismatch the actual content;
- Any other content violating Google Play Developer Policies.
3. Pre-Content Review and Sensitive Word Filtering Mechanism
To prevent the spread of violating content from the source, the app has a built-in pre-content review mechanism. When you create/modify your user nickname or upload resource names and descriptions, the system automatically checks for sensitive words and violating text. For content containing political, pornographic, violent, abusive, or other violating words, the system will automatically block and refuse the upload.
4. Real-time Reporting and User Blocking Mechanism
To ensure the safety and purity of the community, the app provides content governance tools for all users:
- Real-time Reporting of Resources: If you find any violating names, descriptions, or abnormal presets in the public market, you can tap the [Report] button next to the resource item at any time. When a public content item receives violation reports from multiple different users reaching a system-set threshold, the system will automatically trigger a protection mechanism to temporarily hide or remove it from the public market. Meanwhile, the developer will also manually review and finalize the violation resolution for the received report list.
- Block/Mute Authors: If you do not wish to see content published by a specific user, you can use the [Block this Author] function. Once blocked, all past and future resources uploaded by this author will immediately become invisible to you and be completely isolated from your public market list.
- Credential Ban: For users who maliciously publish violating content, manipulate likes, or attempt to compromise the cloud API, the platform reserves the right to ban their local Ed25519 public key credentials, permanently terminating their access to the cloud market.
5. Disclaimer
Preset instructions in the community market are voluntarily recorded and uploaded by users. Limited by the intelligence of user-uploaded resources, system version upgrades of various phone manufacturers, and minor tweaks to underlying interfaces, we cannot guarantee that all public instructions will run 100% perfectly on your specific device. Please assess the risks yourself before downloading and executing.