epolar Privacy Policy
Scope: This Privacy Policy applies to the epolar apps for iOS/iPadOS, Android and HarmonyOS, and our website. Zhang Fengfeng (张峰峰) is responsible for processing your personal information. For privacy questions, contact support@epolar.cn. Common practices are explained below, followed by platform-specific permissions, beauty effects and payment services.
Your photos and videos are processed on your device and are not uploaded to epolar's servers. Signatures stay on your device by default; selected signatures are uploaded only when you enable cloud sync. The Android beauty component also sends performance and usage statistics, as explained in the MediaPipe section. This Policy describes features available in different app versions. Updating this Policy does not activate data processing for a feature your version does not provide. Optional features request permissions or consent when you choose to use them.
1. Information we process and why
- Photos, videos and editing on your device
- Camera images, selected photos and their file metadata are used locally for previews, filters, composition, frames, signature rendering, Live Photos and saving. Import uses the system picker to access the files you select; it does not scan other photos. An original file may contain capture dates or location metadata. Reading that file does not mean the app requests your device location. epolar does not upload this media, photo indexes or facial landmarks to its servers, or use them for advertising or model training. System photo backups and recipients you choose to share with handle content separately under your system settings and their own rules.
- Optional accounts, verification codes and sign-in
- We process the mainland China mobile number or email address you enter, verification requests and verification results to register or sign you in, link sign-in methods and verify sensitive actions. The server creates an account ID and stores the account creation time, the version of the terms you accepted and verification times. Sign-in identifiers are encrypted; keyed hashes support matching, and masked values support display. Verification codes are not stored in plain text. Email matching ignores letter case but does not merge plus-address aliases or remove dots. The app does not read your text messages, device phone number or email content. The server stores session-credential hashes, expiry times and necessary verification times, while the device securely stores sign-in details. Purchase credentials cannot replace account credentials.
- Pro access and purchase ownership
- Account IDs, access sources and status, purchase links, and refund or revocation records are used to verify access, prevent duplicate assignment and check valid access for the same account across platforms. Sharing account access does not sync photos or signature libraries. Payment-related processing is explained under Third-party services.
- Voluntary support payments and verification
- Only when you use this feature, the device creates and stores a random credential for checking payments and the pending order details it needs. The server stores an ownership identifier derived from that credential using a keyed hash, along with a request ID, platform, support order number, amount, currency, creation time, payment-provider transaction number, and payment and refund verification status. These records are used to create orders, confirm receipt of funds, prevent duplicate charges and resolve payment problems or disputes. The credential is not a hardware identifier and is not used for sign-in or advertising tracking. Support orders are not linked to your epolar account and do not include your phone number, email, photos or signatures. These records can be linked to a transaction and are de-identified, not fully anonymous. The current page checks the pending payment; it does not provide a support-payment history or cross-device restoration. Alipay, WeChat OpenSDK and WeChat Pay are described under Third-party services.
- Optional signature cloud sync
- Sync is available only after verified sign-in, with valid account-based Pro access, and when you explicitly enable it. It processes the signatures you select, including strokes, names, ink colors, pen widths, dimensions, placement settings and applicable transparent previews, plus signature IDs, versions, deletion markers and update times. Signature content is encrypted in a private application database. Photos, videos and photo indexes are not uploaded. Libraries are separated by account and platform: iOS/iPadOS, Android and HarmonyOS have three separate libraries that do not currently sync with one another. Signing in does not automatically upload or link local-only signatures. Enabling sync for the first time or requesting a sync retrieves cloud changes. With sync enabled, additions, edits and deletions are saved locally before background submission. Turning sync off does not delete existing local or cloud copies. Free-access promotions do not include cloud sync.
- Language and local preferences
- Versions with language settings let you follow the system language or choose Chinese or English in the app. Your choice is stored locally. The system language helps select the interface language, and the device region suggests phone or email sign-in; you can change the suggested method. Device region is not GPS location and does not establish your nationality or actual location. Changing language does not create an account, change purchase ownership or automatically upload photos or signatures.
- Film catalog and asset downloads
- The app requests and caches film pack identifiers, visibility, versions, checksums and previews. It fetches high-resolution files when you select a missing asset or choose to download it. Pro assets also require account verification or a valid iOS guest purchase. Buying Pro does not download all assets. Resource services receive the IP address, request time, path, status and temporary download credentials needed to serve files, but not your photos, signatures or composition settings. HarmonyOS currently primarily uses bundled assets. Versions without downloads do not upload or download your content merely because this Policy mentions the feature.
- Suggestions, feedback and support
- We process the category and text you submit, the submission time and a request ID that prevents duplicate submissions. Feedback text is encrypted and accessible only to authorized administrators. Photos, signatures and diagnostic logs are not attached automatically. In-app replies are not currently available. Current iOS and HarmonyOS feedback uses an anonymous endpoint without sign-in or purchase credentials; a keyed IP-address hash is used for temporary rate limiting. Android feedback currently requires sign-in and is linked to your account ID; it is deleted when that account is deleted. Anonymous feedback is not automatically removed by account deletion. Contact support with the submission time and a summary to request its deletion. If you email us, we process the address, message and necessary attachments you provide. Please do not send passwords, verification codes or unrelated personal information.
- Network access and security
- Catalog, sign-in, verification, feedback and sync requests include necessary feature parameters, platform, build number and distribution channel. Connections produce records such as IP addresses, request paths, times and response status, used to deliver services, limit excessive requests, protect security and troubleshoot problems. Verification codes, passwords, session credentials and purchase credentials are not recorded as ordinary log content. Hashing and de-identification do not make data fully anonymous. We do not currently integrate advertising or cross-app tracking SDKs, or request access to contacts, device location, SMS messages or phone-call status. Statistics from the Android beauty component are described below.
We process information to provide the services you request, on the basis of valid consent where required, and to meet applicable legal obligations. Where separate consent is required, reading or accepting this Policy does not replace it. Declining optional sign-in, signature sync, beauty effects or their permissions does not affect unrelated free features.
2. iOS/iPadOS: on-device processing and permissions
- Camera: Requested when you enter camera mode, for previewing and taking photos. You can still import through the system photo picker if you decline.
- Microphone: Requested only when you enable Live Photos with sound, to record a short period of audio around the shutter press. If you decline, you can still take silent Live Photos and ordinary photos. Temporary video and audio are processed locally. The corresponding recording stops when you turn Live Photos off or leave the camera screen.
- Selecting and saving photos: The system picker provides only the content you select; importing does not require full photo-library access. Manual saving, or Auto-Save that you explicitly enable, creates new photos using system photo-library permissions.
- In-app Library: Versions offering this feature separately request photo read/write access when you open the Library. You can grant access to selected photos only. The app uses system photo identifiers in its local index to load epolar photos and thumbnails in pages, without scanning other photos. Declining affects in-app browsing, not importing through the system picker. Saving follows the system's add-photo permission. Deleting a photo, after system confirmation, deletes the corresponding photo from the system library. epolar does not keep a separate photo backup.
- Beauty effects: Apple Vision and Core Image locate faces and facial landmarks on your device for smoothing, brightening and face-shaping effects. epolar does not identify people, create facial profiles or upload images or landmarks.
- Secure storage: Sign-in credentials and iOS purchase-access credentials use system secure storage. Purchase-access credentials verify access and permit asset downloads; they cannot sign you in to an epolar account.
You can manage or revoke permissions in iOS/iPadOS Settings. Declining a permission affects only features that depend on it. iCloud Photos and system backups follow your system settings and Apple's rules; they are not photo cloud sync provided by epolar.
3. Android: on-device processing and permissions
- Camera and network: Camera access is used for previewing and taking photos. Network access supports online features you use and connection-status checks. Declining camera access does not prevent importing through the system picker.
- Orientation sensor: Only after you accept the Privacy Policy, grant camera access and activate the camera does the app use the accelerometer to determine device orientation and align the preview and saved photo. Android's system interface queries the list of accelerometers to find an available sensor, then reads acceleration data during camera use. Listening stops when you leave the camera screen or the app enters the background. Raw readings are not retained, uploaded or used for advertising or profiling. Sensor listening does not start if you decline camera access or only import and edit photos.
- Photos: The current app supports Android 10 and later. It imports through the system picker and saves app-created photos through MediaStore. The in-app Library queries app-created photos using URIs recorded locally. It does not request broad access to photos, videos or storage, or scan other photos. Deletion follows the system confirmation flow. Sharing grants temporary read access to the selected photos only to your chosen recipient.
- Microphone: The current Android app does not request recording permission or record sound for Live Photos.
- Local data: Signatures, preferences, film pack status, photo identifiers and dates are stored locally. Thumbnails use a limited cache as needed; epolar does not create a separate backup of full-size library photos. The app disables system automatic backup of its app data. Photos in the system library remain subject to the system's separate services.
Google MediaPipe beauty component and separate consent
Android versions that include this component create it only after you read the notice, give separate consent and enable beauty effects. It is provided by Google LLC. Input images and facial landmarks are processed on your device, are not sent to Google or epolar, and are not used for identity recognition or facial profiles.
The component sends Google performance and usage statistics. These may include the app ID, SDK and session usage, inference counts, performance and errors, system and version details, and general characteristics of processed media. It may also contact Google for fixes, models or hardware compatibility information. These communications include necessary network information and may be processed outside mainland China. General media characteristics are not the photo content itself. epolar does not provide the component with your phone number, email, account credentials or Pro records. The purposes are measuring use, troubleshooting, maintaining and improving the component. See the official MediaPipe terms and privacy information and Google Privacy Policy, including provider contact details and privacy-request options.
You can decline beauty effects without losing ordinary photography, import or unrelated features. To withdraw consent, open Camera → Beauty → Withdraw beauty consent. No new beauty processing starts after withdrawal. Withdrawal does not automatically delete statistics previously processed by Google; use Google's privacy-request channels for those records. This component disclosure does not apply to versions that do not include MediaPipe.
4. HarmonyOS: on-device processing and permissions
- Camera: Requested when you enter camera mode. Imports use the system picker to access only your selected content. You can still import if you decline camera access.
- Library browsing: Versions with an in-app Library query app-created photos and thumbnails using locally saved URIs. They do not request access to the entire image and video library or scan other photos. Saving uses the system's media-creation facilities or save control and does not overwrite the imported file.
- Deletion: WRITE_IMAGEVIDEO permission is requested only when you choose to delete a photo. After system confirmation, the corresponding system-library photo is deleted. Declining permission or cancelling does not delete it. Declining does not affect in-app browsing, ordinary photography or import.
- Audio: Live Photos with sound are available only in versions that provide the feature and declare recording permission. Those versions request microphone access when you enable it. Versions without recording permission do not record audio. If you decline, ordinary photos and any supported silent Live Photos remain available. Images and audio are processed locally.
- Beauty effects and secure storage: Core Vision detects faces locally. Images and landmarks are used only for the current beauty effect, without upload, identity recognition or facial profiles. Sign-in details use system secure storage such as Asset Store. System components' own processing follows the device and Huawei service notices.
The current app manifest declares camera, network and the WRITE_IMAGEVIDEO permission needed for deleting photos. This Policy does not grant microphone or full-library access. Temporary imports and rendered files are held in the cache; photo indexes, preferences and local signatures are stored in the app's directory. Uninstalling or clearing data removes them according to system rules.
5. Third-party services, payments and disclosures
- Apple StoreKit and the App Store — iOS/iPadOS only
- Apple provides product lookup, purchase, restoration and transaction verification services and independently handles its account and payment data. epolar processes product IDs, transaction identifiers, transaction environment, signed transaction credentials and refund or revocation status, retaining necessary verification results or credential hashes. The appAccountToken sent when you explicitly link a purchase is a random purchase-intent identifier, not your phone number, email or photos. epolar does not receive your Apple password, bank card information or Apple Account email. See the Apple Privacy Policy.
- APP支付客户端SDK (Alipay App Payment SDK) — where offered
- The provider is Alipay (Hangzhou) Information Technology Co., Ltd. (支付宝(杭州)信息技术有限公司) Supported Android and HarmonyOS versions use the relevant SDK for Pro purchases; versions offering Alipay support payments on iOS/iPadOS, Android or HarmonyOS use it for that feature. On iOS/iPadOS, Alipay is used only for Support the Developer, not Pro. Checkout is invoked only when the channel and feature are enabled and you choose to pay. Confirm the amount on the purchase or support screen and in Alipay. Under its privacy notices, Alipay processes app and device identifiers, device details, network status, IP addresses, products, orders, amounts and payment status for payment and fraud prevention. epolar does not send Alipay your phone number, email, photos or signatures, or receive payment passwords or full bank card details. Our server handles credentials, notifications, ownership, status and refund verification, confirming receipt only after signature validation and provider checks. Verified Pro purchases grant access under the relevant rules; support payments do not change Pro access. No Alipay payment is initiated unless you select it. Declining or cancelling does not affect free features. See the Alipay SDK privacy notice.
- 微信OpenSDK Android (com.tencent.mm.opensdk) / WeChat OpenSDK for iOS
- Provided by Shenzhen Tencent Computer Systems Company Limited (深圳市腾讯计算机系统有限公司). In versions offering WeChat payments, the SDK is invoked when you choose WeChat Pay or when its payment callback is handled. It passes the payment order identifier to WeChat and returns the result. Android SDK collection/processing scope: app package name and signature, whether WeChat is installed, app and merchant identifiers in the payment request, order identifiers, payment parameters and callback results. These are exchanged with WeChat to identify the calling app, open checkout and return payment results; the SDK processes information needed for that service under its privacy policy. The app checks WeChat installation status rather than reading a complete installed-app list. On iOS, cross-app communication may read and write information for that interaction through the system clipboard. epolar does not use this SDK to obtain your WeChat profile photo, nickname, contacts or chats, and payment does not authorize WeChat sign-in. See the WeChat OpenSDK personal information rules.
- WeChat Pay
- Provided by Tenpay Payment Technology Co., Ltd. Where enabled, Android and HarmonyOS versions use it for Pro purchases or support payments; iOS/iPadOS use it only for support payments. Tenpay handles payment-account details, orders, amounts, status, and device and network information needed for payment security. epolar sends necessary order parameters and processes transaction numbers, verified notifications, order checks and refund results. It does not receive payment passwords or full bank card details. Pro access requires server verification; support payments do not grant Pro. Declining or cancelling does not affect free features. See the Tenpay Privacy Policy.
- Alibaba Cloud SMS verification
- Alibaba Cloud Computing (Beijing) Co., Ltd. provides phone-verification services. Only when you request an SMS code does our server submit the phone number, country code and information needed for verification, and process the sending-request identifier, code and verification result. Photos and signatures are not sent. The app does not read text messages or obtain your phone number automatically. See the SMS verification service information.
- Alibaba Mail verification emails
- Alibaba Cloud Computing Co., Ltd. provides the email service. When you request an email code, our server sends it from noreply@epolar.cn to your chosen address over encrypted SMTP. The service processes the recipient address, message and necessary delivery information. These emails do not include your phone number, orders, photos or signatures and are not used for marketing. The app does not integrate an email SDK or read your mailbox. Your receiving email provider also processes the email. See the Alibaba Mail privacy policy.
- Alibaba Cloud ECS, RDS, OSS and CDN
- These infrastructure providers process data on our behalf to host the accounts, payment verification, feedback, encrypted signatures and public app assets described in this Policy. Application servers, databases and asset storage are in Shanghai, mainland China. Public resources are distributed through a CDN, and high-resolution resources use temporary download links. User photos, videos and facial landmarks are not uploaded to these services; signatures are not uploaded to the public asset CDN. Provider and contact information is available on the Alibaba Cloud website.
- System components, receiving email services and sharing
- Apple and HarmonyOS system components support local photography, image processing, media selection, saving, browsing, sharing, deletion with your confirmation and secure storage. Android uses its corresponding system components, plus the separately described MediaPipe component. System cloud backups you enable, your receiving email service and services you choose for sharing handle content under their own rules and may process it outside mainland China. This does not mean epolar provides cloud photo backup.
We do not proactively move our mainland China application database abroad. Statistics from the Android beauty component, and email, system or sharing services you choose to use, may involve processing outside mainland China as explained above. Before introducing cross-border processing by us, we will complete the notices, consent and other steps required by applicable law. We do not disclose, transfer or publicly release personal information except to provide your requested services, meet applicable obligations or with the required consent. Providers processing data on our behalf must apply appropriate safeguards.
6. Where information is stored and when it is deleted
- Local content: Signatures, account associations, preferences, film pack status, photo identifiers and dates stay on your device. Temporary media and rendering caches are cleaned up as part of the relevant feature. Compatibility upgrades may retain local migration backups until app data is cleared; these are not part of routine cloud sync. Photos in the system library are managed separately.
- Accounts and sessions: Account information is retained while the account exists. Account deletion removes it from the live application database and revokes all sessions; signing out revokes the current session. Sign-in sessions normally last no more than 30 days and scheduled tasks remove expired sessions.
- Verification codes: Codes normally expire after five minutes and cannot be reused after successful verification. Email codes are stored as keyed hashes. Successful verification clears that request's encrypted email-delivery value and code hash. Anti-abuse records older than 24 hours are removed by an hourly task, normally within about 25 hours. Email messages and delivery records held by sending and receiving mail services follow those services' retention rules.
- Cloud signatures: Content is retained until a deletion sync succeeds or the account is deleted. Successful deletion removes the handwriting data. While the account exists, IDs and deletion versions without the handwriting are retained to prevent an offline device from restoring deleted content. Turning sync off or losing Pro access does not automatically remove existing copies. You can contact support to request deletion.
- Orders and access: Records are retained for the shortest period necessary for verification, duplicate prevention, refunds, disputes and applicable obligations. Necessary de-identified records retained after account deletion no longer contain your phone number or email, but are not fully anonymous. They are deleted or anonymized when their purpose ends and no other retention basis applies.
- Support-payment records: Pending order details on your device are cleared when payment, refund or order closure is confirmed. The separate query credential may remain for future support payments you initiate. Uninstalling, clearing data or changes to secure storage may affect your ability to check an order on that device. The server retains necessary payment and verification records for the shortest period needed for verification, refunds, disputes and applicable legal obligations. They are not automatically deleted when you sign out or delete your epolar account. Contact support to request access, a copy or deletion. Where the law requires retention, records are retained only as necessary and not used for other purposes.
- Feedback, support and security logs: Records are retained only as long as needed to address the issue, protect security and meet applicable obligations. Account-linked Android feedback is deleted with the account. Anonymous feedback requires a separate deletion request. Any longer retention required for a security incident or by law is limited to that need.
Backups are kept for the periods needed for recovery and applicable obligations. Completed deletions remain effective after recovery; a backup is not a reason to resume using deleted data. Information independently processed by Google, Apple, Huawei, email providers and system services follows their own privacy notices, retention rules and request procedures.
7. Your choices, rights and security
You may request access to, a copy of, correction of, supplementation of or deletion of your personal information, withdraw consent, and ask us to explain our processing. You may request data transfer where the legal conditions are met. Account settings let you view masked sign-in methods, link an unused identifier, sign out and delete your account. Self-service replacement of identifiers and transfer of linked purchases are not currently available. For a full copy, correction, deletion, sign-in problems or other privacy requests, contact support@epolar.cn. We will review your request promptly and respond within applicable legal deadlines, verifying only what is necessary. We will not ask for passwords, payment-account passwords or verification codes.
You can revoke permissions in system settings and turn off beauty effects or signature sync in the app. Turning sync off does not delete cloud content, and deleting a local copy while sync is off does not delete the cloud copy. Complete deletion with sync enabled or contact support. Account deletion removes account identifiers, sessions and cloud signatures. It does not automatically issue refunds, reassign purchases or delete system-library photos or local signatures not associated with an account. Anonymous feedback, account deletion, purchase refunds and local deletion are handled separately.
We protect information using HTTPS, encryption of identifiers, feedback and cloud signatures, credential hashing, system secure storage, private database connections, access controls and rate limits. No system can guarantee absolute security. If an incident occurs, we take remedial action and notify affected users and authorities as required by law.
epolar is not specifically directed at children. Minors should use it with a parent or guardian's guidance. Children under 14 should not submit a phone number, email address or feedback containing personal information on their own. We obtain parental or guardian consent first where required by law. Parents and guardians can contact us to investigate and delete information submitted without required consent.
8. Website, policy updates and contact
The public introduction, changelog and legal pages on epolar.cn do not require sign-in. The website does not use advertising, analytics scripts or tracking cookies, and does not request camera, microphone or location permissions. Browsing causes the server to process the IP address, request path, time, browser request headers and response status needed to deliver pages, protect security and troubleshoot problems. We do not use these records to create advertising profiles. If you follow links to the App Store, filing-information lookup services or third-party notices, or send an email, those services handle information under their own rules.
Film Frame Workshop: When you enter an invitation code, the server verifies it and processes the invitation ID, expiry, usage count, session-credential hash, and session creation and expiry times. A keyed IP-address hash is used for rate limiting. Your browser stores a necessary secure session cookie for workshop access, not advertising tracking. A session lasts up to 30 days and no longer than the invitation's validity; signing out revokes it, and expired sessions are cleaned up hourly. Invitation-management records are retained only as needed for access management, security and disputes. The workshop does not require an epolar account. Imported artwork, previews and ZIP exports are processed locally in your browser, without automatic upload or publication. Clearing cookies affects workshop sign-in, not your app account or Pro access. Contact support to request deletion of related records.
Updates to this Policy will show a date and version. We will notify you through the app or another appropriate means of material changes, including changes to processing purposes, methods or information categories. Where consent or renewed consent is required, we obtain it before processing; continued use is not a substitute for an explicit choice. System permissions, separate consent for the beauty component and enabling signature sync are managed independently.
Operator and person responsible for processing your personal information: Zhang Fengfeng (张峰峰). Privacy contact: support@epolar.cn.