Data handling at Beeline.

Beeline collects only the information needed to operate accounts, run reservation bees that a diner launches, and measure whether its public pages lead to useful actions.

Information used to provide the service

• Account details: name, email address, derived password record, verification and session records.
• Connected-service details: encrypted Resy authentication and saved payment references supplied by the diner.
• Reservation bee details: venue, party size, acceptable dates and times, authorization choice, and status or confirmation reference.
• Private availability observations: watched venue, party size, service date, observation time, and available-slot summaries used in the signed-in restaurant analysis view.

Service providers and actions

Application data is stored in Cloudflare D1. Account verification, password-recovery, and booking-buzz email is delivered through Resend when configured. An active, authorized bee sends the necessary booking request to Resy when matching availability is detected.

Measurement

Beeline stores funnel event type, public source page, call-to-action placement, supplied campaign parameters, and timestamp. These acquisition rows are deliberately separate from account identity and do not contain contact details or Resy connection values.

Retention and abuse controls

Private availability observations are deleted after 180 days. Short-lived request-throttling counters are deleted after 48 hours and are used to limit abuse of account and signed-in actions.

Your controls

From the dashboard, a signed-in diner can pause or delete reservation bees and disconnect the saved Resy connection, which pauses active bees. Do not connect a profile or authorize a charge unless you accept the restaurant's policies.

This notice describes the behavior implemented in the Beeline application as of May 31, 2026. Beeline is not affiliated with or endorsed by Resy.