Article 29: Direct marketing

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

1. Without prejudice to the Telecommunication and Information Technology Act or any other related laws, before Processing Personal Data for Direct Marketing purposes, the Controller shall abide by to the following:

  1. Obtain consent from Data Subject in accordance with the provisions of Article (11) of this Regulation.
  2. Provide a mechanism that enables the Data Subject to opt out of receiving marketing materials when desired, and ensure that the procedures for opting out of receiving such materials are easy, straightforward, and at least as easy as the procedures for giving consent to receive them.

2. When sending direct marketing materials to a Data Subject, the identity of the sending entity shall be clearly stated without any anonymisation.

3. In case the Data Subject withdraws their consent for Direct Marketing, the Controller shall immediately stop sending related marketing materials without undue delay.

Best practices
How to implement:
Article 29: Direct marketing
This policy on
Article 29: Direct marketing
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. Without prejudice to the Telecommunication and Information Technology Act or any other related laws, before Processing Personal Data for Direct Marketing purposes, the Controller shall abide by to the following:

  1. Obtain consent from Data Subject in accordance with the provisions of Article (11) of this Regulation.
  2. Provide a mechanism that enables the Data Subject to opt out of receiving marketing materials when desired, and ensure that the procedures for opting out of receiving such materials are easy, straightforward, and at least as easy as the procedures for giving consent to receive them.

2. When sending direct marketing materials to a Data Subject, the identity of the sending entity shall be clearly stated without any anonymisation.

3. In case the Data Subject withdraws their consent for Direct Marketing, the Controller shall immediately stop sending related marketing materials without undue delay.

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 29: Direct marketing
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 29: Direct marketing
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
Guidelines for marketing and awareness communications
Critical
High
Normal
Low
3
requirements
Privacy
Informing and data subject requests

Guidelines for marketing and awareness communications

This task helps you comply with the following requirements

Getting a proper consent for potential commercial utilization purposes of customer-owned data
Critical
High
Normal
Low
3
requirements
Privacy
Processing principles and accountability

Getting a proper consent for potential commercial utilization purposes of customer-owned data

This task helps you comply with the following requirements

Limiting marketing and advertising use of personal data processed under a contract
Critical
High
Normal
Low
3
requirements
Privacy
Processing principles and accountability

Limiting marketing and advertising use of personal data processed under a contract

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.