Effective Date: July 27, 2026

MarkWare LLC (”we,” “us,” or “our”) built DinePilot as a restaurant-decision app for individuals, couples, and groups. This policy explains what information DinePilot handles and how.

Information We Collect

Data you enter. DinePilot stores the restaurants you add to “My Spots,” the rules and filters you configure, and your decision history, entirely to power the app’s core features.

Location data. If you use DinePilot’s restaurant search (Assistant), the app may request your device’s approximate location to find nearby restaurants via the Google Places API. Location is used only for that search and is not stored on our servers, because we don’t operate any servers that receive it.

Share Code data. If you choose to share your spots and rules with a partner or friend, that data is packaged into a code you send them directly (e.g., via Messages, email, or however you choose to share it). We do not have a server that stores, sees, or relays this data.

How Your Data Is Stored

Everything DinePilot stores — your spots, rules, and history — lives on your device. If you have iCloud enabled, this data syncs privately across your own devices via Apple’s iCloud service, governed by Apple’s Privacy Policy. We do not have our own servers or databases that store your data.

Third-Party Services

DinePilot uses the Google Places API to search for nearby restaurants when you use Assistant. Requests made through this feature are subject to Google’s Privacy Policy. No other third-party services are used.

What We Don’t Do

Children’s Privacy

DinePilot is not directed at children and does not knowingly collect data from children under 13.

Changes to This Policy

If this policy changes, we’ll update the effective date above. Continued use of DinePilot after changes constitutes acceptance of the updated policy.