SEEFOOD PILOT · UPDATED OCTOBER 26, 2026

App privacy

This notice covers the current SeeFood iPhone pilot. The public website has a separate website privacy notice.

What the app uses

Account information includes your email, name, sign-in provider, account role, and optional profile photo. Firebase Authentication manages sign-in, and Firebase stores account and restaurant information. Apple or Google also processes sign-in when you choose that provider.

Order information includes the items selected, amounts, order status, restaurant, customer contact details, pickup check-in and order messages. Customers and the assigned restaurant use these details to fulfill and discuss an order. Access is restricted to order participants and authorized SeeFood administration.

Payments

Live card payments are currently disabled. When enabled for an onboarded restaurant, Stripe processes payment details through its payment interface. SeeFood stores payment identifiers, statuses, totals, fees and related reconciliation records. Full card numbers are not stored in SeeFood’s restaurant or order database.

Device permissions and scans

Camera and motion access support AR viewing and dish capture. Original dish-capture photos and reconstruction checkpoints stay in local app storage; publishing uploads the selected model and preview image. Location access helps find nearby restaurants when you allow it. Notification permission and a device registration token allow order updates. You can change permissions in iPhone Settings.

Optional diagnostics

In the latest pilot build, app analytics and crash diagnostics are off by default. You can enable or disable them from Profile. These diagnostics help assess app reliability and usage; the latest build does not attach your account identifier. Earlier pilot builds enabled diagnostics automatically. Providers may retain historical operational records under their own retention controls.

Account deletion

Open Profile → Delete account. Confirm your identity and the permanent deletion. Unfinished orders must first be completed or cancelled. Deletion starts automatically without a support call. Sign-in access is disabled during cleanup; the profile, profile photos, saved account data, personal order details and associated private messages are removed. Completed payment, payout and audit records remain for reconciliation, with personal order fields redacted.

For restaurant owners, deletion closes their SeeFood listing and removes its public menu and uploaded dish scans. Account-associated local scan drafts marked by the latest build are cleared on the requesting device. Unassigned demo drafts or local data on another device may remain in that installation; removing SeeFood from that device removes its local app data. Deletion does not cancel an obligation to settle an existing order or financial balance.

Contact and controls

Questions about your information can be sent to seefoodarapp@gmail.com. Do not include card numbers, passwords or sensitive identity documents in an email.