1. Core Telemetry & Data Principles

This privacy declaration governs the technical data mapping workflows deployed across the cryptographic network nodes operated by MeteoAnalytics Pty Ltd (ABN: 48 702 682 282)

Our infrastructure architecture treats consumer operational parameters with absolute privacy guardrails. Unlike traditional web aggregators, WEATHER ENDPOINT™ explicitly avoids behavioral tracking, profiling tracking matrices, or the commercialization of client identity layers. We collect infrastructure metrics solely to uphold API service accessibility, coordinate request thresholds, and safeguard machine-to-machine data security.

2. Telemetry Ingestion & Inbound Logging Data

When software scripts ping our server channels via designated access tokens, our data validation loops log specific technical metrics within a centralized, secure system environment:

• Token Performance Metrics: Inbound X-Meteo-Client-Token keys are logged alongside active request counts to calculate strict maximum volume quotas.
• Spatial Search Parameters: Query data elements including localized coordinate inputs (Latitude/Longitude positions) are temporarily loaded by the database engine to return precise 1km grid spatial predictions.
• Network Handshake Logs: Standard request structures, system routing codes, timestamps, and server response logs are kept temporarily to maintain stability.

3. Secure Settlement Tracks & Financial Data Safeguards

All automated subscription accounting data layers are processed through isolated payment network channels. All transaction ledgers and statements resolve universally under the merchant identifier WEATHER.GS

• Merchant Vault Processing: Credit cards, Apple Pay, Google Pay, PayID, and Osko instant transaction tokens are transmitted securely directly via Stripe's encrypted API vaults.
• No Local Card Caching: MeteoAnalytics Pty Ltd never processes, parses, or caches raw corporate credit card strings, card verification codes, or bank account credentials on local file system databases.

4. Multi-Tenant Telemetry Guardrails & System Architecture

We enforce rigorous architectural data boundaries to protect query tracking strings and metadata records from internal or external visibility leaks:

Telemetry extraction pipelines are heavily sandboxed. Once a grid calculation task finishes and is securely signed via asymmetric validation codes, its cache layer logs are completely overwritten to guarantee absolute zero telemetry leakage.

5. Data Lifecycle Boundaries & Account Rights

Active developer tokens are retained for the duration of the active subscription cycle. Quota reset utilities parse database tables monthly to clear consumption limits back to zero. Developers can request immediate database node purges or account cancellations by contacting our centralized support terminal infrastructure.