Privacy Policy

Updated November 5, 2026

This Policy explains how Menu by me n u, Inc., a Delaware corporation (“Menu,” “we,” or “us”), handles information when you use reserved.menu, the Menu app, our waitlist, matching and messaging features, and restaurant and reservation services.

1. Information you provide

• Account and contact information: name, email address, phone number, authentication status, Apple sign-in identifier if used, and communication preferences.
• Profile and matching preferences: birth date or age, gender, dating preferences, sexual orientation where provided, biography, hometown, school, education, occupation, company, height, ethnicity, lifestyle, relationship goals, prompts, photos, video and voice answers. We also collect your food and restaurant interests, ranked food preferences, dietary needs, food allergies, budget preferences, and availability when you provide them.
• Interactions: likes, passes, matches, direct introductions, text and audio messages, selected GIFs, blocks, reports, restaurant saves and interests, table requests, proposed and accepted times, and responses.
• Booking information: booking contact name, email and phone, restaurant, reservation date and time, party size, seating selection where available, reservation and confirmation identifiers, booking status, and the restaurant policies and choices associated with a booking. If a supported booking requires a deposit, guarantee or other payment, the relevant provider may collect payment details and return limited payment or fee status to us.
• Waitlist, referrals and purchases: application status, invite code, referral attribution, optional borough or phone verification data, subscription and entitlement status, purchase identifiers, and purchase-verification results.
• Safety and support: selfie or photo-verification material if requested, reports, moderation decisions, and information you send to Support. A photo check is not a guarantee of identity or safety.

Some profile, location and dietary information may be sensitive, including information that reveals sexual orientation, racial or ethnic origin, religious beliefs or health conditions. Provide only information you want Menu to process. Where the law requires separate consent, we must obtain that consent for the relevant purpose; acceptance of this Policy does not replace it. Profile visibility and consent to processing are separate choices.

Audio messages: When you choose to record and send an audio message, Menu receives the recording and processes its duration and waveform to deliver and play it in your conversation. Microphone permission is requested before recording. Audio messages are stored privately with access controls for eligible conversation participants; they are not end-to-end encrypted. Authorized safety staff may access relevant audio when investigating a report. Unsent recordings remain on your device until you send them or discard them. Uploaded audio that is no longer referenced by a message is removed by scheduled cleanup, subject to the retention exceptions in Section 10.

2. Usage, device and location information

We collect device and app version, IP address, timestamps, operational errors and security logs, and records of your use of available features. These records include app openings and recent activity, profile and restaurant interactions, introduction and messaging events, reservation requests and status changes, and purchase events. We use them to operate features, recommend people and restaurants, understand engagement, measure performance, troubleshoot problems and prevent abuse. Usage records may be linked to your Menu account.

We collect campaign and referral information, such as landing page, referring domain and campaign, placement or medium values in links. The website uses cookies or similar browser storage for functionality, preferences and advertising measurement, as described in Section 6.

With device permission, Menu uses location on your device for map positioning and neighborhood selection. The current app saves the city and neighborhood you choose, rather than uploading your exact device coordinates or selected home pin to Menu. Apple processes map and geocoding requests under its own privacy practices. IP addresses can also indicate a general location. You can withdraw device location permission in iOS Settings. We do not display your precise live location to other members.

We store connections created through Menu, including matches, conversation participants and referral relationships, to deliver messaging, invitations and account features. We do not import your phone address book.

3. Calendar and availability

If you connect your device calendar, Menu uses calendar access on your device to identify busy times and adjust the availability you share with Menu. The availability calculation uses event times and all-day status, rather than uploading your existing event titles, notes, locations or attendee lists to Menu. The resulting availability is saved with your profile and may be used to coordinate plans with other members.

With your permission, Menu can also add or update Menu plans in your device calendar. Calendar entries may be visible to people with access to that calendar or your device. You can disconnect calendar access or change permissions in device settings. Editing or deleting a calendar entry does not change or cancel a restaurant reservation.

