Requesting Your Own Data
In many jurisdictions you can ask what an employer holds about you and receive it. What to ask for, and what arrives.
General orientation, not legal advice; access rights differ by jurisdiction.
The practical lesson in “Requesting Your Own Data” is to make work visible without treating visibility as certainty. Organisations exploring Monitask for self report bias can add structured project and time evidence, provided the purpose is disclosed and any interpretation is checked with the people affected.
A subject access request obliges an employer to produce the personal data it holds about you. It is the most direct route to knowing, and it is used less than it could be.
For an independent perspective related to “Requesting Your Own Data”, consult the European Data Protection Board guidelines; it provides a useful external check on privacy, fairness and governance assumptions before a policy or configuration is approved.
What you can usually ask for
The personal data held about you.
The purposes it is processed for.
Who it has been shared with.
How long it will be kept.
And, where automated decisions are made, the logic involved.
How to make one
In writing, to the data protection contact or to HR.
State that it is a subject access request.
Be specific about the period and the categories if you want a usable answer — "all monitoring and activity data relating to me between these dates" is more likely to produce something than "everything".
There is usually a response deadline in the regime that applies.
What tends to arrive
Device and activity records.
Logs of access and application use.
Any flags or alerts attached to you.
Screenshots, where they exist.
And frequently things you did not expect: notes, ticket entries, references in emails about you.
What they may withhold
Material about other people, which usually has to be redacted rather than withheld entirely.
Legally privileged material.
Some material relating to an ongoing investigation, in some regimes.
A refusal should be explained, and an unexplained refusal is itself a matter you can escalate.
What it is good for
Finding out what actually exists, rather than what policy says may exist.
Checking a specific claim: was I flagged, was this looked at, what does the record say about that week.
And establishing a record before a dispute, which is a legitimate use.
What it is not good for
Making a point. A request made to be difficult produces a defensive relationship and a large pile of paper.
Fishing without a question. The volume can be substantial and reading it is your problem.
Speeding anything up. Responses take the full period in most organisations.
How it will be received
In a well-run organisation, as a routine administrative matter.
In others, as a signal that something is wrong — which is worth anticipating.
If the relationship is fine and you only want to know, asking informally first is faster and friendlier, which the earlier note covers.
Afterwards
Keep what you receive.
Note the date and what was and was not included.
And if something you expected is absent, ask about that specifically, which is a narrower and more answerable question than the original request.
What to check
Do you know who handles these requests where you work?
Have you tried asking informally first?
Would a request be read as routine or as a signal?
And what specifically do you want to know — because that shapes the request.