Weatherly Diary Privacy Policy
DJ (디제이), represented by Dongjun Choo (추동준), operates Weatherly Diary. Dongjun Choo is the privacy contact. Send access, correction, processing-restriction, deletion and privacy requests to studio@cdjstudio.xyz. Do not send passwords, verification codes, card numbers or raw payment tokens.
1. Local records and optional transfers
Tasks, schedules, memos, diary entries, outfits and photos are managed on your device by default. When you consent to an encrypted connected workspace, supported text records and settings, and separately selected AI conversations and memories, can be synchronized. Photo files are not included in general cloud backup. Images selected for AI analysis, support attachments and sharing are separate transfers. Check your records and recovery options before removing the app.
2. Information and purposes
| Information | Purpose and scope |
|---|---|
| Location coordinates, approximate grids and place queries | With the relevant consent and OS permission, coordinates support weather and geocoding requests. Server-derived location caches use two-decimal grids. You can also choose a place manually. Not permanently storing raw coordinates in a dedicated database column does not mean all external request logs are absent. |
| Installation, device, workspace and reward-wallet identifiers | Authentication, device linking, request limits, restoration and abuse/duplicate-reward prevention. Pseudonymous identifiers may be associated with accounts or grants. Native wallet credentials use secure storage; server credential verification uses hashes. |
| Optional display name, device/OS/app versions, interactions and diagnostics | Personalization, compatibility, reliability and abuse prevention. A real name is not required. Your chosen name and necessary record context can be included in AI requests. |
| Tasks, calendar events, memos, diary entries and AI conversations | Local records, calendars you connect, optional encrypted synchronization and selected AI requests. Granting OS calendar access does not itself publish every event. Your selected import, integration and AI-context scope applies. |
| Selected photos, short videos and screenshots | Calendar/memo import, AI analysis and support when you choose to send them. Asynchronous requests and results may use private server storage. Review AI suggestions before saving. |
| Optional mail and selected-app notification content | When you enable the relevant connection or notification access and AI-summary feature, necessary mail or selected-app notifications may be included with schedule/task context in the summary request. Only the scope of your enabled connections and selected features applies. |
| Weather feedback, support messages, attachments and optional reply-notification tokens | Feedback and customer support. Support images may be re-encoded with EXIF/GPS metadata removed before private storage. APNs/FCM tokens are registered when you opt into reply notifications and permit them in the OS. Support message bodies and attachments are not included in push payloads. |
| Purchase, subscription, restoration and original paid-app evidence | Store, product and transaction identifiers, verification status/timestamps, installation associations and proof hashes support entitlement verification, restoration and refunds/revocations. Apple or Google processes payment; the app does not receive card numbers. |
| Legacy-purchase reward ledger | Verified purchase-identifier hashes, original purchase date/version, wallet links, grants, balances, redemption requests, permanent skins and announcement history. Raw Apple JWS is not stored in the reward ledger or printed in logs. Google eligibility uses reviewed historical paid-download evidence, not installation date or current licensing alone. |
3. Retention and deletion
Purposes and cleanup rules differ by information type. External-provider request, security and payment logs, and legally required records, have separate rules. There is no universal automatic-deletion period.
- Inactive derived location records have a 30-day cleanup rule. Withdrawing location consent clears associated location projections.
- Raw operational heartbeats have a 45-day rule; latest installation state uses 180 days of inactivity. Location-consent-change evidence uses 1,095 days and weather feedback 90 days.
- Asynchronous AI/calendar-import jobs have a 24-hour expiry rule. Some synchronous analysis does not retain the input image in app-owned D1/R2. This is not a promise of immediate deletion for all AI paths or every external provider.
- Leaving a support conversation hides it while retaining its history. Explicit content deletion verifies ownership, removes private attachments and scrubs content and relevant credentials. Partial storage failures may require retries. Minimal pseudonymous operational records or separately delivered email copies may not disappear immediately.
- Purchase/subscription information is retained as needed for verification, restoration, disputes and applicable legal obligations. The stores retain their own payment records under their policies.
- The reward ledger has no automatic expiry. Grant/redemption history and purchase-identifier hashes are retained for permanent-skin restoration and duplicate prevention. Support handles deletion requests after ownership checks and explains credential/link removal, effects on balance/skin restoration and any necessary retention. Uninstalling or signing out does not automatically erase the ledger or generate another grant.
- Local records and native secure caches are affected by app/OS deletion actions. Android reinstallation can remove recovery credentials; check connected-device/recovery options first.
4. External providers and international processing
When you use an online feature, necessary information can be transferred through HTTPS to overseas providers and their processing infrastructure. A provider's corporate location is not a guarantee of the country of every processing or storage server. Global routing and subprocessors can change the countries involved.
| Provider / location information | Information, purposes and retention |
|---|---|
| Cloudflare, Inc. — a US company operating a global network | API traffic, identifiers/diagnostics, optional encrypted sync, support/attachments, asynchronous AI jobs and purchase/reward ledgers use Workers, D1, R2 and related infrastructure. App-owned retention rules are in section 3. Infrastructure/security logs and subprocessors are described in Cloudflare's privacy policy and data-processing terms. |
| OpenRouter and routed model providers — overseas infrastructure, including the United States | Selected AI requests, conversation context, names, schedules, memos, attachments and optional mail/notification summaries. App AI routing requests no provider data collection and zero-data-retention endpoints. This does not mean app-owned asynchronous storage or OpenRouter usage/security metadata is never retained. Model processing providers can vary by request. See the privacy policy and data-processing guide. |
| MET Norway — Norway; OpenWeather — United Kingdom; Open-Meteo — Switzerland | Necessary coordinates, queries and request information support weather, air quality and geocoding. Provider service/log policies differ. Open-Meteo describes a 90-day individual API-log cleanup policy. See MET Norway, OpenWeather privacy and Open-Meteo terms/privacy. |
| OpenStreetMap/OSM services and Windy maps | Opening map features may send map areas, tile/place requests and connection information to the relevant service. OSM describes UK/Netherlands storage, EU backups and a global tile-cache network; individual service paths differ. See OSM privacy and Windy privacy. |
| Apple and Google — overseas store, account and notification infrastructure | Selected sign-in, purchase/restoration verification, and APNs/FCM token/delivery processing. Payment retention and account/device services follow Apple's and Google's policies. |
You can decline international processing by not using or disconnecting the relevant online features, including location, cloud connections, AI analysis/summaries, external maps and optional notification/account connections. Those online features will then be limited; local records can be managed separately. Contact support for access/deletion of previously transferred information or to identify the provider involved in a request. Processor use, user-initiated transfers and a store's definition of third-party sharing are not identical concepts.
5. Permissions, security and choices
Location, camera/photos, calendars, notifications and optional connections follow feature-specific explanations, consent and OS permissions. You may choose a place without current-location access. Connected devices/web sessions can be disconnected; disconnection is not the same as server-data deletion.
App-owned network requests use HTTPS and server records have ownership/operator access controls. Encryption and pseudonymization do not make all processing anonymous or uncollected. The app does not use information for advertising or tracking across other companies' apps/websites. Recipients or sharing services may independently retain information you choose to share.
6. Rights and changes
Send access, correction, deletion or processing-restriction requests to studio@cdjstudio.xyz. After minimum ownership verification, support explains the scope, restoration consequences and any separate retention obligation or processing limitation. See deletion instructions.
The app is not designed for children. Applicable guardian-consent requirements must be followed where relevant. Material changes will be announced with their effective date and scope. Weather and AI results do not replace medical, legal or safety decisions.