Issue and source identifiers
Issue, source and event identifiers support routing, tracking and duplicate handling.
GDPR by design
SLA monitoring without customer personal data in supported integration payloads.
SLApulse keeps the supported Jira Cloud and generic webhook flows focused on the operational references needed to calculate and explain an SLA. This page explains that boundary and the part your team plays in keeping it intact.
The retained SLA event
A closed set of operational fields
For a supported event, SLApulse retains only the references and codes needed to route an issue, calculate SLA state and explain the result.
Controlled SLA signals
Event, change, status, priority and configured issue-type values support SLA rules and workflow state.
Relevant timestamps
Creation and occurrence times let SLApulse calculate the SLA clock and explain its outcome.
What happens to other fields
Extra payload fields are discarded before storage.
Supported generic webhook payloads are reduced to the listed SLA fields before they are stored or passed through the SLA processing flow. Titles, descriptions, comments, attachments, reporter and assignee details, user profiles and arbitrary nested objects are not part of that retained event.
Payloads that are not valid event objects, such as a top-level array, are rejected. Jira Cloud responses can contain additional data in short-lived transit; SLApulse projects the response immediately to the operational fields it needs and does not persist, publish or log the extra response content.
Your setup
Send neutral operational values only.
Keep names, email addresses, free text, attachments and other personal information out of your supported integration payloads. Use neutral, source-controlled status and type values; do not put personal information in a status or type label.
If your source system cannot meet this boundary, pause the integration setup and contact us before sending data. This data boundary describes the supported SLA integration flow. It is not a statement that every customer use case or every part of the service is fully GDPR compliant.
Account and service relationship
Your account details have a separate privacy context.
SLApulse still needs to handle account, contact, support and billing information to run the service. Read the Privacy Policy for that controller processing, or contact us with a question about your setup.