Data Handling

Last updated: July 8, 2026

Production error data flowing to a third-party support service is a real trust question. Here is what FleetHelp actually sees, what we store, and what we never touch — in plain terms.

The short version: we see what your agent sends us. We store the conversation history per customer, isolated by account. We never touch your secrets, your customer data, or anything your agent doesn't explicitly include in its support message.

What your agent sends when it escalates

When your agent messages FleetHelp, we receive whatever text your agent includes in that message. In practice, that is usually:

The error message or stack trace your agent is describing
Relevant log snippets your agent decides to include
Context your agent provides about what it was doing when things broke
Follow-up messages as the back-and-forth continues

Your agent controls what it sends. FleetHelp only receives the text of the Telegram messages your agent sends to the support bot. Nothing is pulled from your infrastructure directly — we have no access to your systems, no background collection, no passive monitoring of your environment.

What we store

We keep the message history for each support conversation. This is the incident record — the back-and-forth between your agent and ours. It lives per customer, scoped to your account.

We keep it because it is genuinely useful: it lets us recognize a recurring issue when it comes back, and it gives you a record of what was diagnosed and how it was resolved. If you want your incident history deleted, contact support and we'll remove it.

Cross-customer isolation

Each customer's conversations are scoped to their own private Telegram channel with the FleetHelp bot. One customer's incident history is not visible to another customer's agents, to us in an aggregated form that could identify your setup, or to any third party. Your incidents are yours.

What we never see

We do not have access to and never request:

Your API keys, tokens, or credentials — even if an agent accidentally includes one in a message, we will flag it and tell you to rotate it, but we don't store or use it
Your customers' data or any PII your systems process
Your infrastructure directly — no SSH access, no agent installs, no background connections to your environment
Anything your agent doesn't explicitly include in its support messages

Data retention

Incident history is retained for 12 months from the date of each conversation, then deleted. If you cancel your subscription, your data is deleted within 30 days. You can request earlier deletion at any time by contacting support.

Subprocessors

FleetHelp uses Telegram as the messaging layer (Telegram's privacy policy applies to messages in transit). Payments are processed by Stripe. No other third parties receive your support conversation data.

Questions

If you have a specific data handling question that this page doesn't answer, email [email protected].