4. Booking details and reservation services

OpenTable is Menu’s preferred reservation integration provider. Where an OpenTable booking feature is available and you choose to use it, we transmit the contact and reservation information needed to perform your request to OpenTable and the participating restaurant. This may include your booking name, email, phone number, restaurant, time, party size and supported seating or special-request information. Do not include sensitive information in a special request unless you want the recipient to receive it.

We receive information needed to display available options and the result of your request, such as restaurant details, reservation identifiers, confirmation or cancellation status, and applicable policies. Feature availability depends on the restaurant, provider and enabled integration. Using this integration does not mean Menu imports your entire OpenTable account or dining history.

OpenTable and restaurants process the information they receive under their own policies and applicable law. Review OpenTable’s Privacy Policy and the restaurant’s notice. OpenTable handles reservation confirmations, reminders and dining-related communications for its integration. Privacy requests to Menu do not automatically delete records independently maintained by OpenTable or a restaurant.

Menu does not request your OpenTable password. Booking contact details and any supported provider credentials are kept server-side with access controls; sensitive booking contact and provider records are encrypted. Other authorized reservation services, when available, are identified in the relevant flow and receive information needed for the action you request.

Resy connections: When you connect Resy or request a supported Resy action, Menu uses Ophelia as a reservation connector. We send the booking name, email, phone number, verification code when required, a Menu account reference, and the reservation details needed for the action. We retain connection and session references, expiry information, reservation results and limited card-on-file status. Connecting Resy does not give other members access to your provider credentials or booking contact details. Full card entry, when required, takes place in the provider’s payment flow.

Saved booking details: we save the reservation name, email and mobile number you provide so you can reuse them for later bookings. For phone-number sign-up, we may prefill your verified Menu sign-in number. We do not prefill booking email or phone from Sign in with Apple. After you enter booking email and phone for OpenTable, we may prefill those details in the Resy connection flow; you can use a different booking number and, where supported, different contact details for each provider. Saving contact details does not by itself connect or verify a reservation account. Booking contact details are not displayed on your public dating profile.

Requests and account authorization: sending a restaurant-and-time request and another member accepting it can initiate a reservation using the designated booking owner’s details and supported provider authorization. We process acceptance, verification and provider confirmation as distinct events. A provider may require an additional code, payment action or sign-in. Enter verification codes only in the booking flow you initiated, not in chat or support email. Any supported reusable provider authorization is stored server-side and used within its permitted scope; availability of that authorization depends on the provider.

Resy and Ophelia: where enabled, we use Ophelia to process reservations with Resy or other identified providers. The service receives the booking contact and reservation details needed to execute and reconcile your request, and a verification code if you submit one to continue that request. The reservation provider and restaurant may retain their own account and booking records. See Ophelia’s Privacy Policy and Resy’s Privacy Policy. We do not use booking verification codes as reusable account credentials.

Payment collection: Menu Reserve and in-app message-credit purchases use Apple’s in-app purchase system. We associate Apple purchases with your Menu account and receive transaction information to deliver purchases, restore eligible access and process refunds. Restaurant guarantees, deposits and cancellation fees are separate from Menu Reserve. If an enabled reservation flow requires card details, the flow identifies the payment or secure-vault service collecting them and any further approval required. We receive only the information needed for the integration, such as a payment reference, authorization result or limited card display details. Saving a booking contact does not save a payment card or authorize unrelated charges.

OpenTable card capture through Stripe: when this flow is enabled, card details you enter in Menu are sent directly from your device to Stripe for tokenization. Menu receives a single-use token, the last four digits and booking-related authentication results, and passes the token to OpenTable for the requested booking. Menu’s backend does not receive the full card number or security code. A bank may require additional authentication. This token is not a reusable saved card; a later attempt may require fresh entry. The token and last four digits are stored in encrypted server records for the booking attempt. Tokens and authentication references are bound to the booking attempt and subject to expiry and replay controls. Expiry limits their use; it does not mean all associated records are immediately erased. See Stripe’s Privacy Policy.

