Privacy Policy
This policy explains how Private Bite handles user information.
1. Overview
Private Bite has no login system and no developer-operated server for storing app data. Meal records, restaurant and dish names, ratings, prices, notes, saved photos, and settings are generally stored on the user's device and are not accessible to the developer.
2. Photos and location
If a selected photo contains GPS data, the app uses it to suggest a restaurant, city, and country. The saved copy is re-encoded without GPS EXIF metadata. Extracted latitude and longitude may be stored on the device as part of a record saved by the user.
Current location is used when the user requests map positioning or recommendations from the user's own records near the current location. It is not collected continuously or used for advertising, tracking, or profiling.
3. External services
Apple MapKit and CLGeocoder: Coordinates or search text may be processed by Apple when looking up an address, city, or nearby restaurant. Apple's Privacy Policy applies.
OpenStreetMap: Map tiles are requested only when the map screen is opened. OpenStreetMap Foundation may process IP address, User-Agent, and tile coordinates representing the viewed area. The app does not send complete meal records, photos, ratings, prices, or notes to OpenStreetMap. See its Privacy Policy and Tile Usage Policy.
Frankfurter API: The app sends the date, source currency code, and target currency code to obtain an exchange rate. It does not send restaurant or dish names, photos, ratings, notes, or the entered price. The service provider may process general connection information, such as the IP address, when the request is made. See the service information.
Google Maps: Only when the user chooses "Open in Google Maps," the app passes a restaurant name, city, or coordinates to the Google Maps app or browser. Google's Privacy Policy applies.
4. Sharing and backups
Only when the user starts sharing does the app pass selected text and images to the iOS share sheet. Only when the user exports a backup does the app pass a JSON file containing records, photos, categories, and settings to a destination chosen by the user. The terms and privacy policies of the chosen services apply.
When you use the CSV import feature to add records, the CSV file is parsed entirely on your device and is not sent anywhere. Only if you choose currency conversion on the confirmation screen are the date and currency codes sent to obtain an exchange rate, using the same Frankfurter API request described in "3. External services."
5. Retention and deletion
On-device data remains until the user deletes records in the app or deletes the app. Backup files are controlled by the user at the chosen destination; the developer cannot view, delete, or recover them.
Support emails are used to respond and review support history. Unless retention is required by law or for security, they are deleted within 12 months after the request is resolved.
6. Changes and contact
This policy may be updated when app features or external services change. The last-updated date will be revised.