TodayWeather · 1.1.0 · 2026-10-01

Privacy policy

1. Operator and scope

The legal operator is 주식회사 플라잉. Privacy contact: 김동환, 제품팀 (Product Team). Contact: todayweather@wizardfactory.net. This document covers the Android/iOS TodayWeather app; TodayAir and web/PWA are excluded. Viewing weather requires no account or login.

2. Weather and location

We send coordinates, city/address searches and relevant settings to provide weather and air quality for current or selected locations. GPS coordinates are reduced to three decimals but can still represent precise location. Saved cities and units are stored on your device. You can search a city without GPS permission. Requests can involve IP address and environment logs and forwarding coordinates/addresses to weather or geocoding services.

3. Optional notifications

Notification services can associate a push token and device UUID with city coordinates, time, conditions, language and app version. These records are device-linked, not described as anonymous. We use Firebase Cloud Messaging and operating-system notification services. Removing permission or uninstalling does not immediately erase every server registration.

4. Optional analytics and withdrawal

The release candidate starts with usage analytics off. Explicitly choose Allow under “Optional usage analytics” in the app menu to enable Firebase Analytics. Data can include screen usage, weather outcomes/timing, saved-city changes, permission outcomes, ad diagnostics and SDK app/device/installation/session information. Custom events exclude actual coordinates, addresses, push tokens and UUIDs. Choose “Decline / withdraw” in the same menu to stop future collection. Weather remains usable. Earlier server data requires a separate deletion request and verification. Analytics advertising storage/use/personalization consent remains denied.

5. Ads and privacy choices

AdMob remains enabled. Advertising services can process ad interactions, approximate IP-derived location, identifiers and diagnostics for delivery, measurement and fraud prevention. Declining Analytics does not disable all advertising SDK processing. Open “Ad privacy choices” in the app menu; a form may not be required in every region. On iOS the app shows an App Tracking Transparency (ATT) explanation and the system permission prompt once per install. If you allow tracking, the device advertising identifier (IDFA) is used to show personalized ads and to measure ad performance; Apple defines this as tracking. If you do not allow it, you still see ads, but the app requests only non-personalized ads and keeps the publisher first-party ID off. Where consent is required, for example in the European Economic Area, personalized ads also need that consent. You can change the choice at any time in iOS Settings > Privacy & Security > Tracking. Analytics (Firebase Analytics) does not use the advertising identifier.

6. Diagnostics and configuration

Firebase Crashlytics can process crashes and device/installation diagnostics. Remote Config processes installation/connection information to deliver app settings. These services and notifications are separate from optional Analytics.

7. Support

Sending email provides your address, message and any environment attachments for support. The app can prepare app version, UUID and user agent in a draft you can edit before sending. Do not send passwords, payment details, raw push tokens or unnecessary precise location.

8. Providers and international processing

We use AWS infrastructure, Google ads/analytics/diagnostics/configuration/notification services and weather/location providers. Processing can occur outside South Korea. Actual recipient roles, countries, items, method, purpose, timing, retention and applicable basis must be verified against deployed services/contracts before the final document. We do not treat all transfers as processor-only simply because the recipient provides a service.

9. Rights and deletion

Send access, correction, deletion or processing restriction requests to todayweather@wizardfactory.net. We will identify related device records and verify authority with minimum necessary information. A UUID alone is not authentication; government identification and passwords are not routinely requested. Procedures to distinguish server registrations, provider data and backup handling are being prepared.

10. Retention proposal and effective date

The periods below are proposals, not verified current limits. Purpose completion, verified deletion requests, expiry, backups and any specific legal preservation requirements must be implemented and verified before finalization. Uninstalling does not mean all server records disappear. The effective date follows release/operational readiness; changes will be recorded here and, where needed, in the app.

11. Audience

TodayWeather serves a general audience and is not specifically directed at children. Final safeguards and store audience settings must reflect actual processing.

Proposed retention — not enforced yet

Request/error logs
90 days from creation
Analytics event/user-level data
2 months
BigQuery event exports
90 days from event date
Support email
1 year after resolution
Notification registrations
While enabled; remove upon unregister/verified request/invalid-token cleanup
On-device preferences
Until user removal/reset/uninstall
Other SDK data
Verify each service’s actual retention/deletion

Firebase privacy · Google privacy