# Reducing Handling Time for Data Access Requests

> TechSupport Team supported PrivacyAxis’ Python and Kafka workflow for data subject access requests. Over five months, the client’s Jira Service Management data show average handling time falling from 11 to 1.4 days and manual data mapping from 80 to 10 hours per week.

- Publisher: TechSupport Team
- Canonical page: https://techsupport-team.com/case-studies/privacy-saas-dsar-workflow-automation/
- Updated: 2026-11-16

Client: PrivacyAxis · Security & Compliance · EU privacy SaaS (90 staff)

## Client and engagement facts

- **Client:** PrivacyAxis
- **Industry:** Security & Compliance
- **Business context:** EU privacy SaaS (90 staff)
- **Delivery model:** Privacy workflow engineering
- **Application:** GDPR DSAR handling platform
- **Supplied geography:** EU
- **Company size in source:** 90 staff

## Application stack and tools

### Application stack

- Python
- PostgreSQL
- Kafka
- AWS

### Tools used

- Jira Service Management
- Jira
- client compliance register

Related services: [Application support](https://techsupport-team.com/services/application-support/)

## Why Support Was Needed

Four upstream systems were documented, and discovery identified twelve. The engineers mapped the sources before automating collection, report generation and deadline alerts.

## Technical Work

- Automated data-mapping from 12 source systems (client had documented 4).
- Built a DSAR PDF-generation pipeline.
- Added deadline alerting 5 days before each deadline.

## Representative Incident

The client received a regulator deadline extension in month four. The team recorded the extension in the compliance register and excluded it from the missed-deadline measure.

## Results and how they were measured

Table: Reported results and their measurement scope

| Metric | Baseline | Result | Units | Measurement window | Source and scope |
| --- | --- | --- | --- | --- | --- |
| DSAR handling | 11 days | 1.4 days | days | 5 months | Client JSM |
| Manual data-mapping | 80 h/wk | 10 h/wk | h/wk | 5 months | Client Jira |
| Missed deadlines | 6/q | 0/q | /q | 5 months | Client JSM; Scope: The five-month deadline measure excludes one granted extension. |

## Evidence and Limitations

The five-month deadline measure excludes one granted extension. Handling time and mapping hours come from the client’s issue trackers.

## Data Source Change Process

The engagement provided for ongoing discovery and updates to the mapping within five business days.

## Scope a Similar Engagement

Share the request types, source systems and handoffs that delay work in your application. [Request a support plan](https://techsupport-team.com/contact/) or explore [application support](https://techsupport-team.com/services/application-support/).

## Related pages

- [Application support](https://techsupport-team.com/services/application-support/): The related service for this engagement.

## Contact

Request engineers from TechSupport Team or ask a question: https://techsupport-team.com/contact/
