XianNow Privacy Policy
Last updated: October 9, 2026
Effective: October 9, 2026
Welcome to XianNow (苋在, the “App,” “XianNow,” or “we”). We value your personal information and privacy. This Policy explains what information is processed when you use XianNow, why it is processed, how it is protected, and how you can exercise your rights. Please read it before using the App. You must accept the Terms and this Policy before using the App. If you do not agree, stop using the App. Except where the law permits otherwise, we will not process relevant personal information before obtaining any authorization that is required.
The App is operated by independent developer Han Yue. For questions about this Policy or our processing of personal information, email hanr6969@gmail.com. Do not include your Apple Account password, payment password, or unnecessary photo content in your email.
1. Information We Process
1.1 Camera, Frames, and Photos
When you use the shooting feature, the App accesses the camera and processes the live image on your device to provide the viewfinder, capture, Frame/template composition, and filter effects. At your direction, completed photos or Live Photos are saved on the device and in the system photo library. If you enable Live Photos, the App uses the microphone—after you grant permission—to record audio associated with the Live Photo.
When you actively select an item from your photo library for an avatar, template, or creation, the App reads only the selected item and processes it on your device. XianNow does not automatically upload personal photos, videos, avatars, user-created templates, personal filters, or creative content to our servers. This version has no XianNow account, cloud backup of creations, or cross-device sync. If you choose to share through the system share sheet, the system or third-party app you select processes the shared content.
1.2 Device Permissions
You can manage permissions at any time in iOS Settings. If you deny or withdraw a permission, a feature that depends on it may not work, but unrelated features remain available.
| Permission | Purpose |
|---|---|
| Notifications | After you allow access, provide film, inspiration and recap reminders, plus XianNow’s own news, re-engagement messages and film gifts. Turn them off in the app or iOS Settings. |
| Camera | Preview the scene, take photos, and preview Frame effects. |
| Photos | Save finished images; read only the items you select or items saved by XianNow when you manage them. |
| Microphone | Record audio for a Live Photo only when you enable Live Photos and allow access. Ordinary photo capture does not require the microphone. |
| Location | Obtain the device's location once after you actively enable local weather, in order to retrieve local weather and display a weather mood. Location is not used for advertising or profiling. If you disable location, local weather may be unavailable. |
Local weather uses Apple WeatherKit. Apple processes the relevant coordinates to return weather results. XianNow stores only the most recent location/weather state needed by the feature on your device and does not build a location history. Apple's processing is governed by the Apple Privacy Policy.
1.3 Online Official Template Catalog
After you agree to this Policy and enter the App, XianNow requests the published official template catalog through cloud services provided by Supabase so that the latest official templates can be displayed. The request retrieves only public template configuration. It does not upload your photos, videos, avatar, user-created templates, personal filters, creative files, contacts, or precise location. If the network or service is unavailable, the App continues to use the local templates bundled with the App, and core shooting features remain available.
To deliver requests, secure the service, and diagnose faults, Supabase and its infrastructure providers may process and retain for a limited period an IP address, request time, request path, response status, and network-connection information, and may infer an approximate region from the IP address. We do not use this information for personalized advertising, cross-app tracking, or user profiling. Supabase's processing, storage locations, and retention periods are governed by its Privacy Policy and the service configuration of the project we use.
1.4 Operation, Purchases, and Diagnostics
To keep the App working, iOS, Apple StoreKit, or Apple WeatherKit may process device, system, network, transaction, or service-operation information through their own mechanisms. Film-roll items are offered and processed through the Apple App Store. We do not collect or store your bank card number, payment password, or Apple Account password.
We use the RevenueCat purchase-validation SDK to verify App Store film-roll orders and prevent duplicate fulfillment. The SDK initializes only after you agree to this Policy and enter the App. It generates an anonymous App user identifier and processes App and device information needed to provide purchase validation. When you make or restore a purchase, RevenueCat also processes the purchase history, product identifier, and transaction-validation information provided by StoreKit. We have no account system and do not associate the anonymous identifier with your name, email address, or phone number. RevenueCat does not receive your photos or creative files, bank card number, payment password, or Apple Account password. Purchase records are used for purchase validation, order fulfillment, and related product analytics—not for cross-app advertising tracking. See the RevenueCat Privacy Policy for details.
1.5 Umeng Mobile Analytics SDK (U-App)
We use Umeng Mobile Analytics SDK (U-App), provided by Umeng Tongxin (Beijing) Technology Co., Ltd., to understand new and active users, retention, page usage, and key product conversions. You must accept the Terms and this Policy before using the App. After acceptance, the App initializes the SDK and automatically submits all configured usage events without a separate analytics switch. Existing users must confirm this revised Policy after updating. Before acceptance, the App does not initialize Umeng or submit usage events.
The SDK may process device model, operating system and version, App version, language, network status, IP address, device identifiers such as IDFV or SDK-generated identifiers, and session information to distinguish devices and calculate activity and retention. The App generates and stores a random installation-instance ID locally to connect events from the same installation. This is not an Apple Account, hardware serial number, or natural-person identity. Switching store accounts within that installation does not change it; separate devices have separate IDs, and reinstalling or losing local data creates a new ID. The ID directory is excluded from system backup. If persistence fails, the App retains a temporary process ID and marks its storage status. Each custom event includes this ID, its installation scope and storage status, distribution environment and detection source, App version, and build number to distinguish production, TestFlight/sandbox, development, and simulator usage. Custom events cover launches, first use, policy acceptance, onboarding, page views and duration, template browsing/filtering/search-result counts and editing-feature categories, filters and beauty controls, companion creation and selection, capture and permission states, save and deletion outcomes, albums and recaps, settings, weather-request outcomes, film-roll packs and purchase outcomes, redemption entry, sharing entry, help, and feedback-flow outcomes. Diagnostic events include only a fixed stage, error category, or code. These events do not contain photos, videos, facial landmarks, contacts, precise location, template names, user-entered content, transaction identifiers, or payment credentials. We disable ASA and SKAdNetwork attribution collection, do not request IDFA, and do not use analytics for personalized advertising or cross-app advertising tracking.
Data are sent to Umeng's analytics service. The SDK manages caching, batching, and upload, including pending logs when connectivity returns; timing and limits depend on the SDK and server. Processing, storage, and retention are governed by the Umeng Personal Information Processing Rules. We use analytics for product analysis and to evaluate XianNow’s own notification campaigns, do not associate it with your name, email, or phone number, and do not use it for AI training. This version no longer sends the former anonymous daily usage counters to Supabase. Supabase processes the push registration, reservations and related events described in Section 1.7.
To withdraw the relevant consent, stop using the App and contact us by email to make an applicable access, deletion, or withdrawal request. Uninstalling the App does not automatically delete data already received by Umeng. An individual's contribution to anonymized aggregate statistics may not be identifiable or separately removable.
1.6 Face Data and On-Device Retouching
Data and purpose. When you enable retouching or makeup effects, XianNow uses Apple Vision on the device to detect two-dimensional face bounds, contours, and landmarks around the eyes, eyebrows, and inner and outer lips. These geometric data are used only for smoothing, brightening, face slimming, eye enlargement, blush, eyeshadow, lip color, and stabilizing these effects. They are not used to identify or authenticate anyone, create a face-identity database, advertise, profile users, collect usage analytics, or train AI models.
Sharing and storage. Face detection and rendering take place on the device. XianNow does not upload facial landmarks or face geometry to our servers, Supabase, RevenueCat, Umeng, or any other third party, or write them to creative files, databases, or analytics logs. Calling on-device Apple Vision does not cause XianNow to upload these data to Apple. Preview detection results are held temporarily in running memory. Photo and Live Photo rendering also occurs locally.
Retention and deletion. Preview landmarks are replaced as detection results update. The preview cache is cleared or released when retouching is disabled and the next frame is processed, the camera session stops, or the processing object is released. Stopping the camera explicitly clears the cache on the frame-processing queue. Temporary detection data used in photo or Live Photo rendering are released as processing ends and processing objects are released. We do not retain a persistent facial-landmark record.
Photos containing faces. Saved originals, finished photos, and Live Photos may contain face images and are separate from temporary landmark data. During capture, original photos or Live Photo video may be staged in the App's local directory for rendering or retry after a failure. Once processing completes, original files are removed for records where keeping the original was not selected. When you choose to keep originals, originals and finished files remain locally until you delete them using the deletion scope offered by the App or uninstall the App. Copies saved to the system photo library are managed through iOS Photos or the App's system-photo deletion action. Deleting only an App copy or uninstalling the App does not automatically delete system-library copies. System backups or iCloud Photos sync, if enabled by you, are managed by Apple and your system settings, not a XianNow face-data upload service. Only when you actively use system sharing are the selected photos or videos passed to your chosen recipient; no separate facial-landmark record is attached.
1.7 Notifications and Reminders
After you accept this privacy policy and allow system notifications, XianNow can provide film reminders, photography inspiration and recap reminders, as well as messages about XianNow’s own new templates, styles, companions and film gifts. We may select these messages using your notification preferences and most recent activity time. You can turn off notifications in the app’s notification settings or revoke notification permission in iOS Settings.
To schedule reminders, limit message frequency and verify film gifts, our push service processes a randomly generated installation identifier, an installation authentication credential, an Apple push device token, notification permission and subscription settings, interface language, time zone, app version, most recent activity time, and notification campaign identifiers, types, scheduled times, expiry times and processing results. The authentication credential is stored in your device’s Keychain; the server stores its digest to verify the installation.
To understand whether a notification was clicked, whether its destination opened and whether a film gift was actually credited, we record notification clicks, destination results, gift claims and gift popup actions, as well as the stages and times of opening the camera, taking a shot and successfully saving a photo after a notification click. These records are associated with the installation identifier and used to provide features, analyze usage and evaluate XianNow’s own campaigns. Notification events are also processed through our existing Umeng analytics service. Apple push device tokens are not sent to Umeng.
Local reminder eligibility is determined on your device, while notification reservations are synchronized with the server to coordinate the frequency of local and remote messages. A favorite-template reminder’s reservation and campaign identifiers may include the relevant template identifier. The push service does not upload photo or video files, photo identifiers, creative text, precise coordinates, your Apple account or your film balance. Film gift records include the number of films granted and whether they were actually credited.
Apple Push Notification service (APNs) delivers remote messages and receives the device token, notification content and related information needed for delivery. Supabase provides services for push registration, reservations, gift verification and event records. Umeng receives notification analytics events and their installation association, as described in this policy’s existing Umeng section.
Turning off notifications in the app cancels pending local reminders. Once your choice is synchronized with the server, future remote campaign messages stop. If your device is offline, the server may not yet have received your choice; you can also disable system notifications in iOS Settings. Turning off notifications does not automatically delete stored push registration, delivery, event or gift records and does not turn off the Umeng usage analytics described in this policy.
Retention and deletion. The on-device queue of push events awaiting synchronization holds at most 256 entries. When synchronization is attempted, entries older than 30 days are discarded; this does not mean that server records are automatically deleted after 30 days. The push service currently has no fixed automatic expiry or cleanup mechanism. We retain registration, delivery, event and gift records for as long as needed to provide notifications, manage frequency, verify gifts, prevent duplicate grants and handle related disputes. Turning off notifications or uninstalling the app does not automatically delete these records. For access, deletion or withdrawal requests, contact the email address in this Policy. After verifying the request and the relevant installation, we handle deletion or de-identification under applicable law and explain any information that must still be retained for legal requirements or necessary verification.
2. How We Use, Store, and Protect Information
- We process only the information needed for the purposes described in this Policy: shooting, creating, saving, weather, purchase fulfillment, analytics, notifications, XianNow’s own campaigns, and secure operation. We do not sell personal information.
- Creative files, photos, and most settings are stored on your device. Uninstalling the App, clearing App data, damage to the device, or changing devices may make local data unrecoverable. You manage anything saved to the system photo library through iOS Photos. Weather cache and local settings can be cleared with the App's data.
- Supabase provides the online official template service and the private push service described in Section 1.7, Umeng provides mobile analytics, RevenueCat validates purchase orders, and Apple processes data through StoreKit, WeatherKit, and system photo services under its own rules. Each provider processes necessary information under its privacy terms and service agreement. The relevant recipient and purpose are described above.
- We use reasonable technical and administrative safeguards, restrict access, and minimize unnecessary collection. No internet transmission or electronic storage is absolutely secure. If a security incident legally requires notice, we will respond as required by law.
3. Sharing, Transfer, and Public Disclosure
We do not provide personal information to third parties except:
- after you agree to this Policy and enter the App, to send Supabase the network-request information needed to retrieve the online official template catalog and secure the service;
- to provide Apple with information necessary for weather queries, App Store purchases, or system photo/sharing services that you actively use;
- after you accept this Policy, to provide Umeng with the device, session, and usage-event information described in Section 1.5;
- to provide RevenueCat with the transaction and necessary service information returned by StoreKit in order to validate and fulfill a film-roll purchase you initiate;
- after you allow notifications, to provide Supabase with installation registration, reservation, event and verification information, and Apple APNs with delivery information, for the reminders and campaigns described in Section 1.7;
- where required by applicable law or by a lawful request from a judicial or administrative authority, or where necessary to protect you, other users, the public, or our lawful rights and interests.
We do not publish your photos or creative content, sell or rent it, or use it to train artificial-intelligence models. If the service architecture or data recipient changes materially, we will update this Policy and obtain any authorization required by law.
4. Your Rights and Choices
To the extent provided by applicable law, you may request access to, correction of, or deletion of personal information; withdraw consent; restrict processing; or object to processing by contacting us below. We will verify and respond to a request within the period required by law. Because this version has no XianNow account system, photos, templates, filters, shooting history, and the film-roll balance are mainly stored on your device. You can manage or clear them through App features, iOS Settings, or by uninstalling the App. Uninstalling does not automatically delete photos already written to the system photo library.
You can turn off camera, photo, microphone, location or notification permission in iOS Settings. See Section 1.7 for notification choices and push-record retention and deletion. Information necessary for purchase validation may be processed as needed for purchase records and order verification. To exercise deletion, access, or other rights relating to that information, contact RevenueCat or email us, and we will help route or address the request. See Section 1.5 for analytics withdrawal and Section 1.6 for face-data and photo retention and deletion. To exercise a right or ask a question, email hanr6969@gmail.com.
5. Children
XianNow is a general-audience App and is not directed to children. A parent or other guardian should read and agree to this Policy before a child under 14 uses the App. Children's personal information is sensitive personal information under applicable law. We process it only where the law permits, for a specific and necessary purpose, with adequate safeguards, and with the guardian's consent where required. A guardian who learns that a child provided personal information without consent can contact us using the details below. Minors should use shooting and purchasing features under a guardian's guidance.
6. Updates to This Policy
We may update this Policy when product features, legal requirements, or processing practices change. We will give reasonable notice of material changes through a prominent in-App message or similar means and obtain renewed consent where required by law. We will not use a policy update to expand existing processing without required notice or authorization. The date at the top shows when this Policy was last updated.
7. Contact Us
Operator: Han Yue
Email: hanr6969@gmail.com
Related Policies
Language
This Policy was originally written in Chinese. This English version is provided for convenience. If the versions conflict, the Chinese version controls to the extent permitted by law.