Privacy policy

Scout finds restaurants and requests Resy reservations for you. This page says what Scout stores, which services it talks to, and how you take it all back. Last updated Oct 24, 2026.

What Scout stores

Your account. Your email address and name from sign-in, your timezone, and your saved searches, favorites, and notification settings.

Your home location, if you add one. Scout saves the address you type and a Google place identifier to start Discover near home. Google Maps receives your address as you type to suggest matches. If you choose “Use my current location” and allow browser access, your browser sends its coordinates to Google Maps to find the location; Scout saves only the place identifier after you confirm. Google resolves the saved place when needed. Returned address details and device coordinates stay in the current page only; nearby restaurant searches receive an approximate location and city. Home-location details are kept out of connected-assistant and booking-device profiles. You can skip this step or change or remove your home location in Settings.

Membership and billing. Stripe processes subscription and successful-booking payments. Scout sends your account email and billing identifiers to Stripe and stores customer, subscription, invoice and payment-status identifiers. Card entry takes place on Stripe; Scout does not receive or store your full card number. Scout retains the fee amount you agreed to and the reservation evidence needed to verify the service. Alpha invitation passwords are checked against a salted hash and are not stored as plaintext.

Your Resy connection. When you connect Resy, Scout keeps an encrypted session token for your Resy account so it can check availability and, only after you approve a request, book a table. Scout stores the display name of your Resy payment method (for example the card brand and last four digits) so you can see which card a restaurant would use. Scout never stores your Resy password or full card numbers. The one-time code Resy emails you is used once and discarded.

Restricted OpenTable pilot. For enrolled accounts, Scout uses an isolated browser and stores its OpenTable sign-in state encrypted. Verification codes are used for the current connection and are not retained in the connection record. Browser state, codes and private reservation-management links are excluded from diagnostic replay and public responses. Each reviewed test is recorded separately, including uncertain outcomes and verified cleanup. OpenTable restricts automation without its authorization and may suspend access or cancel reservations; Scout does not claim that authorization.

Reservations and requests. The restaurants, dates, party sizes, and time windows you ask for; the availability Scout observed; and the reservations it booked or found in your Resy account, so it can show status and avoid double booking.

Your Beli connection, if you add one. Scout signs in to Beli with the email and password you enter, keeps only the resulting Beli session tokens and account name, encrypted, and never stores your Beli password. Scout uses it to show your Beli ratings next to restaurants. Disconnecting deletes the session.

Assistants you connect. The name of each assistant or personal access token, what it is allowed to do, and the requests it created. Tokens are stored only as hashes. An assistant sees only the requests it made.

Operational records. Which routes were called, when, and with what outcome, kept to run and secure the service. Scout does not keep the text of your conversations with an assistant.

How you found Scout. On your first visit Scout keeps, in a first-party cookie, the website that linked you here (its address without any query), any campaign tags in the link, and the page you landed on. Scout counts that visit without your IP address or device details, and if you then create an account it saves the same information with it.

Website sessions. Scout uses a temporary first-party cookie to count website visits and measure observed session duration while a page is visible and focused. A session ends after 30 minutes without a foreground signal or when you sign out or switch accounts. Signed-in sessions can be linked to your Scout account. Session records are retained for 90 days; they do not include your IP address, device details, page contents or query parameters. A visit with only one recorded signal has an unknown duration.

Customer diagnostics. Scout uses Sentry to understand how signed-in customers use the service and where they encounter errors or friction. All eligible signed-in sessions are recorded while this capture is enabled. Recordings include text, ordinary form inputs, choices and images. Feature usage events record screen views and categorical action outcomes. Stripe payment flows are excluded, and the last four digits of Resy payment cards are masked. Scout does not collect network bodies or console logs. Sentry receives an opaque account identifier and technical connection information. External sign-in pages are not recorded. Global Privacy Control and Do Not Track turn this capture off.

Advertising measurement. Scout may use Google Ads and Meta to measure whether an ad led to a newly created account. Measurement stays off when you turn it off below or when your browser sends Global Privacy Control or Do Not Track.

The Google and Meta tags receive network metadata, including IP address and browser/device information. They may use cookies to connect an ad click to a signup. Scout privately saves an eligible Google ad click identifier with a new account to connect signup to the ad click. This attribution record stays with the account after the browser cookie expires; turning measurement off blocks future capture and measurement. Scout sends an opaque new-account identifier and validated advertising click information; it does not send your email, name, restaurant choices, or reservation data. Google ad personalization and Meta automatic matching are disabled. Scout requests Google's restricted data processing and Meta's Limited Data Use. Only a newly created account counts as a signup; signing back in does not.

Notifications. Scout stores your notification preferences, enabled browser subscriptions, notification history and send outcomes. If you choose text alerts, it also stores your phone number, verification status and SMS consent.

Services Scout uses on your behalf

• Resy, using your own account, to search availability and book. Resy's terms prohibit automated access, and Resy may deactivate accounts it identifies as automated. You accept that risk when you connect Resy.
• Sentry for customer session recordings, feature usage events and browser-error diagnostics within the limits above.
• WorkOS for sign-in. WorkOS handles your email login and passes Scout your email and a session identifier.
• Anthropic and OpenAI models to read the free-text description of a dinner you type or that an assistant sends, and to summarize public restaurant information. Scout sends the text of the request and public restaurant data. It does not send your Resy credentials, payment details, or conversation history.
• Google Places for restaurant addresses, photos, ratings, and reviews.
• Google Ads, subject to the measurement limits and controls on this page, to measure new-account conversions.
• Meta, subject to the measurement limits and controls on this page, to measure new-account conversions.
• Beli, using your own Beli account, only if you connect it.
• Residential proxy providers to route requests to Resy. The proxy sees the request traffic to Resy, not your Scout account.
• Resend and Twilio deliver enabled email and text notifications. They receive the delivery address or phone number and message content needed for that channel. Twilio also verifies phone ownership. SMS consent and phone numbers are not shared for third-party marketing.
• Web push through your browser's push service, if you turn on notifications.

Scout does not show third-party advertising or share your data with restaurants beyond what a reservation requires. Advertising measurement is described above and can be turned off below. Scout also holds no reservations of its own: every booking is made in your name, in your own account on the platform you connected, and belongs to you. Scout never sells or transfers a reservation, and the terms ask the same of you.

Assistants and AI agents

When you connect an assistant, whether through a personal access token or an OAuth connection, it acts within the permissions you chose. Automatic booking never happens until you approve the exact request in Scout. You can revoke any assistant on the Assistants page; its open requests stop at once.

Ad measurement controls

These controls apply to this browser. Turning measurement off does not affect your Scout account or Searches. Your preference is remembered for 180 days unless you clear cookies. Browser privacy signals take precedence.

Checking this browser’s preference…

Your controls

Choose booking and action alerts in Settings. Disable push separately on each browser or device. Text alerts are optional; reply STOP to stop them. Receiving notifications is not a condition of using Scout.

• Disconnect Resy or Beli in Settings at any time. Scout deletes the stored session, and for Resy stops all booking work.
• Revoke any assistant or token on the Assistants page.
• Ask for a copy of your data or deletion of your account by writing to the address on the support page. Scout deletes account data within 30 days of a verified request, except records it must keep to resolve a booking already in progress.

Retention and security

Resy sessions are encrypted at rest and are deleted when you disconnect or when they expire. Short-lived operational data such as availability checks is pruned on a rolling basis. Scout runs on a single cloud host in the United States.

Changes

If this policy changes in a way that matters, Scout will say so on this page with a new date.