Privacy Policy

Lunch Loop is a meal-planning service operated by Craig Kohler (“Lunch Loop,” “we,” “us,” or “our”). Lunch Loop helps small, private groups take turns choosing a restaurant, record decisions, and maintain a shared restaurant database.

For privacy questions, requests to access or delete information, or questions about this policy, email support@lunchloop.app. Signed-in members may also use the Feedback link in Lunch Loop.

We collect only information needed to operate Lunch Loop:

• Account information: your email address, display name, profile image URL when supplied by Google, authentication provider, and a technical account identifier.
• Lunch Loop information: the groups you join or own, member display names and order, invitations (including an optional owner-only name label for a shareable invite), restaurant entries, decisions, vetoes, planned meal times, notes, and feedback you submit.
• Area information: a loop owner’s chosen city/area center, search radius, and time zone. Lunch Loop does not ask for or use your device’s precise GPS location.
• Restaurant information: place names, addresses, maps, hours, ratings, phone numbers, categories, and place identifiers returned by Google Maps Platform when a member searches or adds a place.
• Service and security information: limited request, device, browser, IP/log, and error information processed by the companies that host and protect Lunch Loop.
• Optional communications: invitation email delivery information and, if a loop owner enables it, Discord webhook configuration and the chosen Lunch Loop event messages.

Lunch Loop uses Google only to sign you in. We request the standard openid, email, and profile permissions. Through that sign-in, we receive basic profile information: your name, email address, profile-photo URL when Google provides one, and a technical account identifier.

We use that information to create and secure your Lunch Loop account, show who is participating in a loop, and let a loop owner tell members apart. A profile photo is stored as a URL provided by Google; Lunch Loop does not upload or host a copy of that photo as its own file.

Lunch Loop does not request or read your Gmail, Google Drive, Calendar, Contacts, Google Maps Timeline, or device location from Google.

Lunch Loop uses essential first-party authentication cookies from Supabase to keep you signed in and protect your session. We use ordinary browser caching for application files so the web app can load efficiently. We do not use advertising cookies, cross-site tracking cookies, or third-party analytics trackers.

We use this information to authenticate members; run the private group decision flow; search for and display restaurants; send invitations and optional notifications; provide exports, recovery, support, and feedback handling; prevent abuse; protect the service; and improve Lunch Loop.

We do not sell personal information or use it for targeted advertising. We do not request payment-card information in Lunch Loop.

Lunch Loop is intentionally collaborative. Members of the same loop can see the group’s display names, restaurant list, picks, vetoes, history, and related statistics. The loop owner can also see member account email addresses and authentication-provider labels in Settings so they can manage invitations and the roster.

Craig Kohler, as the service administrator, may access information when reasonably necessary to operate, secure, support, investigate abuse, or improve Lunch Loop. We do not make one group’s information available to another ordinary group.

We use trusted providers to run Lunch Loop:

• Google: Google Sign-In and Google Maps Platform, including Google Places and Google Maps.
• Supabase: authentication, database, and access-control services.
• Vercel: application hosting, delivery, and operational logs.
• Resend: invitation and operational email when email delivery is enabled.
• Discord: only when a loop owner voluntarily configures a Discord webhook.

These providers process information under their own terms and privacy practices. We may also disclose information when required by law, to protect people or the service, or in connection with a business transfer.

Lunch Loop uses Google Maps Platform to search for, display, and map restaurants. Your use of Google Maps features in Lunch Loop is also subject to the Google Terms of Service, the Google Maps Additional Terms of Service, and the Google Privacy Policy.

Google may receive information when you use Google Maps content, as described in Google’s policies. Google-provided restaurant information can change; we use and retain Google Maps Platform content subject to the applicable Google Maps Platform terms and policies.

Discord is optional and is enabled only when a loop owner connects a Discord webhook. When enabled for a selected event, Lunch Loop sends that Discord channel the relevant group activity, which can include display names, loop name, restaurant name, the planned day/date/time, and pick, veto, winner, schedule-change, or next-turn details. Discord then processes that information under its own rules and privacy practices.

The webhook URL is kept in Lunch Loop’s access-controlled database and is not shown back to the owner after it is saved. A loop owner can disconnect Discord at any time in Settings.

We keep account and active-loop information while it is needed to provide Lunch Loop. A loop owner can export, transfer, or archive a loop. Archived loops have a 30-day recovery window before permanent deletion becomes available. Invitations expire after 14 days unless they are accepted, revoked, or otherwise closed.

Leaving a loop is not the same as deleting an account. A member may ask the loop owner to remove them from a loop, or contact us for help. Removal ends future access to that loop, but past contributions—such as the display name attached to restaurant additions, picks, vetoes, and history—may remain in that loop’s historical record. Removing a member does not automatically delete their Lunch Loop account or information associated with other loops.

Personal-data export and account deletion are currently handled through support, not self-service buttons. To request account information or account deletion, email support@lunchloop.app. Before processing a request, we will explain how it affects any solo-owned loops, shared loops, active decisions, and ownership responsibilities. We are reviewing a clear, friend-readable export and self-service deletion experience before making either available.

Your feedback submissions are deleted with your account. We retain only basic security and usage records that are reasonably needed for support, safety, and service operations.

We use account authentication, row-level database access controls, server-side API keys, rate limits, and operational safeguards designed to protect Lunch Loop. No online service is perfectly secure, so please protect your Google account and do not share invitation links or one-time codes publicly.

Lunch Loop is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided us personal information, contact us so we can take appropriate action.

Lunch Loop is currently operated from the United States. If you use it from another country, your information may be processed in the United States and other places where our service providers operate.

We may update this policy when Lunch Loop changes. We will post the new effective date here and, when a change is material, provide additional notice in the app or by email when appropriate.