Effective August 1, 2026

Privacy Policy

Big Beautiful Restaurant Log (“the app,” “we,” or “us”) is designed to keep dining history private. The app works locally without an account; optional circle syncing uses a developer-operated service described below.

Information the app handles

Depending on the features you use, the app can handle restaurant names and locations, meal dates, ratings, comparisons, dishes, notes, companions, photos, and restaurants you want to try. This information is entered or selected by you and is used to provide the app’s dining-history and ranking features.

Where your information is stored

On your iPhone

Your dining log is stored locally using Apple’s Core Data framework. Small preferences such as onboarding completion, haptic settings, and the selected circle are stored in app-scoped system preferences.

On the sync service

Circle syncing is optional and off until you turn it on. When it is on, every record and every photo is encrypted on your iPhone using AES-GCM before it is uploaded to the sync service, which is hosted on Supabase. The encryption key is created on your device and kept in the iOS Keychain, where it is included in your end-to-end encrypted iCloud Keychain so a replacement iPhone can still read your log. It reaches another member only inside a key envelope that their join code unlocks. The service never receives the key or the code, so the developer cannot read restaurant names, dates, ratings, dishes, notes, companions, photos, or the name of your circle.

The service does see the structure around that content: how many records a circle holds and of which kinds, when they changed, an app-generated device identifier, the size of each photo, and which accounts belong to which circle. Access to a circle’s rows is restricted by database row-level security to its members.

Circle syncing uses Sign in with Apple. Supabase Auth stores the Apple-derived account identifier and the email address Apple provides (which may be a private relay address) so it can authenticate the account. The refresh token is stored in the iOS Keychain. Supabase may process ordinary network metadata, such as IP address and user agent, to operate and secure the service. We do not use this information for advertising, profiling, or analytics.

Location

With your permission, the app uses approximate or precise foreground location to suggest nearby restaurants while you log a meal. The app does not request “Always” location access and does not track location in the background. Search terms and map coordinates may be sent to Apple through MapKit to return place results. Coordinates saved with a restaurant or meal may also be included in encrypted sync records when circle syncing is on; the sync service cannot decrypt them.

Photos

You may select meal photos using Apple’s system photo picker without granting the app access to your full photo library. An optional backfill scan can request read access to photos for a date range you choose. Photo analysis and grouping occur on-device. Copies stored by the app are re-encoded without embedded GPS or EXIF metadata; the original photos are not modified.

If you import a Beli data-export ZIP, the archive is parsed on-device. Restaurant names and cities may be sent to Apple through MapKit so you can review location matches. Photo URLs in the export are requested directly from Beli’s photo hosting service and processed on-device. Account, email, phone, device, follower, and social-profile fields in the export are not retained by the app or sent to the developer.

Sharing

Sharing is optional and initiated by you. An invited participant can see and edit records in the shared dining circle after opening your invitation. An invitation is a twelve-character join code. It can be typed into the app or tapped as a link that carries the code after the # fragment, which browsers do not send to this website. The code unlocks your circle’s encryption key, so send it directly to the intended person and never post it publicly. A code works once and expires after seven days. Do not add information about another person unless you have permission to share it with the circle. You can turn syncing off on a device, sign out, or remove a member at any time.

Analytics, advertising, and tracking

The app contains no advertising SDK, analytics SDK, third-party tracking SDK, or cross-app tracking. The developer does not sell, rent, or use your information for advertising or profiling.

Your choices and deletion

• You can decline or revoke location and photo permissions in iOS Settings.
• You can delete individual outings from their detail screens and remove restaurants that have no outings. Removing a restaurant also removes its Want to Try entry and comparison records.
• You can turn circle syncing off on a device, sign out, or remove a member in the app.
• An owner can permanently delete a circle’s encrypted records, photos, invitations, and memberships from the service while preserving the local log.
• You can delete your sync account and its owned service data in Settings. Memberships in circles owned by someone else are removed, while those circles remain for their other members.
• You can export a full local backup or erase every on-device record in Settings.

The developer cannot decrypt, retrieve in readable form, or export synced dining content because the service never receives the circle key. The in-app controls can permanently delete the stored ciphertext and photo objects. See the privacy choices guide for help.

Data retention

Local records remain until you delete them or erase the app. Synced ciphertext and photos remain until the circle owner deletes the synced copy or deletes the owning sync account. Removing a member removes access but preserves the shared circle for its remaining members. Expired and redeemed invitation records are removed with their circle.

Children’s privacy

Big Beautiful Restaurant Log is a general-audience dining utility and is not directed to children under 13. We do not knowingly create sync accounts for children under 13.

Security

The app relies on iOS application isolation, Apple’s Core Data and Keychain, AES-GCM encryption applied on your device, and database row-level security on the sync service. No system can guarantee absolute security, so protect your iPhone and Apple Account with a strong passcode and current security settings, and treat circle invitations as sensitive.

Changes to this policy

If the app’s data practices change, this page will be updated and the effective date will be revised. Material changes will also be reflected in the app’s App Store privacy disclosures.

Contact

For privacy questions or support, contact the developer through the Big Beautiful Restaurant Log support page or the public support request form. Please do not include private dining records, precise locations, or personal photos in a public request.