Privacy

This website

• No cookies, no analytics, and no third-party scripts, fonts or trackers.
• If you switch between light and dark, the choice is stored in your own browser and never sent to us.
• The site is hosted on Cloudflare, which handles your IP address to deliver the pages, as any web host does.

The waitlist form

• We collect what you type: your name, email address, restaurant or group, how many venues, and your message.
• We use it only to reply to you about Regular.
• It is stored in a database on Cloudflare. If you send the form again with the same email address, your entry is updated, not duplicated.
• To stop abuse, we limit how often one connection can send the form. For that we keep a salted, one-way hash of your IP address, never the address itself, and delete it within 24 hours.
• Submissions that fill in a hidden field meant to catch bots are discarded and not stored.

The product

Regular handles messages and calls between restaurants and their guests, on the restaurant’s behalf.

• What it handles: the messages guests send through the channels a restaurant connects, call events from its phone system (who called, when, answered or missed), and bookings from its booking system.
• Kept separately: each restaurant’s data is in its own database. No restaurant can see another’s. Within an organization that runs several restaurants, recognizing the same guest across them is off unless the organization turns it on, and nothing ever crosses between organizations.
• The AI provider: to understand messages and draft replies, Regular sends message content to the AI provider the restaurant chose. That can be a model the restaurant runs itself. On Cloudflare, provider keys are stored encrypted.
• Notifications: push notifications to staff phones name the guest and summarize what they need, and are delivered through Firebase Cloud Messaging.
• Junk: messages filtered as junk are kept for a recovery period (30 days by default) and then deleted, including their content in the activity log.
• Accountability: every decision, by the agent or a person, is recorded in an activity log the restaurant can review.
• Credentials: sign-in uses Google, Apple or an emailed link; there are no passwords. Access tokens are stored only as one-way hashes.