Privacy, explained clearly.

Who this policy covers

Global Weather 3D is operated by the developer identified on its App Store listing. In this policy, "we" and "us" refer to that developer. Questions or privacy requests may be sent to [email protected].

This policy applies to the Global Weather 3D website and to the iPhone app when its Cloudflare analytics feature is included in the build. It does not describe unrelated apps, websites, or services.

Your analytics choice

Usage analytics is off until you explicitly tap Agree on the in-app privacy page. Declining does not limit Weather features.

The consent page appears only after the normal globe scene has been visible for at least two seconds. It does not wait for Weather Information or another data layer to load. If you decline, the app may ask again on a later launch, but automatic prompts stop after three explicit declines. Merely seeing the page does not count as a decline.

You can change your choice at any time under Settings > Privacy & Data. Turning sharing off immediately stops measurement, erases unsent analytics, and requests authenticated deletion of selectable server-side records. If the network is unavailable, the app retains only the protected deletion command and retries it.

No analytics identifier, analytics report, App Attest enrollment, or usage metric is created before affirmative consent. If you later opt in again after withdrawing, the app creates a fresh identifier that is not linked to the old one.

What usage analytics collects

The app counts activity locally and transmits bounded daily summaries rather than an event for every tap, search, scrub, or layer change. Counts, durations, forecast ranges, response sizes, and latency values are placed into broad ranges before transmission.

Current summary families are:

• launch, session, and foreground-time ranges;
• feature exposure, use, success, and active-time ranges;
• activation and active-time ranges for the ten weather data layers;
• timeline opens, scrubs, playback, time jumps, and forecast-range use;
• numbers of searches, successful selections, unique selected cities, and saved-city additions, removals, and totals;
• allowlisted configuration states and configured-item count ranges;
• allowlisted weather-service request, cache-hit, failure, latency, and response-size ranges; and
• bounded cancellation, validation, network, availability, permission, and performance-fallback counts.

Each report also contains a UTC reporting day, app identifier and version, contract and consent versions, OS major version, device family (iPhone or iPad), bounded report identifiers, and a random analytics installation identifier. The random identifier is not an Apple ID, account ID, IDFA, or hardware identifier. It rotates every 90 days, and the server stores a one-way digest where installation-level association is required.

Apple App Attest is used to confirm that reports come from a valid instance of the app and to resist abuse and replay. Short-lived challenges, keys, tokens, deletion proofs, and security counters are processed only to authenticate reports, enforce limits, and honor deletion.

No experiment summary is currently accepted. Any future experiment requires a separately approved fixed registry and a policy and consent review before collection begins.

What analytics never collects

The analytics system does not collect:

• city names, place identities, search text, result identities, or saved-place identities;
• coordinates, precise location, location history, or hashes derived from location;
• weather request parameters, URLs, request or response bodies, or weather payloads;
• exact activity times, individual gesture streams, free-form text, error messages, or stack traces;
• names, email addresses, account data, contacts, photos, or other direct identity information;
• Apple advertising identifiers, cross-app identifiers, or advertising profiles; or
• payment, purchase, or other financial information.

We do not sell analytics, use it for advertising, combine it with third-party data for tracking, or share it with data brokers or advertising networks. We do not attempt to identify a person from the random analytics identifier.

Why usage data is collected

We use consented analytics to understand feature reach, frequency, depth, outcomes, friction, possible limit pressure, service cost, reliability, performance, and seasonal or release-period differences.

Anonymous aggregate trends help us improve the app. They help us understand feature usefulness, usability, reliability, and performance without observing a person's exact activity.

Analytics will not be repurposed for advertising, eligibility decisions, or unrelated profiling. A material change to the collected fields or purposes requires a new contract review, an updated policy, and a new in-app consent review where required.

Weather and location requests

Weather functionality is separate from usage analytics. To provide forecasts, maps, ocean conditions, air quality, precipitation, aurora information, and related layers, the app requests data from third-party weather and environmental services when the relevant feature is used.

