Find and sort the privacy requests in your inboxes

Fields

• Channel (email, chat, help centre form, social message, letter)
• The whole message or conversation

Questions

1. Does the person getting in touch ask to exercise a right over personal data, such as seeing, correcting or deleting it, or stopping marketing? Yes / No

   Count a request to see or get a copy of personal data, to be told what is held or who it was shared with, to delete, correct, move or restrict it, to object to a use of it, to stop marketing, to opt out of its sale or sharing, or to withdraw consent. Count it in any words, such as "everything you have on me" or "the notes about me", whether or not a law or right is named, and when it sits inside a message about something else. A request for a routine document, such as a payslip, an invoice or an employment letter, is not a data request. Read only what the person getting in touch says, not the agent. Yes: They make at least one such request about their own data or the data of someone they act for. No: They make no such request. A general question about the privacy policy is No.

2. What does the sender mainly ask for about personal data? Choice

   When the sender asks for more than one right, pick the one they ask to be done first.

   • Access A copy of their data, or to be told what is held, who it was shared with or where it came from.
   • Deletion Erase their data, or close the account and delete what is held.
   • Correction Fix or complete data that is wrong or out of date.
   • Portability Their data in a usable file, for themselves or to pass to another company.
   • Objection or restriction Stop or pause a particular use of their data other than marketing, or not be subject to an automated decision.
   • Stop marketing Stop marketing emails, texts, calls or post sent to them.
   • Opt out of sale or sharing Stop their data being sold or shared with other companies, including for targeted advertising.
   • Withdraw consent Take back a consent they gave for something other than marketing, such as location or health data in the app.
   • Complaint about data handling Complains about how their data was used, shared or protected, without asking for any right above.
   • Question about privacy Asks about our data practices or the privacy policy, with no request.
   • No privacy matter The message raises nothing about personal data.

3. Does the sender ask for more than one right over their personal data, such as a copy and then deletion? Yes / No

   Count these rights: access, deletion, correction, portability, objection or restriction, stopping marketing, opting out of sale or sharing, and withdrawing consent. Yes: The sender asks for two or more different rights. No: The sender asks for one right, or none.

4. What is the relationship to us of the person whose data the message is about? Choice

   Judge the person whose data it is. When someone writes for another person, judge that person. Use the context to tell our own customers from members who use the app through a gym.

   • Our customer or user Has or had an account, an order, a subscription or an app sign-up directly with us.
   • User of a business customer's service Uses a service we run for one of our business customers, such as a member using the app through their gym; that business customer answers the request.
   • Current or former employee Works or worked for us.
   • Job applicant Applied for a job with us and did not join.
   • Never a customer Never had an account or an order: a marketing contact, a website visitor, or someone whose details reached us from elsewhere.

5. Is the person getting in touch acting for someone else, such as a relative, carer, parent, lawyer or claims firm? Yes / No

   Count anyone who says they are getting in touch for the person whose account or data it is. Someone who writes for themselves and copies in a lawyer is acting for themselves. Yes: The person says they act for someone else. No: The person acts for themselves, or makes no request.

6. Does the message concern the personal data of someone under 18? Yes / No

   Count it when the message says or clearly shows the person is a child, such as "my son's account" or a stated age under 18. Do not guess an age from writing style. Yes: The data is about a person the message shows to be under 18. No: Nothing in the message shows the person is under 18.

7. Does the sender mention a lawyer, legal action, or a complaint to a data protection authority or other regulator? Yes / No

   Count a threat, or a statement that it has already been done. Do not count a plain question about how to complain. Yes: The sender says they have gone, or will go, to a lawyer, a court, a data protection authority or another regulator. No: No such step is mentioned.

8. Does the sender complain about us, or raise a claim or a dispute, in the same message as the request? Yes / No

   Count dissatisfaction about any matter in the same message, such as a late order, a charge, unwanted contact or how they were treated, and an employment dispute. Yes: The message contains a complaint, a claim or a dispute as well as, or instead of, a request. No: The sender raises no complaint, claim or dispute.

9. Does the message give details that would let staff find the records of the person it is about? Yes / No

   Count an account email, a customer or member number, an order number, a phone number or a gym membership given in the message, or a sender address in email headers. Yes: At least one such detail appears. No: No such detail appears, so staff would have to ask for one.

10. Is it clear enough what the sender wants for staff to start the request without writing back? Yes / No

    Judge only what the sender asks for, not whether their identity is proven; code and the privacy team handle identity. Yes: The message is a privacy request, and it is clear which data and which right it concerns. No: The request is too vague to start, or the message makes no privacy request.

Lens columns

data_request, data_request_probability, primary_right, primary_right_probability, multiple_rights, multiple_rights_probability, requester_relationship, requester_relationship_probability, on_behalf_of_other, on_behalf_of_other_probability, concerns_child, concerns_child_probability, legal_or_regulator_threat, legal_or_regulator_threat_probability, complaint_alongside, complaint_alongside_probability, locating_details_given, locating_details_given_probability, enough_to_act, enough_to_act_probability