Leaf

Privacy Policy

Last updated 30 September 2026

Who we are

Leaf (“Leaf”, “we”, “us”) is a conversational customer-support service operated by Tealdroid LLP. Leaf helps online merchants answer their customers' questions — on WhatsApp, Instagram, and Facebook Messenger, by email, and in comments on the merchant's Facebook and Instagram posts — by looking up information from the merchant's connected store and replying, or drafting a reply, on their behalf. This policy explains what data we handle and why.

Data we process

When a merchant connects their accounts and a customer sends a message, we process:

  • Message content sent to a connected WhatsApp, Instagram, or Messenger account, and the reply we generate.
  • If the merchant connects a mailbox: the emails that arrive in it — the sender's name and address, the subject and the text — so we can tell customer support emails from other mail and answer or draft a reply. For email we identify as something other than customer support (such as newsletters or automated notices), we keep only a record that it was skipped, not its content.
  • If the merchant turns on comment replies: comments left on the merchant's Facebook Page or Instagram posts — the comment text and the commenter's name or username and platform-scoped ID — and the reply, which may be posted publicly under the comment or sent to the commenter as a private message.
  • The customer's channel identifier — a phone number (WhatsApp), an email address (email), or a platform-scoped user ID (Instagram, Messenger, and comments).
  • Order information from the merchant's connected Shopify store needed to answer a question — such as order status, fulfilment, and tracking. Where an order is looked up, we read the contact details on that order (name, email, phone) only to confirm the person asking is entitled to it.
  • Account and connection data for the merchant: store domain, connected channel identifiers and mailbox addresses, the access tokens that authorize Leaf to act for them, and the email address the merchant chooses for alerts.
  • How Leaf's replies performed: a confidence score for each reply, drafts Leaf wrote for the merchant's team and whether they were sent, edited or discarded, and suggested knowledge base entries.

How we use it

We use this data solely to provide the service:

  • To understand a customer's question and generate a relevant reply.
  • To look up the specific order or information a question is about.
  • To verify that a customer is entitled to the order details they ask for, before revealing them.
  • To maintain the conversation so replies have context.
  • To score how confident Leaf is in a reply, and so decide whether it is sent automatically or passed to the merchant's team with a suggested draft, as the merchant has chosen.
  • To suggest knowledge base entries from how the merchant's team answered customers. A suggestion is only used once the merchant approves it.
  • To alert the merchant by email when a conversation needs a person.

We do not sell personal data, use it for advertising, or use message content to train general-purpose AI models.

Service providers

Leaf shares data with a small number of processors, only as needed to run the service:

  • Meta Platforms — to receive and send messages on WhatsApp, Instagram, and Messenger, and to read and reply to comments on the merchant's Facebook and Instagram posts.
  • Shopify — to read order and store information from the merchant's connected store.
  • Microsoft Azure — to host the service and to generate and assess replies using Azure AI (OpenAI) language models.
  • Microsoft 365 — if the merchant connects a Microsoft 365 or Outlook mailbox, to read and send email in that mailbox; and to send Leaf's own notification emails.
  • Google — if the merchant connects a Google Workspace mailbox, to read and send email in that mailbox through the Gmail API, and to be notified of new mail through Google Cloud Pub/Sub.
  • Zoho — if the merchant connects a Zoho Mail mailbox, to read and send email in that mailbox through the Zoho Mail API.
  • Supabase — to store conversations and connection data.

Each provider processes data under its own terms and only for the purposes above.

Data retention

We keep conversation history and connection data for as long as the merchant's account is active, so the assistant can maintain context and the merchant can review past conversations. When a merchant disconnects a channel or mailbox, or uninstalls Leaf, the associated access tokens are revoked or deleted. Incoming messages we could not process are kept for about a week for troubleshooting, then deleted. You can request deletion of stored data at any time (see below).

Your rights and data deletion

Depending on where you live, you may have the right to access, correct, or delete personal data we hold, or to object to its processing.

To request deletion of data associated with you or your account, email support@tealdroid.com with the phone number, email address, or account the messages came from. We will delete the associated conversation data and confirm once done. Merchants can also remove their data by uninstalling Leaf and contacting us to erase stored records.

Security

Access tokens and customer data are stored in access-controlled systems and transmitted over encrypted connections, and access tokens for connected accounts and mailboxes are encrypted at rest. Access to production data is limited to what is required to operate the service.

Children

Leaf is a tool for businesses and is not directed at children. We do not knowingly collect data from children under 13 (or the minimum age in your jurisdiction).

Changes to this policy

We may update this policy as the service evolves. Material changes will be reflected by updating the date at the top of this page.

Contact

Questions about this policy or your data? Email support@tealdroid.com.