Privacy

Clear about your data.

Effective date: July 11, 2026

Knowday isn't on the App Store yet. This policy describes how the app and this website handle data today — and it's honest about a couple of things we may add later.

The short version

• No account. You don't sign up, log in, or give us your name or email to use Knowday.
• Your location is used for a forecast and area label. Open-Meteo receives an area coordinate; Apple location and Maps services may receive a device coordinate or place-search text. Knowday adds no account or advertising identifier.
• No analytics today. The current app has no analytics or third-party crash SDK, and the website has no analytics or tracking scripts.
• We don't sell your personal data.
• We may add basic usage analytics and possibly ads in the future. If we do, we'll say so here first and update our App Store privacy details. (See "What might change later.")

What the app does with your data today

To tell you what today is good for, Knowday needs to know roughly where you are:

• With your permission, the app requests one Core Location fix when it needs a forecast; it does not continuously track your location. You can also search for a city or ZIP code instead.
• Before a forecast request leaves the app, Knowday rounds the coordinate to the nearest 0.01° — roughly 1.1 km latitude grid spacing, with a maximum rounding shift of about 0.56 km — and sends that area-level coordinate to Open-Meteo over HTTPS. This preserves the usefulness of Open-Meteo's highest-resolution regional models without sending raw GPS precision.
• Open-Meteo also receives ordinary network metadata needed to answer the request, such as your IP address. Knowday does not put location in request headers or a custom user agent and does not add a name, email, account, or device identifier.
• Apple's Core Location, reverse-geocoding, and Maps search services provide the device fix, broad city/region label, and city/ZIP results under Apple's privacy terms. Reverse geocoding is given the device coordinate; place search is given the text you enter.
• Knowday does not write the raw current-location fix to its stores. The purgeable forecast cache and widget snapshot carry the coarser 0.1° forecast/cache bucket, cached forecast, and broad city/region label.
• For manual-watering isolation, the app derives a SHA-256 token from a roughly 0.001° cell (about 110 m north/south). Only the opaque token is stored—not the cell or coordinate text. It is still treated as approximate location data. App and widget use the same token, and superseded Current Location tokens and their watering events are removed when relocation is observed.
• Saved places retain a random stable ID, selected place name, and source coordinate in local app settings so distinct saved places stay distinct. Renaming keeps the ID; deleting a saved place removes its manual-watering events from local and widget stores.

Local settings and widget data

The app's local UserDefaults record contains saved-place names, stable IDs and coordinates; selected location; pinned or hidden activities; unit, theme, clothing and onboarding preferences; and manual-watering events. A watering event contains a random event ID, time, amount, and either a saved-place ID or the opaque Current Location token.

Knowday's sandboxed App Group lets only the app and its widget extension share two files: the latest widget snapshot and a location-scoped manual-watering mirror. The snapshot includes the 0.1° cache bucket, broad label, cached forecast, selected settings needed to render the widget, the opaque location identity, and any retained manual-watering events. App Group UserDefaults holds only snapshot schema and freshness dates.

Manual-watering events in both local settings and App Group files use the same exact rule: events at the 15-day cutoff remain until they cross it; older events are removed the next time either store is read, written, or migrated and are never returned or rewritten. Old identity-less events are quarantined, never used for guidance, and use that same deadline. If neither the app nor widget runs after a cutoff, stale bytes cannot be pruned until the next access or app deletion. Explicit known-empty and unavailable states are preserved for current saved IDs. The current build implements no iCloud, CloudKit, or ubiquitous key-value sync. Apple-controlled device backups may include local app data depending on your backup settings; that is separate from app-level sync.

Third-party services

• Open-Meteo provides forecast data. The app sends the 0.01° area-level coordinate in an HTTPS query. Open-Meteo receives normal transport metadata, including IP address, and handles it under its own terms and privacy information at open-meteo.com.
• Apple location and Maps services provide location authorization and fixes, reverse geocoding for the broad area label, and city/ZIP search results. Those services may process the device coordinate or search text under Apple's privacy terms.

What might change later (told honestly, up front)

We want Knowday to get better, and to keep it sustainable. So we may, in the future:

• Add usage analytics / telemetry to understand how the app is used (for example, which features people rely on and where the app is confusing), and
• Show advertising.

If we do either, it could involve things like device identifiers, usage data, and third-party analytics or advertising tools. We're disclosing this now so it isn't a surprise. Before we turn any of it on, we will update this policy and update the privacy information shown on our App Store listing, and — where it applies — give you a way to opt out (see "Your choices"). We are not doing these things today.

App Store privacy details — how we answer the questionnaire

This is the conservative, honest mapping we use for Apple's App Privacy questions, for the current (pre-analytics, pre-ads) build.

Children

Knowday is not directed to children under 13, and we don't knowingly collect personal information from children under 13.

Your choices

• Location: you control Knowday's location permission anytime in iOS Settings → Privacy & Security → Location Services, or skip it entirely and enter a city / ZIP instead.
• Saved places and watering: deleting a saved place deletes its associated manual-watering events from the app's settings and App Group stores. Deleting the app removes its installed local containers; Apple-controlled backups follow your Apple backup settings.
• Analytics / ads (if and when added): if we add usage analytics or advertising, we'll provide a way to opt out at that time and explain it here. Until then, there's nothing to opt out of.

Data retention & where processing happens

• Saved places and preferences remain in local app settings until you remove them, reset app data, or delete the app. A saved-place deletion also deletes its watering events.
• Manual-watering events older than fifteen 24-hour periods from event time are removed on the next local/App Group read, write, or migration and are not returned or rewritten. Legacy unassigned events use the same deadline. With no app or widget execution, physical cleanup waits for the next access or app deletion.
• Only one active opaque Current Location watering identity is retained. A new observed Current Location cell replaces the prior identity and deletes its events; saved-place stable IDs are unaffected.
• Up to eight area-level forecast snapshots may be cached in the app's purgeable Caches directory. They are replaced, evicted by least-recently-used capacity, purged by iOS, or removed with the app; there is no fixed time guarantee.
• The latest area-level widget snapshot remains in the App Group until replaced, deleted with its bound saved location, or removed with the app. Manual-watering events inside it still receive the 15-day pruning above.
• Knowday does not run its own forecast server. Open-Meteo handles forecast requests and normal transport metadata under its own terms and privacy policy; Knowday does not control or claim that provider's retention period.

This website

Our marketing site (knowday.app) currently uses no analytics. If we ever add privacy-respecting, cookieless analytics — aggregate page-view counts only, with no profile of you — we'll update this page first.

Changes to this policy

If we change how we handle data, we'll update this page and change the effective date at the top. For meaningful changes (like turning on analytics or ads), we'll update our App Store privacy details too.

Contact

Questions about privacy? Email [email protected].