5. Why we use information and what members see

• Authenticate accounts, maintain profiles and operate applications, waitlists and referrals.
• Recommend people and restaurants using preferences, interests, availability and interaction signals, and provide recent-activity indicators.
• Deliver likes, direct introductions, matches, messages, table requests and reservation coordination.
• Verify purchases and subscriptions, reconcile booking results and permitted partner payments, and resolve billing or support issues.
• Investigate reports, moderate content, prevent fraud and repeat abuse, enforce rules and protect members.
• Analyze usage and campaign results, test and improve features, reliability and accessibility, and comply with legal obligations.

Eligible members may see your photos, first name, age, biography, prompts, interests, selected background details, availability and an approximate recent-activity indicator. Dietary information is visible according to your profile visibility settings. Private budget preferences and private ethnicity selections are not displayed to other members. We do not display your email, phone number, birth date, authentication credentials, raw activity logs or precise live location.

Recipients see messages and direct introductions you send them. Participants in a plan may see its restaurant, time, party size, status and confirmation details. Share information in messages and plans with that visibility in mind.

Optional social links and Instagram verification: a social handle you add may be shown on your profile and opens the relevant external service when tapped. If you choose Instagram verification, we process the submitted handle, verification challenge, relevant incoming verification-message information and provider account identifiers needed to check control of that account. Where offered, we also process verification/activity timestamps used to maintain the badge. This does not give Menu access to your entire Instagram inbox and does not establish your legal identity or safety. Instagram processes activity on its service under Meta’s privacy practices.

Profile loading: the app may fetch and temporarily cache eligible profile information and photos in advance, including upcoming People cards and profiles associated with the first restaurants on Map, to reduce loading delays. This does not make private profiles public or grant access to features your account is not eligible to use.

6. Website advertising and privacy choices

Our public website uses first-party campaign measurement and Meta Pixel on public pages and supported signup flows to measure page views and conversions. Meta can receive browser, device, IP-address, page URL, referrer, cookie or similar identifiers, and event information. Our event code does not deliberately include your email, phone number, private messages, dietary details or sensitive profile fields. Meta’s handling of information is described in its Privacy Policy.

Disclosure of website event information to Meta may constitute a “sale,” “sharing” for cross-context behavioral advertising, or targeted advertising under applicable privacy laws, even without a money payment for the data. We do not use sensitive profile information for targeted advertising.

Your Privacy Choices lets you stop Menu from loading Meta Pixel in this browser. We also apply a supported Global Privacy Control signal to stop that loading. The choice does not stop essential service or security processing, or first-party campaign measurement. It does not remove information already received by Meta. Browser choices are specific to this browser and may need to be repeated after storage is cleared or on another device. Contact Support for privacy requests concerning information associated with your account.

7. Other recipients

