Meteric is a weather app for iPhone and Apple Watch. This page explains, in plain language, what data it uses and - just as importantly - what it doesn't.

How Meteric works

Meteric fetches forecasts, observations, radar, warnings, air quality, satellite imagery and webcam images directly from Slovakia's SHMÚ (Slovak Hydrometeorological Institute), Czechia's ČHMÚ (Czech Hydrometeorological Institute, for Czech radar), the EUMETNET OPERA European radar composite, EUMETSAT (European lightning), NOAA / National Weather Service (US radar and alerts), Windy (webcams), Open-Meteo, and MeteoAlarm. These requests go straight from your device to those providers.

Airport observations (METAR). When no fresh SHMÚ station reading is available (and abroad), the app asks our server for the nearest airport's latest report. For that it sends the place's coordinates and ground height - nothing else. The server answers from a copy of the public METAR feed of NOAA's Aviation Weather Center, so your location is never passed on. You can turn this off in Settings → Data source.

Meteric also has an optional companion server, MetericCast, which keeps the precipitation Live Activity up to date (and ends it when rain stops) even while the app is suspended in the background - something the app can't do on its own, since iOS stops running it shortly after you leave it. MetericCast is an integral part of Meteric operated by us; it is not a third-party service. When MetericCast is enabled, the app sends it the minimum it needs to push those updates (described below). If MetericCast is turned off, the app falls back to on-device-only evaluation and stops sending anything for the nowcast.

One other feature talks to the same server, independently of that setting: the European radar. Outside Slovakia and Czechia, radar frames come from the EUMETNET OPERA composite, which our server fetches, reprojects and colours before the app downloads the finished images. Those requests ask for a product and a frame identifier only - they do not include your location - but like any web request they do reveal your IP address to our server. This happens whenever you open the radar screen at a European location, whether or not MetericCast is enabled.

What the app sends to the MetericCast server

When MetericCast is enabled, the app sends the following to our server so it can recompute the radar nowcast and deliver Live Activity push updates:

• Push tokens - the Apple-issued Live Activity and push-to-start tokens needed to address update/end pushes to your device, plus the standard APNs device token used for silent background refresh nudges
• Location - your latitude and longitude (so the server can fetch the right radar data for your area) and your city name (so the Live Activity can display it)
• Display preferences - language, 24-hour clock, and whether precipitation is shown as snow - used only to format the pushed Live Activity content
• A stable per-install device identifier - so the server can correlate your push tokens with your running Live Activity (e.g. avoid starting a duplicate activity). This is a random UUID generated on first launch; it is not tied to your Apple ID or device hardware
• A usage ping - at most once an hour, when any part of the app runs (the app, a background refresh or a widget), it sends only that same identifier, so we can count how many devices use Meteric. It contains no location, screens, taps or content, and is never shared

The server keeps these tokens and the associated location on disk so it can keep pushing updates until the activity ends or you disable MetericCast, at which point the app tells the server to stop and unregister them. The server also fetches radar data from SHMÚ for your location to compute the nowcast - that request comes from our server, not from your device.

Location

If you choose to use your device's location (instead of picking a city manually), Meteric asks iOS for permission in the usual way and uses your coordinates for two purposes: to request weather data from the providers above, and - when MetericCast is enabled - to send to our server so it can compute the radar nowcast for your area. Your location is never sold or shared with advertisers.

What's stored, and where

Your preferences - selected location, temperature/wind units, language, display settings - are stored locally on your device using Apple's standard local storage (UserDefaults), shared privately between the app, its widgets, and your Apple Watch via an App Group container that only Meteric can access. This data never leaves your devices. The MetericCast server separately stores the push tokens and location described above, only while MetericCast is active.

Purchases and subscriptions

Meteric Premium is sold through Apple's App Store using StoreKit. Payment is handled entirely by Apple - we never see or receive your card details, billing address, or Apple Account credentials, and none of that ever reaches our server.

Whether you have an active subscription is checked on your device, by asking StoreKit what your Apple Account is currently entitled to. That answer is used locally to decide which features are unlocked, and it is shared privately with Meteric's own widgets and Apple Watch app through the same App Group container as your other preferences. It is not sent to the MetericCast server, and there is no account to create - we have no user database and no way to link a purchase to a person.

Apple provides us with aggregated, anonymous sales and subscription reports in App Store Connect (for example, how many subscriptions were active in a country last month). These contain no information that identifies you. Apple's handling of your purchase is covered by Apple's Privacy Policy.