Those functional requests may include coordinates, forecast parameters, and ordinary network information such as an IP address. When remote place search is requested, search text may be sent to a platform-operated search service. These services receive the information needed to return the requested result and operate or secure their systems. It is not inserted into the Cloudflare usage-analytics reports described above.

If you enable device location, iOS asks for permission. The app uses the permitted location to show relevant weather. Saved cities, app settings, and Weather caches are normal app data stored separately from analytics. Source acknowledgements and licence information are available on the website's Attributions page.

Retention

Retention limits are maximums, not minimums. Data may be removed earlier when you withdraw consent, when it is invalid, after an incident, when analytics is shut down, or when the data is no longer needed for the purposes described in this policy.

• Unsent daily reports expire from the device after 7 calendar days.
• Per-installation accepted reports and daily summaries expire no later than 90 days after their reporting day.
• Ingress and idempotency records expire after 14 days.
• Queue and dead-letter messages expire within 24 hours.
• Bounded operational records and diagnostics expire within 30 days.
• Thresholded, identifier-free population aggregates may be retained for up to 395 days.
• Cloudflare may retain limited aggregate security and operational metrics according to its platform policies.
• Production database recovery history may remain technically recoverable for up to 30 days, but it is not active analytics data and is not available to the app.

Automated maintenance enforces expiry. Retrying, aggregating, or restoring a record does not extend its original retention deadline.

Withdrawal and deletion

Turning analytics off in Settings > Privacy & Data deletes local unsent analytics and sends an authenticated deletion request. After the request is processed, installation-scoped analytics reports and associated authentication records are deleted or revoked.

Infrastructure backups may retain recoverable copies temporarily according to the service provider's retention policies. Aggregated statistics that no longer contain an installation identifier cannot be associated with or selectively removed for one installation.

Deleting the app removes local app data but does not reliably send a server deletion request. To request server deletion, turn analytics off in Settings before uninstalling. You may also contact [email protected] for help.

Service providers and international processing

Cloudflare provides hosting, security, and optional analytics processing. Apple provides App Attest. These providers process data on our behalf or provide security and platform services under their applicable terms and privacy commitments.

These service providers may temporarily process ordinary network and security information, such as an IP address, request time, browser or app details, and security signals, to deliver and protect their services. Source IP addresses are not included in product-usage summaries or identifier-free population aggregates. Service providers may operate infrastructure in multiple locations, so information may be processed outside your country subject to applicable contractual and legal safeguards.

Security and incidents

Controls include encrypted HTTPS transport, Apple App Attest, short-lived authorization, strict payload and metric allowlists, request-size and rate limits, pseudonymous rotating identifiers, bounded retention, deletion tombstones, least-privilege operational access, and monitored purge and abuse controls.

No system can guarantee absolute security. If a data incident creates a notification obligation, we will notify affected users or authorities as required by applicable law.

Your rights

Depending on where you live, you may have rights to request access, correction, deletion, restriction, objection, or information about processing, and to complain to a data-protection authority. Because analytics deliberately excludes direct identity data, we may be unable to locate a report without the protected deletion proof held by the app.

Use the in-app control for the fastest withdrawal and authenticated deletion. For other requests, contact [email protected]. We may need enough information to verify and fulfill a request without collecting unnecessary identity data.

Children's privacy

Global Weather 3D is a general-audience weather visualization and is not designed to collect direct identity information from children. Usage analytics remains off until someone using the device affirmatively agrees. If a parent or guardian believes a child has provided information contrary to this policy, contact us so we can review and delete eligible data.

This website

The website does not ask visitors to create an account and does not use advertising, product analytics, tracking pixels, or non-essential cookies. Cloudflare may process limited technical information, such as an IP address, request time, requested page, browser details, and security signals, to deliver and protect the site.

Policy changes

We may update this policy as the app, legal requirements, or service providers change. The effective date and policy version below will be updated. Material changes to app analytics will be communicated in the app and will trigger a new consent review where required before the changed collection begins.

Contact

Privacy questions and requests can be sent to [email protected]. Messages are forwarded securely to the project's monitored inbox.