Privacy Policy

Last updated: November 12, 2026

1. Introduction and scope

This Privacy Policy explains what information ChatShield collects, receives and stores when you use the ChatShield website at chatshield.cloud and the ChatShield app, including our Zendesk and Intercom integrations. It covers how that information is used, who it is shared with, and how you can ask us to delete it.

It applies to people who create a ChatShield account (“customers”) and, where relevant, to the people whose support conversations are analyzed through a customer's connected helpdesk (for example, end customers and support agents).

2. About ChatShield

ChatShield is a software service that reviews customer-support conversations — written by AI chatbots or human agents — and flags replies that may create legal or liability risk, so a person can review them. ChatShield does not provide legal advice.

Customers choose which helpdesk workspace to connect and which conversations are processed through ChatShield. ChatShield processes this information to provide its conversation monitoring and risk-analysis services. Zendesk and Intercom are independent companies with their own privacy policies.

3. Information we collect from you

  • Account information: your email address, password (processed by our authentication service, which stores it in hashed form; ChatShield's own code does not save passwords), and, if you provide them, your full name and business name.
  • Subscription information: your plan and subscription status, plus the customer ID and subscription ID that our payment provider, Paddle, assigns to you. We do not receive or store your card or bank details.
  • Integration information: the Zendesk subdomain or Intercom workspace ID you connect, and the access credentials (tokens) those services issue to ChatShield.
  • Emails we send: to send account emails (for example email verification and password reset), we pass your email address to our email delivery provider.
  • Messages you send us: if you email our support address, we receive what you send.
  • Transcripts sent to your private ingest address: each account has a private web address that can receive conversation transcripts from other tools. Any transcript sent to it is stored with your account in the same way as helpdesk conversations.
  • Technical information: our hosting and database providers process standard request information (such as IP address, browser details and request times) to deliver and protect the service. ChatShield does not build profiles from it.

4. Information received through Zendesk

When you connect Zendesk, you sign in on Zendesk and approve these permissions: tickets:read, users:read, webhooks:write, triggers:read and triggers:write.

What we read from Zendesk

  • Recent ticket list (up to 25 most recently updated tickets): ticket ID, subject, description, status, priority, requester ID, ticket URL and created / updated times. This list is shown to you on your dashboard and is not saved by ChatShield.
  • Individual tickets and their comments, when a ticket is analyzed: ticket subject and all comments, including each comment's text, author ID, time and whether it is public. We also read the names and roles of the people who wrote the comments.
  • Private internal notes: Zendesk returns internal (non-public) comments together with public ones, and ChatShield currently includes them. Internal notes are therefore analyzed and stored in the same way as public replies.

What we store

  • The ticket ID, subject and a written transcript of the ticket made up of each comment's author name and text.
  • The risk-analysis results described in section 7.
  • Your Zendesk subdomain, access token, refresh token and token expiry time, so the connection keeps working.

We do not store requester email addresses, ticket priority, tags, attachments or other Zendesk records.

Webhook

After you connect, ChatShield asks Zendesk to create a webhook named “ChatShield Ticket Events” in your account. When Zendesk sends us an event, we use it only to identify your account and the ticket ID, and then fetch that ticket as described above. We do not keep the raw event.

5. Information received through Intercom

When you connect Intercom, you approve ChatShield on Intercom's own authorization screen, which shows the permissions granted. ChatShield stores the access token Intercom issues and your Intercom workspace ID.

  • Conversations: when Intercom notifies ChatShield about a conversation, we fetch that full conversation. For each message we use the text and the author's display name and type (customer, agent or bot). If no name is available, we label the author “Customer” or “Agent”. ChatShield does not filter out internal notes, so any note that appears in the conversation is analyzed and stored too.
  • What we store: the Intercom conversation ID, subject (if any), the messages (author name and text) and the risk-analysis results.
  • Workspace: we read your workspace ID from Intercom to match incoming events to your account.

We do not store customer email addresses, phone numbers or other contact attributes from Intercom.

6. How we use information

  • To create and secure your account and let you sign in.
  • To connect your helpdesk and keep that connection working.
  • To analyze support conversations, find replies that may be risky, and show you the results with the surrounding conversation.
  • To manage your subscription and access through Paddle.
  • To send account emails such as verification and password reset.
  • To answer your support requests.

7. AI-powered conversation analysis

To analyze a conversation, ChatShield sends the conversation transcript to an AI model. The transcript includes the ticket or conversation subject and every message's author name and text — including any names, contact details or other personal information that people wrote in those messages, and any internal notes included as described above.

The request goes through the Lovable AI Gateway (operated by Lovable) to a Google Gemini model. The AI returns a risk level and a list of flagged messages, each with a category, a severity and a quote of the flagged text. ChatShield stores these results with the conversation.

AI results can be wrong or incomplete. They are signals for human review, not legal conclusions or legal advice.

How long Lovable and Google keep request data, and whether they may use it, is governed by their own terms. ChatShield does not make separate promises about provider retention or model training.

8. Service providers and data sharing

We do not sell personal information. We share it only with the service providers we use to run ChatShield:

  • Website hosting (Lovable, delivered through Cloudflare) — serves the ChatShield website and runs its server-side functions, so it processes the requests and data that pass through the app.
  • Database and authentication (Lovable Cloud, built on Supabase) — stores account data, connection tokens, conversations and analysis results, and handles sign-in.
  • Lovable AI Gateway — transmits conversation transcripts to the AI model and returns the results.
  • Lovable visitor analytics — records website usage statistics as described in section 13.
  • Google (Gemini) — the AI model that analyzes conversation transcripts.
  • Paddle — processes payments and subscriptions as merchant of record. Paddle collects your payment details directly under its own privacy policy.
  • Resend — delivers account emails and receives your email address and the email content.
  • Zendesk and Intercom — the helpdesks you choose to connect. ChatShield exchanges data with them at your direction.

Each provider handles data under its own terms. We may also disclose information when required by law or legal process, to protect the rights, safety or security of ChatShield, our customers or others, or as part of a merger, acquisition or sale of the business. We do not sell personal information.

9. Data storage and security

  • Data is stored in a managed PostgreSQL database provided through Lovable Cloud (built on Supabase). We do not make additional claims about storage location or encryption at rest.
  • Database row-level security limits each signed-in customer to their own account record and their own conversations.
  • Connections between your browser and ChatShield, and between ChatShield and Zendesk, Intercom, the AI gateway, Paddle and Resend, use HTTPS.
  • Helpdesk access tokens are kept in your account record and are not encrypted separately by ChatShield. They are protected by the database access controls above, and the signed-in account owner's own browser session can read them for that account.
  • Zendesk access tokens expire and are renewed automatically using the refresh token.
  • Payment events from Paddle are verified with a cryptographic signature before we act on them. Incoming Zendesk and Intercom events are not currently signature-verified; ChatShield instead uses them only to identify a ticket or conversation, and then fetches the content directly from Zendesk or Intercom using your connection.

10. Data retention

ChatShield does not currently delete stored conversations or analysis results automatically after a set period. They are kept until you delete them or ask us to delete them, or your account is deleted.

11. Data deletion and disconnecting a helpdesk

  • Disconnecting Zendesk removes the stored access token and subdomain, so ChatShield stops reading your Zendesk data. The stored refresh token and token expiry time are not currently removed automatically; you can revoke ChatShield's access in Zendesk at any time, and we will delete them on request.
  • Disconnecting Intercom removes the stored access token and workspace ID.
  • Disconnecting does not delete conversations and analysis results already stored in ChatShield. The webhook created in Zendesk is also not removed automatically; you can delete it in Zendesk.
  • There is no self-service account deletion button yet. To delete your account and all associated data, email us at the address below and we will delete it from the ChatShield database. Copies held by providers (for example in their backups or logs) are handled under those providers' own retention terms.

12. International data transfers

Our service providers may process information in countries other than your own. Please contact us if you need details about where specific data is processed.

13. Cookies and analytics

ChatShield uses your browser's local storage to keep you signed in. Our hosting network (Cloudflare) may set a short-lived security cookie used to protect the site from abusive traffic. We do not use advertising cookies.

We use Lovable's visitor analytics on chatshield.cloud. It uses no cookies, stores nothing on your device, doesn't keep IP addresses and doesn't identify visitors. It records the pages visited, where visitors came from, their country, browser, operating system and device type, how long they stay, how fast pages load, errors, and which buttons and links are clicked. These are recorded for every visitor. Detailed data is kept for 90 days and daily summaries for a year. Lovable collects this data for us. Lovable's privacy policy explains how it handles it.

When you open checkout or subscription management, Paddle's own scripts load and may use cookies under Paddle's policy. An Intercom chat widget loads only for ChatShield's own administrator account, not for customers or visitors.

14. Your privacy choices and requests

You can view and update your account details in the app, disconnect a helpdesk at any time, and contact us to access, correct or delete your information.

If you are an end customer or agent whose conversations were analyzed through a ChatShield customer's helpdesk, please contact that business first, as they control that data. You can also contact us and we will help where we can.

15. Children's privacy

ChatShield is a business service and is not directed at children. We do not knowingly collect information from children through account sign-up.

16. Changes to this policy

We may update this policy when ChatShield changes. We will update the date at the top of this page when we do.

17. Contact

Privacy questions or deletion requests: support.chatshield@gmail.com