• Service providers: hosting, database, authentication, storage, messaging, email, moderation, support and purchase-verification providers, including Supabase, Netlify, Twilio, Resend and Apple as applicable, receive information needed for their services.
• Maps and media: Apple MapKit supplies restaurant and map information. GIPHY processes GIF searches and interactions for functionality, analytics and personalization; its iOS SDK disclosure describes these records as anonymous and not used for tracking. See GIPHY’s Privacy Policy.
• Photo safety checks: Menu sends uploaded profile images to Amazon Web Services Rekognition for content moderation and face-presence detection. We store safety labels, face counts, image hashes and review outcomes. The current check does not identify who a face belongs to or create a face-identity matching database. Automated results may be reviewed by authorized safety staff.
• Spotify artwork: Album and song artwork is loaded directly from Spotify’s image delivery service when it is displayed, even before playback. That service receives the requested image address and network information such as your IP address, together with standard request headers that can identify the Menu app version and operating-system networking software. Menu does not attach your Menu account identifier or profile fields to these image requests.
• Spotify music: When you search for songs or albums, Menu processes your search text and sends it through its server to Spotify’s public catalog service using Menu’s application credentials. Spotify returns public catalog information, including titles, artists and artwork addresses. Menu saves the selections you choose with your profile so members who can view your profile can see them. This feature does not connect your Spotify account or import your Spotify library or listening history. Menu receives basic player status, such as ready, playing, paused or an error, to display playback controls. Before the first preview, Menu shows a Spotify notice. Choose Play preview to load the player, or Not now to keep browsing without loading it. The notice appears again after Menu goes into the background or you sign out or change accounts. Spotify’s embedded player receives the requested content, your IP address, browser/device information and playback interactions. The player uses isolated, nonpersistent web storage within Menu. Spotify’s player can generate session, playback and correlation identifiers and send interaction, performance and error information to Spotify and its diagnostic provider, Sentry, even when you are not signed into Spotify. Temporary web storage does not prevent these transmissions or Spotify and its providers from retaining information on their servers. Spotify’s processing, including its stated analytics, personalization and advertising purposes and available choices, is described in Spotify’s Privacy Policy and Cookies Policy. Menu does not pass your Menu account identifier, profile text, messages or precise device location to the player. Choosing Not now does not load the player; artwork requests still occur when artwork is displayed. Menu’s website advertising choices do not configure Spotify’s embedded player. Spotify’s available privacy choices are described in its policy; a choice made in another browser is not necessarily applied inside Menu’s isolated player. External Spotify links open Spotify’s own service. Spotify is an intended third-party beneficiary of this Privacy Policy and our Terms, as explained in the Spotify content provisions of our Terms. Menu is responsible for the searches and profile selections it processes; Spotify operates its own services and handles information it receives under its policies. Spotify’s published policy includes advertising and partner-sharing uses where applicable. Menu’s use of temporary player storage does not make a provider request anonymous or limit Spotify’s processing to playback.
• Reservation and payment participants: OpenTable, Resy, Ophelia, relevant restaurants and payment processors receive the information needed for requested bookings, payments and related support, as explained in Section 4 and the booking flow. Menu does not receive your full payment-card number from Apple.
• Advertising partners: Meta receives the website event information described in Section 6; it is not described here solely as a processor acting for Menu.
• Safety and legal recipients: authorities, advisors, affected members or other parties where reasonably necessary to respond to danger, fraud, abuse or legal process, or protect rights and safety.
• Business transactions: a successor or relevant parties in a merger, financing, reorganization or sale, subject to applicable confidentiality, notice and privacy protections.

8. Reservation analytics and future commercial uses

Menu uses reservation and usage records for the purposes described above, including understanding demand, completed and cancelled plans, feature performance and service reliability. Menu does not currently operate a program selling identifiable reservation records for money. Website advertising disclosures are separately described in Section 6.

We may develop paid reports or other commercial products based on reservation or usage data in the future. Before starting a new sale or licensing program, we will describe the information involved, recipient categories, purposes, retention and available choices in an updated notice, obtain any required permission or consent, and provide applicable opt-out rights. We will not treat this paragraph as consent to sell your personal information or as permission to override a provider agreement or earlier privacy promises.

Any information represented as de-identified must meet applicable de-identification requirements, not merely have names removed. If we disclose de-identified information, we will take reasonable measures to prevent identification, commit to maintaining it in de-identified form except for permitted testing, and require recipients to maintain those protections and not attempt re-identification. Restrictions on provider-supplied data continue to apply.

9. Text messages and notifications

Menu sends texts after the applicable opt-in or authentication request. Message frequency varies; message and data rates may apply. Reply STOP to opt out or HELP for help. SMS consent is optional for joining the website waitlist. With notification permission, we use your device push token and account association to deliver enabled notifications about messages, date requests and booking updates through Apple. Notification previews may be visible on your lock screen or to someone using your device; manage previews and permissions in iOS Settings. Turning off notifications does not cancel a date request, reservation or subscription. OpenTable or restaurant communications are governed by the choices and terms of those senders.

