YayMow Privacy Policy

Who we are

YayMow is operated by Pintcode, LLC. This policy describes how YayMow currently handles information when you use the app and related support services.

Information YayMow uses

• your device location when you allow foreground location access
• weather data returned for that location
• a lawn name you choose inside the app
• your units preference
• your appearance preference
• whether onboarding has been completed on the device
• your email address when you sign in for Mowing History
• mowing history entries you create, including date, time, lawn area, mower height when saved, duration, lawn condition if saved, clippings method if saved, and timezone

Location information

YayMow requests foreground location access so it can retrieve local weather and generate mowing guidance for your lawn. The app does not currently use background location tracking.

Depending on your device, operating system, and permission settings, the app may receive more precise or more approximate coordinates while you are using it. YayMow uses those coordinates to retrieve weather information for the area you choose to use with the app.

How weather requests work

When location access is available, YayMow sends latitude and longitude to a Pintcode-operated weather gateway. That gateway forwards the coordinates to Open-Meteo to retrieve forecast data used by the app.

YayMow uses the returned weather data to generate mowing guidance, recommended windows, Timeline guidance, and Forecast summaries. The app does not ship an Open-Meteo API key to your device.

Gateway and provider handling

The Pintcode weather gateway is not designed to persist lawn locations or build location profiles from forecast requests. Pintcode does not intentionally store forecast coordinates in a gateway database as part of the current architecture.

Forecast responses may be cached temporarily to reduce repeated requests and improve performance, reliability, and resilience. That temporary cache is generally short-lived and is not used as a persistent location-history or lawn-profile database.

Automatic Cloudflare Worker invocation logs are currently disabled for the gateway. As with most internet services, ordinary infrastructure and network providers may still process limited request information as needed to operate and secure their services.

Open-Meteo may process ordinary API-request information under its own terms and privacy practices. You can review Open-Meteo at open-meteo.com.

Information stored on your device

YayMow currently stores a small set of preferences locally on your device:

• home lawn name
• unit preference
• appearance preference
• whether onboarding has been completed
• a local working copy of your mowing history when you use Mowing History

These preferences help the app remember how you want YayMow to look and behave on that device. The mowing history copy helps add, edit, and delete actions feel immediate, including when sync needs to retry. YayMow does not currently store a saved physical Home Lawn address or coordinate profile in the app.

Account-backed Mowing History

When you sign in for Mowing History, YayMow stores your mowing log with your YayMow account using Supabase. This can include your email address, mowing activity entries, selected lawn area, mower height if saved, duration, lawn condition if saved, clippings method if saved, activity date and time, timezone, and sync information needed to keep entries consistent.

YayMow uses this information to provide Mowing History and account-backed save and sync. Mowing history is not sold and is not used for third-party advertising.

Older mowing records are saved when they move outside the recent history window shown in the app. Deleting a mow entry in the app removes it from your visible history and uses a deletion marker so sync can stay consistent across your account.

Accounts, advertising, analytics, and crash reporting

YayMow includes account sign-in for Mowing History. YayMow does not currently include advertising SDKs, third-party analytics SDKs, payment processing, or third-party crash-reporting SDKs. Product analytics are collected through a Pintcode-operated analytics service.

Analytics

YayMow collects limited information about how the app is used, such as which main screens are viewed and whether certain app features or controls are shown or used. This helps Pintcode understand feature usage, improve YayMow, and identify areas that may be difficult to discover or use.

Analytics events may include the event name, app platform, app version and build, screen or interface element names where applicable, and a temporary random session identifier created when the app launches. This identifier is kept only in memory for that app session, is not reused across app launches, and is not based on your device, account, email address, or another persistent identifier.

YayMow does not include location coordinates, weather values, lawn information, mowing-history records, account identifiers, email addresses, or user-entered content in analytics events.

Analytics events are sent to a Pintcode-operated analytics service and may be forwarded to Google Analytics for aggregate product analytics. The Pintcode-operated service does not persist event payloads or session identifiers or maintain an event backlog. Ordinary network infrastructure may process connection information, such as IP addresses, as needed to transmit and secure requests. Pintcode does not intentionally use that connection information to derive or store location for product analytics or forward an IP or location override to Google Analytics.

Google Analytics receives a temporary derived identifier rather than the app's raw session identifier. It does not receive an account ID, email address, advertising identifier, or persistent install identifier through this analytics service. YayMow uses this information for product analytics only, not for advertising, targeted advertising, cross-app tracking, or the sale of user information.

Third-party account and data storage

YayMow uses Supabase to provide account sign-in and account-backed Mowing History storage. Supabase processes account and mowing history information as needed to provide those services for YayMow.

Google processes forwarded product-analytics events as a service used by Pintcode for aggregate analytics. This analytics pipeline does not send Google your Mowing History, location coordinates, account identity, or weather values.

Data retention and deletion

Local preferences generally remain on your device until you change them, clear app data through device settings where supported, or uninstall the app.

Mowing History records are saved with your YayMow account when you sign in. Older records are saved, not deleted, when they move outside the recent history window shown in the app.

The Pintcode-operated analytics service does not retain event payloads or session identifiers. Product-analytics events forwarded to Google Analytics may be retained there according to the analytics settings managed by Pintcode.

You can delete individual mow entries in the app. Deleted entries are retained as deletion markers for sync consistency. To delete your account and account-backed Mowing History, see Delete your YayMow account. For account or data deletion questions, contact Pintcode using the address below.

Your choices

You can stop location sharing with the app by changing the YayMow location permission in your device settings. You can also remove the app from your device if you no longer want to use it.

Security

YayMow uses HTTPS for weather and analytics requests and stores device preferences using standard platform storage. No system can promise perfect security, but Pintcode aims to keep the service limited to the data needed for app functionality and product improvement.

Contact

If you have privacy questions about YayMow, contact Pintcode, LLC at [email protected].