Privacy Policy.
In plain English.

Vespar Guest Texts is operated by Vespar, LLC for participating restaurants. We use your number and messaging records to deliver the specific texts you request, keep the restaurant’s conversation and booking records together, and honor your messaging choices. Consent to one link does not subscribe you to reminders, texts for another restaurant, or marketing.

We do not sell or share your SMS opt-in data or personal information with third parties for marketing purposes.

The restaurant handling your enquiry and the service providers needed to operate and deliver these texts process the relevant information for those purposes. Your opt-in is not permission for them to market to you. We keep a record of consent and opt-out requests so that we can apply your preferences.

Read the guest text messaging guide for the opt-in steps and the SMS Terms for message frequency, charges, and help. Reply STOP to the number that texted you to unsubscribe, or HELP for assistance.

Some venues have their host answer the phone. When it does, your conversation with the host is recorded.

• What is kept: the recording, a written transcript and a short summary of the conversation, the number you called from (unless you withheld it), when you called and for how long, and the details you gave the host.
• Calls from ads: if the venue connects its Google Ads account, Google’s report of a call from one of its ads (its time and length, and the caller’s country and area code, never the full number) is matched to the recorded call when the two line up, so the venue can see which ad led to it.
• Where it is kept: in private storage that is never public, and with ElevenLabs, which runs the line’s voice and keeps its own copy.
• How long: there is no automatic expiry. A call is the venue’s record of what was asked and agreed, and of which ad led to it, so it is kept until you ask us to delete it.
• Who can hear it: members of the venue’s team who have access to its guest records, inside the venue’s signed-in dashboard, and our own team when helping that venue. Recordings are never published and never shared with another venue.

To have your calls deleted, see Your rights below. We delete the recording and transcript from our storage and from ElevenLabs, and remove your number and details. The venue keeps only what identifies no one: that a call happened, when, for how long, and which ad it came from.

This part is for venue owners, and connecting is optional. If you connect your venue’s Google Analytics or Search Console to Vespar, you either sign in with Google and choose the property to share, or add Vespar’s reporting account to that property as a viewer. Either way the access is read-only: we cannot change anything in your Google accounts.

• What we read: aggregated figures only. From Analytics: visits, visitors, traffic sources, landing pages, and visits by channel. From Search Console: clicks, impressions and average position, broken down by search query, page and day; and, for pages you choose to check in Marketing, Search, whether Google has indexed them, when it last crawled them and the address it chose for them. We do not request data about individual visitors.
• What we use it for: your venue’s own reports and suggestions inside Vespar: the Analytics and Search pages, research, and your setup plan, and nothing else.
• What we store: an encrypted access credential, if you signed in with Google, and the ID of the property you chose. We also keep two results: the index checks for pages you saved in Marketing, Search, until you check those pages again, and your setup plan, which can name up to three of your search queries with the page each one leads to. Other report figures are held in a short-lived cache for at most one hour and then discarded.
• Who else receives it: when someone on your team asks a question in Marketing (on the Analytics, Search or Research pages) or asks the dashboard assistant about your marketing, the figures that question needs, including these, are sent to our AI model provider to write the answer shown to that person. That happens only when a question is asked. We do not use these figures to train AI models.
• Who at Vespar sees it: our staff do not review these figures. A member of our team who opens your dashboard to help with a support request you raised will see your report as you do.

We never sell this data, never use it for advertising, and never share it with another venue. If you signed in with Google, you can disconnect at any time in Setup, Connections. That deletes our stored credential and the property you chose with it straight away, and any copy of the credential still held in a running server’s memory expires within five minutes. You can also remove Vespar’s access on Google’s side at myaccount.google.com/permissions. If you added Vespar’s reporting account instead, remove it from the property in Google Analytics or Search Console, or ask us to. Either way, the two results above stay after access ends. To have them removed, write to us at info@vespar.ai.

Vespar’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

This part is for venue owners, and connecting is optional. A venue can connect a Google Calendar, an Outlook calendar, or both. You sign in with Google or Microsoft and choose the calendar your bookings belong on. From Google we ask to view and edit your calendar events, to see the list of your calendars, and for your account’s email address; from Microsoft, to read and write your calendars and to keep that access while you are connected. We use them for the things below and nothing else.

• What we read: for a date a guest asks about or picks on the ordering page, or your team enters when adding an event, which times are busy on the calendar you chose. Google’s answers also carry the titles and details of your entries; we use only each entry’s times and whether it is marked free, and discard the rest. From Outlook we ask only for each entry’s times and whether it shows as busy. We also read the names of the calendars you can edit, so you can choose one, and on Google, Test connection reads one entry to confirm access.
• What we write: when a deposit is paid, three entries on that calendar: the booking (its title names the event type, the guest, the guest count and the room, and its notes carry the room, the guest count and the email address and phone number the guest gave us), and a setup block and a teardown block an hour either side. If the booking changes or is cancelled in Vespar, we update or delete those entries. We only ever change entries Vespar created. On Outlook, Test connection also adds a short test entry marked free, then removes it.
• What we store: an encrypted access credential for each calendar you connect, the calendar you chose (for your main Google calendar, that is your account’s email address), and the IDs of the entries we created. We do not keep a copy of your calendar; the busy times the ordering page shows for a day are held for at most one minute.
• Who else receives it: when a guest asks your host about a date, the busy times found (times only, never titles or details) go to our AI model provider to write the answer, and the reply can mention them. The ordering page can tell a visitor that you already have something on at a time they pick, by time only. We do not use these times to train AI models.
• Who at Vespar sees it: our staff do not read your calendar. A member of our team who opens your dashboard to help with a support request you raised sees the same availability results you do.

