Beta provider details
Google/Firebase provides authentication, saved account content/media, cloud processing, security and optional Product Analytics. Google Maps/Places processes map views, location and place searches under its own service practices. Optional Analytics is separate from operational, security and requested-feature traffic. Existing location permission can allow Maps entry to acquire location and load saved spots.
Supabase hosts weather and public-reference helpers and processes their requests and network metadata. These helpers are intentionally public reference services; a shared project key is not per-tester authentication. Public catalog search uses bundled data: publisher attribution does not mean each publisher receives your search text. Weather requests forward coordinates and forecast/astronomy parameters to Open-Meteo. Waterbody identification sends geographic selectors to USGS and may query public reference records, Illinois DNR services and an Overpass service. Those routes are configurable; the defaults identified in reviewed source are not independent verification of every effective operator. Public reference records, including contact and notes fields, are intended for public access.
Open-Meteo also receives supported location-search requests. A proxy does not anonymize coordinates. Its free-service notice describes coordinate-bearing technical/abuse logs and a 90-day deletion period; this is not a guarantee covering every endpoint or copy. Our retained permission covers development and the initial TestFlight beta, not later expanded commercial use. Reverse-label and astronomy route support remains unconfirmed; attempted requests can still disclose information even when a route returns no useful result.
Enabled map/reference requests include Google, USGS and configured state/ArcGIS services, USDA Forest Service Canopy Cover and ISRIC SoilGrids surface-soil services. Tile, bounds and point selectors reveal a viewed area, together with network information. Data publishers and service operators may differ. Coverage is partial where stated; modeled terrain, canopy and soil products are not current field measurements. Ownership boundaries are not permission to enter or pursue an activity.
Requested Plan, Guide, Feedback, follow-up and image processing sends relevant text, context/history and deliberately selected images through our backend to OpenAI. OpenAI processes API submissions under its applicable service and data-processing terms. We do not promise special project-specific retention protections. Conservatively, ordinary API abuse-monitoring retention may be up to 30 days with legal/safety exceptions, including image review. We do not promise ZDR, immediate deletion of provider copies, anonymity or a special project arrangement. App records and uploads have separate deletion handling. Declining AI processing is intended to prevent that requested AI transfer. Avoiding future submissions is separate from deleting historical records.
Optional Analytics can be declined or withdrawn in Settings. Withdrawal concerns future app Analytics collection, not all operational traffic or deletion of historical provider records. Apple processes TestFlight distribution and feedback; support email uses Cloudflare Email Routing and Gmail. User-selected external reference/navigation links are processed under the destination's practices.
Account deletion can remain pending verification. Completion is confirmed only after the required reconciliation; a pending message is not completed deletion. Beta costs are variable. No newly proposed daily submission, image or application spending cap has been activated or promised.