10. Retention and deletion

We retain account and profile information while your account is active and as reasonably necessary for the purposes disclosed here. Waitlist records are kept until the waitlist winds down or you ask for deletion. Booking, transaction, consent and support records may be needed to manage upcoming reservations, reconcile payments, address disputes and satisfy legal or provider obligations. Security and enforcement records may be kept longer to prevent repeat abuse.

Retention depends on the type and sensitivity of the information, whether the purpose still exists, account status, legal requirements, contractual obligations and backup cycles. Following deletion, we remove or de-identify information except where continued retention is reasonably necessary for these purposes. Information retained for an exception is limited to that purpose. Provider credentials and booking contact records are removed when no longer needed for an authorized connection or following account deletion, subject to applicable legal exceptions.

Removing a music selection in Edit profile removes it from your Menu profile when you save the change. Stopping playback or removing that selection does not delete information Spotify or its providers already received; use the privacy request process described in Spotify’s policy for that information. Deleting a Menu account does not itself cancel a reservation, cancel an Apple subscription, remove records another member independently saved, or delete information independently held by Spotify, a restaurant, OpenTable or another provider. Manage those obligations separately.

Limited purchase records, including transaction identifiers and the pseudonymous app-account token used to bind a purchase to a Menu account, may be retained after account deletion to prevent receipt reuse, process refunds and meet recordkeeping obligations. Account deletion does not itself cancel an Apple subscription or a restaurant reservation; use Apple’s subscription controls and the applicable booking cancellation flow.

11. Your rights and choices

• Edit profile, preference and available visibility controls in the app.
• Change location, calendar, photo, camera, microphone and notification permissions in device settings.
• Unmatch, block or report using available tools.
• Request access, correction, a portable copy or deletion through Delete Account or meet@reserved.menu.
• Use Your Privacy Choices for browser advertising controls, or contact us to exercise applicable rights to opt out of sale, sharing or targeted advertising.
• Withdraw consent where processing depends on consent, including for sensitive information. Some features cannot operate without the information they need.
• Reply STOP to Menu SMS and use unsubscribe controls for marketing email.

Depending on your location, you may have additional rights to limit sensitive-information use, object to certain processing or profiling, use an authorized agent, appeal a denied request, or complain to a regulator. To appeal, email us with “Privacy appeal” in the subject. We handle requests within applicable legal deadlines, may verify identity where appropriate, and may apply lawful exceptions. We do not discriminate against you for exercising applicable privacy rights. Browser advertising opt-out does not require an account.

12. Security

We use access controls, encrypted network connections, server-side secrets, encryption for sensitive reservation records, and administrative and technical safeguards appropriate to the information. Menu messages are transmitted over encrypted connections and stored on our servers for delivery, moderation and enforcement. They are not end-to-end encrypted; authorized personnel can access them for purposes permitted by this Policy. No system is completely secure.

13. International processing and adults only

Menu is based in the United States. Providers may process information in the United States and other countries where they operate, subject to safeguards required by applicable law. Feature and geographic availability may vary. Menu is for adults 18 and older. We do not knowingly permit minors to use the Service; report a suspected minor through Support.

14. Changes to this Policy

We update this Policy as the Service changes. We will identify the updated date and provide notice of material changes before they take effect, with additional notice or consent where required. We will not rely solely on a revised policy or continued use to apply a materially incompatible new use to information collected under an earlier promise. Any required consent must be obtained before that new use begins.

15. Contact

For privacy questions or requests, contact Menu by me n u, Inc., 155 Wooster Street, New York, NY 10012, at meet@reserved.menu. Do not email passwords, verification codes, government IDs or intimate images.