Privacy Policy

1. Controller and contact details

The personal information controller for SnipCC is Zhao Shikuan (individual developer), responsible for the SnipCC app, account and membership authorization services, and support materials received by the developer. Contact 260244206@qq.com for privacy, access, correction, deletion and account requests. Official website: https://snipcc.com. This policy takes effect on October 6, 2026.

This policy explains how SnipCC processes information to provide its features. Third-party transaction platforms, payment providers and your selected cloud services process information within their own services. Their rules do not replace the developer's responsibilities for SnipCC's own processing.

2. Local content and processing

Screenshots, annotations, OCR and translation results, AI conversations and history are stored locally according to the app's features. Directories and files depend on the feature and your settings. Local storage does not mean that all files, images and databases are encrypted.

Local OCR and translation run on your device. Model downloads and updates require a network connection, and download servers may receive network and version information. Downloading a model is different from uploading images or text for recognition.

Local OCR traces record operational information such as request IDs, times, models, stages, durations and errors. They do not record image content, recognized text or translated text. Recording a local log does not automatically upload it as feedback.

3. Account and device information

Account features send your email address, verification codes, password verification requests and voluntarily supplied profile information to the SnipCC account service for registration, sign-in, identity verification and profile management. Optional avatar uploads send the selected image to that service.

Membership activation, device registration and authorization process codes, account and membership status, installation identifiers, device names, operating systems and app versions. The developer operates account and membership services at https://tool.kitio.cn:88/api. Online services also receive request information necessary for network communication.

Client sign-in tokens and third-party API keys use secure storage supported by the operating system. Necessary authentication information is still sent to the configured service when you use it. Secure storage does not mean that keys never participate in network requests.

4. Payments, codes and orders

When purchasing, the client sends the selected product, quantity, payment channel and contact email to wzyp.cn and queries payment and code delivery status. The platform and payment providers process transaction information under their services. Check the provider and order amount before paying.

Pending order details, including email, order number, plan, amount, payment link and code, are kept in local secure storage for recovery and order lookup. Agreement confirmation version, time, purpose, necessary plan, amount and order identifiers are stored in local configuration; account identifiers separate records in digest form. These are client confirmation records, not proof of upload or server retention. Order records are not payment account passwords; this client order interface does not require Alipay or WeChat Pay passwords.

When the website embeds the code shop or opens shop and payment pages, those third-party pages receive the corresponding access requests and may use cookies or other web technologies under their policies. Their policies do not replace the developer's responsibilities for this app's data processing.

5. Cloud AI, OCR and translation

When you select a cloud feature and send a request, relevant input text, conversation context, images or attachments and necessary authentication information may be sent to the selected service to fulfill it. Recipients depend on the actual service address and configuration, including services you configure yourself.

Check content and recipients before sending; do not submit others' information without authority. Cloud recipients' retention, use and deletion rules are described by their services. We cannot promise that every provider stores no content or excludes it from model training.

Accepting the account agreement does not replace separate notices or consent that may be required for specific third-party sharing, sensitive information or cross-border processing. Mechanisms must comply with the selected service and applicable law. You can stop cloud requests, disable services or remove credentials. Requests concerning information already sent must follow the recipient's rules.

6. Error reports and refund requests

When you choose to send an error report, the client submits the error identifier, summary, version, operating system and processed diagnostic information shown in the preview for troubleshooting. Voluntary feedback is not described as automatic collection of all usage content.

Refund requests are handled by email. The developer receives the email, order number, payment screenshots, issue description, Alipay receiving account and necessary recipient verification information you provide, for verification, refunds and dispute handling. Redact unrelated information. Do not submit payment passwords, SMS codes or ID photos.

Support emails and manual refund records involve processing outside the app. Refund information is used only for the relevant support request and necessary verification, not advertising. Alipay and related services process transaction information when a transfer is made.

7. Retention, deletion and your rights

Local content remains on your device. Retention depends on features, directories and your cleanup actions. Use the available history management, configuration editing or file management features to manage it. Check and back up content you want to keep before deletion.

Account information is retained while account services are provided. Membership, redemption and device records are retained as needed to provide and verify benefits. Support and refund materials are retained as needed for verification, transfers and necessary disputes. Retention depends on ongoing services, pending orders or disputes and legal requirements. When the purpose is complete and continued retention is not legally required, personal information is deleted or anonymized. Legally retained information is used only for that retention purpose.

Email requests for access, correction, copying, deletion, withdrawal of consent or account closure, specifying the scope. After necessary identity verification, the developer will handle the request under applicable law or explain why it cannot be completed immediately. Account closure is requested by email; signing out does not close an account. Withdrawing consent does not affect lawful processing based on valid consent before withdrawal.

Signing out, deleting cloud device records and uninstalling do not delete all account, order, external-directory or third-party records. Contact the relevant provider about information held by third-party services.

8. Policy updates and minors

When features or the purposes, methods, information categories or recipients change, the policy will be updated and necessary notices provided. Where renewed consent is required, it will be obtained. Updating the policy alone does not expand existing authorization.

The app has no child-specific service. Minors should use it under guardian guidance. Children under 14 should not independently register accounts or submit personal information. Guardians may email to request verification and deletion of information submitted without consent; the developer will handle requests under applicable law.