What the app sees, and what stays on your phone.
The short version: Bitez is an on-device app. There is no Bitez server, no Bitez account, no Bitez tracking, no Bitez analytics, and no Bitez ads. The only times anything leaves your phone are when the app asks Google Places where the restaurants are, when it asks Apple WeatherKit about severe weather in your area, and when iOS itself sends Apple a crash report. Everything else stays local.
What stays on your device
The following data is stored only inside the Bitez app on your iPhone, using iOS's standard local storage (UserDefaults). It never gets transmitted anywhere:
- Your name (entered during onboarding).
- Your city or ZIP (entered during onboarding, optional).
- Your cuisine preferences and dietary preferences (chosen during onboarding).
- Your budget tier ($, $$, $$$, $$$$).
- Your distance preference (Walk, Nearby, Wider).
- Which restaurants you said "I'm going" to and which ones you skipped — used to learn your taste over time.
- The restaurants we've recently shown you — used so we don't keep recommending the same place every time.
- What you type into the free-text dish input ("curry, something hearty") — this is parsed locally by Apple's on-device LLM and never leaves your phone.
- A cache of restaurant data previously fetched from Google Places, so the app works fast and uses less data on subsequent opens.
What gets sent off your device — and to whom
1. Google Places API (New). When you ask for a restaurant pick, Bitez sends your approximate coordinates and your filter criteria (cuisine, price tier, search radius) to Google Places so it can return restaurants near you. The app does not send your name, your history, what you typed into the dish input, or any persistent identifier — only the data needed to ask "what restaurants exist around these coordinates with these characteristics?" Google's handling of that data is governed by their own privacy policy.
2. Apple WeatherKit. Bitez asks WeatherKit whether there is an active severe-weather alert at your coordinate, so that during a blizzard or hurricane it can refresh restaurant hours instead of trusting yesterday's cache. The coordinate goes to Apple. Apple's WeatherKit handling is covered by their Apple Weather Privacy Policy.
3. Apple Foundation Models (on-device). When you type something into the dish input field, Bitez uses Apple's on-device LLM to understand what you wrote. This model runs entirely on your phone. Your typed text does not leave the device. It is not sent to Apple, OpenAI, Bitez, or any third party.
4. iOS crash reports (only if you opt in). If you have "Share with App Developers" enabled in iOS Settings → Privacy & Security → Analytics & Improvements, iOS will send anonymized crash and hang reports to Apple, which the developer can access through Xcode's MetricKit. These reports contain technical diagnostic information (stack traces, memory state) — not your name, location, or app content. If you disable that iOS setting, nothing is sent.
What Bitez does not do
- No account. You don't sign up, you don't log in, you don't have a password.
- No analytics SDKs. No Mixpanel, no Amplitude, no Firebase Analytics, no Segment, no Sentry, no Branch.
- No advertising SDKs. No tracking pixels, no ad networks, no IDFA collection.
- No cross-app tracking. Bitez does not request App Tracking Transparency permission because there is nothing to track.
- No persistent identifier sent off-device. Your local profile has an internal random ID for app state, but it never goes off your phone.
- No selling, renting, or sharing of your data. The app has no business model that involves your data.
Location permission
Bitez requests Location When In Use so it can find restaurants near you in real time. You can refuse this and the app will fall back to your manually entered city or ZIP. You can revoke it at any time in iOS Settings → Privacy & Security → Location Services → Bitez.
Children
Bitez is rated 4+ on the App Store. The app does not knowingly collect any data from children, because the app does not knowingly collect data from anyone in a server-side sense. There is no Bitez database with user records in it.
Changes to this policy
If meaningful changes happen — for example, if Bitez ever adds a backend, an account system, or a third-party integration that handles user data — this page will be updated and the "Last updated" date at the top will reflect that. Material changes will also be noted in the in-app release notes for that version.
Contact
Questions, concerns, or feedback about this policy or how Bitez handles data — write to team.duocraft@gmail.com. Plain English, usually replied to within 48 hours.
Bitez · Published by Duo Craft · New York · 2026