AltitudeNow Product Page

Privacy Policy

Effective: July 23, 2026 · Updated: September 2, 2026

This Privacy Policy is provided by Beijing Qijian Technology Co., Ltd. (“Qijian,” “we,” “us,” or “our”) and applies to the AltitudeNow mobile application and related features. AltitudeNow displays environment information, captures photos, creates altitude keepsakes, and lets you save or share them.

Core features do not require a separate account. Photos, creations, and edit settings are stored on your device by default. First-party operations reporting, advertising, and attribution start only after you agree to this Privacy Policy and the Terms of Use. Domestic Android OAID notice: only after consent, advertising SDKs such as GroMore, Pangle, and Tencent Youlianghui may obtain the OAID (an anonymous device advertising identifier) and transmit it with ad requests over encrypted connections solely for ad delivery, frequency control, fraud prevention, and measurement. It is not used for altitude, weather, camera, creations, or other core features. On iOS, App Tracking Transparency (ATT) determines only whether the app may use IDFA; it is not the startup gate for ads, attribution, or core features. Authorization may enable IDFA. When ATT is denied, restricted, or unresolved, IDFA is disabled; the mainland-China route may still request limited-personalization GroMore app-open and banner ads, other regional routes skip UMP and its cookie form and request Google AdMob Limited Ads, and Ocean Engine attribution may continue its disclosed launch, activation, and valid-touchpoint processing without IDFA. Choosing “Not Now” keeps the app on its privacy notice and starts none of these SDKs or requests.

1. Information We Process

1.1 Location and environment information

With your permission, the app reads your location, altitude, location accuracy, direction, and related time information to display altitude and coordinates, calculate sunrise and sunset, match mountain silhouettes, perform reverse geocoding, and request nearby weather. Precise location is used only for the feature you request. It is not provided by us to Google AdMob, GroMore, Pangle, or Ocean Engine attribution. You decide whether precise coordinates appear in a creation.

1.2 Camera, Photos, and creations

Camera frames, photos you select, edit settings, thumbnails, and exported creations are processed and stored on your device by default. Content is passed to Photos or the system share sheet only when you choose to save or share it. Exported images omit EXIF GPS metadata by default. We do not provide your photos, creations, or edit content to advertising or attribution SDKs.

1.3 Pressure, direction, and weather

The app may read the barometer and compass to improve the environment display. iOS weather requests use Apple WeatherKit. Android sends coordinates reduced to an approximately one-kilometre grid and rounded altitude to MET Norway Locationforecast to return nearby temperature. Android weather requests do not include an account, photos, or creations.

1.4 Help and feedback

When you submit feedback, we process the message, any contact details you choose to provide, app version, platform, operating-system version, submission time, and internal random installation and app-user identifiers. The app uses its anonymous App Auth session so NVPERPay can verify those random identifiers and resolve an internal user ID for support on the server. The App Auth token is used only for server-side verification and is not written to the feedback message, runtime logs, or Feishu notification. These random identifiers do not contain your name, phone number, advertising identifier, or hardware identifier. Feedback does not automatically include photos, creations, precise coordinates, or full logs.

1.5 First-party operations reporting

After consent, the iOS, Google Play, and domestic Android builds may send NVPERPay a random app-user identifier, random installation and session identifiers, app version and build, operating-system version, language, time zone, fixed distribution channel, and allowlisted lifecycle and feature events. Feature events are limited to the environment-load result, opening capture, photo source type (camera, library, or demo image), completed editing, aspect ratio, export destination and preset, starting share, and second launch. They support runtime analysis, stability, core-feature conversion, and product improvement. This information does not include photo or creation content, file paths, precise coordinates, advertising identifiers, search content, feedback text, or contact details.

1.6 Ad impression revenue

After consent, the app sends NVPERPay the revenue value, currency, estimation precision, ad format, mediation platform, and ad source for each displayed ad. We use it to measure advertising revenue, impression performance, and advertising value aggregated by a random installation identifier. This data is stored separately from ordinary behavior events and does not include IDFA, OAID, GAID, ad creative IDs, photos, creations, file paths, or precise location.

1.7 Display advertising

After consent, the app may request an app-open ad during cold launch and a fixed banner on the Environment screen; the main interface and ad entry do not wait for the ATT result. iOS locally combines the App Store storefront, system region, and system time zone and starts only one advertising stack: if any signal clearly indicates mainland China, it uses GroMore; otherwise it uses Google AdMob. The app does not save or upload these regional signals and does not read the iCloud account, device language, or GPS for this decision. The two stacks never fall back to one another. This iOS release is unavailable in the 27 European Union storefronts; availability in the United Kingdom, Norway, Iceland, Liechtenstein, Switzerland, and other non-EU regions follows the actual App Store Connect configuration. In the AdMob path, when ATT is authorized, UMP first handles applicable advertising privacy choices and normal ads are requested only when Google allows them. When ATT is denied, restricted, or unresolved, the app skips UMP and its cookie form, sets `gad_has_consent_for_cookies=0` before Google Mobile Ads initialization, and continues with Limited Ads. The domestic Android build uses GroMore only, may serve ads from Pangle or Tencent Youlianghui, and contains neither Google Mobile Ads nor UMP; it never falls back to Google AdMob. The Google Play version uses Google AdMob only and does not contain Android GroMore, Pangle, or Tencent Youlianghui.

