Legal
Privacy Policy
Effective: November 5, 2026
Bucket Global, Inc. (“Bucket,” “we,” “us,” or “our”) takes your privacy seriously. This Privacy Policy explains how we collect, use, share, and protect Personal Information when you use our website and the services we provide at trybucket.ai (the “Services”). By using the Services you consent to the practices described here.
I. What this Privacy Policy covers
Bucket provides an AI operations agent (“Emma”) that businesses (“Operators”) use to manage customer communications, bookings, payments, and marketing across the channels they choose to connect. This Policy applies to:
- Operators who create an account and use the Services to run their business; and
- Customers of Operators whose information we process when they contact, or are managed by, an Operator through a connected channel (for example a message sent to a business’s connected social, messaging, or email account).
“Personal Information” means information that identifies, relates to, or could reasonably be linked to an individual. It does not include aggregated or de-identified information that cannot reasonably be used to identify a person.
II. Lawful basis for processing
Where required by law, we rely on one or more lawful bases to process Personal Information: performance of a contract (providing the Services you or an Operator request); our legitimate interests in operating, securing, and improving the Services; your consent, where applicable (which you may withdraw at any time); and compliance with legal obligations. Where we rely on consent and you withdraw it, we will stop the relevant processing going forward.
III. What information we process
A. Information you provide
When you create an account or use the Services, we process information you provide - such as your name, email address, phone number, password (stored in hashed form), business details, and any content, settings, and records you create or import in the course of using the Services.
B. Information processed automatically
When you access the Services we automatically process certain technical information, such as device and browser data, IP address, log data, and usage information, including through cookies and similar technologies. See “Do Not Track” below.
C. Information from accounts you connect
Operators may connect third-party accounts and platforms - for example messaging, social, calendar, and payment accounts - so that Emma can operate on the Operator’s behalf. When you connect an account, we process the information necessary to provide the features you enable, limited to the access you grant, and we stop collecting from an account when you disconnect it. See Section VI for how we handle data from connected social and messaging platforms, Section VII for Google accounts, and Section VIII for Microsoft accounts, including what happens to information already received.
D. Communications
We may process the contents of communications handled through the Services - including messages exchanged between an Operator and its customers on connected channels - to provide, secure, and support the Services. We may also contact you with service, security, and administrative messages.
E. Discovery through external AI assistants
Bucket Operators can be discovered and booked through third-party AI assistants and agents - for example ChatGPT - using Bucket’s public agent endpoints. When a person searches for an experience through such an assistant, we receive and log the search text and basic search parameters (such as an approximate location) to return relevant results and to improve search quality. This search endpoint requires no Bucket account and we do not ask for or attach any personal identifier to these searches; the information we return to the assistant is Operator and experience listing data (titles, prices, locations, availability, and booking links), not a searcher’s personal information. Raw search text is retained for a limited period (currently 90 days) and then removed, while aggregate, non-identifying search statistics may be retained longer. Any booking a person chooses to complete happens on Bucket’s own secure checkout and is covered by the rest of this Policy.
IV. How we use information
- Provide, operate, maintain, secure, and improve the Services.
- Enable Emma to respond to inquiries, prepare quotes, place and manage bookings, and - only within the configuration and approvals an Operator sets - process payments and other actions on the Operator’s behalf.
- Process transactions and send related confirmations, receipts, and reminders.
- Provide support and respond to requests.
- Detect, prevent, and address fraud, abuse, and security issues.
- Comply with legal obligations and enforce our agreements.
Some features rely on automated systems and third-party technology providers to process content and generate responses, suggestions, and summaries. Actions that move money or create binding commitments run through the Operator’s configuration and approval; our automated systems do not charge a customer on their own.
V. How we share information
We do not sell Personal Information. We share it only as described below.
A. Service providers
We engage service providers to perform functions on our behalf - such as hosting and infrastructure, data storage, payment processing, communications delivery, analytics, security, and technology services that power the Services. Service providers may access Personal Information only to perform these functions for us and are bound to protect it. We may change the service providers we use at our discretion.
B. Connected platforms
When an Operator connects a third-party platform, information is exchanged with that platform as needed to provide the connected feature, in accordance with that platform’s terms.
C. Business transfers
If we are involved in a merger, acquisition, financing, or sale of assets, Personal Information may be transferred as part of that transaction, subject to this Policy or a successor policy.
D. Legal and protection
We may disclose information where we reasonably believe it is necessary to comply with law or legal process, enforce our agreements, or protect the rights, property, or safety of Bucket, our users, or others.
E. With your consent
We may share information for other purposes with your consent.
VI. Connected social & messaging platforms
Operators may connect social and messaging platforms - including Meta platforms such as Facebook, Instagram, and WhatsApp - so that Emma can send and receive messages, and, where the Operator enables it, publish posts and manage comments on the Operator’s own accounts. Information obtained through these platforms is used solely to provide the features the Operator has enabled, in accordance with the applicable platform terms (including the Meta Platform Terms and Developer Policies). We do not sell this information and do not use it for advertising. We retain it only as long as needed to provide the Services or as required by law, and you may request its deletion at any time - see our Data Deletion page.
VII. Google user data
Operators may sign in with Google and connect Google accounts so that Emma can work with them. This section covers information Bucket receives from Google APIs (“Google user data”). If anything else in this Policy conflicts with this section, this section controls for Google user data.
A. What Bucket accesses
- Sign in with Google: your name, email address, and profile photo, to create your account and sign you in.
- Google Calendar: when a booking is confirmed, Bucket adds it as an event on your primary calendar with the booking’s details (the experience, time, party size, any booking notes, and the customer’s name and contact details) and may add the customer as a guest on the event. It updates the event when the booking changes and deletes it when the booking is cancelled. Bucket does not read your other events or your free/busy times.
- Gmail: you choose your inbox or one Gmail label. From then on, Bucket reads each new message that arrives there (for a label, also older messages you later add to it), files it in your Bucket Inbox, adds the sender to your customer list or matches them to an existing customer, and notes what the customer says about themselves and their party, such as preferences, occasions, and dietary or access needs, so that Emma can answer as your settings allow and tailor later messages to that customer. It does not file spam, trash, drafts, bounces, automatic replies, or mail sent from your own address, and it never changes labels, filters, settings, or other mailbox content. From your Gmail address, Bucket sends replies, quotes, booking confirmations and updates, reminders, and follow-ups. Marketing (messages Bucket sends on its own to bring a customer back, such as return-visit and birthday notes, suggestions, and offers) never goes out from your Gmail: Bucket sends it from its own email service and never uses what a customer said in an email conversation to pick or write it. It also shows the connected account’s Google profile photo in Settings.
- Google Business Profile: when you connect, Bucket reads the accounts and locations you manage so that you can choose your listing. It then reads the listing’s reviews, rating, and daily performance figures; posts the review replies and updates that you approve or that your settings allow Emma to post, and removes an update you cancel; and adds your booking link to the listing. Once you publish your Bucket storefront, it shows your Google rating, review count, and recent reviews there, with each reviewer’s name as Google shows it. Bucket also uses your rating and review count to rank experiences in Bucket’s search, including searches made through AI assistants, and uses your listing’s place ID to link customers to your Google review page.
B. What we keep and how we protect it
For each connection we store the access and refresh tokens Google issues and the details needed to use it, such as your Gmail address and chosen label, or your Business Profile account and location. From Gmail we keep the text and subject of each message Bucket files (not its attachments), with the identifiers that thread replies to it, as part of the conversation in your Inbox, the sender’s name and address on the customer’s record, the details Emma notes about the customer, and the conversation history she uses to recall context. From Calendar we keep the identifier of each booking’s event. From Business Profile we keep your listing’s reviews, rating, review count, and daily performance figures, and its place ID, region, and map location, which also fill in your Bucket business profile.
Tokens are encrypted with AES-256-GCM before they are stored, Google user data travels only over encrypted connections, and access to it is limited as described below and in Section IX.
C. How we use and share it
We use Google user data only to provide and improve the features described in this section. We do not sell it, transfer it to data brokers or information resellers, use it to serve advertising (including retargeted, personalized, or interest-based ads), use it to determine creditworthiness or for lending, or use it to create, train, or improve artificial intelligence or machine-learning models.
To understand customer emails and Google reviews, draft replies, and note customer details, Emma sends their text to our AI service provider (currently OpenAI), which processes it only to provide these features and does not use it to train its models. Our hosting, data storage, and email delivery providers process Google user data only on our behalf. Beyond what you publish through Bucket, such as your storefront, we share it only with these providers, when the law requires it, or to protect against fraud and abuse. If Bucket is involved in a merger, acquisition, or sale of assets, we will ask for your consent before Google user data is transferred.
People at Bucket do not read Google user data unless you ask us to for support, it is needed for security, or the law requires it.
D. Disconnecting, retention, and deletion
You can disconnect Google Calendar, Gmail, or Business Profile in Settings at any time. Bucket then deletes the stored tokens for that connection, asks Google to revoke its access, and stops reading from or writing to that account. You can also remove Bucket’s access, including Sign in with Google, from your Google Account at myaccount.google.com/connections. Information Bucket already holds, such as filed messages, customer records, reviews, and performance figures, stays in your account, and events Bucket added stay on your calendar.
We keep Google user data only while your account is active. When you ask us to delete it, we do so within 30 days, except booking and payment records the law requires us to keep. To make a request, see our Data Deletion page.
Bucket’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
VIII. Microsoft user data
Operators may connect a Microsoft account so that Emma can work with Outlook mail and Outlook Calendar. This section covers information Bucket receives from Microsoft APIs, such as Microsoft Graph (“Microsoft user data”). If anything else in this Policy conflicts with this section, this section controls for Microsoft user data.
A. What Bucket accesses
- Your Microsoft account: the email address of each account you connect, and for Outlook mail also its account identifier, so that Settings shows which account is connected and one mailbox cannot be connected to two businesses.
- Outlook mail: Bucket lists the names of your mail folders so that you can choose your inbox or one folder. From then on, Bucket reads each new message that arrives there, files it in your Bucket Inbox, adds the sender to your customer list or matches them to an existing customer, and notes what the customer says about themselves and their party, such as preferences, occasions, and dietary or access needs, so that Emma can answer as your settings allow and tailor later messages to that customer. It never reads mail in your Sent Items, Drafts, Deleted Items, Junk Email, or Outbox; does not file drafts, bounces, automatic replies, meeting requests, or mail sent from your own address; and never moves, changes, or deletes your mail, folders, rules, or settings. From your Outlook address, Bucket sends replies, quotes, booking confirmations and updates, reminders, and follow-ups. Marketing (messages Bucket sends on its own to bring a customer back, such as return-visit and birthday notes, suggestions, and offers) never goes out from your Outlook address: Bucket sends it from its own email service, never uses what a customer said in an email conversation to pick or write it, and never sends it to an address that reached Bucket only in an Outlook email.
- Outlook Calendar: when a booking is confirmed, Bucket adds it as an event on your default calendar with the booking’s details (the experience, time, party size, any booking notes, and the customer’s name and contact details), marked as Bucket’s so that Bucket can find it again. It updates the event when the booking changes and deletes it when the booking is cancelled. Bucket does not read your other events or your free/busy times.
B. What we keep and how we protect it
For each connection we store the access and refresh tokens Microsoft issues and the details needed to use it, such as the account’s email address and identifier, your chosen folder, and the subscription through which Microsoft tells Bucket about new mail. From Outlook mail we keep the text and subject of each message Bucket files (not its attachments), with the identifiers that thread replies to it, as part of the conversation in your Inbox, the sender’s name and address on the customer’s record, the details Emma notes about the customer, and the conversation history she uses to recall context. From Outlook Calendar we keep the identifier of each booking’s event.
Tokens are encrypted with AES-256-GCM before they are stored, Microsoft user data travels only over encrypted connections, and access to it is limited as described below and in Section IX.
C. How we use and share it
We use Microsoft user data only to provide and improve the features described in this section. We do not sell it, transfer it to data brokers or information resellers, use it to target or serve advertising, or use it to create, train, or improve artificial intelligence or machine-learning models.
To understand customer emails, draft replies, and note customer details, Emma sends their text to our AI service provider (currently OpenAI), which processes it only to provide these features and does not use it to train its models. Our hosting, data storage, and email delivery providers process Microsoft user data only on our behalf. We share it only with these providers, when the law requires it, or to protect against fraud and abuse. If Bucket is involved in a merger, acquisition, or sale of assets, we will ask for your consent before Microsoft user data is transferred.
People at Bucket do not read Microsoft user data unless you ask us to for support, it is needed for security, or the law requires it.
D. Disconnecting, retention, and deletion
You can disconnect Outlook or Outlook Calendar in Settings at any time. Bucket then deletes the stored tokens for that connection and stops reading from or writing to that account. Disconnecting does not remove Bucket from the apps your Microsoft account has allowed: you can withdraw that permission at any time at account.live.com/consent/Manage for a personal Microsoft account, or at myapps.microsoft.com for a work or school account, where your organization’s administrator may need to remove it. Information Bucket already holds, such as filed messages and customer records, stays in your account, and events Bucket added stay on your calendar.
We keep Microsoft user data only while your account is active. When you ask us to delete it, we do so within 30 days, except booking and payment records the law requires us to keep. To make a request, see our Data Deletion page.
Bucket’s use of information received from Microsoft APIs follows the Microsoft APIs Terms of Use.
IX. Security
We maintain administrative, technical, and organizational safeguards designed to protect Personal Information, including encrypted transport, hashed credentials, scoped access, and least-privilege access controls. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.
X. Information you can access
Through your account settings you can access and update much of the information associated with your account. You may also contact us to request access to, correction of, or deletion of your Personal Information, as described below.
XI. Your rights
Depending on where you live, you may have rights to access, correct, delete, port, or restrict the processing of your Personal Information, and to object to certain processing or withdraw consent. To exercise these rights, contact go@trybucket.ai. We will not discriminate against you for exercising your rights.
European Union / United Kingdom
If you are in the EU or UK, you have the rights described above under the GDPR and UK GDPR. You also have the right to lodge a complaint with your local supervisory authority. Where we process Customer information on behalf of an Operator, the Operator is the controller and we act as its processor; please direct such requests to the relevant Operator, and we will assist as needed.
California
If you are a California resident, you have rights under the CCPA/CPRA to know, access, delete, and correct your Personal Information, and to opt out of any “sale” or “sharing” of it. We do not sell or share Personal Information as those terms are defined under the CCPA/CPRA. To exercise your rights, contact us using the details below.
XII. Retention
We retain Personal Information for as long as your account is active or as needed to provide the Services. We retain booking and transaction records as required for tax, accounting, fraud-prevention, and legal purposes, after which we delete or de-identify information we are not required to keep.
XIII. Children
The Services are not directed to children, and we do not knowingly collect Personal Information from anyone under 18. If you believe a minor has provided us information, contact us and we will delete it.
XIV. Do Not Track
We use strictly-necessary cookies for authentication and a limited set of analytics cookies to operate and improve the Services. We do not use third-party advertising cookies. Because there is no common industry standard for “Do Not Track” signals, we do not currently respond to them.
XV. Changes to this Privacy Policy
We may update this Privacy Policy from time to time. Changes take effect when posted, as indicated by the “Effective” date above, and we will provide additional notice where required.
XVI. Questions or concerns
Bucket Global, Inc. - 1080 Folsom St, San Francisco, California 94103, USA. Contact go@trybucket.ai with any privacy questions or requests.