Scope. This Policy applies to the international Android app “Rapixa: GPS Timestamp Camera,” package com.cqian.photo.watermark_camera.global.
1. Who we are
Rapixa is provided by Shanghai Shunqi Wujie Technology Co., Ltd. (上海瞬启无界科技有限公司), based in Shanghai, China (“Rapixa,” “we,” “us,” or “our”). Privacy questions and requests may be sent to official@shunqiwujie.com.
Rapixa is a local camera, watermark editor, and device-gallery tool. It does not provide an App account, team workspace, social community, cloud photo storage, or media synchronization. It contains no advertising SDK and does not use personal data for cross-app targeted advertising.
2. Data used for App features
When you choose the relevant feature, Rapixa accesses or processes the following data. Most content processing occurs locally; the limited off-device cases are described below:
- camera frames, photos, and videos for capture, preview, watermarking, editing, and saving;
- microphone audio when you record video with sound;
- photos, videos, thumbnails, folders, and media metadata made available through the Android media library, so Rapixa can provide its complete local-gallery experience;
- foreground approximate or precise location and available altitude for a location watermark;
- place-search terms you enter, and place names or addresses returned by Android or the device provider’s geocoding service;
- watermark text, custom locations, dates, times, project labels, and imported logo images; and
- App settings, language, templates, local indexes, free-use quota, and a local membership cache.
Rapixa does not use a Rapixa server to cloud-process or store your photo, video, recorded audio, watermark text, place-search term, or precise coordinates. When you search for a place or convert coordinates into an address, Rapixa passes the search term or coordinates to Android’s Geocoder. The geocoder implementation is supplied by Android or the device provider and may use a network connection under that provider’s terms. Content you deliberately send through Android’s share sheet is handled by the app or service you select.
3. Permissions and your choices
- Camera: take photos and videos.
- Microphone: record sound with video.
- Photos and videos: browse the complete local timeline and folders, repeatedly open media for watermarking or playback, share it, and perform user-confirmed media management.
- Approximate or precise location: create a foreground location watermark. Rapixa does not request background location.
- Legacy storage: read or save shared media on older Android versions.
You may deny or revoke permissions in Android settings. On supported Android versions, selected-media access limits Rapixa’s gallery to the media Android makes available. Denying a permission limits the related feature but does not buy or cancel membership.
4. Home-screen operational content
Rapixa periodically retrieves a small, read-only configuration file hosted on Alibaba Cloud for the image shown in the home-screen operational slot and its approved HTTPS destination. The App does not add an account identifier, advertising identifier, photo, video, watermark, or location to this request. Access logging is disabled for the exact public configuration path, although network infrastructure necessarily handles an IP address long enough to deliver the connection.
5. Analytics, crashes, and performance
Rapixa uses the international Umeng U-App and U-APM components when the App starts to understand usage and improve reliability. Depending on SDK behavior and configuration, Umeng may process App launches, sessions and screens; App/SDK version and distribution channel; device model, Android version, language, time zone, screen and network context; IP address; SDK-generated analytics or diagnostic identifiers; crash stacks, ANR information, startup measurements, and performance diagnostics.
Before Umeng initialization, Rapixa disables the SDK collection switches for AID, IMEI, IMSI, ICCID, and Wi-Fi MAC, and Rapixa does not request phone-state, Wi-Fi-state, or advertising-ID permissions. We do not represent analytics as optional in the current build because no verified in-App analytics opt-out is presently provided.
6. Google Play purchases and membership
Google Play processes checkout and payment credentials. Rapixa uses RevenueCat to retrieve products and localized prices, complete and restore purchases, verify transactions, and return the verified Rapixa Pro entitlement and expiration state. RevenueCat CustomerInfo is the only authority used by the App to grant VIP access.
Google Play, RevenueCat, and Rapixa’s purchase-history service may process a randomly generated RevenueCat App User ID and aliases, a random installation credential or its cryptographic hash, App/device/OS/network technical information, product and base-plan identifiers, localized price and currency, purchase token, transaction or order identifier, purchase/expiration/status timestamps, and pending, refund, revocation, chargeback, entitlement, and restore status.
Our Alibaba Cloud service stores a limited mirror of authenticated RevenueCat webhook events and returns masked, read-only purchase history to the current installation. That history cannot grant, extend, restore, or revoke VIP access. Rapixa does not receive your complete card number, Google password, or Google account credentials.
7. Support and public websites
If you email us, we process the address, message, attachments, and any App version, device details, masked order identifier, or diagnostic information you choose to provide. Our public legal pages do not use advertising or third-party analytics scripts. Ordinary web security logs may contain IP address, browser or WebView User-Agent, request time, requested path, and response status.
8. Service providers and disclosures
- Alibaba Cloud: operational configuration, purchase-history backend, PostgreSQL database, backups, and public legal pages.
- Umeng U-App and U-APM: analytics, crash reporting, ANR, and performance diagnostics. See Umeng’s privacy policy.
- Google Play: App distribution, billing, purchase processing, restoration, refunds, and purchase state. See Google’s privacy policy.
- RevenueCat, Inc.: offerings, purchase completion and verification, acknowledgement, restoration, and entitlement status. See RevenueCat’s privacy policy.
- Android and device-provider services: permissions, media access, location, geocoding, and sharing.
These providers may handle data in their own infrastructure as described above and in their policies and agreements. Umeng’s published policy says that it may process lawfully collected data using de-identification, anonymization, or pseudonymization techniques to build a data-intelligence platform, and may provide processed or de-identified data to advertising or media partners under confidentiality and security obligations. Rapixa does not integrate an advertising SDK or use these data for its own cross-app targeted advertising. We may disclose limited information when legally required, to protect users or our rights, or as part of a corporate transaction with appropriate safeguards. We do not sell personal data.
9. International processing
Rapixa is offered internationally. Our Alibaba Cloud infrastructure is currently in Shanghai, China. Provider processing may also occur in China, Singapore, Germany, the United States, or other places described by the relevant provider. Where required, we use applicable contractual or legal transfer safeguards.
10. Retention and deletion
- On-device data remains until you delete it, clear Rapixa data, or uninstall the App. Exported media in the shared gallery must be deleted separately.
- The first-party operational configuration endpoint has access logging disabled. Ordinary website and API access/security logs are generally rotated within 10 days unless needed longer to investigate abuse or satisfy law.
- Current database backups are access-restricted, stored on the same Alibaba Cloud server as the database, and deleted on a daily schedule approximately 14–16 days after creation. Deleted data may remain in a backup until that backup expires.
- Purchase and transaction-support records are kept while reasonably necessary for entitlement support, restoration, refunds, chargebacks, fraud prevention, accounting, tax, consumer-protection, and legal obligations, and are then deleted or de-identified.
- Support and privacy-request records are kept while the request is open and as reasonably necessary to document its resolution.
- Umeng, RevenueCat, Google, and other providers retain data under their terms and our applicable agreements.
Rapixa has no App account, so there is no App-account deletion flow. You may still request access to or deletion of data we can reasonably identify by emailing official@shunqiwujie.com with the subject “Rapixa Privacy Request.” We may ask for limited installation or masked purchase information to locate records and prevent unauthorized disclosure. Some transaction records may be retained where law, fraud prevention, refunds, or disputes require it.
11. Security
Safeguards include Android sandboxing and runtime permissions, HTTPS with cleartext disabled in release builds, exclusion of App-private data from Android cloud backup/device transfer, restricted administration access, masked order identifiers, authenticated and replay-protected webhooks, database access controls, and backups. No system is completely secure.
12. Your rights
Depending on where you live, you may have rights to request access, correction, deletion, restriction, objection, portability, or withdrawal of consent, and to complain to a regulator. Email us to exercise a right. We may verify the request and may retain or withhold limited information when legally permitted or required.
13. Children and teenagers
Rapixa is currently intended for adults aged 18 and over and is not directed to children or teenagers. We do not knowingly create profiles of minors or collect data for child-directed advertising. A parent or guardian who believes a minor provided data may contact us.
14. Changes
We may update this Policy when App features, providers, or legal requirements change. We will update the date above and provide additional notice where required.