1. Information we may collect
ZestInbox may process account information, workspace settings, team member details, support widget configuration, customer messages, tickets, AI outputs, and usage metadata needed to run the service.
Privacy
Privacy overview.
Draft privacy content for the ZestInbox beta. This page should be reviewed by a qualified privacy or legal professional before public launch.
Last updated: July 19, 2026
2. Customer messages and tickets
Customer messages submitted through a website or app widget may include names, email addresses, message content, metadata, and conversation history. Workspace owners are responsible for how they respond to customers.
3. AI processing
ZestInbox may send relevant ticket content to AI systems to generate summaries, categories, priority scores, recommended actions, and draft replies. AI outputs should be reviewed by a human before being sent.
4. Billing and account data
Billing providers may process subscription, invoice, tax, payment, and plan information. ZestInbox should store only the billing metadata needed to manage account access and plan limits.
5. How information is used
Data may be used to operate the inbox, deliver customer replies, enforce plan limits, improve support workflows, protect against abuse, maintain security, and provide customer support.
6. Sharing and service providers
ZestInbox may use providers for hosting, authentication, email delivery, billing, AI processing, analytics, monitoring, and support. Final privacy terms should list material subprocessors before launch.
7. Security and access controls
The product should protect workspace data with role-based access, workspace isolation, secure authentication, audit history, and reasonable technical safeguards.
8. Retention and deletion
Retention periods, customer deletion, ticket deletion, workspace deletion, exports, and audit-log retention should be documented clearly before public launch.
9. Your choices
Users should be able to update account details, manage team access, control workspace settings, request deletion where applicable, and contact support with privacy questions.