Published 11 September 2026. Version 1.0. Contractual terms take effect through the applicable agreement mechanism.
Permissions and boundaries
Triage Helper requests freshservice.tickets.view, freshservice.tickets.conversations.view and freshservice.requesters.view. Four fixed GET templates use the current Freshservice host. The app does not assign, edit, reply to or close tickets.
Data handling
Permitted ticket and conversation responses are processed in browser memory. Responses may contain personal profiles or message bodies; those fields are discarded. Ticket subjects remain potentially sensitive. There is no PezTech application backend, persistent ticket cache, analytics or automatic diagnostic upload. Freshworks manages OAuth, request proxy and settings.
Controls
Host and numeric IDs are validated, displayed strings are escaped, and raw errors are replaced with safe messages. Identity changes and access loss cancel or clear results. Scan budgets and pacing bound requests; incomplete evidence and failed refreshes remain visible.
Validation and limitations
Version 0.3.0 passed automated checks and normal Freshworks validation/packaging, plus representative live development acceptance. A second organisation and exhaustive concurrency/accessibility combinations were not exercised. Freshservice's minimum outer-page width requires horizontal scrolling at 200% zoom; app controls remained usable. These checks are not a security certification or Marketplace approval.
Report an issue
Email support@peztechsoftware.co.uk. Include safe reproduction steps; do not send credentials or unrelated customer information. Privacy Notice · Customer DPA.