When must a controller respond to a UK GDPR rights request?

Without undue delay and ordinarily one month beginning with the relevant time. Provide information on action taken or give the required refusal information. Article 12A now defines the clock. Necessary identification, an eligible extension and a justified access-request clarification pause must be established separately.

Responsible actor. Controller receiving a rights request.

Latest applicable receipt, requested identity-information or permitted fee-payment event.

Article 12A now defines the clock. Necessary identification, an eligible extension and a justified access-request clarification pause must be established separately.

Article 12A now defines the clock. Necessary identification, an eligible extension and a justified access-request clarification pause must be established separately.

1. Provide information on action taken or give the required refusal information.
2. Use the statutory month, not 30 days. Article 12A(5) excludes the inclusive clarification-request-to-receipt interval where its conditions are satisfied.
3. Article 12A now defines the clock. Necessary identification, an eligible extension and a justified access-request clarification pause must be established separately.

Use the statutory month, not 30 days. Article 12A(5) excludes the inclusive clarification-request-to-receipt interval where its conditions are satisfied.

Use the statutory month, not 30 days. Article 12A(5) excludes the inclusive clarification-request-to-receipt interval where its conditions are satisfied. Article 12A now defines the clock. Necessary identification, an eligible extension and a justified access-request clarification pause must be established separately.

Article 12A now defines the clock. Necessary identification, an eligible extension and a justified access-request clarification pause must be established separately. Use the statutory month, not 30 days. Article 12A(5) excludes the inclusive clarification-request-to-receipt interval where its conditions are satisfied. The actual latest applicable receipt, requested identity-information or permitted fee-payment event and required completion must be established before using a final date.

The controller receiving a rights request has established the applicable procedure and latest applicable receipt, requested identity-information or permitted fee-payment event. Article 12A now defines the clock. Necessary identification, an eligible extension and a justified access-request clarification pause must be established separately. Provide information on action taken or give the required refusal information. Without undue delay and ordinarily one month beginning with the relevant time. No computed final date is supplied.

A proposed completion raises a nonbusiness-day or time-boundary question for provide information on action taken or give the required refusal information. Use the statutory month, not 30 days. Article 12A(5) excludes the inclusive clarification-request-to-receipt interval where its conditions are satisfied. Resolve this boundary under the identified provision and actual completion route. Use the statutory month, not 30 days. Article 12A(5) excludes the inclusive clarification-request-to-receipt interval where its conditions are satisfied.

The controller reasonably needs information to identify the access request’s subject matter. Article 12A now defines the clock. Necessary identification, an eligible extension and a justified access-request clarification pause must be established separately. Article 12A now defines the clock. Necessary identification, an eligible extension and a justified access-request clarification pause must be established separately. No automatic final date follows from this scenario.

Applicable procedure and actual event

Article 12A now defines the clock. Necessary identification, an eligible extension and a justified access-request clarification pause must be established separately.

Counting and completion boundary

Use the statutory month, not 30 days. Article 12A(5) excludes the inclusive clarification-request-to-receipt interval where its conditions are satisfied.

• Article 12A now defines the clock. Necessary identification, an eligible extension and a justified access-request clarification pause must be established separately.
• Controller receiving a rights request. Latest applicable receipt, requested identity-information or permitted fee-payment event. Provide information on action taken or give the required refusal information. Use the statutory month, not 30 days. Article 12A(5) excludes the inclusive clarification-request-to-receipt interval where its conditions are satisfied.

• Latest applicable receipt, requested identity-information or permitted fee-payment event.
• Provide information on action taken or give the required refusal information.
• The controller reasonably needs information to identify the access request’s subject matter.
• Provide information on action taken or give the required refusal information. Article 12A now defines the clock. Necessary identification, an eligible extension and a justified access-request clarification pause must be established separately.