Privacy and data handling
Effective July 25, 2026. Applies to the Sendrel app for Zendesk, published by 3Bit Machine LLC.
Sendrel handles your customers' conversations, so this page is specific about what the service touches, what it keeps, and what it never does.
Access scopes
Sendrel requests two Zendesk OAuth scopes: tickets:read and tickets:write. Nothing else. It cannot read your users, your organizations, your settings, or anything outside tickets.
Ticket content is not stored
When an agent sends a forward, the selected comment content passes through the service to build and send the email, and is then discarded. Sendrel does not keep copies of comments, attachments, or email bodies.
Only metadata is kept: which comments were forwarded, to whom, and when. This is what powers the sending history in the sidebar.
The summary feature
When an agent turns on the summary feature for a send, the selected comments are sent to an LLM API to generate a draft. Three controls apply:
- It is opt in, per send. The default is to forward the comments as they are.
- An administrator can disable the feature for the whole account.
- The agent always reviews and can edit the draft before it leaves.
No model training
Customer data is not used to train models, by us or by our LLM provider under the terms we hold with them.
Credentials
OAuth tokens are encrypted at rest. All traffic between your browser, Zendesk, and the service uses HTTPS.
This website
This site sets no cookies, loads no analytics or trackers, and serves all assets, including fonts, from its own domain.
Questions
Write to help@sendrel.app. A person reads it.