The terms that apply to a purchase - billing, renewal, cancellation and refunds - are in the Terms of Use.

Apple Watch

If you use the Apple Watch app, your iPhone sends weather data (and, for the radar feature, map imagery it renders itself) to your watch using Apple's WatchConnectivity framework. This stays entirely between your own paired iPhone and Apple Watch. The watch app can also fetch the freshest observation directly from SHMÚ (or Open-Meteo abroad) so its complications stay current - the same public feeds the iPhone app uses.

Feedback and bug reports

"Request a feature" and "Report a bug" (in Settings) submit your message through the MetericCast server, which creates a page in our Notion workspace so we can track it. Your email address (so we can reply) and your message are sent; bug reports also include a read-only stats block (app version, iOS version, device model, language, units and selected city) to help us reproduce the issue. The Notion integration secret lives only on the server - it is never in the app.

Screenshots. You can attach up to three screenshots to either kind of report. They are only ever the images you pick yourself - the app has no access to the rest of your photo library, and nothing is attached unless you choose it. Each one is resized on your device before it is sent.

The diagnostic log attached to bug reports. Every bug report carries the app's recent diagnostic log, because without it most reports can't be acted on. It is shown in full in the compose screen before you send, and it contains more than the stats block above: your coordinates and the place/weather-station names in use, your location-permission setting, the per-install identifier described earlier, and a timestamped list of the app's recent internal events (data refreshes, widget and watch updates, background wake-ups, errors). It contains no message content, contacts, browsing history, or anything from other apps. If you would rather not send it, use the e-mail address on this page instead of the in-app form.

A copy of each submission is also emailed to us, so a report can't be lost if the connection to Notion fails. That email contains the same information you sent - your email address, your message, any screenshots, and (for bug reports) the stats block and diagnostic log - and goes only to our own inbox.

Reports, including their attachments, stay in our Notion workspace and inbox until we have dealt with them; we delete a report on request - just reply to the confirmation e-mail or write to us.

Server logs and abuse prevention

Like any web server, our server records a short log entry for the requests it receives: the IP address the request came from, the time, the path, and the response status. We use these logs only to keep the service running and to protect it - for example, to limit how often a single source can submit feedback, and to block repeated password guessing against our own admin tools. Recent entries where a limit was hit are visible to us in an internal dashboard.

These logs are kept briefly and then deleted automatically: our web server's access logs are rotated after 14 days, and the application's own logs roll over once they reach a fixed size. IP addresses are not stored alongside your push tokens or location, are not used to build a profile of you, are never combined with the app data described above, and are never sold or shared. Under the GDPR we rely on our legitimate interest in the security of our network and service (Recital 49).

What the app doesn't do

• No user accounts, sign-in, or passwords
• No analytics, crash reporting, or advertising SDKs in the app (the hourly usage ping above goes only to our own server)
• No tracking across apps or websites
• No selling or sharing of data with advertisers
• No third-party dependencies of any kind - Meteric is built entirely on Apple's own frameworks

This website

This website (the page you're reading now) uses a self-hosted, cookieless analytics tool that we run on our own server - not a third-party service. It doesn't set tracking cookies, doesn't collect your IP address or anything else that identifies you individually, and only records aggregate information such as which page was visited, the referring site, browser/OS, and country. This applies to the website only - it has no connection to the app or the data described above.

Third-party data providers

Requests the app (and, for radar data, the MetericCast server) makes to the services below are subject to those services' own privacy practices, since they operate independently of Meteric:

• shmu.sk - Slovak Hydrometeorological Institute (observations, forecasts, warnings, Slovak radar)
• open-meteo.com - Open-Meteo (worldwide forecast, air quality, pollen, geocoding)
• meteoalarm.org - MeteoAlarm (warnings outside Slovakia)
• aviationweather.gov - NOAA Aviation Weather Center (airport METAR observations, fetched by our server only)
• opendata.chmi.cz - Czech Hydrometeorological Institute (Czech radar; requested by the app directly)
• EUMETNET OPERA - European radar composite, via Open Radar Data under CC BY 4.0 (requested by our server, not by your device)

Feature requests and bug reports are forwarded to Notion for tracking; see Notion's privacy policy.

Children's privacy

Meteric isn't directed at children and doesn't knowingly collect personal information from anyone, of any age - see above.

Changes to this policy

If this policy changes, we'll update this page and the "last updated" date above.

Contact

Questions about this policy: bajzath.jakub@gmail.com