Effective date: October 19, 2026
Last updated: November 12, 2026
Great Dane Holdings LLC, a Wyoming limited liability company, doing business as Booqer. Mailing address: PO Box 120386, Clermont, FL 34712. Contact: support@booqer.ai.
Shop listings
A shop listing shows the shop name, the city, the offerings, and the hours. A listing does not include a street address.
Booking requests
A booking request includes the customer name, phone number, email address, the shop, the offering, a preferred time, the problem or job summary, and the service address. Booqer stores the service address and the problem or job summary and shares them with the shop you chose. When a shop has more than one location, the ZIP code in the service address chooses the location. Booqer also stores how the visit reached the booking page and shares a short source label with the shop.
Who receives a request
Booqer sends your request to the business you chose so it can respond to it. That can happen by email, through a scheduling tool the business connected (such as Jobber), or through a webhook the business registered.
Booqer uses service providers to host, store, process, and deliver requests: Vercel (hosting), Supabase (database), and Resend (email). They handle this information to run Booqer, not for their own marketing.
Booqer does not sell personal information. Booqer does not give your name, email address, phone number, or booking details to unrelated businesses for their marketing. Site visit measurement with Meta and Google Ads is described under Site visits and cookies.
Jobber connections
When a shop owner connects Jobber, Booqer stores that connection so it can read open times and write a request the shop accepted.
Calendar connections (coming soon)
Connecting a Microsoft Outlook or Microsoft 365 calendar, or a Google Calendar, is coming soon for shop owners. It is not available yet. When it is, it will work as described in this section. Booqer will ask for access only when an owner chooses to connect, and the owner can disconnect at any time.
What Booqer will read: whether each time on the calendars the owner connects is free, busy, tentative, or out of office, with its start and end. Booqer will not read or store event titles, descriptions, locations, attendees, or attachments. Booqer will also read the name and email address of the connected account, so the owner can see which account is connected.
What Booqer will write: Booqer will create one calendar named "Booqer bookings" in the owner's account and add an event there for each booking the shop accepts, or that the shop's rules confirm right away. The event holds the time, the service, the customer's name and contact details, the service address, the job summary the customer gave, and a link to the booking. With Outlook, the customer may be added to the event, so Outlook sends the customer an invitation. Booqer will change or cancel only the events it created in that calendar. Booqer will watch only those events, so it can tell the shop when an owner moves or deletes one. It will not cancel or reschedule the customer on its own.
How it will be used and shared: Booqer will use free and busy times only to work out which times to offer for that shop. Customers, and assistants they use such as ChatGPT, will see only the open times, never the shop's calendar entries or why a time is busy. Booqer will not sell calendar data, will not use it for advertising, and will share it only with the service providers on this page that run Booqer. Booqer will not use calendar data to train or improve artificial intelligence or machine learning models. Booqer staff will not look at a shop's calendar data unless the owner asks for help with a specific problem, it is needed for security (for example, to investigate abuse), or the law requires it.
How it will be stored: the sign-in tokens for a calendar connection will be stored encrypted, with keys managed by Amazon Web Services. Free and busy times will be read when availability is checked, kept in memory for no more than 15 minutes, and not saved in Booqer's database. For each event Booqer creates, it will keep the event's ID so it can update or cancel that event, and will delete the ID with the booking under Data retention below. When an owner disconnects, Booqer will delete the tokens right away and stop reading and writing. Events already added to "Booqer bookings" stay in the owner's calendar, where the owner controls them. An owner can also remove Booqer's access in their Google Account (myaccount.google.com/permissions) or their Microsoft account (myapps.microsoft.com), or through their organization's administrator.
Google user data: Booqer's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of information received from Google Workspace scopes will adhere to the Google Workspace User Data and Developer Policy, including the Limited Use requirements. Booqer will not use, transfer, or keep Google user data to develop, improve, or train generalized artificial intelligence or machine learning models.
Microsoft data: Booqer will reach Microsoft 365 calendars through Microsoft Graph, with the permissions shown on Microsoft's consent screen, and will use that data only as this section describes.
Questions about calendar data, or a request to delete it, go to support@booqer.ai.
Webhooks to shops
Booqer posts a booking event to a webhook URL the shop registers. The event includes the request details the shop needs. A customer cancel, an owner decline, and an admin cancel each post booking.cancelled. The delivery log stores the HTTP status and a redacted response. It does not store the signing secret.
Assistants and the public MCP endpoint
Booqer is live in ChatGPT. An assistant such as ChatGPT can read the listings of shops on Booqer at booqer.ai/shops and book a time with one of them through the public MCP endpoint at booqer.ai/mcp. Finding and booking a listed shop there is instant. Depending on the business's rules, a request is either confirmed right away or held for the business's approval. New shops are being onboarded. The request Booqer stores is the same booking request described above: name, phone when provided, email, shop, offering, time, problem or job summary, and service address. Booqer stores those fields and shares them with the shop you chose. Booqer does not sell that request and does not use it to train a model.
Site visits and cookies
To limit abuse, Booqer counts requests using a one-way hash of your IP address rather than the address itself. Some pages log a visit with the page path and the referring source. The browser user agent is stored only as a one-way hash. That visit log does not store an IP address, a name, an email address, or a phone number. Calls to the public MCP endpoint are logged the same way: the method, the tool, the kind of assistant, a short one-way session key, whether the call worked, how many businesses or open times were returned, the shop ids, and a search query of at most 120 characters with email addresses, phone numbers, long numbers, and street numbers removed. That log does not store a name, an email address, a phone number, a street address, an IP address, the raw user agent, or a session token. Those rows are deleted after 180 days. A first-party HttpOnly cookie named booqer_ft remembers how you first arrived at Booqer for 90 days: the referring website's domain, any campaign tags in the link (utm_source, utm_medium, utm_campaign, utm_content and utm_term), and a Facebook (fbclid) or X (twclid) click ID when the link has one. If that first visit had no campaign tags, the first later visit that has them replaces it. Once a visit with campaign tags is saved, later visits do not change it. It holds no name and no email address. A separate first-party HttpOnly cookie named booqer_vid lasts 90 days. Booqer stores only a one-way hash of it, the same id used to count page views. It holds no name and no email address. When a booking is stored, Booqer keeps that first-visit source with the request: whether it came from the website, an assistant, or an API; which assistant when one is known; the referring website's domain; the campaign tags; whether the link included a Google (gclid), Facebook, or Microsoft (msclkid) click id; the first page path; and the time of that first visit. A Google or Microsoft click id is recorded only as present or absent. The id itself is not stored on the booking and is not shared. Booqer shares a short source label and the campaign tags with the shop. It does not share the click id, the visitor cookie, or the full referring address. Vercel Web Analytics also counts visits to public pages. Booqer does not send it a name, email address, or phone number. Booqer also uses the Meta Pixel on its public pages to measure visits and form submissions for advertising, such as when a shop sends an application or a customer sends a booking request. Meta may set or read cookies in your browser and may use this information under its own privacy policy. Booqer does not send Meta your name, email address, phone number, address, or what you type in a form. The Meta Pixel does not run on private preview pages, shop sign-in or owner pages, or Booqer's internal pages. You can opt out by blocking cookies or trackers in your browser settings, or by changing your ad preferences in your Facebook or Instagram account settings. Booqer also uses the Google Ads tag on its public pages to measure page views for advertising. A conversion is recorded only after a shop application is received, not when a page is merely viewed. Google may set or read advertising cookies in your browser. Booqer does not send Google your name, email address, phone number, address, what you type in a form, or claim-link addresses. The tag does not run on private preview pages, claim links, shop sign-in or owner pages, or Booqer's internal pages. You can opt out of those advertising cookies in your browser settings or at Google's ad settings. Shop owners and staff who sign in get a sign-in cookie so they stay signed in.
Shop applications
When a business applies at booqer.ai/apply, Booqer collects the business name, a contact name, an email address, an optional phone number, the trade, the service area, an optional note, and the applicant's consent to be contacted.
Booqer uses this information only to review the application and to contact the applicant about setting up the shop. Booqer sends the applicant an acknowledgment email and sends Booqer staff a notice of the new application. Booqer does not sell this information or share it with shops or other businesses.
Booqer deletes an application that was never approved 12 months after it was submitted. A test or demo application, including one sent from brian+demo@booqer.ai, can be deleted 30 days after it was submitted. To ask Booqer to delete an application, email support@booqer.ai from the address you applied with.
Data retention
Booking details are shared with the business you chose and with that business's CRM, so the business can respond. A status expiry is not deletion of the booking request.
Booqer deletes an unconfirmed, expired, or abandoned booking request, and a hold that never became a booking, 90 days after it was made.
For a completed or cancelled booking, Booqer removes the customer name, email address, phone number, service address, and notes 24 months after the booking date. Booqer keeps the anonymized booking, the signed receipt digest, and the billing record for that booking for 7 years, so it can meet a tax obligation or resolve a dispute. Removing those details does not change the signed receipt. The receipt digest is a hash of the public receipt, which does not include the customer name, email address, phone number, service address, or notes, and the public verification page still matches that digest.
Booqer deletes a shop application that was never approved 12 months after it was submitted. A test or demo application, including one from brian+demo@booqer.ai, can be deleted 30 days after it was submitted.
Booqer deletes assistant usage rows for the public MCP endpoint 180 days after they were made. Those rows have no name, email address, phone number, or street address.
To ask Booqer to delete a booking request, or the other personal details Booqer holds about you, email support@booqer.ai.
Security
Booqer limits access to personal information to the people and systems that need it to run the service, and uses access controls on its database. No system is perfectly secure.
Privacy requests
To ask what Booqer holds about you, or to ask Booqer to correct or delete it, email support@booqer.ai.
Changes
Booqer may update this page. The effective date above shows when it last changed.