This policy describes how the iOS app Pick and Peck (“the App”)
handles information. The App is an independent group restaurant picker.
It is not a third-party restaurant brand and is
not affiliated with Google.
Summary
No ads and no third-party analytics or tracking SDKs in the App as shipped.
You join a flock with an anonymous Firebase session plus a display name and emoji you choose. The App does not use Google Sign-In.
Location is used to find restaurants near the host pin (Apple MapKit is the default source).
Live flock state (group code, members, votes, preferences, thin restaurant stubs, and a few session timestamps such as when the host leaves the lobby) is stored in Firebase/Firestore so everyone in the flock can participate. We do not use Google Analytics or other tracking SDKs.
Restaurant cards and map images may be stored in Apple CloudKit’s public catalog for the App so later flocks can reuse place details. That catalog is not your personal iCloud Drive.
Optional Google Places lookups (off by default) use a developer API key for public place details. They do not access your Google account.
Optional tips use Apple In-App Purchase. Apple processes the payment; we do not see your card number. Tips do not unlock features.
We do not sell your personal information.
Information the App uses
Account / session — an anonymous Firebase user ID, plus the display name and emoji you enter. This is not a Google account.
Location — when you allow it, to search for restaurants near the host pin.
Flock activity — group code, ready state, lobby messages, votes, filters, thin restaurant identifiers, and coarse session timestamps (deck published, host left lobby, first swipe, results) needed to run and improve the session. Not a per-person screen recording.
Device settings — preferences such as whether optional Google Places enrichment is enabled in debug builds.
Google APIs
The App does not request Google user OAuth scopes (it does not ask for Gmail, Drive,
Photos, or your Google profile). If Google Places enrichment is turned on, the App may
call Google Places with a developer API key to look up public restaurant information
(for example a phone number or website). That is not signed in as you.
Pick and Peck’s use and transfer to any other app of information received from Google APIs
will adhere to the
Google API Services User Data Policy,
including the Limited Use requirements.
Firebase
Firebase Authentication (anonymous) and Cloud Firestore hold the live flock so members
can join, vote, and see results. Firebase is operated by Google. Google’s terms and
privacy policy apply to that infrastructure. We do not use Firebase for ads or analytics
in the App as shipped.
Apple MapKit and CloudKit
Nearby restaurant search and place details use Apple MapKit. Shared place cards and map
snapshots may be written to the App’s CloudKit public database so other users of Pick and Peck
can reuse them. Public CloudKit data is stored against the App’s container, not your personal
iCloud quota. Apple’s privacy policy applies to those services.
Website lookups
If a restaurant has a public HTTPS website, the App may fetch that page to read publicly
visible metadata (for example cuisine clues or a phone number). The App does not log you
into those sites.
Children
The App is not directed at children under 13. Do not provide personal information of children through the App.
Data retention and deletion
Leave or finish a flock to stop live session updates on your device.
Delete the App to remove remaining on-device data.
To request deletion of flock data associated with your anonymous session, email
rodrcode@gmail.com
and include the flock code if you have it.
Your choices
Decline location permission; you can still join a flock whose host already set a pin.
Do not enable Google Places enrichment (it is off by default).
Use a display name that is not your legal name if you prefer.
Third parties
Apple provides the App Store, iOS, MapKit, and CloudKit. Google provides Firebase and,
if enabled, Places. Restaurant businesses and their websites are independent third parties.
Their terms and privacy policies apply to those services.
Changes
This policy may be updated when the App’s data practices change. The “Last updated” date at the top will change accordingly.