PECKISH
South Florida
PECKISH
South Florida
HomeDinersRestaurants

Peckish information

Clear, current, and written for people

Privacy Policy

How Peckish handles waitlist, account, restaurant, order, payment, location, support, and allergy-related information.

Last updated: July 31, 2026

Need help with Peckish?

Support covers accounts, privacy, orders, restaurant tools, and allergy-information questions.

Visit Support
01

Overview

Peckish provides food discovery, allergy-aware dining information, restaurant ordering, and restaurant-owner tools. This Privacy Policy explains how Peckish handles information through the public website, waitlist, iOS app, ordering features, support channels, and restaurant dashboards.

02

Information we collect

  • Waitlist details such as name, email address, launch city, and whether you are joining as a diner or restaurant owner.

  • Account details such as name, email address, phone number, preferred language, profile preferences, saved restaurants, and sign-in identifiers.

  • Health and dining profile information you choose to provide, including food allergies, allergy caution settings, dietary preferences, religious food preferences, custom avoidances, dining-relevant medical notes, and emergency-card settings.

  • Address, city, map, and location information used for distance estimates, checkout, and restaurant discovery when you provide it or grant permission.

  • Order, cart, menu customization, payment status, wallet summary, review, dining note, support request, content report, blocked-account, and account-deletion information.

  • Restaurant listing, menu, kitchen-practice, cross-contact, owner-dashboard, application, order, review, and support information submitted by restaurant owners or operators.

  • Public business information about potential restaurant partners, such as business name, business contact details, website and menu availability, licensing context, source URLs, and observation dates.

  • Device, browser, usage, diagnostics, IP-derived security signals, and audit events needed to operate the service, improve reliability, enforce rate limits, and prevent abuse.

03

How we use information

  • To operate the waitlist and send launch-related updates.

  • To personalize restaurant and menu discovery, including allergy-aware context when users choose to provide allergy information.

  • To support ordering, wallet setup, payments for real-world food orders, restaurant listings, dashboard tools, and customer support.

  • To moderate reviews, process reports, let users block review authors where public reviews are enabled, and investigate support or safety issues.

  • To improve security, prevent abuse, debug issues, understand product performance, enforce agreements, and comply with legal obligations.

  • To research potential restaurant partners using public business sources, prepare founder-reviewed business outreach, honor do-not-contact requests, and prevent duplicate or excessive contact.

04

Allergy information

Allergy, medical, religious, and emergency-contact information can be sensitive. Peckish uses this information only to provide features such as personalized allergy guidance, factual allergy marks, order notes, and the Dining & Emergency Card. Peckish does not sell personal allergy profiles. Allergy-related features are informational support only and do not replace professional medical advice or direct confirmation with a restaurant.

05

How information is shared

  • Restaurants receive the order, customization, pickup or delivery, and selected allergy or dietary context needed to review and fulfill an order. Do not include unrelated medical information in an order note.

  • Service providers process information only for hosting, authentication, payments, messaging, maps, monitoring, moderation, and other services Peckish directs them to provide.

  • Peckish may disclose information when required by law, to investigate fraud or security incidents, to protect users and the service, or as part of a business transaction subject to appropriate safeguards.

  • Peckish does not sell personal information or personal allergy profiles and does not use sensitive profile information for cross-company advertising.

06

Service providers

  • Peckish may use trusted service providers for hosting, database storage, authentication, payment processing, messaging, analytics, maps, error monitoring, email, SMS, and operational support.

  • Providers used or enabled by Peckish may include Supabase, Vercel, Stripe, Apple services such as Apple Pay, Sign in with Apple and MapKit, Google Sign-In, Sentry, and email or SMS delivery providers.

  • These providers may process information only as needed to provide their services to Peckish.

  • Peckish does not use service providers as permission to sell personal allergy profiles or payment information.

07

Data retention and security

  • Account and profile information is kept while the account is active and is deleted through the signed-in deletion flow, except for records Peckish must retain for payment, tax, fraud, dispute, security, or legal purposes.

  • Waitlist information is kept until launch communications are complete, the person unsubscribes, or deletion is requested, subject to suppression records needed to honor opt-outs.

  • Restaurant prospect research is refreshed or removed after 12 months when unused. Source, approval, and send records may be retained for four years, while suppression records are kept as needed to honor do-not-contact choices.

  • Orders are deidentified after account deletion. Allergy and dietary handoff details, separate-preparation context, and item instructions are removed, while transaction, refund, tax, and dispute records may be retained for the period required by applicable law or payment-provider rules.

  • Security, rate-limit, moderation, support, and audit records are retained only as long as reasonably needed to investigate abuse, protect accounts, resolve requests, and meet legal obligations.

  • Peckish uses access controls, row-level security, encryption in transit, server-side payment processing, audit logs, and other safeguards. No online service can guarantee absolute security.

08

Your privacy choices

  • You may request access, correction, or deletion of personal information where applicable.

  • You may opt out of marketing messages where supported by the message or by contacting Peckish.

  • You may manage profile, saved address, notification, language, wallet, and account settings where those controls are available.

  • Signed-in users can permanently delete their account in the app. A successful deletion cannot be undone, although limited deidentified or legally required records may remain.

  • Depending on where you live, applicable law may provide rights to access, correct, delete, restrict, object to, or obtain a copy of personal information.

  • For support, privacy, account deletion, access, correction, portability, or consent-withdrawal requests, email alecdevs@trypeckish.app.

09

Cookies and tracking

Peckish may use necessary cookies or similar technologies for login, security, preferences, fraud prevention, and basic site operation. Peckish does not currently sell personal information. If Peckish adds non-essential analytics, advertising cookies, or tracking that requires consent, the product should add the required consent controls before those technologies are used.

10

Children

Peckish is not directed to children under 13 and does not knowingly collect personal information from children under 13. If you believe a child provided personal information, contact Peckish so the information can be reviewed and deleted. A parent or guardian should supervise a minor's use of restaurant ordering and sensitive dining-profile features.

11

Automated systems

Peckish may use automated systems for security, abuse prevention, moderation, and product operations. Peckish will not send personal allergy, medical, address, payment, or support-message content to a third-party AI service for a new purpose without updating disclosures and obtaining consent where required.

12

Security incidents

If Peckish discovers unauthorized access to personal information, Peckish will investigate, contain the issue, preserve evidence, and provide notices to affected people and regulators when required by applicable law. Security concerns can be reported through the public Security page or by emailing alecdevs@trypeckish.app with the subject Security Report.

13

Updates

Peckish may update this Privacy Policy as the product develops. When changes are made, the updated date on this page will be revised.

These pages describe the current Peckish service in plain language. For account, privacy, order, or allergy-information support, email alecdevs@trypeckish.app.
Peckish

Food discovery with clearer context.

PrivacyTermsCommunity GuidelinesSupport