The normal advertising path may process basic device, app, network, performance, ad-request, impression, click, conversion, security, and anti-fraud information for delivery, frequency control, and measurement. The mainland-China iOS GroMore path always limits personalized ads and disables location, Wi-Fi BSSID, optional device-information upload, and motion sensors; when ATT is not authorized, it also explicitly forbids IDFA without stopping app-open or banner requests. In other iOS regional routes, Limited Ads used while ATT is not authorized does not access IDFA or use local identifiers for personalization, frequency capping, or ad measurement. Google may still process the IP address needed to deliver an ad, security and fraud-prevention signals, and cookies or local storage used solely to detect invalid traffic. We do not permit cross-app tracking in this mode or provide photos, creations, precise location, search content, feedback text, or contact details to advertising providers.

Purpose, method, and scope of OAID processing in the domestic Android build: only after you tap “Agree & Continue,” advertising SDKs such as GroMore, Pangle, and Tencent Youlianghui may obtain the OAID (an anonymous device advertising identifier) through Android or a device-manufacturer identifier service and send it with ad requests over encrypted connections to the corresponding advertising provider. Processing is limited to ad delivery, frequency control, fraud prevention, and measurement in the domestic Android advertising path. It is not used for altitude, weather, location, camera, creations, feedback, or other core features and is not read or sent when you choose “Not Now.”

1.8 Advertising attribution

After consent, Apple AdAttributionKit or SKAdNetwork may submit aggregate activation measurements that do not identify you or your device. The app also initializes the Ocean Engine attribution SDK (BDASignalSDK 2.0.0), which may process advertising callback data, click IDs, cached open URLs, touchpoint time, and device or network information required by the SDK, and may send a valid touchpoint to NVPERPay to measure our advertising. ATT controls only this SDK’s IDFA switch: authorization may enable IDFA; denial, restriction, an unresolved status, or later withdrawal disables IDFA while the SDK may continue its disclosed launch, activation, and valid-touchpoint processing. This path does not receive photos, creations, precise location, feedback content, or other information not disclosed in this policy.

2. Third-Party SDKs and Services

2.1 National SDK Management Service Platform Registration

The domestic Android build contains the following SDKs introduced through the advertising aggregation path. Their registered SDK names, developers, and privacy-policy links are disclosed exactly as listed by the National SDK Management Service Platform:

Registered SDK NameDeveloperSDK Privacy Policy
优量汇 Android SDK深圳市腾讯计算机系统有限公司https://e.qq.com/dev/help_detail.html?cid=2005&pid=5983
抖音SDK(安卓版)北京微播视界科技有限公司https://developer.open-douyin.com/docs/resource/zh-CN/dop/operation-standard/service-protocol/douyinsdk_pingtaiyinsizhengce

2.2 SDK and Service Purposes

SDK or ServiceProviderPurposeInformation That May Be Processed
Core Location, Core Motion, Camera, Photos, system sharingApple Inc.Location, altitude, direction, pressure, capture, selection, saving, and sharingEnvironment information, media, and permission status you authorize or select
WeatherKit / MET Norway LocationforecastApple Inc. / Norwegian Meteorological InstituteNearby temperature, sunrise, sunset, and weather attribution on iOS and AndroidiOS query coordinates; Android coordinates reduced to an approximately one-kilometre grid, rounded altitude, time, and network information needed for the request
Google Mobile Ads SDK (iOS 13.7.0 / Android 25.4.0) and UMP (iOS 3.1.0 / Android 4.0.0)Google LLCiOS app-open and banner ads after privacy consent: UMP-managed normal ads when ATT is authorized and Limited Ads when it is denied or restricted; advertising privacy choices and ads in the Google Play versionNormal-path privacy-choice status and basic device, app, network, performance, and ad-interaction information; Limited Ads does not use IDFA or local identifiers and may process IP address plus cookies or local storage used solely for invalid-traffic detection
GroMore (iOS 7.6.1.8 / Android 7.6.4.3) and PangleBeijing Ocean Engine Network Technology Co., Ltd. and affiliatesApp-open and banner ads in the mainland-China iOS regional route and domestic Android aggregation; the Android Google Play version does not contain this SDKAfter consent, it may process basic device and network information, ad requests, and ad interactions. iOS always limits personalization and disables location, Wi-Fi BSSID, optional device-information upload, and motion sensors; it forbids IDFA when ATT is not authorized. Domestic Android OAID processing is described above
优量汇 Android SDK深圳市腾讯计算机系统有限公司Domestic Android aggregated ad delivery, frequency control, fraud prevention, and measurementAfter consent, it may process OAID, basic device and network information, ad requests, and ad interactions; it is not used for core features
AdAttributionKit / SKAdNetworkApple Inc.Privacy-preserving aggregate advertising measurementAggregate activation conversion value; no user or device identifier supplied by us
Ocean Engine attribution SDK (BDASignalSDK 2.0.0)Beijing Ocean Engine Network Technology Co., Ltd. and affiliatesAdvertising activation and valid-touchpoint attribution after privacy consent; ATT controls only the IDFA switchCallback data, click ID, cached open URL, touchpoint time, and required device/network information; IDFA is enabled only with ATT authorization and disabled in every other ATT state
NVPERPayBeijing Qijian Technology Co., Ltd.First-party operations reporting and ad-impression revenue measurement in the iOS and Android builds, plus receipt of valid iOS attribution touchpointsRandom user, installation, and session identifiers; app/system context; allowlisted events; ad revenue value, currency, estimation precision, format, mediation platform, and source; disclosed attribution fields when a valid touchpoint exists
Company feedback relayBeijing Qijian Technology Co., Ltd.Receive and route feedback you submitFeedback, optional contact details, app/system versions, submission time, internal random installation and app-user identifiers, and an anonymous App Auth token used only for server-side verification and never forwarded

