Your reservation bee should stay under your control.

Beeline handles account information and a connection capable of making an authorized reservation. This page states the safeguards implemented in the application code and avoids claims that have not been independently certified.

Stored account and reservation data

Beeline stores your name and email, password verification record, session records, encrypted Resy connection values, bee parameters, buzz recipient email addresses and delivery status, private availability observations, and bee status in Cloudflare D1. When you disconnect Resy, the saved connection is removed and active bees are paused.

Connection and password protection

• Resy authentication and saved payment references are encrypted with AES-GCM before database storage.
• Passwords are verified with PBKDF2-SHA-256 using a random salt and 100,000 iterations, the supported Worker cryptographic limit.
• Login sessions use Secure, HttpOnly, SameSite=Strict cookies and expire after seven days. Password changes revoke other sessions.
• Production requests are directed to canonical HTTPS, and account-changing requests enforce same-origin checks and request throttles.

Booking authorization

Every automatic booking bee requires a confirmation that venue-required deposits or charges may be submitted using your saved Resy payment method. Without that confirmation, the application rejects launch of the bee. If the result of a submission cannot be confirmed, the bee pauses and instructs you to check Resy rather than submitting again automatically.

Acquisition measurement

To understand whether public information helps diners, Beeline records limited funnel events: a start-button click, completed signup, verified email, and created bee. Event rows may include the public page, button placement, and supplied UTM campaign fields. They do not include an email address, name, Resy token, or payment reference.

Scope

No third-party security certification or guarantee is claimed here. Beeline is independent from Resy; diners remain responsible for restaurant terms, cancellation rules, and charges they authorize.