We never sell this data, never use it for advertising, and never share it with another venue. When a guest asks us to delete their data, we remove their details from the entries Vespar created, or ask you to if your calendar is no longer connected. You can disconnect either calendar at any time in Setup, Connections. That deletes our stored credential and your calendar choice straight away, and any copy still held in a running server’s memory expires within five minutes. Entries already on your calendar stay where they are. Disconnecting does not remove Vespar from your account: do that at myaccount.google.com/permissions for Google, or at myaccount.microsoft.com under App permissions for Microsoft.

Vespar’s use and transfer of information received from Google APIs, including Google Calendar, adheres to the Google API Services User Data Policy and the Google Workspace user data and developer policy, including the Limited Use requirements.

This part is for venue owners, and connecting is optional. If you connect your venue’s Google Business Profile, you sign in with the Google account that owns or manages it and confirm which restaurant is yours. Google offers one permission for this, which it words as managing your Business Profile, and it cannot be limited to reading. Vespar reads your profile on its own, and changes it only when an owner presses a button to publish.

• What we read: the names and addresses of the restaurants your account manages, so you can pick one; then that restaurant’s name, address, phone number, website, category, review link and the Reserve and Order buttons on its listing, to show them to you and to fill in your review link and table-booking link where you have not already saved one. When Vespar builds your setup plan, we also read your 20 most recently updated reviews (the comment, cut to 500 characters, and whether you replied) to show you a few and suggest replying to unanswered ones.
• What we change on Google: nothing on our own. We add, change or remove a Reserve or Order button on your listing only when an owner confirms the destination and presses Publish or Remove.
• What we store: an encrypted access credential, the restaurant you confirmed, and, only where you had none, your review link and your table-booking link. We show your name, address and the rest live from Google and do not keep them. To show you a few reviews during setup, we cache up to three comments for five minutes, and then they expire. We keep no review text after that, and we never store reviewer names or ratings. Your setup plan can keep a suggestion to reply to recent reviews and a link to your listing on Google Maps; neither contains review text.
• Who else receives it: your review link is offered to guests on the thank-you page of our post-event survey. Your table-booking link is given to a guest who asks the venue’s host for a table, and it passes through our AI model provider as part of writing that reply. Nothing else from your profile leaves Vespar. We do not use it to train AI models.
• Who at Vespar sees it: our staff do not review your profile. A member of our team who opens your dashboard to help with a support request you raised sees what you see.

We never sell this data, never use it for advertising, and never share it with another venue. You can disconnect at any time in Setup, Connections. That deletes our stored credential and your restaurant choice straight away, and any cached review comments expire within five minutes. The review link and booking link you saved stay, because they are your settings, and so do any buttons already on your listing and your saved setup plan. To have the setup plan removed, write to us at info@vespar.ai. Disconnecting does not remove Vespar from your Google account; you can do that at myaccount.google.com/permissions.

Vespar’s use and transfer of information received from Google APIs, including the Business Profile APIs, adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Wherever you are, we honor the core rights of the EU GDPR and the California CCPA/CPRA:

• Access / export: request a machine-readable copy of everything we hold about you.
• Deletion: request erasure; we remove your identity and conversations, including call recordings, keeping only what the law requires (e.g. invoices) or fully anonymized statistics.
• Correction: ask us to fix inaccurate details.

To exercise access or deletion, request it here. We email a link to confirm it’s really you (nothing happens until you open it), and then answer within 30 days. Every request is logged for accountability.

If you called a venue and never gave its host an email address, email info@vespar.ai instead, with the number you called from. We may ask you to confirm that the number is yours.

For corrections, or to reach a person about anything on this page, email info@vespar.ai from the address your booking used.

We use Google Analytics to see which pages are useful. That is the only thing here we ask about, and the notice on your first visit lets you refuse it. We run no advertising trackers, nothing that follows you to other sites, and no cookie that sells or shares what you did.

In regions where we require prior consent, analytics waits for you to accept. Elsewhere it may start while the notice offers a choice. Choosing “Reject optional” prevents future analytics collection, including when the tag has already loaded. Cookies already set may remain until they expire or you clear them. We remember your choice when browser storage is available.

The rest is essential or stays with you. A login cookie if you sign in to the venue dashboard. An anonymous session token in local storage, kept for 30 days, that lets the chat widget remember your conversation. A draft of a form you started, and the page you first arrived on, both held in this tab’s session storage so a form can survive a mistake and we can tell which page brought you here. On a venue’s own website that has installed our chat script, the script makes its note as the page loads, even where the chat button does not appear: the first time a tab arrives from another site or through a tagged link, it keeps the page you arrived on, the address of the page that referred you, that link’s campaign tags, which kind of advertising click marker it carried (never the marker itself), and the time, in that tab’s session storage. The guided intake saves your answers when you submit, restores them if submission fails, and clears them after success or a fresh start. Session storage stays in this tab and is cleared when the tab closes. When you send a chat message or an event request, the arrival details go with it and are saved on that venue’s record of your enquiry, kept as described under “How long we keep it”. They are shared only with that venue. Nothing else here is shared with anyone.