Provider privacy information: Apple; Google; GroMore; Pangle; Ocean Engine.

3. Retention, Security, and International Processing

Local creations remain until you delete them, clear app data, or uninstall the app. Feedback, operations, ad-revenue, and attribution records are retained only as long as reasonably necessary for support, measurement, security, legal compliance, and dispute handling. Advertising providers retain information under their own policies. We use access controls, encrypted transport, credential isolation, and auditing to protect server-side information. We do not sell your personal information.

We are located in China, and Apple, Google, MET Norway, and their service providers may also process information outside the European Economic Area. Where required by applicable law, international processing relies on an adequacy decision, Standard Contractual Clauses, or another lawful transfer mechanism and remains limited to the purposes and data described in this policy. Feedback you choose to submit may be processed in China; the providers’ privacy notices and contractual safeguards govern their respective advertising and weather-service transfers.

4. Your Choices and Rights

You can view, edit, or delete creations; hide precise coordinates; and withdraw location, camera, Photos, motion, or ATT permissions in system settings. ATT controls only IDFA. When ATT is denied, restricted, unresolved, or withdrawn, the mainland-China route may still request limited-personalization GroMore ads without IDFA, other regional routes skip UMP and its cookie form and request Google Limited Ads, and Ocean Engine attribution continues its disclosed processing with IDFA disabled. Core features remain available. Choosing “Not Now” at first launch prevents the applicable NVPERPay, UMP, AdMob, GroMore, Pangle, and Ocean Engine attribution paths from starting. Where available after ATT authorization, you can reopen Google advertising privacy choices from About AltitudeNow. You may contact us to request access, correction, or deletion of feedback information, subject to identity verification and applicable law.

5. Users in the EEA, United Kingdom, and Switzerland

If you are in the European Economic Area, United Kingdom, or Switzerland, we process personal data under applicable data-protection law. Beijing Qijian Technology Co., Ltd. is the controller for the processing described in this policy. You can contact us at support@nvper.com.

5.1 Legal bases

We process information necessary to provide location, weather, capture, saving, sharing, and support features you request. We rely on legitimate interests for proportionate security, troubleshooting, and abuse prevention where those interests are not overridden by your rights and freedoms, and on legal obligations where applicable. On iOS, Google UMP is loaded only after ATT authorization and requests any additional consent required for advertising personalization, device storage or access, and other advertising processing. You may deny ATT or refuse or withdraw advertising consent without losing core features.

5.2 Your GDPR rights

Subject to applicable conditions, you may request access, correction, erasure, restriction, or portability of personal data; object to processing based on legitimate interests or direct marketing; and withdraw consent at any time. Withdrawal does not affect processing lawfully completed before it. You may also complain to the data-protection authority where you live. We may reasonably verify your identity to prevent unauthorized access and will respond to a valid request within 15 business days and no later than the applicable legal deadline.

5.3 Advertising choices and automated processing

After ATT authorization on iOS, the Google UMP message available in applicable regions offers “Consent,” “Do not consent,” and “Manage options.” You can reopen Google advertising privacy choices from About AltitudeNow when that option is available. Advertising partners may personalize ads or measure audiences according to your choices. We do not make decisions based solely on automated processing that produce legal or similarly significant effects on you.

6. Children

AltitudeNow is not directed to children below the minimum age required by applicable law. Children should use the app with a parent or guardian and should not publicly share a home address, school location, precise live route, or other sensitive location information. If we learn that we processed a child’s personal information without required authorization, we will delete it or take other legally required protective steps.

7. Policy Updates

We may update this policy when features, SDKs, data uses, or legal requirements materially change. We will provide an appropriate notice in the app or on this page and request consent again when required.

8. Contact

Controller and service provider: Beijing Qijian Technology Co., Ltd.
Email: support@nvper.com