Article 37: Filing and processing complaints

Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.

1. The Data Subject may complain to the Competent Authority within a period not exceeding (90) days from the date of the incident or the date on which the Data Subject became aware of it. The Competent Authority shall determine whether to accept the complaint or not after this period in cases where there are reasonable causes that may have prevented the Data Subject from submitting the complaint in time.

2. The Competent Authority shall receive the complaints that are submitted to it, through the designated means and according to procedures that ensure celerity and quality.

3. The Competent Authority shall keep a record of the complaints filed in a register specifically created for this purpose.

The complaint shall include the following information:

  1. Place and time of the violation.
  2. Name, identification, address, and telephone number of the complainant.
  3. Information about the complained entity.
  4. Clear and specific description of the violation, along with the evidence and the information provided with the complaint.
  5. Any other requirements specified by the Competent Authority.

Best practices
How to implement:
Article 37: Filing and processing complaints
This policy on
Article 37: Filing and processing complaints
provides a set concrete tasks you can complete to secure this topic. Follow these best practices to ensure compliance and strengthen your overall security posture.

1. The Data Subject may complain to the Competent Authority within a period not exceeding (90) days from the date of the incident or the date on which the Data Subject became aware of it. The Competent Authority shall determine whether to accept the complaint or not after this period in cases where there are reasonable causes that may have prevented the Data Subject from submitting the complaint in time.

2. The Competent Authority shall receive the complaints that are submitted to it, through the designated means and according to procedures that ensure celerity and quality.

3. The Competent Authority shall keep a record of the complaints filed in a register specifically created for this purpose.

The complaint shall include the following information:

  1. Place and time of the violation.
  2. Name, identification, address, and telephone number of the complainant.
  3. Information about the complained entity.
  4. Clear and specific description of the violation, along with the evidence and the information provided with the complaint.
  5. Any other requirements specified by the Competent Authority.

Read below what concrete actions you can take to improve this ->
Frameworks that include requirements for this topic:
No items found.

How to improve security around this topic

In Cyberday, requirements and controls are mapped to universal tasks. A set of tasks in the same topic create a Policy, such as this one.

Here's a list of tasks that help you improve your information and cyber security related to
Article 37: Filing and processing complaints
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
No other tasks found.

How to comply with this requirement

In Cyberday, requirements and controls are mapped to universal tasks. Each requirement is fulfilled with one or multiple tasks.

Here's a list of tasks that help you comply with the requirement
Article 37: Filing and processing complaints
of the framework  
Personal Data Protection Law (Saudi Arabia)
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Procedure for managing data protection complaints
Critical
High
Normal
Low
1
requirements
Privacy
Informing and data subject requests

Procedure for managing data protection complaints

This task helps you comply with the following requirements

Document complaints and their disposition
Critical
High
Normal
Low
2
requirements
Privacy
Security and responsibilities

Document complaints and their disposition

This task helps you comply with the following requirements

The ISMS component hierachy

When building an ISMS, it's important to understand the different levels of information hierarchy. Here's how Cyberday is structured.

Framework

Sets the overall compliance standard or regulation your organization needs to follow.

Requirements

Break down the framework into specific obligations that must be met.

Tasks

Concrete actions and activities your team carries out to satisfy each requirement.

Policies

Documented rules and practices that are created and maintained as a result of completing tasks.

Never duplicate effort. Do it once - improve compliance across frameworks.

Reach multi-framework compliance in the simplest possible way
Security frameworks tend to share the same core requirements - like risk management, backup, malware, personnel awareness or access management.
Cyberday maps all frameworks’ requirements into shared tasks - one single plan that improves all frameworks’ compliance.
Do it once - we automatically apply it to all current and future frameworks.